ECO Fails In The Queue For The BOM Item Type Error (Doc ID 1462802.1)

Last updated on MARCH 08, 2017

Applies to:

Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite - Version 11.1 and later
Information in this document applies to any platform.

Goal

 

ECO fails in the PLM queue with following error:

<corecom:Text languageCode="" languageLocaleCode="">Org Code: ECO Name: ECO#12126 Err Msg: Entity Id: ITEM Message Text: The column BOM_ITEM_TYPE must have one of the following values: 1 (Model), 2 (Option Class), 3 (Planning), 4 (Standard).</corecom:Text>

as numerous subclasses were created in Agile, many of them mapping to BOM Item type of standard with a unique common value, the issue was addressed by mapping all the agile subclass types to BOM item types in the DVM ITEM_BOM_ITEM_TYPE_CODE dvm.  

 

Now, Agile and O2C, reside on the same system.  While the above is now addressed for Agile, this now causes a fault on the O2C integration between EBS and Siebel due to multiple values for bom item type standard in the DVM.  Error noted below:

oramds:/deployed-composites/default/UpdateProductEbizReqABCSImpl_rev1.0/xsl/EgoItemSyncOpVCollectionToSyncItemListEBMType.xsl&lt;Line 200, Column 196&gt;: XML-22044: (Error) Extension function error: Error invoking &apos;lookupValue&apos;:&apos;oracle.tip.dvm.exception.DVMException: The source column &quot;EBIZ_01&quot; has already multiple occurences of source value &quot;4&quot; in dvm &quot;oramds:/apps/AIAMetaData/dvm/ITEM_BOM_ITEMTYPE_CODE.dvm&quot;.

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms