SAP ABAP IMG Activity SIMG_CFMENUOM00OJIN3 (Define Message Type for Summarized JIT Call)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   PP-MRP-BD (Application Component) Master Data
     MD0C (Package) Customizing R/3 Material Requirements Planning
IMG Activity
ID SIMG_CFMENUOM00OJIN3 Define Message Type for Summarized JIT Call  
Transaction Code S_ALR_87005481   IMG Activity: SIMG_CFMENUOM00OJIN3 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOM00OJIN3   Define Message Type for Summarized JIT Call 
Customizing Activity SIMG_CFMENUOM00OJIN3   Define Message Type for Summarized JIT Call 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOM00OJIN3    

In this step, you define the message types for summarized JIT calls.

Message types represent various message contents, such as EDI and forms for printing in the summarized JIT call.

To define a message type, you must make the following entries:

  • Message type (condition type)

    Alphanumerical key of up to four figures, which uniquely identifies the message type.

  • Description

    Text describing the message type

  • Access sequence

    Key of access sequence

  • Detailed data (only the most important are explained):
    • Multiple transmission
    • Indicator used to define whether a message can be dispatched several times to the same partner. If you flag the indicator, enter the program and the FORM routine, with which the change message is created, under the heading "Change messages". In the standard system, these are the program FM06AEND and the FORM routine CHANGE_FLAG. You must also flag the indicator "New message determination", in the message schema for the query.
    • Transmission medium
    • One-figure, numerical key, which defines the method of message processing (such as printout, transmission per fax or mail).
    • Time-spot
    • One-figure, numerical key, which defines the time at which message processing is carried out (for example, immediately a document is saved,or in the next selection run).
    • Partner role
    • Partner role to define the recipient
    • Access to conditions
    • Indicator, which defines that the message proposal for a message should take place via the condition technique.

Note

The values you enter as detailed data for transmission medium, timespot and partner role are copied automatically to the message type as default values when you create the message record.

Standard settings

Recommendation

To create a new message type, copy a similar, existing one, and make the necessary changes.

If you define your own message types, the key should begin with the letter Y or Z , since the system is shipped as standard with these namespaces kept free.

Activities

Examine the extent to which you can use, or must make changes to, the message types contained in the system as standard.

Define your message types for the summarized JIT call.

Assign your message types to the schema.

Further notes

Business Attributes
ASAP Roadmap ID 259   Establish Forms and Messages 
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 SIMG_CFMENUOM00OJIN3 0 HLA0006762 KANBAN Control 
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
VN_T685B C - View cluster OJIN3 01 WFMC: Output Types 
History
Last changed by/on SAP  19981222 
SAP Release Created in