E-BOM Exchange Mapping Configuration Example

This section provides two examples of configuration.

This page discusses:

E-BOM Exchange Mapping Configuration Example with Type Derived from Type Part

An E-BOM type whose symbolic name is type_CustomPart has been created. This type inherits from type_Part (whose corresponding XPDMXML entity is Part) and has additional customized E-BOM attributes whose symbolic names are attribute_CustomAttr1 and attribute_CustomAttr2. To exchange this new type, a new mapping must be defined for the XPDMXML entity Part with MappingType=CustoPart.

The following entries needs to be added in the pdm-cust-config.xml file (assuming the value of MappingType is CustoPart):

<Object XPGXMLType="Part" MappingType="CustoPart" V6Type="type_Part" V6CustoName="type_CustomPart">
    <attribute V6Name="attribute_CustomAttr1" XPGName="Property" type="dateTime" Export="true" Import="true" />
    <attribute V6Name="attribute_CustomAttr2" XPGName="Property" type="double" Export="true" Import="true" />
</Object>
Note: The value of XPGName attribute must always be Property.

This generates the following XPDMXML file at export of an object of type type_CustomPart:

<XPDMXML>
<EBOMStructure id="ID1" rootRefs="ID2" updateChildMode="RemoveExistingNotProvided">
<Part id="ID2" mappingType="CustoPart">
<ID>P1</ID>
<Name>P1</Name>
<TimeCreated>2011-12-08T14:59:33+01:00</TimeCreated>
<TimeModified>2011-12-09T07:01:58+01:00</TimeModified>
<Property name="attribute_CustomAttr1" type="dateTime">
<Value>2011-12-09T02:23:23+01:00</Value></Property>
<Property name="attribute_CustomAttr2" type="double">
<Value>0.0</Value></Property>			
<UniqueID External="DD9DE348C88ED6E70F0F417F5DEFDFE40F0F0FBD" XID="DD9DE348C88ED6E70F0F417F5DEFDFE40F0F0FBD"/>
<Maturity>Preliminary</Maturity>
<RevisionName>1</RevisionName>
<Owner>Test Everything</Owner>
<Lifecycle>EC Part</Lifecycle>
<EstimatedCost>0.0</EstimatedCost>
<TargetCost>0.0</TargetCost>
<Weight>0.0</Weight>
<MaterialCategory>Metal</MaterialCategory>
<PartClassification>Unassigned</PartClassification>
<ProductionMakeBuy>Unassigned</ProductionMakeBuy>
<UnitOfMeasure>EA (each)</UnitOfMeasure>
<SparePartType>No</SparePartType>
<LeadTime>Unassigned</LeadTime>
<Originator>Test Everything</Originator>
<EndItem>No</EndItem>
</Part>
</EBOMStructure>
</XPDMXML>

E-BOM Exchange Mapping Configuration Example with Type Derived from Abstract Type Part-Specification

Some 3DEXPERIENCE platform types are abstract in 3DEXPERIENCE platform data model such as part specification. The customized entities derived from such types can also be exchanged since these types are available in the E-BOM Exchange default mapping. This can be done by providing a new mapping with a specific MappingType in pdm-cust-config.xml file as in the example below:

<Object XPGXMLType="PartSpecification"  MappingType="CustoPartSpecification" V6Type="type_PartSpecification " V6CustoName="type_CustoPartSpecification ">
<attribute V6Name="attribute_CustomAttr1" XPGName="Property" type="dateTime" Export="true" Import="true" />
<attribute V6Name="attribute_CustomAttr2" XPGName="Property" type="double" Export="true" Import="true" />
</Object>

Following entities appears in XPDMXML:

<PartSpecification MappingType="CustoPartSpecification" id="ID4">
<ID>A-0000150</ID> 
<Name>A-0000150</Name> 
<Property  name=”attribute_CustomAttr1” type=”dateTime” >
<Value>2010-09-25T13:43:46+05:30</Value>
</Property>
<Property  name=”attribute_CustomAttr2” type=”double” >
<Value>10.0</Value>
</Property>

…….
</ PartSpecification >