SAP-R3-HR2Ident

Workflow for Import to LDAP from a SAP ERP HR file

SAP-R3-HR2Ident imports data from a SAP ERP HR file into the Identity Store. You use it when HR data is delivered as a file and you want a scheduled load into DirX Identity.

Because the workflow runs as a full import, each execution processes the supplied HR file as one complete source set.

The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.

At a Glance

Name

SAP-R3-HR2Ident

Prerequisites

An agent that can run MetaCP.
Access from MetaCP to the Identity Store and a file-based channel configuration for SAP-R3-HR2Ident.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`SAP-R3-HR2Ident_MetaCP`	Import to LDAP	`MetaCP`	start activity

SAP-R3-HR2Ident_MetaCP

Import to LDAP

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`SAP-R3-HR2Ident_MetaCP`	`SAP-R3-HR2Ident_MetaCP`	`MetaCP`	Full Export	`SAP-R3-HR2Ident`	`SAP-R3-HR2Ident`

SAP-R3-HR2Ident_MetaCP

MetaCP

Full Export

SAP-R3-HR2Ident

Configuration Parameters

Table 1. Parameters of job `SAP-R3-HR2Ident_MetaCP`
Parameter	Default value
`debug_trace`	0
`delta_mode`	full
`delta_on`	0
`exact_action`	FALSE
`init_mode`	REAL
`max_trace_entries`	10
`min_source_entries`	0
`notify_not_ok`	0
`statistics`	TRUE
`test_mapping_only`	FALSE
`test_max_entries`	0
`trace_level`	1
`trace_recordcount`	0

A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent with one input and one output channel. Agents exchange their data through files or directly through the meta controller, so a typical workflow consists of an export activity that writes the data of the connected system and an import activity that maps and loads that data into the Identity Store.

You start these workflows manually from the Identity Manager or attach them to a schedule.

The workflow contains one activity, SAP-R3-HR2Ident_MetaCP. MetaCP reads the HR file and applies the import into the Identity Store in a single step.

If that activity fails, the workflow stops immediately because no later activity can continue the import.

Operation

When you start the job, MetaCP opens the SAP-R3-HR2Ident channel and reads the SAP ERP HR file.
The job runs in full mode, so each execution imports the complete file content into the Identity Store.
Because min_source_entries is 0, the workflow can also complete when the source file is empty.