Batch Can Be Closed with Close Date Earlier than Transaction Date of Reversing Transaction (Doc ID 1990531.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Process Manufacturing Process Execution - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Batches

ACTUAL BEHAVIOR
---------------
A batch can be closed with a close date that is earlier than the transaction date of a transaction in the batch, if that transaction is a reversal.

Create and transact a batch.
Close the period in which the transactions occurred.
Do a Correct Material Transaction on an item, such as deleting the WIP Completion for the product.
Because the original WIP Completion date is in a closed period, the WIP Completion Return gets stamped with today's date.
Close the batch with a batch close date earlier than the new WIP Completion Return. It should give an error that the batch close date is earlier than a transaction in the batch, but it does not, it closes successfully.

EXPECTED BEHAVIOR
-----------------------
The normal validation that prevents a batch from being closed with a close date earlier than the dates of any of the transactions should prevent the batch from being closed.

STEPS
-----------------------
See above

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, accounting is wrong because the transaction can be in a later period than the batch close.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms