My Oracle Support Banner

Batch Completion is Creating Unnecessary Resource Transactions, Including Reversals of Existing Transactions (Doc ID 2289017.1)

Last updated on FEBRUARY 27, 2019

Applies to:

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


On : 12.2.5 version, Batches

Customer has WIP batches with WIP steps. The resources in the steps have many completed transactions. The actual usage is greater than the planned usage. When completing the batch and backdating the actual start date, the system is creating new resource transactions. Sometimes these new transactions are a reversal of a previous transaction and a new transaction that is identical to the original transaction (including transaction date). Sometimes, however, the new transaction has a transaction date of sysdate, and a usage that shows as 0.00000 onscreen.

As I understand it, the only time that completing a batch/ step should create resource transactions is if both:

1. No actual usage or resource transactions have been entered, and
2. The Default Actual Resource Usage parameter is checked.

The customer does have this parameter checked, but the resource already has multiple resource transactions and an actual usage, so there is no reason that any new resource transactions should get created, and no reason that existing resource transactions should be reversed.

The problem caused by these sysdate - dated transactions is that they then prevent the batch being closed with a backdated Close date.

The transactions that are created prior to batch completion have a usage that goes out to many decimal places.

Expect Batch Completion / Step Completion not to reverse existing resource transactions and not to create new transactions.

The issue can be reproduced at will with the following steps:
1. Complete a batch that contains resources with completed resource transactions with usages that go out to many decimal places

The issue has the following business impact:
Due to this issue, users sometimes are not able to backdate the Batch Close Date.




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

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