59317468 srm hr replication

ASUG SRM Meeting

SRM & HR Replication

Markus FrieskeProcurement Regional Implementation GroupApril 1st 2009

Overview & DefinitionsOverview about some parameters (table T77S0)We have an issue...Questions & open discussion

Agenda

© SAP 2009 SRM & HR Replication /

SRM Organizational Structure Definition

SRM is using a Organization Model similar like in ERP to maintain attributes like companycodes or cost centers. Additional attributes like a catalog, SRM role or ITS URL (with previousrelease) are also maintained in this structure.

The organizational structure is the technical representation of organizational units in anenterprise, which are arranged in a hierarchy, according to tasks & functions (e.g. companiesor 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 followingobject types examples are used for the organizational plan and for specifying agents orresponsibilities:

Organizational unit (O)Position (S)User (US)Employee (P) / Central Person (CP)


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 maintainedusing transaction SU01. This user cannot work in the live SRM system, since much of theimportant information on the user is stored as attributes in the organization model. For thisreason, the user must be integrated in the organization model. This is carried out using astructure comprising several objects (position, central person, business partner, and SU01user).

As often there are several possibilities to create an SRM user, e.g. manually by anAdministrator, using transaction USERS_GEN or via CUA (Central User Administration).


Organizational Structure Creation

1. Creation of SRM Organizational Structure – The following two methods exists tocreate 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 theSRM Organization Structure (there are additional transactions likePPOSV_BBP (since SRM 5.0) to display suppliers data)

1.2. HR Replication

SRM structure can be replicated from the HR OM (OrganizationalManagement)


Supplier Organization Structure

Since SRM 5.0 externalBusiness Partners (vendors,bidders and their employees)are no longer part of theorganizational model of thecompany that runs SRM.

Please also see OSS note934372 – “SRM/CRM: HRintegration for business partner– new features”


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 tohave an initial distribution and frequently a delta distribution.

The replication of the HR structure into SRM eliminates the duplicate maintenance betweenR/3 & SRM. The process includes the initial replication & the nightly replication of changesmade 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 organizationalunits, positions, and jobs are available in SRM. In addition, an SRM business partner, whichis referenced in the individual processes, is also created for every organizational unit.


Key components


Other application with HR integration

SAP Supplier Relationship Management (SRM)SAP Customer Relationship Management (CRM)SAP E-RecruitingSAP Collaboration Projects (cProjects)SAP Strategic Enterprise Management (SAP SEM)SAP Internet Communication Manager (ICM)


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?

…?


Overview of important switches for using BPObjects with in HR (table T77S0)

HRALX HRAC Activate HR Integration Integration of HR data with BP

HRALX MERID Enter Integration Error in IDOCSwitch defines errors when ALE is used for BPdata transfer to other systems

HRALX MSGRE Recipient of Error Message When Creating BPSwitch defines receiver of email through w/flow forthe errors raised through ALE transfer

HRALX OADBP Business Partner of Standard AddressBP with standard address is needed if address is notmaintained consistently for New org units created in HR

HRALX OADRE Address Necessary for Business Partner? Switch to control the address requirement for a BP object created in HR

HRALX OBPON Integraion O-BP Active Switch to integrate BP with Org Unit

HRALX OBWIG Ignore Business Partner WarningsSwitch to control the warning messages generated during the creation of BPobject

HRALX ONUMB Number Assignment Business Partner (Org. Unit)

Switch setting to control the default number range type for BP object. Setting 1:number range extends from 0000000000 to 9999999999; Setting 2: An individualnumber range interval exists for the business partner with the organizational unitrole. This interval must be indicated as an internal number assignment. (need torefer HRALX -OSUBG); Setting-3: The first two digits of the number range intervalhave to be letters, The business partner in the organizational unit role is toreceive the same number as the corresponding organizational unit

HRALX OSUBG Subgroup of Business Partner (Organizational Unit)

Character-type switch that contains the subgroup of the number range intervalfor the business partner in the organizational unit role; Dependency on HRALX-ONUMB value

HRALX PBPHR Employees Are Replicated from HR SystemThree types of settings for integration between employee and BP: ON, CREATE,OFF

HRALX PCATS Integration P-BP for CATS Active ALE switch to determine replication of time recording in BP

HRALX PINAC Activate ALE Distribution of Inactive Employees Switch to control distribution of INACTIVE employees through ALEHRALX PLEVE Log: Detail Level of Error Messages (1 - 5)

HRALX PNUMB Number Assignment Business Partner (Employee)

Switch setting to control the default number range type for BP object. Setting 1:number range extends from 0000000000 to 9999999999; Setting 2: An individualnumber range interval exists for the business partner with the organizational unitrole. This interval must be indicated as an internal number assignment. (need torefer HRALX -OSUBG); Setting-3: The first two digits of the number range intervalhave to be letters, The business partner in the organizational unit role is toreceive the same number as the corresponding organizational unit

HRALX PQUAL Import Qualifications Switch to control replication of qualifications with BP through ALE

HRALX PRTON Log Active

HRALX PSUBG Business Partner Subgroup (Employees)

Character-type switch that contains the subgroup of the number range intervalfor the business partner in the employee role. Dependent on the valuesmaintained in HRALX PSUBG & HRALX PNUMB


HRALX parameters in table T77S0

HRALX HRAC: HR integration with BP. This setting means that there is integration between HRstructure and business partner. It should be X if business partners have to be created from HRdata (this setting should also be X for an standalone scenario – not ALE connection with an HRsystem, 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 notautomatically transferred to the BP.

HRALX PBPHR: Determines if employees can be created locally.OFF: locallyON: replicated from HR, not locallyCREATE: can be created locally, but if an employee is replicated from HR, it changesto ON.

(continued on next slide)


HRALX parameters in table T77S0(part II)

HRALX PBPON: Integration between employees and BP. This setting is no longer required upSAP_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 notautomatically transferred to the BP.

These settings must be active in order to create BPs.

We have an issue...

ASUG SRM Meeting

SRM & HR Replication


Useful transactions & more

PFAL – Replicate HR master dataSALE – IMG for setting up ALEWE09 – look for IDOCs by content.WE19 – copy IDOCsBD64 – distribution modelBD87 – IDoc/tRFC Monitoring and ReprocessingSM58 – Displays errors in the tRFC queueReport 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 theorganization plan

Spending / approval limit can also be maintained at user / role level (personalization)

help.sap.comhttps://www.sdn.sap.com/irj/bpx

http://help.sap.com/

https://www.sdn.sap.com/irj/bpx


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 # 363187SAP Note # 550055 EBP/SRM: New integration for business partnerSAP Note # 934372SAP 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 'notactive'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


Useful OSS notes – note 1128751 “Loss ofattribute 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-controltab "Attribute":"Attributes" in your production system:

Transaction SM30 -> T77OMFRASSelect 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 themWhen 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 "DoNot Display" (last column).


Activate Change documents

You might like to activate the change documents to track all changes done to the OrganizationStructure and its attributes. You can use the report RHCDOC_DISPLAY to display thesechanges. 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 CentralPerson, O Organizational Unit, etc.), Infotypes & Subtypes


Display Change Documents with reportRHCDOC_DISPLAY


What to do in case of an issue? Open an OSSmessage!

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 youhave to write less!

Provide an user with whom the issue can be reproduced, if it depends on the authorizationprovide 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 SAPSupport 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 datainto 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 cananswer question 24 hours


Questions?


Copyright 2009 SAP AGAll 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 changedwithout 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 aretrademarks 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 displayedare 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials 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 durchSAP 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 diedazugehö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 Namenvon Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. 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 anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrü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 Zwecksowie 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 Verwendungdieser 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 Hotlinkszugreifen, 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 überInternetseiten Dritter ab.

Alle Rechte vorbehalten.