Business Partner in the Human Resources (HR) System Applies to ECC 6.0 (mysap ERP 2005) Summary This white paper is intended to provide knowledge of the Business Object introduced in HR system through the above SAP release. This will help Companies, Consultants and SAP Practice teams to understand the importance of BP and its features. Author(s): Narasimha Rao SSL Bhamidi Company: Tata Consultancy Services Ltd Created on: 12-Oct-07 Author Bio Narasimha has been working as SAP HR Consultant for Tata Consultancy Services Ltd, Mumbai India for the last 4.5 years. Narasimha has been involved with implementation and support projects with clients like Eli-Lilly & Company (Pharma), Adobe Systems and Halliburton Energy Services. 2007 SAP AG 1
Table of Contents Definition... 3 Integration / Switches... 4 Prerequisites... 6 Activities... 7 Synchronization Program... 7 Related Content... 8 Disclaimer and Liability Notice... 9 2007 SAP AG 2
Definition For Global companies implementing SAP Business Suite with SAP ECC 6.0 (SAP_HR 600), SAP has come up with availability of Business Partner (object type BP). As yet another Org Object with ECC 6.0, HR master data and organizational data (object types CP- Central Person, P - Person, and O- Organizational Unit) are integrated with business partner data. This means that applications that depict persons and organizational units as business partners are provided with HR master data and organizational data. Business impact: SRM or CRM extensively use business Partner object for all day to day transactions. The HR position or person is transferred through ALE to SRM / CRM application, which triggers creation of corresponding BP object or simple integration of the BP object. 2007 SAP AG 3
Integration / Switches This object has extensive dependency on the integration switches, due to the importance of it in other SAP application. The following applications use integration with HR master data and organizational data. SAP Supplier Relationship Management (SRM) SAP Customer Relationship Management (CRM) SAP E-Recruiting SAP Collaboration Projects (cprojects) SAP Strategic Enterprise Management (SAP SEM) SAP Internet Communication Manager (ICM) The following switches enable this integration: APPSY RFCSE SEM RFC Connection SEM Enables RFC connection with SEM System (Strategic Enterprise Management) RECFA DTCBA RFC Connection in E- Recruiting System CPERS EEALE Employee data are imported with ALE Switch to transfer employee data to EBP / CRM 2007 SAP AG 4
The following switches are important for using BP object with in HR system. Switch SEMID GSVAL Text Actual description 1 HRALX HRAC X Activate HR Integration 2 HRALX MERID X Enter Integration Error in IDOC 3 HRALX MSGRE 0 Recipient of Error Message When Creating BP 4 HRALX OADBP 153 Business Partner of Standard Address 5 HRALX OADRE X Address Necessary for Business Partner? 6 HRALX OBPON ON Integration O-BP Active 7 HRALX OBWIG X Ignore Business Partner Warnings 8 HRALX ONUMB 1 Number Assignment Business Partner (Org. Unit) 9 HRALX OSUBG Subgroup of Business Partner (Organizational Unit) 10 HRALX PBPHR ON Employees Are Replicated from HR System 11 HRALX PCATS Integration P-BP for CATS Active Integration of HR data with BP Switch defines errors when ALE is used for BP data transfer to other systems Switch defines receiver of email through w/flow for the errors raised through ALE transfer BP with standard address is needed if address is not maintained consistently for New org units created in HR Switch to control the address requirement for a BP object created in HR Switch to integrate BP with Org Unit Switch to control the warning messages generated during the creation of BP object Switch setting to control the default number range type for BP object. Setting 1: number range extends from 0000000000 to 9999999999; Setting 2: An individual number range interval exists for the business partner with the organizational unit role. This interval must be indicated as an internal number assignment. (need to refer HRALX -OSUBG); Setting-3: The first two digits of the number range interval have to be letters, The business partner in the organizational unit role is to receive the same number as the corresponding organizational unit Character-type switch that contains the subgroup of the number range interval for the business partner in the organizational unit role; Dependency on HRALX-ONUMB value Three types of settings for integration between employee and BP: ON, CREATE, OFF. ALE switch to determine replication of time recording in BP 12 HRALX PINAC Activate ALE Switch to control distribution of 2007 SAP AG 5
Distribution of Inactive Employees 13 HRALX PNUMB 1 Number Assignment Business Partner (Employee) INACTIVE employees through ALE Switch setting to control the default number range type for BP object. Setting 1: number range extends from 0000000000 to 9999999999; Setting 2: An individual number range interval exists for the business partner with the organizational unit role. This interval must be indicated as an internal number assignment. (need to refer HRALX -OSUBG); Setting-3: The first two digits of the number range interval have to be letters, The business partner in the organizational unit role is to receive the same number as the corresponding organizational unit 14 HRALX PQUAL Import Qualifications Switch to control replication of qualifications with BP through ALE 15 HRALX PSUBG Business Partner Subgroup (Employees) Character-type switch that contains the subgroup of the number range interval for the business partner in the employee role. Dependent on the values maintained in HRALX PSUBG & HRALX PNUMB Prerequisites Integration of Personnel Administration with Organizational Management Integration between HR master data and organizational data with SAP Business Partner. (Personnel Management Organizational Management Integration Integration with SAP Business Partner or under Personnel Administration Interfaces and Integration Integration with SAP Business Partner One standard address created as part of the Central Address Management. (There is no need for extensive implementation of Central Address Management (CAM) or Business Address Services (BAS) in ECC system. The BP object ID having the standard address needs to be maintained for switch HRALX OADBP in the above mentioned V_T77S0 table. 2007 SAP AG 6
Activities System will automatically create a Business Partner when ever a new Personnel number or Organization unit is created in HR, within the number range provided in ECC system.to enable this, for Employee use Switch #10 & for Org Unit use Switch # 6 in the table above. The above switches also help to transfer all the changes made to infotypes and objects. Please note that you may need to provide EXTERNAL NUMBER RANGE in other Systems in SAP business suite to accomodate the HR BPs transfered through ALE IDOCs. Use Transaction Code BP to create BP objects for Person / Organization Unit / group. Standard system transfers the field values of the following Infotypes IT0001, 0002, 0006, 0105, HRP1000, 1028 & 1032. Hide sensitive fields before distribution. The BP object cannot be pulled through PP01 transaction. The best way to find the BP object number created in the background is to do SE16 search. ( select Object P or O, Related obj type BP and give other values to narrow down the search as required.) In SRM system address for the BP is mandatory. Use Switch # 5 in the above table to enable transfer of address to data to EBP / SRM system. The standard ALE IDOCs may not create applicant data in E-recruitment automatically. There is a bit customization needed to enable this. Synchronization Program Standard has provided Report - HRALXSYNC is useful : To run consistency checks between the transered BPs and the objects in the receiving system. To create BP objects for already existing Personnel numbers or Org Units. 2007 SAP AG 7
Related Content Integration with SAP Business Partner SDN Forum: Business Partner SDN Forum: Business Partner 2007 SAP AG 8
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2007 SAP AG 9