As part of the newly release TM suite in EP4, one mandatory setting spelled out by SAP is to activate the Switch within OM for the Business Partner Relationship. With EP4, SAP is broadening their application of the Business Partner (BP) concept and how they use it. Specific to Talent management, and Performance Appraisals, the BP drives the details within the TREX search engine and the details within the Talent Profile and Performance Appraisal. Both the Talent Profile ivew and the Performance appraisal (PMP) utilize a bit of configuration called the Talent Header. Within the Talent header information like Name, Job Title , Position is contained. Without the BP relationship, these items will appear blank – not many clients will care for this look and to “fix” the header, you need to enable the BP Integration switch and enable the TREX index engine (including HR_SYNC) . Later in the Series I will discuss in detail the steps to enable the TREX Talent Search, so for this post I will focus on the BP integration switch.
To enable the BP switch , within the IMG, In Customizing for Personnel Management, under Organizational Management -> Integration -> Integration with SAP Business Partner, check whether the HRALX HRAC switch is activated (X).
Once activated this switch will automatically create the BP Relationship going forward during the following Infotype Updates within PA and OM:
- PA – Personal Data (0002)
- PA – Addresses (0006)/Permanent Residence (Subtype 1)
- PA – Communication (0105)/Fax (0005)
Communication (0105)/E-Mail (0010)
Communication (0105)/First Telephone Number at Work (0020)
- OM – Object (1000)
- OM – Address (1028)
The updates can occur via BDC, Interface Import, ESS or typical R/3 PA30 transactions. SAP delivers a utility that will look for existing CPs (Central Persons) and create the BP in mass. This job will lock the USERID while it creates the CP – so beware – this process at one client site took over 4 days to run – thus locking all of those users out of R/3 and Portal access till its completion. Not the most efficient program for sure.
So now for the Beware part of this post. If you are at a client who has also implemented the Treasury Module within SAP Financials, and you are on an integrated FI/HCM client, the BP relationship will also create new entries in the Treasury transactions. Before this integration switch is enabled , typically clients will have Vendors as BP’s that they pay remittance to. After enabling this switch, all employees will show up as BP’s, and their information will automatically get copied from the HR PA Infotypes to the BP tables :
- Home Address
- Marital Status
- Bank Account information
By default, with the standard Treasury (BP) transactions, all of this information will be visible to the FI users. HR based Infotype security will not be enforced. Since much of this data is confidential in nature it is very important to make sure the client is not running the Treasury Module, or that the appropriate Treasury Module configuration is completed to Hide the Employee based BP’s from the FI users. Otherwise the FI users will have access to every employee in the company’s Bank Accounts and Home Addresses – in addition the Treasury user can select and Payout directly to an Employee as if they are a vendor. Yikes!
The lesson to learn here is SAP has really expanded the BP relationship across several modules:
- SAP Supplier Relationship Management (SRM)
- SAP Customer Relationship Management (CRM)
- SAP E-Recruiting
- SAP Talent Management
- SAP Collaboration Projects (cProjects)
- SAP Strategic Enterprise Management (SAP SEM)
- SAP Internet Communication Manager (ICM)
Remember: The information required to make one module work can have downstream effects due to integration with modules outside the HCM world in SAP.