SAP ABAP IMG Activity HRLDAP_ATTRIBUTES (BAdI: Changing Attribute Values)
Hierarchy
☛ SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR
   ⤷ EP-PCT-MGR-HR (Application Component) Business Package for Manager Self-Service (HR)
     ⤷ PWPC_MAN_IMG_470FF (Package) PWPC_MAN_IMG_470FF
IMG Activity
ID HRLDAP_ATTRIBUTES BAdI: Changing Attribute Values  
Transaction Code S_AXA_22000001   (empty) 
Created on 20020211    
Customizing Attributes HRLDAP_ATTRIBUTES   BAdI: Changing Attribute Values 
Customizing Activity HRLDAP_ATTRIBUTES   BAdI: Changing Attribute Values 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRLDAP_ATTRIBUTES    

Use

With this Business Add-In (BAdI) you can change the defaults that the SAP standard system generates for the key of an employee record in the LDAP directory, and specify customer-specific keys.

If you are using several HR systems, the description of an employee in the LDAP directory using his or her personnel number is not usually unique. Since a personnel number always describes an employee uniquely within one logical system, we provide a default in the standard that is a concatenation of the name of the logical system that provided the data, and the personnel number of the employee. You can change this default.

If you are using enterprise portals based on a mySAP Workplace system, the Workplace user name of an employee is of central importance. In the standard, we provide the attribute SAP WP User Name (SAP_WP_USER). If an HR user name exists, the system fills the attribute with the HR user of an employee. If there is no HR user name, or if you are using more than one HR system, so that an employee's HR user name is not unique, you must assign a unique Workplace user name for each employee in the Workplace system group.

Requirements

Standard settings

This BAdI is not implemented in the standard system. Unless you create an implementation, the system generates the keys for the LDAP directory according to the defaults defined in the standard system.

Activities

When you call the Implementation Guide (IMG) activity, a dialog box appears in which you enter a name for the implementation.

If you have already created implementations for this BAdI, a dialog box appears that lists the existing implementations. In this box, choose Create, and continue as follows:

  1. In the dialog box, in the Implementation field, enter a name for the BAdI implementation, and choose Create.

    The initial screen for creating BAdI implementations appears.

  2. On the initial screen, in the Short Text for Implementation field, enter a short text for the implementation.
  3. Choose the Interface tab page.

    On the tab page, the system automatically fills the Name of Implemented Class field, since it assigns a class based on the name of your implementation.

  4. Save your entries and make the assignment to a development class.
  5. Position the cursor on each method in turn and double click to call method editing.
  6. Between the commands method <Interface Name>~<Name of Method>. and end method. enter the code you require for the implementation.
  7. Save and activate your code.
  8. Navigate back to the Change Implementation screen.
  9. Choose Save on the Change Implementation screen.

    Note: You can also create an implementation for a BAdI and activate it later. In that case, stop editing now.

  10. Choose Activate.

    Now, when you execue the application program, the system runs the code you stored in the method.

Further Notes:

Interface

Method: Return RDN for a Person

Method: Return Workplace User Names

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRLDAP_ATTRIBUTES 0 HLA0009700 Personnel Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030317 
SAP Release Created in 2002_1_470