Structure Bulkload Using Batches Deletes Components From Other Structures In The Same Batch (Previous Runs) Eventhough They are Not Included in Current Import Batch Run
(Doc ID 2637858.1)
Last updated on FEBRUARY 17, 2020
Applies to:Oracle Product Hub - Version 12.2.5 and later
Information in this document applies to any platform.
On : 12.2.5 version, Catalog items
Existing BOM's components are getting disabled (disable date is set on the child parts) when uploading a new structure using the same Batch ID , even if the uploaded parts are not among the Parent or child of the parts getting disabled.
No Duplicate or additional 'DELETE' type records should be included that are not relevant to current upload.
The issue can be reproduced at will with the following steps:
0. Create a batch in Import Workbench for importing structures with structure contains "All" option (Default is "Changed Records" )
1. Import BOM A (Parent A - Component C1, Parent A - Component C2) -- Successful
2. Import BOM A (Parent A - Component C3 ) -- See C1 and C2 are deleted and C3 is added
3. Import BOM B (Parent B - Component C3) -- See BOM B was created, But component C3 on BOM A has been deleted . Expect no changes to BOM A as it was not included in current run.
Clear out records in BOM_BILL_OF_MTLS_INTERFACE (OR) Update NO_OP records in BOM_BILL_OF_MTLS_INTERFACE from process_flag 1 to 7 for the batch after every successful run.
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