SAP ABAP IMG Activity GRPC_USERDEFHRDE (Create Data Elements in the ABAP Dictionary)
Hierarchy
GRCFND_A (Software Component) GRC Foundation ABAP
   GRC-SPC (Application Component) Process Controls
     GRPC_CUSTOMIZING (Package) Customizing
IMG Activity
ID GRPC_USERDEFHRDE Create Data Elements in the ABAP Dictionary  
Transaction Code S_GR4_71000107   (empty) 
Created on 20090210    
Customizing Attributes GRPC_USERDEFHRDE   Create Data Elements in the ABAP Dictionary 
Customizing Activity GRPC_USERDEFHRDE   Create Data Elements in the ABAP Dictionary 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GRPC_USERDEFHRDE    

Use

In this Customizing activity, you can specify where and how the data for the user-defined fields must be stored in the ABAP dictionary. You create domains and data elements, and then subsequently create a structure that uses these elements.

Note: For the comment and the data in our example, the standard domains can be used. For the dropdown list, you must create a special domain for the domain values .

Requirements

Standard settings

Activities

To create data elements in the ABAP dictionary, you must do the following:

  1. Create the domain
  2. Create the data elements
  3. Arrange the data elements into a structure

Creating the Domain:

  1. Select the Domain field, and enter the domain name, for example, ZPC_COSO_REL.
  2. Choose Create.
  3. Enter the domain description and the data type, for example, - CHAR, length 1.
  4. Select the Value Range tab page, and then enter the domain values:
  5. In the first empty field at the top, enter a value as the default value.
  6. If your organization operates with multiple languages, start transaction SE63 and enter all the languages which your organization is using.
  7. Save, check ,and activate the domain.
    You must store the object into your customer-specific package for transporting.

Creating the Data Elements

You must create specific data elements for each field, because the labels of the user interface elements associated with these fields come directly from the data element definition.

  1. On the ABAP Dictionary: Initial Screen, select the Data Type field , and then enter ZPC_COSO_REL.
  2. Choose Create.
  3. Select Data Element.
  4. Enter the description and domain for each data element, for example, ZPC_COSO_REL.
  5. Select the Field Labels tab page, and enter the text to be used in the UI.
  6. Save, check, and activate the data element.
  7. Repeat the steps for the following data elements:
    • ZPC_COSO_DATE, domain DATS
    • ZPC_COSO_COMMENT, domain TEXT100.

Arranging the Data Elements Into a Structure

  1. On the ABAP Dictionary: Initial Screen, select the Data Type field , and then enter the name as HRI9nnn, for example, HRI9101.
  2. Choose Create.
  3. Select Structure.
  4. Select the Components tab pae, and create the following fields with their respective data elements :
    • ZZCOSO_REL
    • ZZCOSO_DATE
    • ZZCOSO_COMMENT   

      You must include the fields in the customer namespace. The field name can only be 16 characters long.

  5. Save, check, and activate the structure.
  6. Include the short text description (mandatory) and the enhancement category by doing the following:
    1. Select Extras -> Enhancement category.
    2. Sselect Cannot be enhanced, and then choose Copy.

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_USERDEFHRDE 0 GR11000001 Process Controls 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object SE11  
History
Last changed by/on SAP  20100331 
SAP Release Created in 300