My Oracle Support Banner

Duplicate WIP Job Number When Releasing A "Make" Planned Order From SCP Cloud (Doc ID 2641235.1)

Last updated on JUNE 01, 2020

Applies to:

Oracle Supply Planning Cloud Service - Version 11.13.19.10.0 and later
Information in this document applies to any platform.

Symptoms

PROBLEM STATEMENT:
The customer encountered an issue when releasing a Make Planned Order from Cloud to EBS. It seems that when releasing a Make Planned order, SCP Cloud use the Planned Order number as Job Number.

The customer have scenario where the planned order number generated is already used in the WIP job and this caused the WIP Mass Load to fail create the work order.

Example:
1. SCP Cloud released a Planned Order from Supply Plan; item = ABC for Org= XYZ --> Job Number: 123456
2. This Job Number: 123456 already exists in WIP EBS.


STEPS TO REPRODUCE:
1. Run the Supply Plan
2. Release the Make Planned Orders
3. Upload to the EBS
4. Review the WIP Job Number

EXPECTED BEHAVIOR:
To increment to sequence number in SCP Cloud transaction_id so that it is
higher than WIP sequence number to avoid the duplicate issue

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
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.