SAP ABAP IMG Activity RMPS_PRO_REFGENPROF (Create Generation Profile)
Hierarchy
☛ SAP_ABA (Software Component) Cross-Application Component
   ⤷ CA-GTF-RCM (Application Component) Records and Case Management
     ⤷ RMPS_PRO_CUSTOMIZING (Package) PRO: Customizing
IMG Activity
ID RMPS_PRO_REFGENPROF Create Generation Profile  
Transaction Code S_SRM_25000028   (empty) 
Created on 20040928    
Customizing Attributes RMPS_PRO_REFGENPROF   Create Generation Profile 
Customizing Activity RMPS_PRO_REFGENPROF   Create Generation Profile 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RMPS_PRO_REFGENPROF    

Use

In this IMG activity you can create generation profiles. By using a generation profile you can generate extra attribute values using the folder indicator generator in addition to the unique indicator of an object, for example case indicator (see PSRM Terminology). This means that a predefined syntax can take place.

In an generation profile you must create a extra attribute for each attribute that needs generating by entering the corresponding generation rule. This enures that, for example, when objects are reassigned the changes to the attribute values in the system can take place in accordance with the generation rule.

Requirements

Activities

The definition of a generation profile can be divided into a three-way process:

  1. Create a generation profile and its characteristics:
  2. Assign the attributes of the generated attribute values and the corresponding generation rule to the generation profile:
    • Attribute ID of the attribute value to be generated
    • Attribute ID in which the rule name is saved
    • Attribute ID in which the rule type is saved (optional)
    • Automatic Generation (if possible)
  3. Assign a generation rule to each attribute that can be generated:

Example

The following illustrates the creation of a generation profile:

Task Creation:

The following extra attributes should be generated in an object hierarchy of fileplan classes and cases (TNA: folders):

  1. the whole path name
    2. e.g.: Customer / Company_A / Project_1
  2. name of current hierarchy
    3. e.g.: Project_1

List of attributes required:

  • Attribute ID of generated path name: PATH
  • Attribute ID of generated hierarchy name: LEVEL
  • Attribute ID for name of generation rule : PATH_RULE_NAME

Definition of generation rules required:

Two generation rules of type record number are required in order to generate the fileplan class name. One rule for the highest level ("root" of the object tree) and one for the subordinate fileplan classes.

  • PATH_ROOT_LEVEL - Generation rule A for highest hierarchy level:

Element name    Element type    Comment

LEVEL_NAME    Text entry

  • PATH_SUB_LEVEL - Generation rule B for subordinate cases (TNA: folders):

Element name    Element type    Comment

CONTAINER_ID    Fixed text    is replaced by the name of the

        parent object.

DELIMITER    Fixed text    separator: /

PATH_NAME    Rule link    link to rule PATH_ROOT_LEVEL

You need a generation rule of type Case Indicator to generate folder names.

  • PATH_CASE - Generation rule C for cases (TNA: folders):

Element name    Element type    Comment

RULE    Rule link    Link to rule PATH_SUB_LEVEL

Now the prerequisites for defining the generation profile needed for this example have been fulfilled. A generation profile with the attribute PATH to be created is required for the file class plans and cases (TNA: folders).

Generation profile for fileplan classes:

  1. Create generation profile and characteristics.
    • Descriptive text: Generation profile for fileplan classes
    • Obsolete: < >
  2. Attribute IDs of attribute values that can be generated and assign the corresponding generation rule to the generation profile.
    • Attribute ID of the attribute to be generated: PATH
    • Attribute ID in which the rule name is saved: PATH_RULE_NAME
    • Attribute ID in which the rule type is saved: < > (not necessary)
    • Automatic generation (if necessary): < > (is not possible due to manual text entry)
  3. Assign a generation rule to each attribute that can be generated

    Generation rule A: PATH_ROOT_LEVEL

    • Additional information: RMPS_ROOT (This rule is used when there is no parent object)
    • Rule element ID, whose value is to be extracted: LEVEL_NAME
    • Attribute ID of extracted rule element value: PATH_NAME_LEVEL
    • Attribute ID of extracted rule element value key: < > (a text entry does not contain any key information)

      Generation rule B: PATH_SUB_LEVEL

    • Additional information: < >
    • Rule element ID whose value is to be extracted: LEVEL_NAME
    • Attribute ID of extracted rule element value: PATH_NAME_LEVEL
    • Attribute ID of extracted rule element value key: < > (A text entry does not contain key information)

      Generation rule B: PATH_SUB_LEVEL

    • Additional information: < >
    • Rule element ID whose value is to be extracted: LEVEL_NAME
    • Attribute ID of extracted rule element value: PATH_NAME_LEVEL
    • Attribute ID of extracted rule element value key: < >

Generation profile for cases (TNA: folders):

  1. Create generation profile and characteristics.
    • Descriptive text: Generation profile for cases (TNA: folders)
    • Obsolete: < >
  2. Assign attribute IDs of attribute values that can be generated and generation rules to the generation profile.
    • Attribute ID of the attribute to be generated: PATH
    • Attribute ID in which the rule name is saved: PATH_RULE_NAME
    • Attribute ID in which the rule type is saved: < > (not necessary )
    • Automatic generation (if possible): < > (is not possible due to manual text entry)
  3. Assign a generation rule to an attribute that can be generated.

    Generation rule C: PATH_NAME_CASE

    • Additional information: < >
    • Rule element ID whose value is to be extracted: LEVEL_NAME
    • Attribute ID of extracted rule element value: PATH_NAME_LEVEL
    • Attribute ID of extracted rule element value key: < > (a text entry does not contain key information.)

Standard settings

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
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 RMPS_PRO_REFGENPROF 0 ABB0000001 Records and Case Management 
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
VC_RMPSREFGENPRO C - View cluster SM34  
History
Last changed by/on SAP  20040928 
SAP Release Created in 640