Document Category value is wiped out in the Document Sequence setup if the Document Category Value chosen belongs to different Operating Unit (Doc ID 2827853.1)

Last updated on DECEMBER 13, 2021

Applies to:

Symptoms

On : 12.2.7 version, Setup

ACTUAL BEHAVIOR
---------------
Document category value is wiped out in the Document Sequence setup if the Document Category Value chosen belongs to different Operating Unit

EXPECTED BEHAVIOR
-----------------------
Document category should not get wiped out even if the Document Category Value chosen belongs to different Operating Unit

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Two Transaction Types (N) > Oracle Receivables > Setup > Transactions > Transaction Types

Example :

Transaction Type A : OU1 (Operating Unit 1)
Transaction Type B : OU2 (Operating Unit 2)

2. Create Document Sequencing Setup (N) > Oracle Financials for India > Tax Configuration > Define Document Sequencing
3. In Document Sequence Assignments create two records for Inventory Organization Mapped under OU1
4. First Record by picking the Transaction Type A created in OU1 in Document category LOV
5. Second record by picking the Transaction Type B created in OU2 in Document category LOV
6. Save the same.Records are intact
7. Re-Query the same.Document category value (Transaction Type B) is wiped out in the Document Sequence setup

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.