Logical Intercompany Transaction Should Not Create Sales Order Issue Journal
(Doc ID 2884540.1)
Last updated on JULY 21, 2022
Applies to:Oracle Process Manufacturing Financials - Version 12.2.5 and later
Information in this document applies to any platform.
When customer checks the Defer Logical Transactions check box, the Sales Order Issue (which should not get accounted but create Logical Transactions upon running Create Deferred Logical Transaction program) gets accounted when OPM Accounting Preprocessor is run before Create Deferred Logical Transaction program is run. This leads to error in SLA
Sales Order Issue to not have accounting by OPM Accounting Preprocessor when it is supposed to create Logical Transactions
The issue can be reproduced at will with the following steps:
1. Ship Confirm the Sales Order
- Sales Order Issue created at the Material Transactions without the correspondent Logical Transactions and the material transaction still eligible for accounting journal creation.
2. Costing User running the OPM Accounting Preprocessing that cause the journal are created for the above transactions which not suppose to be created because it will be create a logical transactions.
- Journal Created is
3. After step 2 is completed.. Then the Create Deferred Logical Transaction program is running and generated the 3 Logical Transaction for Shipment at point 1.
And it will mark the Material Transaction Sales Order issue as Logical and it become not eligible for accounting journal creation.
And this cause the journal that created at point no 2 become an orphan transactions journal.
So, we see there is a GAP on the process when we enable the "Deferred Logical Transaction" as it is not in sync OPM Accounting Preprocess for the transaction that can be picked for the accounting journal creation.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document