Ansicht
Dokumentation

GRPC_NUMRAN_AUTHORIZ - Administrative Preparation Work: Number Ranges and Authorizations

Vendor Master (General Section) CPI1466 during Backup
This documentation is copyright by SAP AG.

Note: Refer to the SAP Note 1169555 User-Defined Fields - for the most current instructions.

There are slightly different procedures for adding user-defined fields to the HR Org Data tables and for Non-HR.

Adding User-Defined Fields for HR Organizational Data Tables

Master data storage for most objects in Process Control uses HR Organizational data tables. The following example describes how to enhance a control with user-specific fields. Although this example uses the object control, the principles are similar for all Process Control objects which are stored in HR Organizational data tables.

In this example, the control documentation is enhanced with a drop-down list box named COSO Relevance, with the date when this field was set. An additional comment field will also be added for users to enter further information regarding the attribute.

Administrative preparation work: number ranges and authorizations
Creation of data elements in the ABAP Dictionary
Infotype generation (data storage for new fields)
Addition of the new fields to the power user viewing transactions in the SAP GUI
Display/edit of new fields in the WEB UI. Custom fields are displayed on the UI automatically. There is an optional BAdI implementation to change the look of the fields or to default a value etc.
Update of the reporting infrastructure to see the new fields in reporting
Preparation of the structure for the upload possibility

To perform these tasks:

You must have the S_DEVELOP authorization profile or the equivalent.

You must test all changes in the development system before transporting them to the test and production systems.

Note: The changes do not cause conflicts with upgrades since they are not considered as modifications of the delivered SAP standard.

The HR Organizational data is stored in infotypes. Infotypes are numbered with 4-digit numbers, with the numbers up to 8999 reserved for standard delivery. For example, Process Control’s infotypes belong to the interval 5300-5339. Customer-defined infotypes should begin with 9, followed by 3 digits, specifying the infotype itself.

Before you begin, you must understand which infotype numbers can be used in your project. Reserve them for Process Control-specific use. Process Control may not be the only application using HR Organizational data tables, and it is likely that other projects within your organization are using some infotype numbers too. For this example, the infotype number 9101 is used.

An ABAP developer needs to:

Have basic skills with respect to ABAP and DDIC (ABAP dictionary)

Prepare the package where the development will be located according to the project standards of the organization

Prepare the transport request where the development will be stored

Authorize a user to do the development work (grant S_DEVELOP authorization profile or the equivalent)

Adding User-Defined Fields for Non-HR Objects

These steps cover adding user-specific fields for Case objects (related to assessments, test logs, issues, and remediation plans) as well as adding user-specific fields for other non-HR objects (Questions, Surveys, Rules, etc.).

This example describes how to add a user-defined field to a case object. These procedures apply to other objects also. The example shows how to add two fields to the case object: one field contains the calendar date; the other contains a value chosen from a fixed set of options.

1. Creating data elements and storage for new fields in the ABAP dictionary

2. Displaying/editing new fields in the Web UI. Custom fields are displayed on the UI automatically. There is an optional BAdI implementation to change the look of the fields or to default a value etc.

3. Updating the reporting infrastructure to see the new fields in reporting