RoleAttribBCP.xml
This file contains the role attributes (the extra supporting information for the role) and the role details, such as Modified By, Modified On and Expires on. Each role can have many optional attributes. These attributes are displayed on the IRC user interface when viewing the role. However, they will not be displayed in the reports.
Element name | Data type | Length | Mandatory | Key | Notes |
---|---|---|---|---|---|
RoleName | String | 255 | Yes | Foreign | Role Name and Role Type present in the RoleBCP.xml file. |
AttributeName | String | 100 | Yes | ||
AttributeValue | String | 255 | Yes |
This table shows the attributes that are required for correct processing in IRC:
AttributeName | Mandatory | Notes |
---|---|---|
Modified on | No | Date of modification if modified else it can be null |
Modified By | No | Name of the user if modified else set it to null |
Associated Profile | No | For AttributeName Associated Profile, the AttributeValue will be the automatically generated profile name by non-SAP applications. For example, T-17000114. |
Contained Profiles | No | For AttributeName Contained Profiles, the AttributeValue
will be the list of profiles contained within a composite profile or role.
There will be a separate record for each contained role or profile. For
example, if the role R1 contains profiles P1, P2, P3 then there will be 3
records in this file:
|
Contained Roles | No | To show the child roles of a composite role.
Note: You need to indicate that the parent role contains the
child role. However, you need not indicate any information on the child.
|
This example shows how to generate the RoleAttribBCP.xml for non-SAP applications.
To add additional customer-defined role attributes, use this format:
Note: By configuring your non-SAP data mapping to BizRights Interchange
Format (BIF) XML, you can skip the SAP-centric method of having roles assigned
to profiles, which are then assigned to T-codes. You can map your roles
directly to T-codes (using authorizations).