Every Business has its own requirement. With the feature of custom fields we can full fill it to some extent.
Adding Non-HR User-Defined Fields in Access Control 2010
This paper covers adding customer-specific fields for Request objects (related to compliant user provisioning).
Supported customer-specific fields
Staring release 2010 there are more flexibility in defining the customer-specific fields. You can define them as Single value for access controls.
Each category of customer specific fields is stored differently within the databases structures. Single value fields uses customer includes in mater tables of the entities (see chapter “Use Data Elements to Enhance the Data Storage for single value fields” for details).
Example
This example describes how to add a customer-defined field to a request object. These procedures apply to other objects also. The example shows how to add one field to the request object.
Overview of Tasks
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.
To perform these tasks:
You must have the S_DEVELOP authorization profile or the equivalent
You must test all changes in the development system first 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.
Modifying the ABAP Dictionary
As an example, these instructions create the data element for a calendar date.
Creating an extra data element (and not reusing the existing one) is important because the User Interface and reporting take the captions from the definition of the data element.
1. Input transaction SE11 (ABAP Dictionary).
2. Input the name of the Domain. For the example, use ZREQSTAT. Create a logical prefix for your naming convention, starting with Z or Y to indicate that it is a customer-specific namespace.
3. Choose Create and select the data element ZREQSTAT. After you activate the object, you must put the data element into your customer-specific package.
4. To create a new data element, you have to maintain the description and the domain:
Note: Write the description according to your project standards. For the example, the domain is the standard one for the calendar date.
5. Select the Field Labels tab and maintain the texts there based on what you want to see on your Process Control screens and reports.
Note: If multiple languages are needed, input transaction SE63 and enter the text in the languages needed.
6. Save, check and activate your new data element.
Creating a field with a fixed list of possible values
1. Input transaction SE11
2. Input the name of the Data type. For the example, use ZREQSTAT. Create a logical prefix for your naming convention, starting with Z or Y to indicate it is a customer-specific name-space.
3. Choose Create.
4. Enter the Short Description and the Data Type (CHAR).
5. Enter the length of the field. For the example, use 1 in order to store the fixed values associated with a single character:
6. Select the Value Range tab and enter the set of the fixed values and their association with descriptive texts.
Note: If multiple languages needed, input transaction SE63 and enter the text in the languages needed.
7. Save, check and activate the new domain.
Note: Now the domain can be used to create the data element. The procedure is the same as with the data element above: transaction SE11, the data type ZREQSTAT, choose Create, provide the description, as the domain use your brand new domain ZREQSTAT and provide the field labels. Save, check, activate.
Use Data Elements to Enhance the Data Storage for single value fields
Here is the list of all the tables/objects that can be enhanced using similar steps:
Object Name Database Table Customer Include
Request Attributes GRACREQ CI_GRAC_REQ_ATTR
1. Using transaction SE11, and specify the table name. For the example, use GRACREQ.
2. Choose Display.
3. Search through the list of components of the table GRACREQ. At the bottom, locate the customer include. This is where you can add your own fields.
This example focuses on providing one status field explicitly and uses the structure CI_GRAC_REQ_ATTR. This structure will be used within the table, but it does not yet exist. During the next steps, you will create the structure.
1. Select the structure CI_GRAC_REQ_ATTR. A dialog box tells you that the structure does not exist and asks whether you want to create it.
2. Confirm that you want to create it.
3. Provide the Description of the structure and include one field: ZZ_REQSTAT type Z_REQSTAT
Note:
a. The field names are prefixed with ZZ (or YY) to ensure that there is no overlap with the delivered SAP fieldnames.
b. Keep the names unique. All customer fields are used in the global reporting structure. If the same field is used twice, it causes problems.
c. Verify the field name is no longer than 16 characters. Otherwise you cannot activate your customer include structure.
Note: For the structure CI_GRAC_REQ_ATTR you must enter information about the Enhancement Category. Because this Customer Include Structure is already an Enhancement Structure, it cannot be further enhanced. Follow the menu path Extras -> Enhancement Category. In the window that appears, indicate that the structure Cannot Be Enhanced and choose Copy.
4. Save, check and activate the structure. Several dependent structures and database (DB) tables are reactivated too, as they include the structure
CI_GRAC_REQ_ATTR. You require powerful authorization to be able to activate the DB tables (for example, the authorization object is S_DEVELOP, with fields OBJTYPE=TABL and ACTVT=07). After the activation, you receive a warning which informs you about the dependent tables, which are implicitly activated with CI_GRAC_REQ_ATTR.
All the dictionary work is done. The case objects for the issues are enhanced with this additional field.
Regards,
Nidhi mahajan