SRM Org Structure Part 2 Tools, Tables and Reports

Transcription

1 SRM Org Structure Part 2 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. This document describes the Tools Tables and Reports available in SRM which helps in creation, maintenance and enhancements of SRM Organizational Structure. 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 AG 1

2 Table of Contents Tools... 3 TCODE USERS_GEN... 3 Tools - Consistency Check Report... 3 Tools Checking User s Consistency in Org Structure... 5 Maintaining Attribute Characteristics... 6 Planning in Org Structure... 6 Organization Structure Extract Reports... 7 Tables updated with Org Structure Data... 7 Other Content... 9 Disclaimer and Liability Notice SAP AG 2

3 Tools TCODE USERS_GEN USERS_GEN is used to create SRM users using multiple options like upload from a file, Importing users from other systems via RFC, creation of SRM users from existing SU01 Users, and Importing users from an LDAP Directory. User Accounts (SU01 ids) can also be assigned to Employees (CPs) using USERS_GEN. This transaction can also be used to generate multiple Users and Employees Other Uses of USERS_GEN Assigning/ Un-Assigning Central Persons to SU01 ids. This is done by using option Assign User Accounts to Employees. This is possible only when Org structure is not replicated from HR System. Checking consistency of User and its related objects in Org Structure. Creation of Users in Org Structure using Upload from File:- Users can be created using an upload from an external File Users can be created from other Systems using an RFC call Users can be created using the SU01 Records in the system LDAP directory can also be used to create users in SRM System. Tools - Consistency Check Report TCODE - BBP_BP_OM_INTEGRATE (Report BBP_CHECK_CONSISTENCY)- This report is one of the most powerful tool to check the consistency of objects in the org structure. At the same time this report offers the functionality of removing the inconsistencies in some cases. It is recommended to schedule this report in background at least once a week to check the consistency of all objects under the topmost organizational unit in SRM Org structure. This can be done by entering the object id of the respective org unit and selecting the Include All Object Types button SAP AG 3

4 This transaction gives us a variety of options to check the consistency of a number of org structure objects. It is also possible to check the consistency of all or similar objects under any org unit by option Branch from Organizational Unit There are multiple options which can be used to check the consistency of Org Structure Objects as shown in screen. For checking consistency of Central Persons, enter the value of Central person, check indicator Run Attribute Check and Execute the report. For checking consistency of Positions, enter the value of Positions, check indicator Run Attribute Check and Execute the report. For checking consistency of Business partner with Employee Role, enter the value of Business Partner, check indicator Run Attribute Check and Execute the report. For checking consistency of User, enter the value of User, check indicator Run Attribute Check and Execute the report. For checking consistency of Organization Unit, enter the value of Org Unit object id, check indicator Run Attribute Check and Execute the report. For checking consistency of Branch from Organizational Units, enter the value of Org Unit Object id, select the appropriate objects to be checked, check indicator Run Attribute Check and Execute the report SAP AG 4

5 Same report is also called from Check User and Employee data in USERS_GEN transaction. Tools Checking User s Consistency in Org Structure CHECK tab in SRM Org structure (TCODE PPOMA_BBP or PPOCA_BBP) can also be used to check the consistency of a User and the position tied to this user in the org structure SAP AG 5

6 Maintaining Attribute Characteristics All SRM Attributes are stored in table T77OMATTR. In order to change the behavior of an attribute or create a new attribute, this table need to be maintained using SM30. Planning in Org Structure Organizational Management allows us to depict our Company s Structure in past, at present and in future using Plan Version, Validity Periods and Plan Status. Plan versions allow you to manage several organizational plans in the system at the same time. Different plan versions can be used to experiment with different scenarios, for simulations and for comparison purposes. Only one of these plan versions represents the valid organizational plan, and is flagged as the active or integrated plan version Plan versions exist independently of each other This facility enables you to prepare for future staff requisitions or changes and, thereby, respond accordingly. Plan versions allow you to depict alternative plans in the system, however only one plan can be integrated at a time. Plan versions exist independently of each other. They can be created as a copy of the original plan in statements using report RHCOPL00 Copy Plan Version Report RHCOPLPT Reconcile Plan Version supports you when transferring data from an inactive plan version to the active and integrated plan version. Nevertheless, this report is not able to update personal data in info type This can lead to inconsistencies in the integration between Personnel Administration and Personnel Planning (SAP Note ). Note: The plan version.: must not be used or deleted because it is used for transporting data to other clients or systems 2010 SAP AG 6

7 Organization Structure Extract Reports Sometimes it is required to take the dump of whole organization structure for analysis purposes. Transaction RE_RHXSTR00 - RE_RHXSTR06 can be used to download the organization structure data for various combinations like Organizational Hierarchy only, Organizations and Positions, Persons and Positions etc Tables updated with Org Structure Data Table Description HRP1222 Infotype 1222: General attribute maintenance HRV1222B View of Attributes HRV5502A SRM Location HRP1000 Objects details_link to Code HRP1001 Relationships to other objects HRT1222 Table Section Infotype 1222: General Attribute Maintenance HRV5500A SRM: Selection Help for SRM Function 2010 SAP AG 7

8 HRV5500OT SRM Function (OTJID) HRV5501A SRM: Selection Help for Product Responsibilities HRV5501OT SRM Product Responsibility (OTJID) HRV5502A SRM Location HRV5502OT SRM Location (OTJID) T77OMATTR Attributes Table BBP_ATTR_ACCESS Attribute Access Mode BBP_ATTR_DFT Default Values of Basic Attributes BBP_ATTR_VALUE_T Text for SRM Attribute Values 2010 SAP AG 8

9 Other Content For more information, visit the Supplier Relationship Management homepage 2010 SAP AG 9

10 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 AG 10