Define Decentralized Link to R/2

Various definitions must be entered both in the R/2 and R/3 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 R/3 parameters.

Requirements

If the R/2 and R/3 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:
a) The interim storage bin is always defined as a dynamic storage bin, that is, the same as the R/2 document number.
b) 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 -> R/3), mails can be sent.
The following are the individual business transactions (record types) that can be assigned:
Assign the different record types to the individuals responsible.
6. Within the R/2 -> R/3 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:
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 R/3 -> R/2 link:

7. 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 R/3 and R/2 at different times.
Define the necessary queues and activate them.
8. The Warehouse Management system communicates via communication numbers with the R/2 System. Define the communication numbers and assign them to the queue names.
9. During communication from R/3 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.
10. 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 R/3 documentation, refer to the chapter on "Decentralized Warehouse Management".