As of SRM Release 3.0 and CRM Release 4.0, this note provides a revised version of the integration of HR master data (organizational model and employee) with the business partner (in the roles of employee and organizational unit). This note is valid for both scenarios with an ALE distribution of HR master data and for standalone scenarios. Reason and Prerequisites
Note the corrections in the "Related notes" section.
For versions lower than CRM Release 4.0 or SRM Release 3.0, see Note 390380.
The integration of existing structures between an HR system and your CRM or SRM system is not supported. Solution
Apply the attached patches. Notes that correct known errors are attached to this note.
The following changes have been implemented since earlier versions of HR:ALE distribution:
1. Filter settings: Predefined templates that contain the correct filter settings are provided in Note 615896. Alternatively, you can also copy the filter settings contained in Note 312090 as before. In this case, you still have to add a new filter group. Add a filter group for infotype 1001 with the following parameters: Infotype: "1001", object type: "P", type of related object: "S", subtype "B008". You should not add this entry if you plan to distribute only employee data and no positions or organizational units.
2. Customizing: (The following information refers to the T77S0 table; the previous switches no longer apply.)
a) Activation of the integration: First you must activate the integration by using the main switch (HRALX/HRAC=X; formerly switch CPERS/EEALE).
b) Integration (organizational units): To activate the integration between business partners and organizational units, you must activate the HRALX/OBPON=ON switch (formerly: BUPA/SYNC).
c) Integration (employee): To activate the integration between business partners and employees, you must activate the HRALX/PBPON=ON switch.
d) Roles: For the business partner in the organizational unit role, the role description is maintained in HRALX/OPROL=BUP004 (formerly: ORGEH/PROLE), for employees it is maintained in HRALX/PPROL=BUP003 (formerly: CPERS/PROLE).
e) Number assignment: Generally, there are three types of number assignment when business partners are created.
1 = As before, the system uses the number from the general internal interval of the BU_PARTNER number range object.
2 = The system uses the number from a specific internal interval of the object.
3 = The system transfers the number from HR and adds a prefix. In this case, the system uses a specific external interval that must be defined as XX00000000 up to XX99999999. XX represents any two letters.
The system uses HRALX/ONUMB to set the number assignment for organizational units and HRALX/PNUMB to set number assignment for employees.
The number range object for all switch positions is BU_PARTNER, with the interval depending on the switch value. For switch value 1, the system uses the internal standard interval. Otherwise (for switch values 2 and 3), the HRALX/OSUBG or HRALX/PSUBG switch defines the interval. For switch values 2 and 3, you must also create a grouping (transaction BUC2) for these intervals. To ensure that the system can connect the grouping and the number range interval, the name of the grouping must be identical to the name of the relevant number range interval. (The name of the grouping is contained in the first column of the table.) If you select type 3 (switch HRALX/PNUMB = 3) for the number assignment of business partners of the employee role, manually create the HRALX/PSUBG switch in the T77S0 table.
f) Error workflow: If users are to be informed about errors by mail, you can define the recipient in the HRALX/MSGRE switch (0 = no messages, 1 = Workflow administrator is informed, 2 = Mail is sent to user, 3 = Workflow administrator and user are informed).
g) Addresses: If addresses are required to generate correct business partners of the organizational unit role (in SRM, for example), the HRALX/OADRE switch is set to X (formerly: the BUPA/ADDR switch). If it is mandatory for each business partner of the organizational unit role to have an address, but the relevant organizational units do not always have a separate address, you can define a standard address. Create a separate business partner for storing the standard address. The number of this business partner, which is used as a container, is stored in the HRALX/OADBP switch (formerly BUPA/ADRBP).
h) Qualifications for employees (PLM only): If you also transfer qualifications for employees, you must set the HRALX/PQUAL switch to X.
i) Relationship with the user: By default, the system only creates a relationship with the user (infotype 0105, subtype 0001) if the user already exists in the target system. However, you can change this system behavior using the HRALX/USRAC switch. If this switch is set to value 'X', the system creates relationships for the user, even if the user does not exist in the system (see Note 711852). You no longer require a relationship between the position and the user (S-US) (for more information, see Notes 632879 and 752923).
j) Converting the form of address: Since the form of address key of the employee data and the form of address key of the business partner have different meanings, they must be assigned accordingly in the view V_TSAD3HR or V_TSAD3HR_NEW.
3. IDoc status: The status management for IDocs is enhanced, and now the system informs the user or the administrator about problems during the posting of IDocs. In particular, the system informs the user about the following situations in the IDoc status:
a) The integration with the business partner is deactivated: As a result, incorrect IDocs occur when you post employees (READ_NAMTB). Activate the integration.
b) The employee has infotypes that you cannot be transferred to the central person: In this case, the system ignores the infotype and generates an entry in the IDoc log. Adjust the filter settings in the distribution model accordingly.
c) Business partner: If an error occurs when the business partner belonging to an organizational unit or to an employee is either created or updated, the error is displayed in the IDoc log and the IDoc is set to 'Incorrect'. Correct the cause of error (for example, by adjusting the Customizing settings in the business partner or the address management) and send the data again.
4. Initial distribution: The new version of the ALE distribution allows you to send or post objects using the initial distribution as many times as required. (Up to now, the system has generated new business partners each time; as of now, the system only updates the partners that already exist.) However, an initial distribution deletes all information that you maintain locally. In particular, attributes for BBP, SALE and SERVICE maintained for organizational units are lost.
5. Posting employees: The system creates business partners only if the employee is active and has at least infotypes 0000, 0001, 0002 and 0006 (with subtype 1) on the current date. If you want to prevent the system from sending sensitive data from the HR system, see Note 724149.
6. Synchronization: Up to now, you have used the CRMHRALE_CEN TRAL_PERSON or CRM_COM_ORGMAN_BUPA_INTEGRATE report to generate or update business partners for employees or organizational units. The HRALXSYNC program is now available for this purpose. The former programs automatically start this report. Up to now, you have been able to execute the CRMHRALE_DISPLAY program to display the future employee data. This program is replaced with the RHRHAZ00 program.
7. After the upgrade: First set up Customizing as described above. After the upgrade, you must send the relevant employees (personnel numbers) to the SRM or CRM server using the initial distribution if you have already transferred employees from a connected HR system in an earlier SRM or CRM release. In this process, important information about the employee is stored in the target system and therefore, the system correctly transfers changes to the business partner (in earlier releases, this was only partly done using the HRALETMP or PCLHR tables). You do not have to use the SAPKE47016 HR patch. A direct relationship between the position and the user (S-US) is no longer created. This relationship is redundant because a relationship already exists between the position and the user through the central person (S-CP-US). However, for the workflow to work correctly, ensure that you have implemented Notes 632879 and 746188.
If, prior to the upgrade, a comparison was successfully executed with the HRALXSYNC report, you must adjust the relevant entry in the T77ZZ table for the REPID = HRALXSYNC value accordingly: Change the value of the SAPRL field to the current value of the release for component SAP_BASIS or SAP_ABA.
8. As of SRM 5.0 and CRM 5.0: For more information, see Note 934372.