WICMLP : System Cannot Add Or Change Operation Because Of Incorrect Dates

(Doc ID 1985459.1)

Last updated on OCTOBER 28, 2016

Applies to:

Oracle Work in Process - Version 12.1.3.1 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Work in Process > Wip Mass Load

ACTUAL BEHAVIOR
--------------------------

When populating the wip_job_dtls_interface and running WIP MASS LOAD to reschedule the work orders so that operation 20 starts before operation 10, the following error is seen in the log file :

ERROR
----------
 System cannot add or change operation because of incorrect dates


STEPS
--------
The issue can be reproduced at will with the following steps:

1. Populate the wip_job_dtls_interface table.

2. Run WIP MASS LOAD to reschedule the work orders.

3. The log file shows the error above.

4. The issue happens when they try to make operation 20 start BEFORE operation 10 (this is their business process in some cases ). Here is an example:

Work Order Header
SCHEDULED_START_DATE SCHEDULED_COMPLETION_DATE
15-SEP-2014 11:43:00 15.09.2014 23:03:00

Work Order Operation
OP FIRST_UNIT_START_DATE LAST_UNIT_COMPLETION_DATE
10 15.09.2014 11:43:00 15.09.2014 22:24:00
20 15.09.2014 22:24:00 15.09.2014 23:03:00

As you see above Operation 20 starts later than Operation 10

Over the interface, they are sending the following update

wip_job_schedule_interface:

FIRST_UNIT_START_DATE LAST_UNIT_COMPLETION_DATE
13/09/2014 16:25:00 14/09/2014 10:20:00

wip_job_dtls_interface:

OP START_DATE COMPLETION_DATE
10 13/09/2014 23:14:25 14/09/2014 02:39:25
10 14/09/2014 02:39:25 14/09/2014 10:20:26
20 13/09/2014 16:25:08 13/09/2014 17:03:56

5. This used to work in 11.5.9. Now it does not work in R12.

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