Tips for Customizing Transaction Code PPOME
- by Dilek Adak, SAP HCM Applications Manager, Vektora Turkey
- February 18, 2016
Learn all about the customizing options and outcomes of the Structural Graphics tool. All the customizing steps are created in transaction code PPOME. Follow these step-by-step guidelines to get the most from customizing transaction code PPOME.
Reading this article, you will learn how to:
- Make use of user parameters for effective Organizational Management (OM) customization
- Create infotypes, relationships, and object types from scratch
- Present information from an infotype in an organizational schema
- Integrate object types in all parts of transaction code PPOME
- Leverage the hierarchy framework for integration purposes
Structural Graphics is an SAP ERP HCM Organizational Management application tool that lets users display and edit structures and objects in an organizational plan. This tool is particularly advantageous when it comes to customizing the interface according to a company’s needs. SAP offers many options to customize the functionality and appearance of this tool.
In my role as an SAP consultant, I have come across many cases in which Organizational Management (OM) requirements were solved by ABAP programming. When I delved deeper into OM customization interfaces, however, I realized that SAP offers a great framework for customizing the interface of transaction code PPOME that leaves little need for programming.
The steps for customization are not as complex as they are commonly assumed to be. In this article, I show how to use these customization details to transform regular users and super users into OM superheroes. This article consolidates all the OM customization steps in one document and also gives an overview of use cases with some real-world examples.
Transaction code PPOME offers many customization features that provide a flexible environment for users and super users to meet end users’ needs. In the following sections, I discuss the details of these customizing options and show how to do them.
Before carrying out any customization steps, let’s first learn about the technical names of the column framework, hierarchical framework scenario, object manager scenario, and tab pages.
These technical names are important since all the implementation steps in the following sections are carried out using these technical names. To make the technical names visible for these items in transaction code PPOME, the set/get parameters OM_ARRAYTYPE_DISPLAY, OM_FRAM_SCEN_DISPLAY, OM_OBJM_SCEN_DISPLAY, and OM_TABTYPE_DISPLAY should be set, respectively, via transaction code SU3 for that specific user.
Would you like to see this full item?