R/3 -> R/2 Processes - SAP WM

This section describes transactions in the R/3 Warehouse Management component that initiate a communication process in the R/2 System, and shows how this communication process takes place.

Overview of R/3 -> R/2 Processes
Communication from R/3 _ R/2 takes place with the following transactions :

  • Goods movements from Warehouse Management
  • Confirmation of differences (with inventory differences)
  • Transmission of picked quantities for R/2 deliveries

Overview of R/3 -> R/2 Processes

When is a Document Transmitted?
If there is a process from R/3 _ R/2, the data can be transmitted in different ways:

  • Manually
  • Automatically (batch process)
  • Cumulatively

Manually
Here the data to be transmitted is placed into a queue as soon as a transfer order has been processed. The data is then transmitted when the user manually activates the driver.

Automatically
The data transmission can be automated using batch processing. A batch job transmits the communication documents of a queue at regular intervals.

Cumulatively
Direct transmission of individual warehouse transactions means that each transfer order initiates an RM posting. If, for example, finished goods are delivered to production in pallets, a communication record is transmitted to R/2 for each pallet and a goods receipt (GR) document is created.

For this reason, it is often advisable to execute the posting in Inventory Management for an accumulated quantity of material rather than for each transfer order individually.

With this type of data transfer, the WM stock of the posted material is accumulated in the interim storage record (for example, GR area with a dynamic coordinate based on the production order).
The transfer can be manually initiated (via transaction LD11) or it can be planned (using report RLDLVS10) as a regular transfer with a variant to be processed in the background. A communication record is created for each material for the total interim storage quantity. The system transmits this quantity to R/2 and an RM document is generated automatically.

Material-Dependent Data Transmission
The type of transmission can be defined by material. For certain materials, such as slow-moving items, it is often necessary to have the available quantity updated in Inventory Management as soon as possible so that the material can be scheduled for requirements.

Other materials, on the other hand, can be transmitted on a cumulative basis so that the communication process is not overloaded and the number of RM postings is reduced.

Determining the Time of Communication
The time of communication is determined in the following manner:

  • In the assignment table "Movement Type MM-WM R/3 - Host Activity" you set an indicator that determines whether the communication will take place immediately or depending upon each material. See Linking Activity Keys to Movement Types under the topic Sending Communication Documents from R/3 to R/2.
  • If the communication time has been set based on materials, the system checks the warehouse data of the material to determine whether the indicator is set for immediate transmission.

The system places the communication document into the queue. The document is then transmitted either automatically or manually. If the transfer order consists of several items and immediate transmission for a material has been set, the communication document is transmitted immediately.

Stock Transfers from R/3 to R/2
R/3 as the Leading System
The section R/2 _ R/3 Processes is based on the assumption that the R/2 Inventory Management (IM) component is the leading system for posting a goods movement, that is, that each goods movement is posted first in IM, and then a transfer order is created in WM.

However, it is also possible to create the transfer order first in WM and then to execute the stock posting in R/2 afterwards.Organizational factors can play a role in the decision to have WM as the leading component for certain transactions.

If a company runs on a 24-hour operation basis, finished goods need to be taken from the production area and placed into storage in the warehouse. Since the host system is available for limited time periods only, such goods movements are first entered in WM. As soon as the Host system is active again, the goods movements are posted subsequently in IM. This takes place automatically via the interface.

No Checks
When goods movements are entered in WM, the system does not check the posting against data that are stored in the main system.

For this reason, certain transactions, such as goods receipts for purchase orders, should be posted in IM first so that data checks in R/2 can take place (for example, checking the goods receipt quantity against the ordered quantity).

Material Availability
A goods movement is taken into account by the Material Requirements Planning department only after the RM document has been posted in Inventory Management. If there is a considerable time delay between the LVS posting and the RM posting, you must bear in mind that the material availability as stated by the system may deviate from the actual availability of the material.

General Process: Single Data Transfer
If a goods movement is posted first in Warehouse Management and then in Inventory Management, the process is as follows:

Stock Transfers from R/3 to R/2

  1. In the R/3 System you post the transfer order for the stock placements and stock removals without a reference document. (Choose TransOrder Create Without reference from the WM menu bar.) As soon as the physical goods transfer has taken place, you confirm the transfer order.
  2. During the confirmation procedure, the system determines that the transfer order is relevant for Inventory Management and that a communication process has to take place in order for the transferred quantity to be communicated to Inventory Management. The system does not post any quants to the interim storage record. Instead, it creates a communication document, which is then transmitted to the R/2 System either automatically or manually.
  3. After the data transmission, the R/2 System creates a material document (GR/GI document) based on the communication document. This material document updates the stock quantities and values in Inventory Management.

General Process: Cumulative Data Transfer
If you want to have the transfer data transmitted on a cumulative basis, the procedure is as follows:

  1. In the R/3 System, you create transfer orders for stock placements and stock removals without a reference document. (Choose TransOrder Create Without reference from the WM menu bar.)
  2. The system posts the quants to an interim storage record. If there is a stock placement coming from the production department, the quants are posted, for example, to a dynamic storage bin (coordinate = production order). Pallets of the same material are posted as one quant. The system does not create any communication documents for the transfer orders.
  3. A report (RLDLVS10) that reads the interim storage quants is started at regular intervals. The system creates a communication record that is transmitted to R/2. (You can also use transaction LD11 for this process.)
  4. After the communication record has been transmitted, the R/2 System creates a material document (GR/GI document) for each communication record. This document updates the stock quantities and values in Inventory Management.

Technical Process in R/3
If you post a goods movement in Warehouse Management first and then in Inventory Management, the communication process is as follows:

Technical Process in R/3

Creating a Transfer Order
When a transfer order is generated (without confirmation), the system posts quants to the interim storage area for each transfer order item. For example, the quant for the source item is posted to the interim storage area for goods receipts. At this point, no communication takes place because the transfer order must be confirmed first.

Checking Communication Relevance
During confirmation (or creation of transfer orders with simultaneous confirmation), the system checks on the basis of the movement type whether the stock placement or stock removal concerned is relevant for Inventory Management and whether the data should be transferred on a single or cumulative basis.

Creating the Communication Document
The system creates a communication document of the type LDK07 from the data to be transmitted.

Single Data Transfer
The system creates a communication record of the record type WM07 for each transfer order item. This record contains both the transfer order header data as well as the item data (interim storage item).

If an interim storage quant was posted when the transfer order was created, the system clears this quant during the confirmation procedure. No quant is posted to the interim storage area because the goods transfer data (material, quantity, and so on) are transmitted to the R/2 System via the communication document.

Cumulative Data Transfer
When a transfer order is created, the system automatically posts quants to the interim storage area. During the confirmation procedure, these quants are not cleared and the system does not create a communication document right away. In order to create the communication document, you need to initiate a report that reads the interim storage quants and creates a communication record for each material. Only then will the interim storage quants be cleared.

Determining the Receiver
If a communication process is to take place, the system determines the communication number for the respective warehouse number, for transaction activity key 001, and for the movement type in a control table (Control of Single Transactions). Using the communication number, the system finds the queue ID in another control table (Communication Numbers). The receiver is defined here.

Transmitting the Communication Document
The communication document is placed into the queue and transmitted to the R/2 System either automatically or manually.

Technical Process in R/2
If a communication document of the type LDK07 is sent to the R/2 System, this initiates the following actions in R/2:

Technical Process in R/2

Receiving the Communication Document

  1. The communication document is received in R/2 by a receiving routine and stored in table LDK07. At the same time, the system makes an entry in the status record LDK00, which is used to manage the communication document.
  2. The communication records are processed and checked by a further routine.
  3. Via table 340C, the system determines the company code, plant and storage location that are linked to the R/3 warehouse number.
  4. Via table 341C, the system uses the R/3 movement type to determine the transaction and the movement type for the material posting. The standard system supports only transactions TL06 and TL11. The R/3 fields of the communication document are converted to R/2 format. An LDK00 record is created and the goods movement is posted in the R/2 System.
  5. The system posts the goods movement in IM. It records the number of the communication document in the field Material Document (TL11) or in the field Delivery (TL06).

No Interim Storage Posting
When the material document is created, the system determines that the material document was generated by the R/3 Warehouse Management component and does not create a communication document. As a result, neither an interim storage quant nor a transfer requirement is created in Warehouse Management.

Recording Differences
Differences that are recorded during the confirmation of a transfer order or during inventory must be cleared in Inventory Management. This applies regardless of the sequence in which the goods movement is posted (Inventory Management before Warehouse Management or vice versa). Similar to the R/3 _ R/2 processes, the differences can be transferred to Inventory Management either individually per warehouse movement or in accumulated form.

Recording Differences

General Process
The general procedure is as follows:

  1. When you confirm a transfer order, enter the difference quantity.
  2. During the confirmation procedure, the system determines that the difference needs to be transferred to Inventory Management, and therefore creates a communication document. The communication document is then transmitted to the R/2 System either manually or automatically. If data is transferred on a cumulative basis, the quants are first posted to the interim storage area for differences. In this case, you need to start a report that reads the interim storage quants and creates a communication document.
  3. After the data transfer, the R/2 System creates a material document based on the communication document. This material document updates the stock quantities and values in the R/2 system.

Technical Process in R/3
If a difference is entered during the confirmation of a transfer order, the difference data is recorded in the transfer order and then needs to be transmitted to the R/2 System.
Determining the Receiver
The system determines the communication number for the warehouse number, the transaction, and the movement type. Using the communication number, the system determines the queue ID under which the receiver is defined.
Creating the Communication Document
A communication record LDK09 (record type WM09) is created from the difference item for the difference posting. Difference for an R/2 _ R/3 Transaction
If the difference is recorded for a transaction that is posted first in Inventory Management and then in Warehouse Management, the communication document only contains communication records of the record type WM09.

Difference for an R/3 _ R/2 Transaction If the difference is recorded for a transaction that is posted first in Warehouse Management and then in Inventory Management, the communication record for transmitting the difference data is an integral part of the communication document that is created when the transfer order is being confirmed. The communication document in this case consists of communication records of different record types:

  • WM07 for transmitting transfer quantity data
  • WM09 for transmitting differences

Transmitting the Communication Document
The communication document is placed into the queue and transmitted to R/2 either automatically or manually.
No Interim Storage Area for Differences
Since the difference is transferred to Inventory Management directly, no quant is posted to the interim storage area for differences.
Technical Process in R/2
If a communication document with a communication record WM09 is transmitted to R/2, this initiates the following actions in the R/2 System:

Receiving the Communication Document

  1. The communication document is received in R/2 by a receiving routine and then stored in table LDK09. At the same time, the system makes an entry in the status record LDK00, which is used for managing the communication document.
  2. The system determines the RM movement type for transaction TL11 in table 304 on the basis of the stock category.
  3. Based on the communication record WM09, the system posts a material document for the difference posting using the CALL TRANSACTION.

No Interim Storage Posting
When the material document is being created, the system determines that the document is created by the R/3 Warehouse Management component. No communication document is created and, therefore, no quant posted to the interim storage area for differences.

Differences in Source Storage Bin for Transmissions to R/2
However, for goods receipts (for example, from Production Planning), it is generally better to establish the quantity actually produced by adjusting the stock quantities in the source storage bin. This is necessary because the exact quantity to be produced is not always known. This often results in partial pallets.
Using the SAP WM component, It is possible to transmit the actual quantity to the R/2 System, that is, the target quantity is corrected to the actual quantity based on the difference in the source storage bin.

This type of transmission to the R/2 System must be activated as an individual processing control based on the movement type. For processing in R/3, activate the Field Diff.in source bin under Individual processing controls for R/3 to R/2 Communication in the Define decentralized link to R/2 section of the Warehouse Management IMG.

Cumulative Transmission of Differences R/3 -> R/2
The aim of cumulative transmissions from the R/3 System is to accumulate inventory differences (or even goods movements) and then to transmit them all at once to the R/2 System. There are three relevant tables in the R/3 System:
Control of individual processing: "Movement Type Decentral.MM-WM Host Activity"
Control of multiple processing: "Accumulated Messages for the Host (R/2)"

R/3 movement types
You define these tables using the Warehouse Management IMG. To maintain the first two tables, choose Interfaces Define decentralized link to R/2 and then the appropriate table from the list of objects. To maintain R/3 movement types, choose Activities Transfers Movement types.

General Process
Quants are collected in an interim storage area. The ABAP RLDLVS10 reads the data about the quants and creates one transfer order per quant. The transfer order decreases the quantity in the interim storage area and creates a communication document that is sent to the R/2 System over the normal CPI-C interface.
The following factors regarding negative and positive quants in the interim storage area apply:
Negative Quant in the Interim Storage Area
Indicates (a difference for) a goods receipt into the warehouse (resulting from a transfer order for a putaway).
From: the interim storage area (for cumulative transfers) (-)
To: a storage bin in the warehouse (+)
Positive Quant in the Interim Storage Area
Indicates a goods issue from the warehouse (resulting from a transfer order for a pick).
From: a storage bin in the warehouse (-)
To: the interim storage area (+)

Posting Control
To control the postings for the interim storage area, there are two possibilities:

Easy Method
Define a movement type for the goods movement, but do not include it in the table for "Control of individual processes". In the movement type itself, you must define to which storage type the goods are to be sent.

Material-Dependent Method
For all goods movements, the data is transferred directly to the R/2 host unless a specific material has been defined otherwise.

For this process, the movement type must be in the table for "Control of individual processes". In that table, depending upon the direction of movement, you enter 2 in the Source items or Destination items fields accordingly. The system still looks in the material master record and creates communication documents only for materials where the Message to IM check box is marked. For more information about the control of individual processes table, see Sending Communication Documents from R/3 to R/2.

Sending the Quants to Inventory Management
To transmit the quants to Inventory Management in the R/2 System, you use the report RLDLVS10 as follows:

Choose System Services Reporting from any menu bar and choose ENTER.
Enter RLDLVS10 in the Program field and choose Execute.
Enter the warehouse number and storage type for the accumulation interim storage area and choose List Clear online foreground or List Clear online background.

For each quant, the system creates a transfer order that clears the interim storage area.The creation of the transfer order results in the creation of a communication document that is then transmitted to the R/2 System.

How are the Transfer Orders Created?
The movement type in the table "Control of multiple processes" is used to create the transfer orders when report RLDLVS10 is executed.The table below illustrates how this table can be set up to control multiple processing for differences.

Accumulated Messages for the Host (R/2)

Accumulated Messages for the Host (R/2)

To define these movement types see Activities Transfers Movement types in the Warehouse Management IMG documentation. For negative quants, the movement type creates a transfer order for a putaway. The movement type "-" (minus) unburdens, so to speak, the source item in the transfer order. For positive quants, the movement type creates a transfer order for a pick. The movement type "+" (plus) unburdens, so to speak, the destination item in the transfer order.

Where do the transfer orders get their data?
Since the ABAP reads the interim storage area, the correct data (including the requirement tracking number) is automatically retrieved for each of the quants.

Set-up for Inventory Differences Storage Type 999
To configure your system for cumulative transfer of differences from R/3 to R/2, you must set up the tables in the following order:

  1. Define a new interim storage area (for example, storage type 980) for cumulative transfers.
    This storage type should include Mixed storage and Addition to existing stock for stock placement controls and Negative stock and Posting changes in same bin for stock removal controls.
  2. Define a storage section (for example, 001) for the storage area.
  3. Define a storage bin (for example, TEMP) for the interim storage area.
  4. Define two new movement types to be used for the transfers.
  5. Using the movement types shown in the first line of the accumulates messages table above as examples, you need to define movement types with the following characteristics:

    Set-up-for-Inventory-Differences-Storage-Type

  6. Add the new movement types to the table "Control of individual processes"
    For movement type 719 (activity key 001), enter 1 in the Source items field (directly to R/2).
    For movement type 720 (activity key 001), enter 1 in the Destination items field (directly to R/2).
  7. Add the new movement types to the table "Control of multiple processes" (as shown in the first line of the below).
  8. Accumulated Messages for the Host (R/2)

    Accumulated Messages for the Host (R/2)

Example: Set-up for Cumulative Postings
To configure your system for cumulative transfers for goods receipts and goods issues from R/3 to R/2, steps 1 through 6 above are the same. You set up the tables in the following order:

  1. Define a new interim storage area (for example, storage type 904) for cumulative transfers.
  2. Define a storage section (for example, 904 001) for the storage area.
  3. Define a storage bin (for example, TEMP) in 904 001.
  4. Define two new movement types to be used for the transfers. For example:
  5. Set-up for Cumulative Postings

  6. Add the new movement types to the table "Control of individual processes"
    For movement type 819 (activity key 001), enter 1in the Source items field (directly to R/2).
    For movement type 820 (activity key 001), enter 1in the Destination items field (directly to R/2).
  7. Add the new movement types to the table "Control of multiple processes" (as shown in the second line of the accumulated messages table above).
  8. In addition: Define a movement type for goods receipts and goods issues postings in R/3.
    This movement type is optional and should be used when communication documents are to be transmitted immediately to R/2 based on the material or when the quantities are to be sent cumulatively to the R/2 System.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

SAP WM Topics