Kontakt

Ansicht
Dokumentation

RPLDAP_EXTRACT_IDM - Extraction of HR Data to an LDAP Directory

RPLDAP_EXTRACT_IDM - Extraction of HR Data to an LDAP Directory

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this report, you launch the LDAP data extraction of employee records from an HR system in order to transfer data into an LDAP-ready directory service or identity management solution.

As compared with the RPLDAP_EXTRACT report, employee data is copied with this report in a time-dependent manner. This means that data is copied with its start and end dates.

Here is an example for data records of the same employee when surname has changed:
Name = [01012008-31122009] SMITH
Name = [01012010-31129999] MILLER

If you want to update the data in your LDAP directory at regular intervals, you can schedule the report to run regularly in the background.

Integration

This report was developed with the scenario User Administration and Distribution with SAP NetWeaver Identity Management especially in mind.

Prerequisites

The User Administration and Distribution with SAP NetWeaver Identity Management scenarios requires SAP NetWeaver Identity Management 7.1, which you must have licensed.

Features

Selection

The selection options on the selection screen are broken down according to their content using the group box. The report uses the group box to provide the following selection options:

Under Person Selection, you can enter the personnel number whose data you want the system read from the HR system and transfer to the LDAP directory in the Personnel Number field.

If you choose the Delta Download field:

  • the report disables selection using the Personnel Number field
  • only personnel numbers entered in the HRLDAP_PERNR table but not yet processed (not marked with the PROCESSED indicator) are processed.
The HRLDAP_PERNR table is filled using the implementation of the HRBAS00INFTY, HRPAD00INFTY, and HRPAD00INFTYDB Business Add-Ins. SAP delivers the following inactive example implementations:
  • HRPAD00INFTY --> HR_LDAP_EXTRACT_PA

  • HRPAD00INFTYDB --> HR_LDAP_EXTRACT_PA_ITF

  • HRBAS00INFTY --> HR_LDAP_EXTRACT_PD

For more information, see the documentation for the implementations.

If you select the Delete Items from Delta Log field, the entries for all persons that have already been processed (PROCESSED indicator is selected) are removed from table HRLDAP_PERNR, thus deleting the change change history from previous program runs.

Under LDAP Connections, you can restrict your selection with the LDAP Connector (RFC) and LDAP Server fields.

When you run the report for the first time (initial run), setting the Optimize for LDAP Initial Run indicator improves system performance: The system tries to create new data records in the LDAP directory and does not try to update a data record unless there is an error when creating a new data record. Creating a record will fail, for example, when there is already an entry in the LDAP directory for the key of a data record.

If you execute the report again, do not set the indicator. System behavior normally includes updating the data records in the LDAP directory first. To do this, the system checks if comparable data records are already contained in the LDAP directory. After this check, the system updates the existing data records in the LDAP directory or creates new ones.

Under Data Source, you can enter a SAP query as the source for your data transport.

You can define your SAP query more precisely with the following fields:

  • Global Work Area (indicator)
  • User Group
  • Name
  • Variant

Note that the SAP query must be based on a PNP functional area and contain the following fields:

  • Personnel Number (P0000-PERNR) as an identifier
  • Split Begin (SYHR_A_P0002_AF_SPLIT_BEG)
  • Split End (SYHR_A_P0002_AF_SPLIT_END)

The fields are only filled correctly if the following query switches are defined in the infoset (under Extras --> Coding in DATA Coding Block):

Start Code
*$HR$ [P0002]
*$HR$ ADD_FIELDS_SPLIT_DEP = 'X'
*$HR$ SPLIT_DEPENDENT_AF = 'SPLIT_BEGDA'
*$HR$ SPLIT_DEPENDENT_AF = 'SPLIT_ENDDA'
*$HR$ [P0001]
*$HR$ TIME_DEPENDENCE = 'DOMINANT'
End Code

In the standard system, SAP delivers the LDAPEXTRACT604 query, which is based on the /SAPQUERY/HR_LDAP_604 infoset, and the /SAPQUERY/L1 user group.

Under Options, you can delete employee data records identifying employees with a certain employment status from the LDAP directory. This function is useful if the LDAP directory is only supposed to contain active employees (employee data records for employees with employment status 3).

This could lead to memory shortages during the extraction. This generally depends on the number of selected employees and the complexity of the query the extraction is based on. For example, approximately 5 MB of memory are allocated for 1000 employees in the example query we deliver. Depending on the size of the application server, it is therefore recommended to launch the report in multiple, disjunct partitions.

Standard Variants

Output

Activities

Example






PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 7050 Date: 20240601 Time: 092623     sap01-206 ( 105 ms )