Hierarchy

⤷

⤷

IMG Activity
ID | GRPC_USERDEFHROV | Adding HR User-Defined Fields |
Transaction Code | S_GR4_71000113 | (empty) |
Created on | 20090212 | |
Customizing Attributes | GRPC_USERDEFHROV | Adding HR User-Defined Fields |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | GRPC_USERDEFHROV |
Use
In this organizational activity, you can find information about the steps needed to add HR user-defined fields. Master data storage for most objects in Process Control and Risk Management uses HR organizational data tables.
You can specify the user-defined fields as the following:
- Single value
- Multiple value
- Regulation specific value
- Multiple regulation specific value
Each category of user-defined fields is stored differently within the HR databases structures, as follows:
- Single value uses infotypes with time constraint 2.
- Multiple value uses infotypes with time constraint 3. In this case the infotype can contain only single field.
- For regulation specific values we use a subtype in addition to the regulation.
The example provided in this activity describes how you can enhance a control with user-defined fields. Although the example uses the object Control, the principles are similar for all Process Control and Risk Management objects stored in the HR Organizational data tables.
In the example, the control documentation is enhanced using a dropdown list, which is called COSO Relevance, and includes the date when the field was set. An additional comment field is also added to allow users to enter information about the attribute.
Requirements
You must have:
- Authorization for the profile S_DEVELOP or equivalent
- Tested all changes in the development system before transporting them to the test and production systems.
Note: The changes do not cause any conflicts with upgrades since they are not considered as modifications of the delivered SAP standard.
Standard settings
Activities
To add HR user-defined fields:
- Perform the administrative preparatory tasks:. For more information, see the Coordinating Number Ranges and Authorizations section below.
- Perform the tasks in the Customizing activity Create Data Elements in the ABAP Dictionary.
- Perform the tasks in the Customizing activity Generate the Infotypes (data storage for new fields).
- Perform the tasks in the Customizing activity Generate Subtypes (data storage for long text fields), if required.
- Perform the tasks in the Customizing activity Add New Fields to SAPGUI Transaction for Data Maintenance.
- Perform the tasks in the Customizing activity Check User-Defined Fields.
- Perform the tasks in the Customizing activity Maintain New Fields in the Web UI. Custom fields are displayed on the UI automatically.
- Perform the tasks in the Customizing activity Include HR Fields in Online Reporting. Update the reporting infrastructure as required to see the new fields in reporting.
- Perform the tasks in the Customizing activity Allow Custom Fields to be Uploaded
Coordinating Number Ranges and Authorizations
The HR Organizational data is stored in infotypes, which are numbered using 4-digit numbers. Numbers up to 8999 are reserved for standard delivery. For example, Process Control's infotypes belong to the interval 5300-5339. You can begin customer-defined infotypes with 9, followed by 3 digits, specifying the infotype itself.
Before you define the infotype, you must find out infotype numbers that can be used in your project. You can then reserve them for Process Control or Risk Management-specific use. Remember that Process Control need not be the only application that uses HR Organizational data tables; it is likely that other projects within your organization also use infotype numbers. In this example, the infotype number 9101 is used.
For example, an ABAP developer needs to have basic skills with respect to ABAP and DDIC (ABAP dictionary). To ensure this, you need to:
- Prepare the package where the development must be located according to the project standards of the organization.
- Prepare the transport request where the development must be stored.
- Authorize a user to do the development work (by granting S_DEVELOP authorization profile or equivalent).
Example
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | GRPC_USERDEFHROV | 0 | GR11000001 | Process Controls |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20100901 |
SAP Release Created in | 300 |