Last updated on MARCH 23, 2017
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
OPM Production Batch Resource Transactions Getting Overwritten Upon Batch Step Insert
Users are inserting batch steps and when the planned start and planned complete date are the same time stamp for the inserted step, resource transaction dates for all other steps are getting backdated to the Planned Step Dates of the inserted batch step.
When users are inserting batch steps and when the planned start and planned complete date are the same time stamp for the inserted step, resource transaction dates for all other steps should not be getting backdated to the Planned Step Dates of the inserted batch step.
The issue can be reproduced at will with the following steps:
1. OPM Process Execution Batches
1. Batch Created
2. Step 10 existed in the original recipe/routing. Steps
20-50 where manually inserted.
3. Steps 20-40 were added and the default dates were accepted.
The planned start dates default to the planned start date of the batch. The
planned completion date is a result of one resource in the operation is a fixed
lead time of 1 hour. (Illustrated in next screen shot). Step 50 was inserted
using specific manually entered planned dates.
4. Step 40 details. Note the 2nd resource line
is transacted for actual resource usage, the first line is for planning
5. Batch is released and started on 6/10
6. Step 20 is released and resource usage is recorded:
7. Transaction date defaults to the actual start date of
8. Step 30 is released and resource usage is recorded
9. A step is inserted (Step 31)
saved with no planned dates entered, and as expected the dates are scheduled as
follows. Transaction dates are not impacted for previously transacted step
32 is inserted with the planned start and complete date being the same (entered
as opposed to accepting the defaults)
20 transaction dates for completed transactions are updated to 05-JUN-2013 and
with exact time stamp of planned step dates for step 32.
30 was impacted the same:
Resource transactions (completed) for this batch
Reverse_id is null as this bug just updates the resource transaction date. When
correcting transaction dates in the form (which we have been doing), a
reversing transaction occurs for the original date and a new transaction is
created for a new date or period.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms