SAP ABAP IMG Activity SRM_ATTR_DEF_CU (Register/Change Tables/Stuctures for Default Attribute Repository)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-SRV-RM (Application Component) SAP Records Management
     SRM_PROPERTY (Package) Generic Property Handling
IMG Activity
ID SRM_ATTR_DEF_CU Register/Change Tables/Stuctures for Default Attribute Repository  
Transaction Code S_BCE_68002209   (empty) 
Created on 20041206    
Customizing Attributes SRM_ATTR_DEF_CU   Register/Change Tables/Stuctures for Default Attribute Repository 
Customizing Activity SRM_ATTR_DEF_CU   Register/Change Tables/Stuctures for Default Attribute Repository 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SRM_ATTR_DEF_CU    

Use

When using the standard attribute repository, you can use this Customizing activity to register database tables that are used for storing attribute values. You can also register Data Dictionary structures that are used to describe the attributes in an attribute model.

Four types of attribute can be used with the attribute repository:

  • Single-value, language-independent attributes (abbreviated as LIS)
  • Single-value, language-dependent attributes (abbreviated as LDS)
  • Multi-value, language-independent attributes (abbreviated as LIM)
  • Multi-value, language-dependent attributes (abbreviated as LDM)

Attributes that are to be assigned together to an object, such as a document, are stored together in an attribute set. An attribute set is identified by the SAP client and a unique attribute set ID. An attribute set can be used over several database tables. Information about which tables and structures are relevant for storage in the repository is presented in an attribute model. For this purpose, the following information is registered:

  • Name of the database table in which the LIS attributes and the administration data are stored. The table must have the following structure
    • Key fields:
    • MANDT    Data element MANDT
      REC_ID    Data element SRMPROPRECID
    • Include structure for the administration data SRM_PROP_PERS_ADMIN
    • Include structure for the LIS attributes
  • Optional: Name of the database table in which the LIS attributes are stored. The table must have the following structure
    • Key fields:
    • MANDT    Data element MANDT
      REC_ID    Data element SRMPROPRECID
      LANGU     Data element LANGU
    • Include structure for the LDS attributes
  • Optional: Name of the database tables in which the LIM attributes are stored. The tables must each have the following structure:
    • Key fields:
    • MANDT    Data element MANDT
      REC_ID    Data element SRMPROPRECID
      SEQNO    Data element INT4
    • Include structure for the LIM attributes
  • Optional: Name of the database tables in which the LIM attributes are stored. The tables must each have the following structure:
    • Key fields:
    • MANDT    Data element MANDT
      REC_ID    Data element SRMPROPRECID
      SEQNO    Data element INT4
      LANGU     Data element LANGU
    • Include structure for the LDM attributes

Note: Create a table and a structure for each multi-value attribute that is independent of other attributes. If, on the other hand, the attributes are dependent on one another, put them together in a single table and structure.

Example of independent multi-value attributes: an attribute for "key words" is independent of an attribute for "people involved". For each attribute, create a structure with exactly one field and the associated database table.

Example of dependent multi-value attributes: when storing several addresses, the attributes "Street", "Number", "Postal Code" and "City" belong together. In this case, create a structure and a database table containing all attributes required for this address.

Requirements

You have already created an attribute model. You want to store attributes in the standard attribute repository.

Standard settings

Activities

Register all necessary tables and structures for an attribute model. Create these tables and structures in accordance with the conventions described above.

Example

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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SRM_ATTR_DEF_CU 0 B200000302 SAP Records 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
SRM_ATTR_MDL_CL C - View cluster SM34  
History
Last changed by/on SAP  20050117 
SAP Release Created in 700