Learn how to modify the standard organization and staffing interface to integrate custom built infotypes in detailed views of the transaction PPOSE. This integration means users do not have to resort to another transaction to view most custom Organizational Management/Personnel Development infotype information when they are using PPOSE.
A hierarchy framework scenario offers a range of configuration options such as the format of the right screen area, possible ways of visualizing data in structural form in the overview area, the choice of tab pages displayed for each object type in the detail area, and the definition of analysis periods. The SAP hierarchy framework is a Basis development used for visualizing and modifying hierarchical structures and objects. Scenario is a field stored in an SAP system and can be named with up to eight characters. Scenario OME0 is the standard scenario used in the organization and staffing interface. Other examples of scenarios are PBC, a standard scenario for Personnel Budget Plan Management, and MGEGE, a standard scenario for Compensation Overview.
When custom infotypes are created in the SAP Organizational Management (OM)/Personnel Development (PD) modules, users like to view them through transaction PPOSE (organization and staffing interface). When users are viewing information related to OM/PD using transaction PPOSE, they frequently have to go to a new transaction to view the information that is stored in custom infotypes. This multi-step process is time consuming and does not result in a user-friendly experience. SAP standard configuration does not integrate custom infotypes directly in the organization and staffing interface. However, it is possible to integrate them using a step-by-step approach that includes configuration and development.
By modifying and integrating custom infotypes in the PPOSE view, users do not have to navigate to another transaction to view custom infotype information when they are using transaction PPOSE to view most of the existing OM/PD infotypes. Having information in one view reduces the navigation steps necessary to view the required information, saves time, and helps prevent potential errors from navigating from one screen to another.