SAP ABAP IMG Activity _RMPS_SRMDMWB (Edit Attributes for Content Model)
Hierarchy
☛ SAP_ABA (Software Component) Cross-Application Component
   ⤷ CA-GTF-RCM (Application Component) Records and Case Management
     ⤷ RMPS_CUSTOMIZING (Package) Customizing Records Management for Public Sector
IMG Activity
ID _RMPS_SRMDMWB Edit Attributes for Content Model  
Transaction Code S_KRM_01000002   (empty) 
Created on 20020910    
Customizing Attributes _RMPS_SRMDMWB   Edit Attributes for Content Model 
Customizing Activity SRMDMWB   Maintain Attributes for a Content Model 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RMPS_ATTREDITDMWB    

Use

The new content model you have created inherits a fixed set of attributes from one of the SAP content models. In this IMG activity you can change the attributes of your content model by:

  • adding new attributes
  • changing attributes
  • hiding SAP attributes that are not required
  • deleting attributes

Requirements

You have already created a content model in the document area SRM. Records Management provides a wizard to do this. The wizard is in the IMG activity Create Content Model (transaction code SRMCMCREATE).

Standard settings

The content model delivered by SAP has a fixed set of attributes.

Activities

Create a New Attribute

Step 1: Create the attribute

  1. Expand the document area SRM.
  2. Expand the node IO Attributes.
  3. Open the context menu on the node IO attributes and choose Create.

    The new attribute will appear in the list of attributes in alphabetical order.

  4. Double-click on the new attribute.

    The detail display of the attribute appears. The attribute itself has its own attributes to which you can assign values. The attributes have the following meanings:

    • FIELD_NAME: The name of a field of the table/structure that you entered under TABLE_NAME (see below).
      • In this entry you can assign the attribute a type. The typing enables all the services of the data element to be used in the interface. (For example, input help, value checking, conversion, etc.) If you do not enter a value, the attribute will be assigned type 64.
    • TABLE_NAME: The name of a table or structure.
      • This entry is only useful in conjunction with an entry in the attribute FIELD_NAME (see above).
    • The attributes CLIENT_TRANSFERT_F4, MODEL_EXTENSION and PROPERTY_CHECK are not relevant.

      Note: The pushbutton DDIC takes you directly to the data element identified by TABLE_NAME and FIELD_NAME.

  5. Activate the new attribute.

Step 2: Assign the attribute to a content model

  1. Expand the document area SRM.
  2. Expand the node "PHIO Classes" or "LOIO Classes", depending on whether you want to maintain PHIO attributes or LOIO attributes. (PHIO attributes refer to individual versions of the document. LOIO attributes refer to the whole document.)
  3. Expand the template class for the generic service provider SRM_GENERIC_(PH)_V.

    You will see the classes of the content models supplied by SAP (template classes). You can find more information on the SAP content models in the SAP Library under SAP NetWeaver Components -> SAP Records Management -> Customizing -> Standard Service Providers Supplied -> Generic Service Provider -> -> Connection Parameter DOCUMENT_CLASS -> Standard Content Model for Records Management.

  4. Expand one of the SAP template classes.

    You will see the customer template you created.

  5. Expand the customer template class from which the content model whose attributes you want to define inherits.

    You will seee all the content models inherited from this customer template class. There is a template class for each content model. You can only change the attributes of this template class, and not the attributes of the content model itself.

  6. Double-click on the last template class of your content model.

    The detail display opens on the right screen.

  7. Switch to change mode and open the tab page Instance Attributes.

    You will see all the attributes that exist for this content model. The attributes display in blue are inherited from the template class above it.

  8. Select the plus sign Insert Line and enter the technical name of an attribute from the list of IO attributes.
  9. Determine the properties of the attribute. You can enter the following details for the attribute:
    • From LOIO: For a better overview you can enter LOIO attributes in the list of PHIO attributes. Use this flag to do this.
    • Dynamic: Not relevant
    • Mandatory: The user must enter a value.
    • Unique: The attribute can only be assigned one value. Use the pushbutton More to enter further details:
    • Maintenance possible: The user can enter and change attribute values.
    • Hidden: The attribute is not displayed on the screen.
    • Context-relevant: Not relevant
    • Index-relevant: If you set this indicator, you can use the value of the attribute for full text searches. This is usually quicker than the normal attribute search. However, the full text search is not case sensitive, whereas the attribute search is.
    • Classification-relevant: Not relevant
    • Transfer to client: Not relevant

      You can define the following additional attribute characteristics:

  1. SRM_PROPGROUP. You can choose any name you want as the value. All the attributes you assign this value to are put in the same group. This group of attributes can be used when you assign authorizations. For more information see the SAP Library under SAP Web Application Server -> Basis Services -> Records Management -> Role Maintenance -> Authorization Concept of the Generic Service Provider.
  2. SRM_CHANGE_ON_SELECT: If the attribute value is allowed to be entered only using F4 help, assign the value X.
  3. SRM_CHANGE_ONCE: If the attribute value is allowed to be entered once only in the maintenance dialog, assign the value X.
  4. SRM_INHERIT_PRE_VERSION: Only the values of attributes that are modifiable are copied to the new physical version, after the changes have been saved. If you want to also keep the values of specific attributes that are not modifiable in the new physical version, you can enter the value X in the property SRM_INHERIT_PRE_VERSION for these attributes.
  5. RMPS_INHERITED:
    X: The value of the superordinate object is inherited during creation and updated if any changes are made (subsequent inheritance)
    C: The value of the superordinate object is inherited once during creation
    D: The value of the superordinate object is only displayed
    'Blank': If you do not want to support the inheritance of attribute value, do not enter a value.
  6. RMPS_PASS_TO_SUBORD:
    X: The value is passed on to all subordinate objects
    'Blank': If you do not want to support the passing on of attribute values, do not enter a value.
  7. RMPS_LONG_CHAR_VALUE:
    This enables you to save short texts with more than 64 characters - the maximum length is 255 characters. Create a DMWB attribute with DDIC reference in a structure field with length > 64 and max. 255 characters. Assign the DMWB attribute to a content model and do not set the characteristic eindeutig. In other words, you define the attribute in the content model as multi-value.

    If you want to use a content model with a long attribute as a template for further content models, no attribute can have a DDIC reference to a field longer than 64 characters. In this case you must use the following alternative variant:
    Create a DMWB attribute with DDIC reference in a structure field with length = 64 (for example, by using domain SDOK_PROPV ). Assign the DMWB attribute to a content model as a multi-value attribute. Create the desired field for the DDIC reference (with length > 64 and max. 255 characters) as follows as the value for the characteristic RMPS_LONG_CHAR_VALUE: <Structure name>- <Field name>. Then this DDIC reference will be used instead of the field with 64 characters.
  8. RMPS_MAPPING:
    This enables a cross-service provider search using the locator. The objects RECORD, DOCUMENT, CASE, POST, RMPS_PRO_PART, RMPS_PRO_CLASS are supported. Define the generic search under <Object Type>; <Attribute ID>.

    You can use the pushbutton Standard to make the following additional entries: (Double click to copy the attribute to the table below where you can enter a value)

  • Grouping: Not relevant
  • Property01: Not relevant
  • Select_Option: Not relevant
  • Sorting: Assign a number as a value. This number specifies the position of the attribute in the attribute list. If you do not assign a number, it is added to the bottom of the list.

  1. Choose pushbutton Assign Table. Here you can influence the performance when using the attribute for searches.

    With content models there are two ways of saving attributes. You can determine which table the attribute is saved in:

    • In the header table of the content model
      • Attributes saved here can be accessed quickly. There are only ten places reserved for attributes and the attributes must not exceed a specified length. (see below).
    • In the vertical table of the content model
      • Attributes saved here take longer to access. But here you can save any number you want and they have no length restrictions.

      You will see a table and the first column lists all the attributes. In the following columns you can set indicators. The columns have the foll

Business Attributes
ASAP Roadmap ID 899   not to be assigned 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
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
SRMDMWB D - Dummy object DMWB  
History
Last changed by/on SAP  20041007 
SAP Release Created in 110_620