SAP ABAP IMG Activity SIMG_CFMENUOLMLOMMP (Define Decentralized Link to R/2)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       LVS (Package) Application development Warehouse Management (WM)
IMG Activity
ID SIMG_CFMENUOLMLOMMP Define Decentralized Link to R/2  
Transaction Code S_ALR_87002585   IMG Activity: SIMG_CFMENUOLMLOMMP 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLMLOMMP   Define decentralized link to R/2 
Customizing Activity SIMG_CFMENUOLMLOMMP   Define decentralized link to R/2 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLMLOMMP    

Various definitions must be entered both in the R/2 and ERP systems to facilitate communication between a central R/2 System and a decentralized Warehouse Management system (R/3).

In this step you define the necessary ECC parameters.

Requirements

If the R/2 and ERP Systems are intended to communicate with each other, you must install the standard interface CPI-C.

Activities

  1. Install the necessary CPI-C basis and application components.
  2. Activate the warehouse number (field Decentralized warehouse) that is to be installed as a decentralized Warehouse Management system.
  3. Number range interval for allocating communication documents.

    Here you cannot define a new number interval. Number range 01 is standard. You can only reset the number range.

    Check the number range (number range object "Dec. communication") for the communication documents.

  4. With interim storage postings in the Decentralized Warehouse Management system, you can have the system determine the interim storage bin to which the posting is to be made as follows:
    1. The interim storage bin is always defined as a dynamic storage bin, that is, the same as the R/2 document number.
    2. The interim storage bin is determined just as in the integrated Warehouse Management system by movement type definition.
      The default is to use the first type (a) of interim storage type search. The other type (b) must be activated at the warehouse number level.
  5. For certain business transactions (for example, create material masters, postings that change stocks) in the Materials Mangement system (linking R/2 -> ECC), mails can be sent.

    The following are the individual business transactions (record types) that can be assigned:

    • WM01 GR/GI postings
    • WM02 Posting changes
    • WM03 Delivery notes (R/2-Rel. 4.3)
    • WM04 Delivery note appendices (R/2-Rel. 4.3)
    • WM05 Material master maintenance
    • **** all business transactions

      Assign the different record types to the individuals responsible.

  6. Within the R/2 -> ECC connection, it is possible to activate different logging functions.
    The system first searches for an exact table entry match (warehouse number). If no suitable entry is found, the system then searches for warehouse number "***".

    The following parameters are available for you to use:

    • Logging of the communication records transferred from R/2
    • Mail to the person responsible after creating a material master
    • Logging of CPI-C or logical errors
    • Parameters for ouput control (for example, printing time, printer assignment)

      These logging functions may make an error analysis easier during project implementation.
      You do not have to activate all functions in production.

      Activate the necessary logging functions.

All the following activities must be carried out for the ECC -> R/2 link:

  1. Various business transactions (for example, goods receipt from production) generate communication documents for the R/2 System. These communication documents are stored in a queue. Using this technique, data can be transferred between the ERP System and R/2 at different times.

    Define the necessary queues and activate them.

  2. The Warehouse Management system communicates via communication numbers with the R/2 System. Define the communication numbers and assign them to the queue names.
  3. During communication from the ERP System to R/2, communication control is affected by a transaction key. Assign the transaction keys to the WM movement types that are to initiate a posting in the R/2 system.
  4. In the Warehouse Management system, it is not always appropriate to notify the Inventory Mangement system of each individual posting immediately (for example, difference postings, GR from production). These business transactions can be sent to the R/2 System cumulatively.
    Define the storage types and movement types which should trigger a message to the Inventory Management system.

Further notes

The SAP Systems communicate with each other via the standard interface CPI-C. For information as to which host computer types this interface is suitable for and how the communication works from a technical point of view, refer to the SAP information brochures.

In the SAP documentation, refer to the chapter on "Decentralized Warehouse Management".

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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_CFMENUOLMLOMMP 0 HLA0001543 R/2-R/3 Link 
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
IMGDUMMY D - Dummy object OMMP 400 C MM-WM decentralized processing 
VKDV T - Individual transaction object OMMP 9999999999 C MM-WM decentralized processing 
V_T3000 V - View OMMP 0000000004 Decentralized Warehouse Management 
V_T321D V - View OMMP 9999999999 C MM-WM Decentralized processing 
V_T321K V - View OMMP 9999999999 C MM-WM Decentralized processing 
V_T323M V - View OMMP 9999999999 C MM-WM Decentralized processing 
V_T323P V - View OMMP 9999999999 C MM-WM Decentralized processing 
V_T340DF V - View OMMP 9999999999 C MM-WM Decentralized processing 
V_TQCOM V - View OMMP 01 C MM-WM decentralized processing 
History
Last changed by/on SAP  19981222 
SAP Release Created in