My Oracle Support Banner

Cannot Create Items For The Child Organizations Via EGO Import Items Spreadsheet (Doc ID 2661753.1)

Last updated on MAY 28, 2021

Applies to:

Oracle Product Hub - Version 12.2.6 and later
Information in this document applies to any platform.


On : 12.2.6 version, Catalog items

Actual Behavior
For EGO Import Items using an EGO Spreadsheet when CREATEing child org, find ego_bulkload_intf created but not mtl_system_items_intf for child org when only Transaction Type, Organization, and Item Name are entered, only the Master Organization is created in this case and not the Child items.

If additional dropdown is selected such as Engeineering item = No for child org, or even Description is populated in the child organization, any additional attribute does create both the master and child items.

Expected Behavior
Expect when entering all the information for Import Items using an EGO Spreadsheet and specifying master criteria, only the Transaction Type, Organization, and Item Name should be necessary.

The issue can be reproduced at will with the following steps:

  1. truncate table INV.mtl_system_items_interface ;
    truncate table INV.mtl_interface_errors ;
    truncate table EGO.EGO_BULKLOAD_INTF;
    truncate table EGO.EGO_ITM_USR_ATTR_INTRFC;

    ... above allows a fresh test.


2. Import Items

Import from Excel Object: Items
ICC:  <Enter ICC>

Import Format <Enter Import Format>

Excel 2016

CREATE <Master Organization> <Item Name> Description: <Test Item> Item Status <Active>
CREATE <Child Organization>   <Item Name>

3. Customer enters all the required fields

Added a Master line and one additional child org to create and enters for Child line Transaction Type, Organization, Item Name and Engineering Item = No for child, then master and child record(s) is/are created (Note if any dropdown is added then the child record is created, not only Engineering Item = No)

4. Repeat same test but only enter Transaction Type, Organization, Item Name, only the master is created and the child record is not created.

It is seen that child record gets into ego_bulkload_intf, BUT NOT mtl_system_items_intf and then no child item row is created which is not expected behavior.





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

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