SRM Org Structure Part 3 Tools, Tables and Reports

Applies to:
SAP SRM 7.0, SRM 5.0, For more information, visit the Supplier Relationship Management homepage.

Summary
Organization structure has been one of the critical application component of SAP SRM System. It has always been easy to avoid manual maintenance of Org structure elements in SRM if it is possible to integrate HR system organization structure with SRM for automatic replication of HR Org data to SRM org structure. This document talks about the necessary configurations and important OSS notes which should be followed while setting HR-SRM Interface for Org data replication from HR to SRM Author: Virender Singh, CPIM CSCP

Company: Intelligroup Inc. Created on: 14 September 2010

Author Bio
Virender Singh is a SAP SRM 7.0 Certified Professional consultant with more than 9 years of SAP Consulting Experience working with Leading IT Organization serving global clients. He has extensive experience of a number of implementations, upgrades, rollouts and run/maintain lifecycles of SAP Solutions running on SAP SRM, ECC, SNC, and SAP Solution Manager. As a professional member of APICS and APICS Certified CPIM CSCP associate he has adequate knowledge and experience of modern day Supply Chain and Supplier Relationship processes. Currently in Intelligroup Inc., he is involved in providing innovative solutions to Global clients on SAP SRM and SCM.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

SRM Org Structure Part 3 Tools, Tables and Reports

Table of Contents
Background ......................................................................................................................................................... 3 Configurations in HR ........................................................................................................................................... 3 Filter Settings in HR ........................................................................................................................................ 3 Configurations in SRM ........................................................................................................................................ 5 Configure Table T77S0 for Group id HRALX .................................................................................................. 5 Employees ...................................................................................................................................................... 7 Synchronization............................................................................................................................................... 7 Change Pointers(RBDMIDOC) ....................................................................................................................... 7 Important Function Groups and Function Modules ............................................................................................ 8 Related contents ............................................................................................................................................... 10 Important OSS Notes .................................................................................................................................... 10 Disclaimer and Liability Notice .......................................................................................................................... 11

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

SRM Org Structure Part 3 Tools, Tables and Reports

Background
Advantages of having organization structure distributed from HR to SRM: Reduced Data Maintenance Consistency in SRM Org structure as per Enterprises actual hierarchy

The process of integration of HR with SRM for Org data distribution takes place via ALE Distribution. This process consists of two parts: Initial Distribution and nightly distribution in terms of change pointers. When HR sends data from HR to SRM, following objects are picked up from HR and sent to SRM via IDocs: Organization Units (O) Jobs ( C ) Positions (S) Employees (P) Relationships of P with other objects like O and S

Business partner which is an important aspect of any transaction in SRM, is created for every Organizational Unit and Central Person created in SRM.

Configurations in HR
In order for initial distribution and/or change pointers to distribute from HR to SRM, it is required to set up ALE Distribution between HR and SRM with Message type HRMD_ABA. Follow the standard procedure to set up ALE Distribution and use the filter settings shown below for the message type HRMD_ABA in HR using transaction BD64. Generate Partner Profiles and Distribute the model to SRM. Verify the same in SRM whether same filters have got updated there or not. Filter Settings in HR

Recommended Settings
Filter Group Field Value Comments

Filter Group 1

Info type Object Type

1001 C S O

Filter Group Relations

for

Linked (SCLAS)

Object

C S O

Subtype

A002 A007 A008 A012 B002 B007 B008

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

SRM Org Structure Part 3 Tools, Tables and Reports

B012

Filter Group 2

Info type Object Type

1001 S Object P

Filter Group for Relations When Object S is specified

Linked (SCLAS)

Subtype

A008

This relationship links a Position(S) with the Person (P) in HR - Central Person (CP) in EBP

Filter Group 3

Info type

1001

Filter Group for Relations when Linked Object is specified Object Type Note 389326 Linked (SCLAS) Subtype Object S O S O A003 B003 Relationships A003 and B003 are used to link a Position (S) with Org. Unit (O)

Filter Group 4

Info type

1000 1002

Info Type 1000 Object ID & Short Text for Object Types C, O and S Info Type 1002 Long Text/Descriptions for Objects O, C and S Info Type 1028 Address of Org. Unit (O)

Filter Group for Organizational Objects

1028

1032 Object Type C S O Subtype

Info Type 1032 E-mail Address of Org. Unit (O)

Filter Group 5

Info type

0000 0001

Info Types 0000, 0001 and 0002 are for HR Persons (P) Info Type 0000 Actions Info Type 0001 Org. Assignment

Filter Group Employees

for

0002

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

SRM Org Structure Part 3 Tools, Tables and Reports

0009 Object Type Subtype P

Info Type 0002 Personal Data

Filter Group 6

Info type

Info Types 0006 is for HR Persons (P) Info Type 0006 Addresses

Filter Group Employees

for

Object Type Subtype

P 1 Sub type 1 Permanent Address

Filter Group 7

Info type Object Type

105 P 1 5

Info Type 0105 is for HR Persons (P)

Filter Group Employees

for

Subtype

Subtype 0001 SAP User ID Subtype 0010 E-mail address

Filter Group 8

1001

Info Types 0006 is for HR Persons (P) Info Type 0006 Addresses

Object Type Subtype

P B008 Relationship B008 links a Position (S) with the Person (P) in HR Central Person (CP) in CRM

Filter Group 9

Info type Subtype Object Type Type of Object Subtype Related

1001 B008 P CP A209

Info Types 0006 is for HR Persons (P) Info Type 0006 Addresses

Relationship B008 links a Position (S) with the Person (P) in HR Central Person (CP) in CRM

Configurations in SRM
Configure Table T77S0 for Group id HRALX

SEMID
HRAC OBPON PBPON

GSVAL (example values)

X ON ON

Description (ETEXT)
Activate HR Integration Activate Integration between Business Partner and Organizational Units
Activate the integration between business partners and employees

Additional Comment

Formerly CPERS/EEALE Formerly BUPA/SYNC

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

SRM Org Structure Part 3 Tools, Tables and Reports

(No Longer Required) OPROL BUP004 Role of organizational unit in business partner (No Longer Required) Role of employees in business partner (No Longer Required) Business Partner Number Assignment (Org. Unit) Business Partner Number Assignment (Employee)
Formerly HRALX/USRAC

PPROL ONUMB PNUMB

BUP003 1 1

Note on ONUMB and PNUMB For switch value 1, the internal interval is used. For switch values 2 and 3, the interval is defined by switches HRALX/OSUBG and HRALX/PSUNG. Additionally for switch values 2 and 3, a grouping must be created (transaction BUC2) for these intervals. So

that the system can connect the grouping and number range interval, the name of the grouping must be identical to the name of the corresponding number range interval (the name of the grouping is in the first column of the table). If type 3 is chosen (switch HRALX/ PNUMB=3) for the number assignment of business partners of the employee role, switch HRALX/PSUBG need to be created manually in table T77S0.

OBWIG OSUBG

Ignore Business Partner Warnings Business Partner Subgroup (Organizational Unit) (This config is based on what is selected in ONUMB and PNUMB) (This config is based on what is selected in ONUMB and PNUMB) Business Partner Subgroup (Employees)

PSUNG

PSUBG

(This config is based on what is selected in ONUMB and PNUMB) Recipient of Error Message When Creating BP. This configuration is required if users have to be informed by email. Recipients of such emails are driven by this configuration. Here are the settings allowed: 0 No Messages 1 - Inform Workflow Administrator 2 User gets the email 3 Workflow Administrator as well as User gets the email

MSGRE

Address Necessary for Business Partner. OADRE X Remove this entry if Address is not required for all Business Partners. Business Partner of Standard Address. Here we define the standard address, which is assigned to OADBP 0000000001
every organizational unit without its own address. This is done in case we dont transfer addresses of Organizational Units from HR. Refer to OSS note 550055, section (g) for more details on this topic
Formerly BUPA/ADRBP Formerly BUPA/ADDR

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

SRM Org Structure Part 3 Tools, Tables and Reports

PQUAL

Import Qualifications. This switch is used only if we are transferring qualifications from PLM System. Create Relationship to User. Relationship link to the user(info type 0105, subtype 0001) is created only if the user exist in the target system If this switch is activated, system generates a relationship for the user even if the user does not exist in the system. From SRM 5.0 onwards, this indicator is not required because S-US relationship is no longer required as that relationship is driven by S-CP-US Relationship

USRAC

PALEO PALEP

Log: Organizational Units in ALE Log: Employees in ALE Employees Are Replicated from HR System. We can not maintain the fields of Employee Data (Personnel Number and User Name fields) if Employee (object type P) is distributed from HR if the employee exists in the ERP system in which business partner integration is active. In this case PBPHR switch in T77S0 table is set to be ON, otherwise it remains OFF Integration P-BP for CATS Activated Activate ALE Distribution of Inactive Employees. (No Longer Required) 5 Log: Detail Level of Error Messages (1 - 5) Log Active Log: Organizational Units in Dialog Log: Employees in Dialog

Formerly ORGEH/PROLE Formerly CPERS/PPROLE

PBPHR

OFF

PCATS PINAC PLEVE PRTON PSYNO PSYNP

Formerly BUPA/ADDR

Employees The system creates business partners only if the employee is active and has at least info types 0000, 0001, 0002 and 0006 (with subtype 1) on the current date. Synchronization Report HRALXSYNC is used for Synchronization between SRM and HR. BBP_BP_OM_INTEGRATE is the TCODE executing this report, if required. Change Pointers(RBDMIDOC) After the initial setup of the organization model, you have to distribute the changes. Changes may happen any time in HR System. Considering the volume and sensitive nature of the data in HR Organization, it is required to ensure that HR-SRM interface distribute only the changes from HR to SRM. This is done by scheduling the job for change pointers in SRM.. Every change creates a change pointer in HR. Change pointer report RBDMIDOC then collects all these change pointers and creates IDOCS that will distribute these changes to the relevant systems.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

SRM Org Structure Part 3 Tools, Tables and Reports

How does the system know to which systems the changes have to be distributed? The system simply checks the entries in the distribution model and is using all the settings there. This means that it is only distributing these changes to the connections in the distribution model that have an entry for message type HRMD*. In addition, this means that the distribution is done with the same filter settings as for the initial distribution. The IDOCS will be sent in the UPDATE-mode. Thus, it is not deleting the whole object. However, it is deleting the entries for the particular info type that has been changed, and is creating the new entries for this info type

Important Function Groups and Function Modules

BBP_BUPA This Function Group contains all the function module which can be used for functions around Business partners(Internal as well as external). FMs in this Function Group are:

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

SRM Org Structure Part 3 Tools, Tables and Reports

BBP_OM_USER This function group contains Function Modules which could be used for user master integration activities:

BBP_OM This Function Group Contains following FMs:

BBP_OM_STRUCTURE: This Function Group contains following FMs:

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

SRM Org Structure Part 3 Tools, Tables and Reports

Related contents
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a0d5e113-10b1-2d10-5193-87fb808f7074 https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d09945b9-17b1-2d10-e383-ae156a5e6e8f For more information, visit the Supplier Relationship Management homepage Important OSS Notes Note 390380 - Composite SAP note- HR ALE distribution in EBP CRM Note 312090 - Integration HR - EBP-CRM Note 363187 - HR-CA-ALE - Initial distribution w. HRMD_A-HRMD_ABA Note 934372 - SRM-CRM- HR integration for business partner - new features Note 918485 - HRALX- Time dependency Note 1389782 - HRALX - BP_CENTRALPERSON_GET Note 918510- Time dependency of the business partner as of SRM_SERVER 550

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

SRM Org Structure Part 3 Tools, Tables and Reports

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.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11