Authorization Control in XCM

Overview

XCM checks its own authorization objects in addition to the SAP standard authorizations of the Change Record:

Authorization Object Controls
/XCM/CR Process Builder, Process Control BRF+, Enterprise Search, MDG-M request, KPI dashboard
/XCM/CRCL Classification in the Change Record
/XCM/TR Mass Upload of Teams and Responsibility
/XCM/SW, /XCM/SW_EC Switch Framework apps

What to set up in your system

  1. Add the XCM apps you use to your roles and merge the authorization data in PFCG. The apps propose their XCM authorizations (SU24), so most values below are filled in automatically. The column Proposed in the tables shows which ones.
  2. Add the values that are not proposed by hand, if the function is used: /XCM/CR 71 (KPI dashboard), /XCM/CR 64 for BRF+ generation, /XCM/CR 23 and PU (BRF+ decision table), and /XCM/CRCL.
  3. For the Switch Framework, set PROJECT_ID to the switch projects the user may work on, or copy the delivered role templates.
  4. Remove values that are no longer valid. PFCG shows them as invalid after the import. See the notes per object.

1. Authorization Object: /XCM/CR

Field: ACTVT.

ACTVT Function Description Proposed
PR Process Correspondence Change the Process Builder of a Change Record: edit, delete, activate or deactivate, and copy tasks; add or disable agents. Process Builder, Process Route
23 Maintain Change the decision table in Process Control BRF+. Without this activity the decision table is read-only. No
PU Publish Activate changes to the decision table in Process Control BRF+. Without this activity the activation is blocked. No
64 Generate Generate BRF+ applications with /XCM/BRF_GENERATE, and generate the Enterprise Search artifacts and assign their package and transport in the XCM Enterprise Search Cockpit. Enterprise Search Cockpit
59 Distribute Share public views in CR Enterprise Search: create and delete a public view. CR Enterprise Search
AE Change User-Defined Change public views in CR Enterprise Search: rename and overwrite a public view. CR Enterprise Search
CO Complete Complete the MDG-M request linked to the Change Record. MDG-M Change Request
71 Analyze Display the data of the KPI dashboard. Without this activity the dashboard shows no data. No

Note:

  • 59 and AE are only checked when the switch XCM_ESH_PUBLIC_VIEW_AUTH is active. Otherwise every user can share and change public views.
  • The object allows further activity values (08, 60, 70, UL, W9). They are not checked by XCM and do not need to be granted. The values 01, 02, 03, 06, A8 and W7 are no longer allowed; delete them from your roles.

2. Authorization Object: /XCM/CRCL

Field: ACTVT. The checks only apply when the Classification Control switch is active and the record type has an active XCM process version. Otherwise classification in the Change Record is not restricted by XCM.

ACTVT Function Description Proposed
02 Change Unrestricted classification. With 02 the user can assign or remove any class and change any characteristic value in a Change Record. Without 02 the user can only use the classes that are marked as allowed for the record type in the allowed-class customizing (table /XCM/CR_CLF_CLASS); assigning, removing or changing values of any other class is rejected with an authorization error. No
F4 Display in Value Help CR Enterprise Search: Classification Class value help. The value help shows only the classes allowed for the record types the user is authorized to display (/IAM/IAUTH, application CR, activity 03). Without F4 the value help is empty when the switch XCM_ESH_CLASSIFICATION_CONTROL is active. No

Note: Activity 03 is replaced by F4 and is no longer allowed. Roles that granted 03 for the value help must grant F4 instead.

3. Authorization Object: /XCM/TR

Field: ACTVT. Controls the Mass Upload of Teams and Responsibility app.

ACTVT Function Description Proposed
01 Create or Generate Create a new upload. Uploading the file, processing it and creating the Teams in bulk all happen within such an upload. Mass Upload
V4 Delete Version Clear the upload history maintained by the app (Clear History action). Mass Upload

4. Switch Framework: /XCM/SW and /XCM/SW_EC

The Switch Framework apps distinguish two roles. The Solution Owner defines the projects, switches and their dependencies. The End Customer works with the switches delivered to them and maintains the switch user lists.
Both objects have the fields PROJECT_ID and ACTVT. PROJECT_ID restricts the authorization to the switch projects the user may work on; use * for all projects. A user sees only the projects, switches and user lists of the projects they are authorized for.

Authorization Object Used by ACTVT Proposed
/XCM/SW – Solution Owner Manage Switches 01 Create, 02 Change, 03 Display, 06 Delete 03
/XCM/SW_EC – End Customer Display Solution Switches, Maintain User List 02 Change, 03 Display, 06 Delete 03

The proposal fills in display only. Add the change activities and set PROJECT_ID in the role, or copy one of the delivered role templates:

  • /XCM/SW_R_SO – Solution Owner: /XCM/SW with all activities for all projects.
  • /XCM/SW_R_EC – End Customer: /XCM/SW_EC with activities 02, 03 and 06 for all projects.

Note: From XCM 2026.5.1 these objects replace Z_XCMSW_SO and Z_XCMSW_EC, which are deleted with the import. Roles that still contain the earlier objects must be changed to the new ones; the field PROJECT of Z_XCMSW_EC is now PROJECT_ID.

XCM BAdI Implementations for Authorization and Process Control

1. Process Builder Authorization Control

To override the authorization control enforced by the authorization object /XCM/CR (ACTVT PR) when maintaining the Process Builder of a Change Record, implement the BAdI /XCM/PR_EX_PROCESS_BUILDER (interface /XCM/PR_IF_ACTION_CONTROL).
The BAdI has one method, PROVIDE_ACTION_AUTHORIZATION. It receives the Change Record details and returns one flag per action, which allows or forbids that action:

  • IS_EDIT_ALLOWED – Edit a task
  • IS_DELETE_ALLOWED – Delete a task
  • IS_ACTIVATE_ALLOWED – Activate or deactivate a task
  • IS_ADD_AGENT_ALLOWED – Add an agent to a task
  • IS_DISABLE_AGENT_ALLOWED – Disable an agent of a task
  • IS_COPY_ALLOWED – Copy a task
  • IS_INDIVIDUAL_APPROVAL_ALLOWED – Change the Individual Approval flag of a task

2. BRF+ Decision Table Governance and Email Notifications

With the governance feature for the BRF+ decision table described in point 1 of 2026.1.0 - Governance for BRF+ and XCM customizing, MDG cockpit, the users responsible for activation are notified by email. To determine these users, implement the BAdI /XCM/EX_BRF_ADMIN (interface /XCM/IF_BRF_ADMIN).
The BAdI has one method, GET_ADMIN_DETAILS, which returns the users who receive the notification.

3. MDG Request Completion for Change Records

To perform validations before completing the MDG request of a Change Record, or to execute actions after its completion, implement the BAdI /XCM/CR_EX_COMPLETE_MDG_REQ (interface /XCM/CR_IF_COMPLETE_MDG_REQ).
This BAdI provides two methods:

  • BEFORE_COMPLETE_MDG_REQUEST – Executes logic before the MDG request is completed.
  • AFTER_COMPLETE_MDG_REQUEST – Executes logic after the MDG request is completed.

Keywords

record type, Change Record, authorization, authorization object, ACTVT, SU24, PFCG, classification, Extended CR Search, public view, KPI dashboard, Process Builder, BRF+, BAdI, Switch Framework, /XCM/SW, /XCM/SW_EC, Solution Owner, End Customer