Attempting to Re-Release a Batch with Transactions in a Later Period Gives Error: "The batch cannot be released when transactions exist in a closed accounting period." (Doc ID 2936651.1)

Last updated on AUGUST 21, 2024

Applies to:

Symptoms

With a batch that has a transaction in one month, and was subsequently Unreleased, and then attempting to Re-Release the batch with a start date in the previous month (which is still open),
the following error occurs.

ERROR
-----------------------
The batch cannot be released when transactions exist in a closed accounting period.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Release batch (Production Supervisor > Batch Details > Actions > Release)
2. Create transactions with transaction dates in December and January (Production Supervisor > Batch Details > Transact Material)
3. Unrelease batch (Production Supervisor > Batch Details > Actions > Unrelease)
4. Try to Release batch again with start date in December, earlier than any transactions in batch (Production Supervisor > Batch Details > Actions > Release)


This appears to be validation created as part of bug 29333493. That seems to have been intended to prevent a batch from being re-released in a period if there were transactions in an earlier period. But the validation seems to be too restrictive. It is preventing re-release if there are transactions in a later period, and both periods are still open. There is nothing invalid about having an actual start date in December and transactions in December and January. In fact, that was the case even before Unreleasing the batch. So if December is still open, it should not be necessary to prevent the user from again Releasing the batch with a December date, as long as that date isn't later than any of the transaction dates.

There is already validation that will prevent the batch from being Closed with a date in December, since there are transactions in January, and the Close date must be equal or greater than any transaction dates.

It seems the validation should be checking that there aren't any transactions in a period earlier than the new actual start date, or in the same period but earlier than the new actual start date, but instead it is checking if there are transactions in any period, even a later one, then the period of the actual start date.

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.