My Oracle Support Banner

Why Is BOM Replaced By Second Import When Using Level Template (Doc ID 2428956.1)

Last updated on JULY 30, 2018

Applies to:

Oracle Agile Product Collaboration - Version 9.3.5.0 and later
Information in this document applies to any platform.

Goal

Why is BOM replaced by the second import for Case 1?

Case 1: Import Child item first, and then import Parent Item

  1. Login to Web Client, and create below parts:
    P0001
    P0002
    P0003
    P0004
    P0005
  2. Run Import, and select ImportChild.xls with below information, and import setting Template Type: Level Template.
    Level Template
    Level Item Number
    0 P0003
    1 P0004
    1 P0005
  3. Select ECO1, and import in redline mode
  4. Run Import again, and select ImportParent.xls with below information, and import setting Template Type: Level Template.

    Level Template
    Level Item Number
    0 P0001
    1 P0002
    1 P0003
  5. Select ECO1, and import in redline mode
  6. Check the result. See P0001 has correct BOM item, however P0003 no longer has any BOM


Case 2:Import Part item first, and then import Child Item

  1. Run Import, and select ImportParent.xls with below information, and import setting Template Type: Level Template.

    Level Template
    Level Item Number
    0 P0001
    1 P0002
    1 P0003
  2. Select ECO1, and import in redline mode
  3. Run Import, and select ImportChild.xls with below information, and import setting Template Type: Level Template.
    Level Template
    Level Item Number
    0 P0003
    1 P0004
    1 P0005
  4. Select ECO1, and import in redline mode
  5. Check the result. See P0001 has correct BOM item, also P0003 has correct BOM item
     

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.