AuthBCP.xml
Roles must include a set of authorizations (Native Authorization or Authorization Object Instance) which, in turn can have a parent Authorization (Parent Name or Authorization Object). If no parent Authorization is available, the Native Authorization can be taken as Parent Name. This information is stored in AuthBCP.xml.
| Element name | Data type | Length | Mandatory | Key |
|---|---|---|---|---|
| NativeAuthorization | String | 125 | Yes | Primary |
| ParentName | String | 125 | Yes | |
| Description | String | 120 | Yes |
This example shows how to generate the AuthBCP.xml for the non-SAP applications. In case of Parent Authorization, the native Authorization value is same as Parent Authorization.
Note:
- Each Authorization needs to have an entry in this table.
- A parent object value must exist for objects tied to each Authorization.
- For non-SAP systems, the Authorization field must be defaulted to the role name.
- SAP reports in IRC are
based on
S_TCODEas parent object. So it becomes necessary to include S_TCODE as the parent object to view all SAP reports.