SAP ABAP IMG Activity COCB310-13 (Define ABAP Table)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ PP-PI-PMA-MSG (Application Component) Process Message
     ⤷ CMX_PM (Package) Manufacturing Execution: Process Messages
IMG Activity
ID COCB310-13 Define ABAP Table  
Transaction Code S_ALR_87007588   IMG Activity: COCB310-13 
Created on 19981222    
Customizing Attributes COCB310-13   Define ABAP Table 
Customizing Activity COCB310-13   Define ABAP Table 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name COCB310-13    

In this activity, you define the ABAP/4 tables that you want to use as message destinations.

If you use an ABAP/4 table as a message destination, the message data of each message received is written into the table in a separate entry. You can later evaluate the process message data stored in the table. Compared to the process message record, ABAP/4 tables have the following advantages:

  • You can use external tools to access ABAP/ 4 tables.
  • You can sort the message data in the tables according to your needs.
  • By distributing the data of different messages to several tables, you help to improve system performance.

Activities

Define the required ABAP/4 tables.

Notes on Table Maintenance

For general information on maintaining ABAP/4 table, see Application Help. In addition to this, note the following:

  • You can only use transparent tables as message destinations.
  • The table name must be within the name range reserved for customers and partners. The following customer name ranges are permitted:
    • The table name must start with Y or Z.
    • As of Release 4.6C, you can now also reserve your own customer-specific development name ranges apart from those starting with Y and Z.
      • If the table name is within the name range reserved exclusively for your company, you need the namespace licence key to enable the use of object names in your name range.

For more information on namespaces, see the SAP Library under Basis Components -> Change and Transport System -> BC - Namespaces and Naming Conventions.

  • The table must be created in the ABAP/4 Dictionary and active on the database.
  • The table key must contain the following fields:
    • MANDT (client): First key field. The domain must define the same data type and the same field length as the domain MANDT.
    • MSID (message number): Second key field. The domain must define the same data type and the same field length as the domain CO_MSID.
  • The table must contain the field WERK (plant). The domain must define the same data type and the same field length as the domain WERKS.
  • Data type and length of the table field should correspond to the format of the characteristic value transferred to the field. If this is not the case, the value is converted according to the rules valid within ABAP/4. The characteristic formats are processed in the following ways:
    • Characteristic format CHAR, DATE, and TIME like data type C
    • Characteristic format NUM like data type F

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
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 COCB310-13 0 HLA0006278 Process Message 
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
DWBDUMMY D - Dummy object SE11 22 Define ABAP Table 
History
Last changed by/on SAP  20070731 
SAP Release Created in