Definition of attribute mapping

This chapter describes the configuration of attribute mapping. Attribute mapping copies source system attributes to object and process attributes of the fragment instance (PPM attributes).

The rules for the structure of attribute mapping in the XML mapping file are specified in the following extract from the file eventmapping.dtd:

tr_xml_dtd_mapp2

PPM attribute values can be made up of any combination of attribute values of the system event and unalterable texts. The optional specification of the internal PPM attribute name allows source system attributes to be copied to any PPM attributes. PPM attributes can be assigned constant values (value XML element).

Example 1 (standard mapping)

...

<attribute>
<eventattributetype>MATERIAL_CLASS</eventattributetype>
</attribute>

...

The value of the MATERIAL_CLASS system event attribute is copied to the PPM attribute of the same name but including the prefix (e.g., AT_) specified in the attributeprefix XML attribute of the data source, i.e., AT_MATERIAL_CLASS.

Example 2 (explicit mapping)

...

<attribute ppmattributetype="AT_MATERIAL">
<eventattributetype>MAT_NR</eventattributetype>
</attribute>

...

The value of the MAT_NR system event attribute is copied to the AT_MATERIAL PPM attribute.

Example 3

...

<attribute ppmattributetype="AT_IS_SHARED_FUNCTION">
<value>TRUE</value>
</attribute>

...

The AT_IS_SHARED_FUNCTION PPM attribute is assigned the constant TRUE.

Example 4

...

<attribute ppmattributetype="AT_ID">
<eventattributetype>AUFTRAGS_SYSTEM</eventattributetype>
<value>-</value>
<eventattributetype>SYSTEM_NR</eventattributetype>
<value>#</value>
<eventattributetype>AUFTRAGS_NR</eventattributetype>
<value>-</value>
<eventattributetype>POSITIONS_NR</eventattributetype>
<value>-</value>
<eventattributetype>AUFTRAGS_TYP</eventattributetype>
</attribute>

...

The AT_ID PPM attribute is assigned the value XYZ-401#4711-10-C.

Warning

If a specified source system attribute is not available when importing data from the XML output file, the corresponding PPM attribute is not created.

Assign attributes to objects

Created PPM attributes are assigned to particular objects in the fragment instance using the objectattributes XML element. The objname XML attribute specifies the identifier of the relevant object (AT_OBJNAME_INTERN object attribute). Optionally, the object specification can be refined by specifying the graph ID (graphid XML attribute).

The example below copies the value of the END_TIME source system attribute to the AT_END_TIME PPM object attribute for the function with the identifier SAP.AUFT_ANLEG in the AUFTRAG_ANLEGEN fragment instance (graph ID of the fragment definition):

...

<attributemapping>

<objectattributes objectname="SAP.AUFT_ANLEG" graphid="AUFTRAG_ANLEGEN">

<attribute ppmattributetype="AT_END_TIME">

<eventattributetype>END_TIME</eventattributetype>

</attribute>

</objectattributes>

</attributemapping>

...

Assign attributes to processes

Created PPM attributes are assigned to particular fragment instances using the processattributes XML element. It is mandatory to specify the ID of the fragment definition graph in the graphid XML attribute.

To ensure that attributes transferred directly to the process are retained when merging the fragment instances, you must extend the merge configuration accordingly. The calculation effort required to compare the process attributes results in a slight loss of performance.

The example below copies the value of the PROCESSNAME source system attribute to the AT_PROCTYPE PPM process attribute for the AUFTRAG_ANLEGEN fragment instance (graph ID of the fragment definition):

...

<attributemapping>

<processattributes graphid="AUFTRAG_ANLEGEN">

<attribute ppmattributetype="AT_PROCTYPE">

<eventattributetype>PROCESSNAME</eventattributetype>

</attribute>

</processattributes>

</attributemapping>

...