Make Item's Operation Resource Not Replaced Successfully Via Legacy Collections
(Doc ID 1982332.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 188.8.131.52 and later
Information in this document applies to any platform.
On : 184.108.40.206 version, Data Collections
Make Item's Operation Resource Not Replaced Successfully via Legacy Collections
You are in a de-centralized environment where you are trying to replace an existing resource in an operation through legacy collections. Resource A is no longer used, so just like in EBS, you try to delete Resource A and add Resource B. However, when you try to do that, the resource is ignored by the ASCP plan.
Expect to be able to delete the old resource and add new resource through Legacy Collections the same way you can do it through the form using the OperationResource.dat file.
The issue can be reproduced at will with the following steps:
1. Using legacy collection .dat files, load your Calendars, Trading Partners, Category Sets, Items, Departments, BOMs, and Routings
2. Using the OperationResource.dat file, remove an existing resource from an Op Seq using the Deleted Flag and add a row for the new resource you'd like to add
3. Run Legacy Collections and observe that the old resource is still there along with the new resource.
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