E-BOM Exchange Export Initiation and Scope

This section explains how E-BOM Exchange export can be triggered and which objects are added to set of exported objects.

This page discusses:

E-BOM Exchange Export Initiation

Export can only be initiated from 3DEXPERIENCE platform web client selection of a single object deriving from type Part. This root object is referenced in the rootRefs xml attribute of <EBOMStructure> xml element in the XPDMXML file.

Note: This initiation of export can be altered by the E-BOM Exchanges export filtering capability.

E-BOM Exchange Export Completion Scope

The diagram below describes the E-BOM Exchange completion scope from E-BOM Part (or derived) for XPDMXML export:



Note: This initiation of export can be altered by the E-BOM export filtering capability.

E-BOM Exchange Export Filtering

The E-BOM Exchange export is controlled by the 3DEXPERIENCE platform attribute BOM_Type of the 3DEXPERIENCE platform object, which works as a filter on the structure.

For a part to be exported, the value of attribute BOM_Type must correspond to the value defined with the property BOM_Type in file XPGAdapterConfig.properties located at server\STAGING\<enoviaapplicationname>\WEB-INF\classes\XPG.

If BOM_Type is blank or not set in XPGAdapterConfig.properties no filter is applied.

The value of BOM_Type can be BOM, BOD or BOTH.

For example:

For exporting only parts having BOM_Type attribute set to value BOM, the value in XPGAdapterConfig.properties file must be BOM_Type=BOM.