How To Capture Diagnostic Information For Supply Chain Workbench Release Issues
Last updated on AUGUST 08, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 11.5.9 and later
Information in this document applies to any platform.
Many times, planned orders are released from the Supply Chain Workbench in APS (destination), but the corresponding job or purchase requisition is not created correctly in the EBS application (source).
When a planned order is released as a purchase requisition, data is inserted into the PO_REQUISITIONS_INTERFACE_ALL table on the source instance and processed by the Requisition Import (POCIRM) concurrent program.
When the planned order is released as a discrete job, data is inserted into the WIP_JOBS_SCHEDULE_INTERFACE and WIP_JOB_DTLS_INTERFACE tables on the source instance and processed by the WIP Mass Load (WICMLP) concurrent program.
When the planned order is released as a lot based job, data is inserted into the WSM_LOT_JOB_INTERFACE and WSM_LOT_JOB_DTL_INTERFACE tables on the source instance and processed by the Import Lot Based Jobs (WSMPLBJI) concurrent program.
In 12.1 and above, we can also get data from the MSC%INTERFACE tables by using new profile MSC: Retain Released Data
The goal of this note is to assist in gathering additional information to assist product support in providing you with a quick solution.
<Note 1346745.1> has been published with a wealth of information on the Release processes in our applications
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