Batch Close Date was Allowed to be Entered Earlier Than Reversed Resource Transaction Dates
(Doc ID 2393036.1)
Last updated on JANUARY 22, 2020
Applies to:Oracle Process Manufacturing Process Execution - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Batches
Batch Close is not validating Close Date against transaction dates of resource transactions that have been reversed, which causes issues in Financials because there can be resource transactions in a later period than the Close Date period
There is supposed to be validation between transaction dates and batch close date so that batch close date is never earlier than any transaction dates
The issue can be reproduced at will with the following steps:
Note: the transactions do not actually have to be in different periods, simply in this order, but this is how the customer described the steps, and it is clearer this way.
1) Query Batch where resource transaction is in past period ( Period 0)
2) Correct resource transaction, updating usage and changing transaction date to be in period 2
3) Now pick same resource transaction and and change transaction date to be in Period 1.
4) Close Batch with Close Date in Period 1 - later than transaction date entered in Step 3. Batch closed successfully without any error or warning, even though there are reversed resource transactions with trans date in period 2.
The issue has the following business impact:
Due to this issue, resource transactions have a transaction date in a later period than the batch close, and this causes issues in Financials.
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