Srm Hr Replication

ASUG SRM Meeting SRM & HR Replication Markus Frieske Procurement Regional Implementation Group April 1st 2009 Agenda Overview & Definitions Overview about some parameters (table T77S0) We have an issue... Questions & open discussion SRM Organizational Structure Definition SRM is using a Organization Model similar like in ERP to maintain attributes like company codes or cost centers. Additional attributes like a catalog, SRM role or ITS URL (with previous release) are also maintained in this structure. The organizational structure is the technical representation of organizational units in an enterprise, which are arranged in a hierarchy, according to tasks & functions (e.g. companies or purchasing organizations). A model of the task-related functional Organization Structure such as departmental hierarchy, as well as the reporting structure between positions such as purchasing administrator, occupied by holders, employees, or SAP Systems users, in an enterprise. Organizational units are objects that form the basis of an organizational plan. The following object types examples are used for the organizational plan and for specifying agents or responsibilities: Organizational unit (O) Position (S) User (US) Employee (P) / Central Person (CP) © SAP 2009 SRM & HR Replication / Page 3 Users in SRM In SRM it will be distinguised between 2 types of user: the SU01 user and the SRM user. The SU01 user is the user in the standard SAP System, which can be created and maintained using transaction SU01. This user cannot work in the live SRM system, since much of the important information on the user is stored as attributes in the organization model. For this reason, the user must be integrated in the organization model. This is carried out using a structure comprising several objects (position, central person, business partner, and SU01 user). As often there are several possibilities to create an SRM user, e.g. manually by an Administrator, using transaction USERS_GEN or via CUA (Central User Administration). © SAP 2009 SRM & HR Replication / Page 4 Organizational Structure Creation 1. Creation of SRM Organizational Structure – The following two methods exists to create the SRM Organization Structure: 1.1. PPOCA_BBP / PPOMA_BBP – Manually create / maintain system root The above transaction codes are used to manually create and maintain the SRM Organization Structure (there are additional transactions like PPOSV_BBP (since SRM 5.0) to display suppliers data) 1.2. HR Replication SRM structure can be replicated from the HR OM (Organizational Management) © SAP 2009 SRM & HR Replication / Page 5 Supplier Organization Structure Since SRM 5.0 external Business Partners (vendors, bidders and their employees) are no longer part of the organizational model of the company that runs SRM. Please also see OSS note 934372 – “SRM/CRM: HR integration for business partner – new features” © SAP 2009 SRM & HR Replication / Page 6 HR Replication This structure can be created manually in SRM, but also replicated from an ERP (HR) system, The replication to SRM will happen using ALE (Application Link Enabling). It is possible to have an initial distribution and frequently a delta distribution. The replication of the HR structure into SRM eliminates the duplicate maintenance between R/3 & SRM. The process includes the initial replication & the nightly replication of changes made since the previous replication. The following objects are included: Organization units (O) Jobs (C) Position (S) Employees (P) & their Relationships As a result of the replication, the complete enterprise structure - consisting of organizational units, positions, and jobs are available in SRM. In addition, an SRM business partner, which is referenced in the individual processes, is also created for every organizational unit. © SAP 2009 SRM & HR Replication / Page 7 Key components © SAP 2009 SRM & HR Replication / Page 8 Other application with HR integration 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) © SAP 2009 SRM & HR Replication / Page 9 Maintain Org. Structure in HR or SRM? Prerequisite - HR system with Organization Structure exists Which parameter might influence the decision to use HR replication? Number of changes Size of organization structure / number of users SRM release? …? © SAP 2009 SRM & HR Replication / Page 10 Overview of important switches for using BP Objects with in HR (table T77S0) HRALX HRALX HRALX HRALX HRALX HRALX HRALX HRAC MERID MSGRE OADBP OADRE OBPON OBWIG Activate HR Integration Enter Integration Error in IDOC Recipient of Error Message When Creating BP Business Partner of Standard Address Address Necessary for Business Partner? Integraion O-BP Active Ignore Business Partner Warnings 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 HRALX HRALX HRALX HRALX HRALX HRALX ONUMB OSUBG PBPHR PCATS PINAC PLEVE 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 Number Assignment Business Partner (Org. Unit) Character-type switch that as the corresponding organizational unit receive the same number contains the subgroup of the number range interval for the business partner in the organizational unit role; Dependency on HRALXSubgroup of Business Partner (Organizational Unit) ONUMB value settings for integration between employee and BP: ON, CREATE, Three types of Employees Are Replicated from HR System OFF Integration P-BP for CATS Active ALE switch to determine replication of time recording in BP Activate ALE Distribution of Inactive Employees Switch to control distribution of INACTIVE employees through ALE Log: Detail Level of Error Messages (1 - 5) 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 Number Assignment Business Partner (Employee)receive the same number as the corresponding organizational unit Import Qualifications Log Active 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 Switch to control replication of qualifications with BP through ALE HRALX HRALX HRALX PNUMB PQUAL PRTON HRALX PSUBG Business Partner Subgroup (Employees) © SAP 2009 SRM & HR Replication / Page 11 HRALX parameters in table T77S0 HRALX HRAC: HR integration with BP. This setting means that there is integration between HR structure and business partner. It should be X if business partners have to be created from HR data (this setting should also be X for an standalone scenario – not ALE connection with an HR system, but HR structure maintained in transaction PPOMA_CRM or PPOMA_BBP). HRALX OBPON: integration between org units and BPs. ON: Active. If an org. unit is created via ALE the corresponding BP is created. Changes to O are transferred to BP. Changes to BP are not transferred to O. OFF: Inactive. BP is not created from org. units. CREATE: as ON but in this case changes made to the organizational unit are not automatically transferred to the BP. HRALX PBPHR: Determines if employees can be created locally. OFF: locally ON: replicated from HR, not locally CREATE: can be created locally, but if an employee is replicated from HR, it changes to ON. (continued on next slide) © SAP 2009 SRM & HR Replication / Page 12 HRALX parameters in table T77S0 (part II) HRALX PBPON: Integration between employees and BP. This setting is no longer required up SAP_ABA 7.00 (note 934372 section 7). ON: Active. If an employee is created via ALE the corresponding BP is created. Changes to P are transferred to BP. OFF: Inactive. BP is not created from employees. CREATE: as ON but in this case changes made to the employee are not automatically transferred to the BP. These settings must be active in order to create BPs. © SAP 2009 SRM & HR Replication / Page 13 ASUG SRM Meeting SRM & HR Replication We have an issue... Useful transactions & more PFAL – Replicate HR master data SALE – IMG for setting up ALE WE09 – look for IDOCs by content. WE19 – copy IDOCs BD64 – distribution model BD87 – IDoc/tRFC Monitoring and Reprocessing SM58 – Displays errors in the tRFC queue Report RHALECPS – to display ALE change pointers for HR Master Data Attributes inheritance should always be used for values that stay constant for a sub tree of the organization plan Spending / approval limit can also be maintained at user / role level (personalization) help.sap.com https://www.sdn.sap.com/irj/bpx © SAP 2009 SRM & HR Replication / Page 15 SAP Notes SAP Notes: The composite note for the process is 390380 - HR/ALE distribution in EBP/SRM. The initial description of the process can be found in note 312090 - Integration HR EBP/SRM. SAP Note # 363187 SAP Note # 550055 EBP/SRM: New integration for business partner SAP Note # 934372 SAP Note # 918510 (Also reference section referencing time dependency in SAP Note # 934372) SAP Note # 918485, must be implemented in case the time dependency is set as 'not active' SAP Notes relevant w/ Concurrent Employment (SRM 5.0 SP4) 1002114 , 996789, 983743, 981042 , 980380 ,978071 , 977895 , 975633 ,969974, 955686, 953399, 951160, 946345, 946294, 940881 , 939608, 936733, 930542, 927194, 918485 © SAP 2009 SRM & HR Replication / Page 16 Useful OSS notes – note 1128751 “Loss of attribute values in PPOMA_BBP” Some attributes gets lost when maintaining them in PPOMA_BBP In case it does not solve the issue here are the steps to come back to the old NW table-control tab "Attribute": "Attributes" in your production system: Transaction SM30 -> T77OMFRAS Select scenario OMATTBBP in "Scenario Definition (Hierarchy Framework) and navigate to "Tab Page in Scenario for each Object Type" Select all entries containing tab page "BBPATTR" and copy them When copying, exchange the entries "BBPATTR" by "ATTRIB" (tab page) "SAPLBBP_OM_DIALOG_A" by "SAPLRHOMATTRIBUTES" (report name), and "3000 by "0100" (screen). Deactivate the entries containing tab page "BBPATTR" or "BBPATTRL" by the indicator "Do Not Display" (last column). © SAP 2009 SRM & HR Replication / Page 17 Activate Change documents You might like to activate the change documents to track all changes done to the Organization Structure and its attributes. You can use the report RHCDOC_DISPLAY to display these changes. This might be helpful to understand who and when somebody changed any attribute. Activate via view T77CDOC_CUST (Tx. SM30), select for which Object types (like CP Central Person, O Organizational Unit, etc.), Infotypes & Subtypes © SAP 2009 SRM & HR Replication / Page 18 Display Change Documents with report RHCDOC_DISPLAY © SAP 2009 SRM & HR Replication / Page 19 What to do in case of an issue? Open an OSS message! First try to reproduce the issue – an issue with can not be reproduce is also difficult to analyse! Provide the exact steps how to reproduce it, sometimes screenshots will help a lot and you have to write less! Provide an user with whom the issue can be reproduced, if it depends on the authorization provide a second user with more authorization (e.g. SAP_ALL) Report in the message which (SRM) release and Support Package you are using What have you done already, e.g. searched for OSS notes? Mention it in the message, e.g. That note xyz has been applied, but did not solve or note xyz is not valid, etc. Make sure that the remote connection is open, e.g. also over the weekend so that SAP Support can also work on Monday morning in India or Germany on the issue copy a short dump better to a seperate file & attach it instead of copying the complete data into the message (or just add the exact time stap of the short dump) If it is a production down issue please provide a mobile phone number where somebody can answer question 24 hours © SAP 2009 SRM & HR Replication / Page 20 Questions? © SAP 2009 SRM & HR Replication / Page 21 Copyright 2009 SAP AG All rights reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten. © SAP 2009 SRM & HR Replication / Page 22