External Worker

Replicate external worker master data outbound from SAP Fieldglass to SAP S/4HANA and SAP SuccessFactors.

Context

SAP Fieldglass is the source of External Worker (Workforce Person) in SAP Master Data Integration. The replication process uploads the data to make it ready for consumption by other applications.

The high-level data flow is:
  1. Worker data in SAP Fieldglass is changed.

  2. A payload containing the worker data is created in JSON format according to the DMA of Workforce Person and posted via the REST service to the central SAP Master Data Integration service running on SAP BTP.

  3. Once the service processes the posted document, the key mapping is updated in SAP Fieldglass.

Procedure

  1. To create the payloads, on the Configuration Manager Self-Service Dashboard, choose the Payloads tile.
    1. On the Payload List page, choose New.

    2. On the Add Payload page, create the Worker payload with the following values:

      Payload Properties

      Property

      Value

      Payload Name

      Worker

      Description

      Worker payload for MDI

      Module

      Worker

      Linked Modules

      workerPerson

      workOrders

      Linked Modules

      N/A

      Format

      JSON

      Encrypt Flag

      false

    3. Choose Add.

    4. Repeat step 1 to add a WorkOrder payload with the following values:

      Payload Properties

      Property

      Value

      Payload Name

      WorkOrder

      Description

      Work Order payload for MDI

      Module

      Work Order Revision

      Linked Modules

      Worker

      Creator

      Format

      JSON

      Encrypt Flag

      false

  2. To create the end point, on the Self-Service Dashboard, choose the End Points tile.
    1. On the End Point List page, choose Add.

    2. On the Create End Point page, enter the following values:

      • ID = MDI_WORKFORCE_CHANGE_API

      • Category = publishsubscribe

    3. Under Additional Fields, click + Additional Fields to add each of the following fields:

      Additional Fields

      Name

      Value

      __webservice_transport_class

      insite.webservices.onemasterdata.OneMasterDataWebserviceTransporter

      apiVersion

      v1/odm/3.1.0

      To use v1, there's a requisite to enable consolidated worker. For more information, see Consolidated Worker Setup.

      clientId

      <client ID value>

      clientSecret

      <client secret value>

      limitHint

      100

      serviceEndPoint

      The end point you created in the previous step.

      since

      For a new setup, use initial. The system will generate this value after it's created.

      tokenIssuerEndpoint

      https://<system url>/oauth/token

      Refer to the following image:

    4. Choose Submit.

  3. To create the Publish Subscribe entries, on the Configuration Manager Self-Service Dashboard, choose the App Activity Subscriptions tile.
    1. On the Publish / Subscribe list page, choose New.

    2. On the Add Publish / Subscribe page, add a Worker entry with the following values:

      Publish / Subscribe Properties

      Property

      Value

      Payload Name

      Worker

      End Point

      MDI_WORKFORCE_CHANGE_API

      Transporter Class

      Optional property.

      Email

      Optional property.

      Notify at Retry

      Optional property.

      Activities

      Change Primary Cost Center

      Change Supervisor

      Close

      Cost Allocation

      Create

      Edit Security Information

      Edit Worker Dates

      Edit Worker Information

      Edit Worker Name

      Reopen

      Started

    3. Choose Add.

    4. Repeat step 2 to add a WorkOrder entry with the following values:

      Publish / Subscribe Properties

      Property

      Value

      Payload Name

      WorkOrder

      End Point

      MDI_WORKFORCE_CHANGE_API

      Transporter Class

      Optional property.

      Email

      Optional property.

      Notify at Retry

      Optional property.

      Activities

      Accept

    5. Choose Add.

  4. To run the Work Order or Work Order Revision push, create a Worker or Work Order revision and verify that the entry is created in onemasterdata_worker_changetoken.