INCOIN - INV_IOI_REV_BAD_ORDER for Items With Historical Revision (文档 ID 200410.1)

Posted 2021-01-04 pompeii2008

• fact: Oracle Inventory 11.5.5
• fact: INCOIN - Import Items
• fact: MTL_INTERFACE_ERRORS
• symptom: Unable to import items with historical item revisions data
• symptom: INV_IOI_REV_BAD_ORDER
• cause: The cause of this problem is still undetermined.

fix:

Note the following 2 points when importing historical revision information in 
Inventory Item Open Interface:

1. To interface all revisions for an item in the item revisions interface 
 table (including the default revision), user can specify any effectivity dates,
 
 as long as they are in chronological order. However, DEFAULT REVISION 
 must be in the INTERFACE TABLE. Else, the process would create one  
 and put the effectivity date as sysdate. After system does this, it then 
checks 
 for chronological order which may cause the import of that item to fail. 

2. Populate the ITEM_NUMBER column in MTL_SYSTEM_ITEMS_INTERFACE, along 
 with segment1 or instead of segment1. The code compares ITEM_NUMBER 
 from item interface and revision interface tables, and if the revision does 
 not exists in the revisions interface table then a new record is insesrted in 
 revision interface table. 

 For example, if the default starting revision for organization V1 is ‘A‘
 and an item ‘AS18947‘ has the first revision as ‘F‘, then user needs to insert 
 2 records into MTL_ITEM_REVISIONS_INTERFACE table. One for revision ‘A‘ and 
 other for revision ‘F‘ The effectivity date of revision ‘A‘ should be less 
 than equal to that of revision ‘F‘. Both of these dates could be historical 
 dates. User needs to populate the ITEM_NUMBER column in 
 MTL_SYSTEM_ITEMS_INTERACE for the item ‘AS18947‘ instead of or in 
 addition to segment combination values.