Organizational units are created dynamically for functions in the fragment instance.
Define an organizational unit
The orgunit XML element in the mapping file defines an organizational unit. The value of the eventattributetype XML attribute specifies the name of the source system attribute, which contains the name of the organizational unit. This name is assigned to the AT_OBJNAME and AT_OBJNAME_INTERN object attributes for the organizational unit.
The following extract from the mapping file creates two organizational units, whose names are extracted from the PROCESSOR_1 and PROCESSOR_2 source system attributes. The number of executions of the functions is read from the NUM_OF_PROCESSINGS_1 and NUM_OF_PROCESSINGS_2 source system attributes specified by the numeventattributtype XML attribute.
...
<attributmapping>
...
<orgunit eventattributetype="PROCESSOR_1"
numeventattributetype="NUM_OF_PROCESSINGS_1"/>
<orgunit eventattributetype="PROCESSOR_2"
numeventattributetype="NUM_OF_PROCESSINGS_2"/>
...
</attributmapping>
...
Appropriate attribute mapping allows additional attributes to be created for organizational units or existing attributes to be overwritten.
The file extract below assigns the value anonymous processor to the name of the organizational unit displayed in the PPM user interface by overwriting the AT_OBJNAME object attribute regardless of the source system attribute value.
...
<attributmapping>
...
<orgunit eventattributetype="PROCESSOR_1">
<attribute ppmattributetype="AT_OBJNAME">
<value>anonymous processor</value>
</attribute>
</orgunit>
...
</attributmapping>
...
Assign organizational units
Organizational units are assigned to particular functions in the fragment instance using the objectattributes XML element. The objectname XML attribute specifies the identifier of the relevant function (AT_OBJNAME_INTERN object attribute). Optionally, the object specification can be refined by specifying the graph ID (graphid XML attribute).
The example below creates an organizational unit for the function with the identifier SAP.AUFT_ANLEG from the AUFTRAG_ANLEGEN fragment instance (graph ID of fragment definition) from the VBAP-ERNAM source system attribute:
<attributemapping>
<objectattributes objectname="SAP.AUFT_ANLEG"
graphid="AUFTRAG_ANLEGEN">
<orgunit eventattributetype="VBAP-ERNAM"/>
</objectattributes>
</attributemapping>
Organizational units and aggregation
During the temporary aggregation process, the organizational units created during anonymization are retained, whereas users are deleted.
To transfer a real user without anonymization, you have to create the AT_ISUSERGROUP attribute with the value TRUE in the attribute mapping for the corresponding organizational unit.
In the example below, an organizational unit whose content is extracted from the UNIT_GROUP_LABEL source system attribute is created for all functions with the internal object name FCT_A in the process instance fragment with the graph ID FRG_B.
<eventmapping>
<processfragmentmapping>
...
</processfragmentmapping>
<attributemapping>
...
<objectattributes objectname="FCT_A" graphid="FRG_B">
<orgunit eventattributetype="UNIT_GROUP_LABEL">
<attribute ppmattributetype="AT_ISUSERGROUP">
<value>TRUE</value>
</attribute>
</orgunit>
...
</objectattributes>
...
</attributemapping>
</eventmapping>