SAP Master Data Integration

Follow this procedure to set up SAP Master Data Integration (in short, MDI) as a source system.

Prerequisites

You have created a tenant in a subaccount on SAP BTP, Cloud Foundry environment. You can create your own tenant (free of charge), or integrate with an existing one.
You have created a service instance for MDI in the subaccount in order to connect a new system to your tenant and read user account information from it. To learn how, see: Creating Service Instances
You have created a service key in this instance, which contains the necessary credentials to connect to the MDI service. Creating multiple service keys in the same service instance is not supported. To learn how, see: Creating service Instances
Tip

The serviceKey payload provides you with the following properties that you will later need for your system configuration:
- uri =URL
- uaa.url = OAuth2TokenServiceURL
- uaa.clientid = User
- clientsecret = Password

Context

As part of SAP’s data model and integration unification strategy, SAP BTP Integration Suite has Master Data Integration to enable a harmonized integration and distribution of different master data objects and data between SAP solutions. This includes master data for business partners, cost centers, and workforce data. Workforce data is provided for integration scenarios that need data from SAP SuccessFactors Employee Central or other HR systems.

To learn more, see: Integrating SAP SuccessFactors Employee Central with SAP Master Data Integration

You can use Identity Provisioning to configure SAP Master Data Integration as a source system for provisioning of users and HR events to a target system of your choice. The HR events reflect the various stages of an employee’s lifecycle from hire to retire. For example: hire, termination, job change, position change. For more information, see Events in Employee Central.

HR events are read with delta load marker so that the target system is aware of the previous and current instance of the event. The delta load marker is deleted during system reset.

Procedure

Access the Identity Provisioning UI.
- Access Identity Provisioning UI of Bundle Tenants
- Access Identity Provisioning UI of Standalone Tenants
Add SAP Master Data Integration as a source system. For more information, see Add New Systems.

Choose the Properties tab to configure the connection settings for your system.

Mandatory Properties
Property Name	Description & Value
Type	Enter: HTTP
URL	Enter the URL to the relevant integration application running in the relevant region of SAP Business Technology Platform. See the Prerequisites section → serviceKey tip.
ProxyType	Enter: Internet
Authentication	Enter: BasicAuthentication
User	Enter the technical user that has access to the API of your MDI service. See the Prerequisites section → serviceKey tip.
Password	(Credential) Enter the password for this technical user. See the Prerequisites section → serviceKey tip.
OAuth2TokenServiceURL	Enter the OAuth 2.0 Token Service URL. See the Prerequisites section → serviceKey tip.

To learn what additional properties are relevant to this system, see List of Properties. You can use the main search, or filter properties by the Name or System Type columns.

Configure the transformations.

Transformations are used to map the user attributes from the data model of the source system to the data model of the target system, and the other way around. The Identity Provisioning offers a default transformation for the SAP Master Data Integration source system, whose settings are displayed under the Transformations tab after saving its initial configuration.

You can change the default transformation mapping rules to reflect your current setup of entities in your MDI source system. For more information, see:

Manage Transformations

Field Mapping Between Employee Central and SAP Master Data Integration

Default transformation:

Code Syntax

{
  "user": {
    "mappings": [
      {
        "sourcePath": "$.id",
        "targetVariable": "entityIdSourceSystem",
        "targetPath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID']",
        "correlationAttribute": true
      },
      {
        "sourcePath": "$.externalId",
        "targetPath": "$['urn:ietf:params:scim:schemas:extension:enterprise:2.0:User']['employeeNumber']",
        "optional": true
      },
      {
        "sourcePath": "$.profileDetail[0].content.scriptedProfileDetails[0].firstName",
        "targetPath": "$.name.givenName",
        "optional": true
      },
      {
        "sourcePath": "$.profileDetail[0].content.scriptedProfileDetails[0].lastName",
        "targetPath": "$.name.familyName",
        "optional": true
      },
      {
        "sourcePath": "$.profileDetail[0].content.scriptedProfileDetails[0].middleName",
        "targetPath": "$.name.middleName",
        "optional": true
      },
      {
        "sourcePath": "$.userAccount.userName",
        "targetPath": "$.userName",
        "optional": true,
        "correlationAttribute": true
      },
      {
        "constant": true,
        "targetPath": "$.active"
      },
      {
        "sourcePath": "$.emails[?(@.isDefault == true)].address",
        "optional": true,
        "correlationAttribute": true
      },
      {
        "sourcePath": "$.emails",
        "preserveArrayWithSingleElement": true,
        "optional": true,
        "targetPath": "$.emails"
      },
      {
        "targetPath": "$.emails[*].usage",
        "type": "remove"
      },
      {
        "targetPath": "$.emails[*].address",
        "type": "rename",
        "constant": "value"
      },
      {
        "targetPath": "$.emails[*].isDefault",
        "type": "rename",
        "constant": "primary"
      },
      {
        "constant": [
          "urn:ietf:params:scim:schemas:core:2.0:User",
          "urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User",
          "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"
        ],
        "targetPath": "$.schemas"
      }
    ]
  },
  "event": {
    "ignore": true,
    "condition": "($.instance.id EMPTY false) || ($.instanceId EMPTY false)",
    "mappings": [
      {
        "sourcePath": "$.instance.id",
        "optional": true,
        "targetPath": "$.id",
        "targetVariable": "entityIdSourceSystem"
      },
      {
        "sourcePath": "$.instanceId",
        "optional": true,
        "targetPath": "$.id",
        "targetVariable": "entityIdSourceSystem"
      },
      {
        "sourcePath": "$",
        "targetPath": "$"
      }
    ]
  }
}

Now, add a target system to provision users into it. Choose from: Target Systems

Next Steps

Before starting a provisioning job, you can first subscribe for e-mail notifications from the source system you use in your scenario. This way, you will be notified by e-mail about eventual failed entities during the jobs. For more information, see Manage Job Notifications.
Start an identity provisioning job. For more information, see Monitor Provisioning Job Logs.