ASCP Not Using Latest Effective BOM Components For An Assembly. ECO Is Not Involved
(Doc ID 2544920.1)
Last updated on SEPTEMBER 26, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Data Collections in PROD
Down in the BOM of several items there's a phantom item = 17147182. At this direct component level there are 15 plus item and there are 3 phantom assemblies end dated with to date = 08-APR-2019 - this was done manually in the BOM NOT by ECO - They added 3 phantom items on the same sequence id with same from date = 08-APR-2019. After data collections runs it's still picking up the old phantom assemblies that were end dated as well as the new ones that are added. Because of this it's still planning for the components below the old phantoms that were end dated and thus over planning supplies. We saw in View Collected Data that they were still picked up
- 17081019 - Buy
- 17135005 - Sub
- 17156297 - Phantom
- 17156841 - Buy
- 17147182 - Phantom - problem further down in this bom - This is where the 3 phantoms below were end dated with 08-APR-2018
the above 3 still show up in the bom for 17147182 even though they were end dated 08-APR-2019 - the 3 new phantoms were added with same operation on 08-APR-2019 and these are being collected and planned
Expect the old items to drop off the bom and the new items to remain for planning
The issue can be reproduced at will with the following steps:
1. End date several phantoms from BOM for item = 17147182 on 08-APR-2019
2. Add new phantoms with From Date also 08-APR-2019
3. Run data collections and plan
4. Collected data still shows the old phantom items
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