User mapping support report
- Yannic Zinke
Unlike in CC4 for Jira DC, the user mapping for CC4 Cloud must be maintained on SAP side. The Jira account ID must be mapped to the respective business partner e-mail address or number of the user in the SolMan system.
An example mapping can be found here:
To support customers with the user mapping maintenance process, report /XALM/CC4_CUST_JIRA_USERMAP was created. This report searches for users in the SolMan system and sends an API request to Jira to check whether the user exists there. If the user exists, the user´s Jira account ID is saved and displayed in an ALV grid from where it can be copied and pasted into the CC4 partner customizing.
Selection Screen
General
External system: Name of the external system / configuration profile in the CC4 customizing. This parameter is mainly used to determine the URL to the Jira cloud instance and is mandatory.
Attribute: Name of the CC4 attribute for which the user mapping should be maintained. This parameter is optional and the main purpose is to simplify the copy and paste process.
Filter User
The users for processing can be selected either via SAP user ID or via the business partner number.
User: Selection parameter for SolMan user(s). If no value is entered, all available dialog users are processed.
Business Partner: Selection parameter for SolMan business partners. If no value is entered, all available dialog users are processed.
Search user in Jira using…
To check whether the SolMan user exists in the Jira cloud instance, either the business partner e-mail address or the full name of the SAP user as it is maintained in transaction SU01 can be used for the API search.
E-Mail: E-Mail address of the user´s business partner.
Full Name: Full name of the user in the SolMan system.
Result List
