My Oracle Support Banner

API Wip_massload_pub Changed WO BOM Revision For Released WO WIP_JOB_SCHEDULE_INTERFACE (Doc ID 2753172.1)

Last updated on FEBRUARY 18, 2021

Applies to:

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

Symptoms

On : 12.2.9 version, Open Interfaces

ACTUAL BEHAVIOR
---------------
API wip_massload_pub changes the work order BOM revision for released WO.

We have found out bug, which enables change work order BOM revision, even though work order has status released.

After these steps, discrete job revision has changing into 013. This is the bug, because EBS should not allow change the revision for released discrete job. It caused serious problem for our company, because BOM for released discrete job has been replaced.
I attached API_example.sql, which contains example of using API with inserting data into WIP_JOB_SCHEDULE_INTERFACE.

EXPECTED BEHAVIOR
-----------------------
Expect the BOM revision to remain the same for a released WO

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

1. Create discrete job for item W1WW7-HTL-TU-4-T in the newest revision (012).
2. Change discrete job BOM revision date to sydate + 30.
3. Change discrete job status to Released.
4. Create new revision for item W1WW7-HTL-TU-4-T - 013.
5. Run API wip_massload_pub.massLoadJobs.



Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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