Communication Administration - SAP WM

This section is intended primarily for system administrators. It contains instructions on how to set up your system to manage communication documents that are transmitted between the R/2 host system and the R/3 Warehouse Management system.

This section is separated into three main parts with topics that pertain to each part as follows:
PART 1: R/2 _ R/3 Processes
PART 2: R/3 _ R/2 Processes
PART 3: Additional Information

PART 1: R/2 -> R/3 Processes
This section contains topics that primarily describe processes involving the transfer of data from the SAP R/2 Host System to the SAP R/3 System.
Setting up the R/2 Control Tables
Connecting R/2 Movement Types to R/3 Movement Types
Queue Management in R/2
Receiving Communication Documents in R/3
The Analysis Tool
Reposting Communication Documents in R/3
Mail Control in the SAP R/3 System

Setting up the R/2 Control Tables
Before any communication can take place between the R/2 host system and the R/3 Warehouse Management system, you must first link the partner systems together.

Depending upon the system configuration (hardware, operating system, DC system, network, gateway, and so on), communications must be set up for each side of the system. In this section, we explain how to set up application-specific tables for your system.

There are several control tables in the R/2 System that are used to create communication documents that are then transmitted to the R/3 System. As an example, we will describe four important tables.

Setting up the R/2 Control Tables

A goods receipt in the R/2 Inventory Management (IM) system is to be communicated to the R/3 Warehouse Management (WM) system. The posting takes place in Company Code 01, Plant 01 and Storage Location 87 via transaction TL01 and movement type 101.

Process Initialization
Table 340 in the R/2 System initializes the communication to the R/3 WM system. In our example, the system finds a corresponding entry in table 340 and identifies this posting as relevant for the R/3 system. R/3 Warehouse Number 111, R/3 Plant 0001 and Language E are assigned for this posting.

Table 340 in R/2
Process Initialization

Process Initialization

Linking RM-MAT to Warehouse Management
Instead of taking the RM movement type from table 156, the system accesses table 341 to find the reference movement type and other indicators. The following data is provided:

  • Movement type for WM
  • Stock category for the quants created by the movement
  • Indicators controlling the creation of transfer requirements and posting change notices

Table 341 serves, therefore, as a connecting link between the R/2 Inventory Management system and R/3 Warehouse Management.

Connecting R/2 Movement Types to R/3
The following table illustrates how movement types in the R/2 Inventory Management (IM) system are connected to movement types in the R/3 WM system.

Table 341 in R/2
Reference Movement Type Links

Reference Movement Type Links

The first entry in table 341 above is the relevant entry for our example. Here, the following assignments are made:

  • WM movement type 101
  • Stock category of readily available
  • Account assignment to the purchase order number
  • Set goods receipt date for quants
  • Create transfer requirement in R/3 WM

Activity Keys
Activity keys are assigned to communication numbers in table 342.
In table 342 illustrated below, the activity key 001 is used for processing communication documents for goods movements transactions using communication number WMK10, whereas activity key 003 is used to process communication documents for material master records.

Table 342 in R/2
Activity Keys

Activity Keys

Defining the Receiving System
In the R/2 System, table 343 is used to define the receiving system.

Table 343 in R/2
Definition of Receiving System

Definition of Receiving System

The module WE_WA_BUCHEN must be identified as illustrated in the above table for the system to address the proper R/3 transaction for posting goods receipts and goods issues. Using communication numbers, you establish the parameters that are used to define the partner system. With the "Target System" and "Application" parameters, you define the communication at the logical-technical level. The rest of the parameters pertain to the application-specific definition of the communication.

By varying the definitions of the communication numbers, you describe corresponding queues.These queues provide you with the capability to send selected communication documents over separate channels (for example, at separate times).

In column S (start transmission of communication documents), two entries are possible:
M = manual transmission of communication documents
A = automatic transmission of communication documents

For our example, entries in the first line are relevant (see table “Definition of Receiving System” above. The entries "Program SAPML06D" and "Module WE_WA_BUCHEN" cause the receiving routine that is responsible for goods receipts and goods issues to be called up on the R/3 side.

Queue Management in R/2
As described in the General Communication Process, when communication documents are sent from the R/2 host to the R/3 system, it is always an asynchronous process. They are assigned to a DOUT file (queue) and the system attempts to send them as soon as the receiving system becomes available. As described in the previous section, you can establish whether this process is automatic or manual.

Queue Maintenance
To list communication documents that have been created and are still active in a queue in the R/2 System

  1. Execute transaction TMQM by entering ntmqm in the OK field and choose ENTER.
  2. Choose F11 to display a list of the existing queues in the system.
    The number of communication documents for a queue are listed in the TrNr column.
    From this list, it is possible to start the driver to start the program to transmit communication documents from the DOUT queue to the R/3 System (see "Transmitting Communication Documents Manually" below).
  3. To display a list of communication documents (sentences) of a queue, position the cursor on the desired line and choose F12.
  4. To list the contents of a communication record, position the cursor on the desired line and choose F2. The structure of the record displayed is based on a corresponding data dictionary structure.

Communication Record Structure in R/3
The data dictionary structure for communication records in the R/3 System is exactly the same as in the R/2 System. To display the list of fields for a communication record in the R/3 System

  1. Choose Tools ABAP Workbench Development ABAP Dictionary from the SAP main menu bar.
  2. On the screen that appears, enter ldk01 in the Data type field, and choose Display.

Transmitting Communication Documents Manually
If the communication number in R/2 is defined so that communication documents are transmitted manually, and not automatically, to the R/3 System, the driver must be started manually for the corresponding queue (see table 343 under Connecting R/2 Movement Types to R/3).

To send communication documents manually from the R/2 host to the R/3 system

  1. Execute transaction TMQD ("APPC Management Information") by entering ntmqd in the OK field and choose ENTER.
  2. Enter xin the field to the left of the relevant queue(s). If you do not know which queue(s) to select, check table 343 to see which queue is used for the selected process (communication number).
  3. To select only one queue, you do not have to enter xto the left of the queue. Instead, position the cursor anywhere on the desired queue line.

  4. Choose F17 (Start driver) to start the program to transmit communication documents from the DOUT queue to the R/3 System.
  5. Choose ENTER to display the current status.
    A Y appears in column A under "Shipping" of the selected line to indicate that the driver is active. This indicator remains until all communication documents in the queue have been sent successfully.
  6. If, when you choose ENTER again, the line has disappeared, it means that the communication documents in the queue have arrived in the receiving system.

When the communication documents are received in the R/3 System, R/2 is notified that they have arrived successfully and they are physically deleted from the R/2 System.

Receiving Communication Documents in R/3
In the test phase as well as in a productive system, the system manager should periodically check the operation of the system communications. To do this, a regular plan should be established to determine whether communication documents have been received without errors in the R/3 system and to carry out necessary updates.

Errors when Receiving Communication Documents
If errors are found (for example, no transfer requirement exists in the R/3 System for a stock movement that was posted in the R/2 System), you must determine whether the problem is a communication document transmission error (in the CPI-C) or an error in the operation of the Warehouse Management application. You can check this easily by displaying a list of communication documents in the system in which the documents were received.

Analyzing Errors
To identify and analyze errors that occur in the system, three tasks are available:

  • Mail messages
  • System log
  • Analysis tool

To use these tasks, choose Logistics Logistics Execution Internal Whse Processes R/2- R/3 Link Error Analysis from the SAP menu. From the Error Analysis, continue as follows:

  1. To identify errors that occur during the transmission of communication documents, choose Error analysis Incoming mail.
  2. To analyze the system log, choose Error analysis System log.
  3. To display and analyze communication documents that have been received from the host system, choose Error analysis Evaluate commun.doc.

These tasks are discussed in more detail under the topics The Analysis Tool and Mail Control in the R/3 System.

Technical Errors
If the error is a communication error (CPI-C), it is known as a technical error. To resolve technical errors, the communication path must be checked. For detailed information about the CPI-C interface, refer to the BC SAP-Communication: Programming Guide.

Logical Errors
If the error is an applications error, it is known as a logical error (for example, an incorrect entry in a table or missing information in the material master record). For instructions on how to analyze and correct logical errors, see The Analysis Tool.Once you have corrected logical errors, you must repost the communication document to ensure that all necessary updates are carried out by the system.

Where to Look When Errors Occur
When errors occur, it is not always easy to figure out what caused them and where to look to correct them. The following chart in provides a logical sequence of actions and possibilities as to how to analyze and correct most errors that occur when working with the R/3 system. These same procedures can be followed to identify errors that occur when transmitting communication documents regardless of the source or target systems.

Receiving-Communication-Documents-in-R-3

The Analysis Tool
The analysis tool displays an overview of communication documents received from the R/2 system. It provides you with information on whether the communication documents received from the partner system could be processed. In the analysis tool, the overview lists the

  • Total number of communication documents received
  • Number of communication documents that were processed correctly
  • Number of communication documents that are open (yet to be processed)
  • Number of communication documents that could not be processed and are marked "in error"
    The overview may contain one or more of the following communication record types:
  • Delivery documents
  • Goods receipt/Goods issue/Posting changes
  • Material master record documents.From this evaluation list, you can
  • Retrieve information about the contents of a communication document
  • Repost communication documents received with errors

How to Use the Analysis Tool in the R/3 System
To retrieve a list of communication documents using the analysis tool:

  1. Choose Logistics Logistics Execution Internal Whse Processes R/2-R/3 Link Error Analysis Evaluate Commun.Doc. from the SAP menu bar.
  2. Choose Communication Evaluate commun.doc or Error analysis Evaluate commun.doc from the menu bar.
  3. On the initial screen, a typical selection includes the evaluation of all communication documents transmitted in one day. To receive this evaluation, you choose Execute.
  4. On this screen, it is also possible for you to select communication documents based on time and/or record number intervals. The system displays a global overview of communication documents. The number of communication documents listed in the Complete column have been correctly processed and posted in the R/3 System. If a communication document is listed in the Open column, it has been received in the R/3 System but has not yet been processed. If an error has occurred (for example, an attempted goods receipt posting without maintaining the material master in R/3), these communication documents will be listed in the Incorrect column.

  5. To retrieve more information about a specific group of communication documents (for example, all communication documents received for goods receipt, goods issue and posting changes) move the cursor to that number group and choose Overview comm.doc. on the applications toolbar or simply double-click the mouse on the number.
  6. The system displays an overview of the communication documents from that group. For communication documents with errors, the corresponding error message is also displayed with the list.In the overview of communication documents, the document types are identified as follows:

    Communication Document Types

    Communication Document Types

    An X in the D column indicates that a communication document has been sent previously (double transmission).

  7. To display a list of communication records in a specific communication document, move the cursor to the desired document and choose Display comm.doc. on the applications toolbar (or double-click the mouse).
  8. To display detailed information about a specific communication record, move the cursor to a record in the list and choose Display comm.record (or double-click the mouse).

Updating the Global Overview
From the global overview screen (described in step 3 above), you can update the information displayed at any time. To do this, choose Refresh from the applications toolbar.

Reposting Communication Documents in R/3
You can find the number of communication documents that could not be processed in R/3 under the heading Incorrect in the global list of communication documents which you retrieve as described in steps 1 to 3 of the topic The Analysis Tool. Once the error which caused the interruption has been corrected, you must manually repost the communication document, so that all necessary updates in the system are carried out.

A goods receipt is posted in the R/2 System and has been transmitted to the R/3 System, but the material master record for the corresponding material has not been maintained in the R/3 System. In this case, an error occurs because the R/3 receiving program cannot carry out the necessary updates. Once you maintain the material master record in the R/3 System (that is, once you create the Warehouse Management view in the R/3 System), and repost the corresponding communication document, the system will create a transfer requirement and post the corresponding quant to the goods receipt area.

Reposting from the Selective Overview
To repost a communication document from the selective overview using the analysis tool

  1. Retrieve the selective overview of the communication documents received with errors (see step 4 in The Analysis Tool.)
  2. Move the cursor to a communication document number and choose Repost comm.doc.
  3. To repost the communication document in the background, choose Post in background.
    The system reposts the communication document and completes the corresponding transactions in the R/3 System. To repost the communication record in the foreground, choose Post in foreground.The detailed communication record you selected is automatically retrieved and displayed on the screen.
  4. At this point, you can display the communication records of a document when you repost them and (generally, as an exception) change selected fields if you desire to do so. Choose ENTER to initiate the processing of the communication record.

The system posts the modified record to the data base. Due to the possibility of creating inconsistencies between the R/3 and host systems, you should exercise caution in making changes to relevant fields in communication documents when reposting them in the foreground. This should only be done as an exception.

Reposting a Specific Communication Document
If you know the number of a communication document that you want to repost, you can select the reposting task directly without entering the analysis tool function.
To access this task directly:

  1. Choose Logistics Logistics Execution Internal Whse Processes R/2-R/3 Link Communication Warehouse Management Repost Commun. Doc. from the SAP menu.
  2. Enter the number of the desired communication document in the Record number field.
    From this point, you repost communication records using the same procedures as described in "Reposting from the Selective Overview" above.

Bulk Processing When Reposting Open Communication Documents
Very often, several communication documents are processed incorrectly due to a similar type of error. Some errors (such as block errors) can be eliminated automatically by simply reposting the communication documents again. In this case, having to repost one record at a time is painfully slow and time consuming.

Mail Control in the R/3 System
In the R/3 System, there are two tables that allow you to specify users and types of Mail messages to be sent when errors occur or when specific transactions are carried out in the system:

  • Logical Error Recovery Table
  • Parameters for Generating Logs and Mail Messages (R/2 _ R/3)
    You can find both of these tables by selecting objects using the Warehouse Management IMG. The use of these tables is described below.

Assigning Users to Receive Mail Messages
In the R/3 System you can specify a particular user to receive error messages for certain communication documents. You can assign one user per record type for this purpose. To assign users to receive Mail messages, choose Define decentralized link to R/2 in the Interfaces section of the Warehouse Management IMG. You can enter the name of a user for each record type. In this table, you can also designate whether the messages are to be sent as "express" messages by selecting the field User name. This is illustrated in the table below:

Mail Recipient Control

Mail Recipient Control

For example, as shown in the above table for record types WM01 and WM02 (transactions involving goods movements and posting change notices from R/2 Inventory Management to R/3 Warehouse Management), an express mail is transmitted to user MILLER each time an error occurs. For errors involving record types that download delivery data to the R/3 System, an express mail is sent to user SMITH.

Selecting Log and Mail Message Parameters
To control the transmission of Mail messages and other logging functions, choose Define decentralized link to R/2 in the Interfaces section of the Warehouse Management IMG and choose Activate for Log and Mail messages from the list of objects.

In this table you can select options that will cause the system to

  • Send a Mail message when a logical or system (CPI-C) error occurs
  • Send a Mail message when a material master is created in the R/2 System
  • Log each communication document in the spool file
  • Make a log entry in the spool file when an error occurs
  • Print records immediately on a printer (specified in the same table)

Processing a Mail Message
When a user receives an express Mail message, a pop-up window appears with a notice that a message has arrived in the Inbox. From the pop-up window, the user can immediately access the message. From the mail message screen, it is then possible, for example, to maintain the Warehouse Management view of the material master record by choosing Edit Process from the Inbox menu bar.

PART 2: R/3 -> R/2 Processes
This section contains topics that describe the transfer of data from the SAP R/3 System to the R/2 Host.
Setting up the R/3 Control Tables
Sending Communication Documents from R/3 to R/2
Queue Handling in the SAP R/3 System
Receiving Communication Documents in R/2
Reposting Communication Documents in the R/2 System

Setting up the R/3 Control Tables
In the R/3 System, various control tables must be set up to use the R/3 Warehouse Management system. Some of these tables have already been described under R/2 _ R/3 Processes since they pertain to processes in both systems.

To configure the R/3 System, you must

  • Activate the R/2-R/3 link in the R/3 warehouse number record
  • Define and activate queues
  • Assign number range intervals for communication documents
  • Assign activity keys to WM movement types in the R/3 System
  • Define storage types and movement types for which cumulative communication documents are to be sent to the R/2 System (see Cumulative Transmission of Differences R/3 _ R/2)
  • Identify transactions for which Mail messages are to be sent
  • Assign recipients for Mail messages

Most of the activities above can be maintained from the "R/2-R/3 Link" screen by choosing Define decentralized link to R/2 in the Interfaces section of the Warehouse Management IMG.

How the Control Tables are Used
This illustrates how the control tables are used when creating communication documents in the R/3 System.

How the Control Tables are Used

Sending Communication Documents from R/3 to R/2
Certain transactions result in a data transfer from the R/3 System to the R/2 System. These include:

  • Putaways
  • Picks
  • Difference confirmation
  • Transmission of picked quantities for R/2 deliveries

Linking Activity Keys to Movement Types
The manner in which activity keys and movement types are assigned to communication numbers in the R/3 System affects how and when transactions that are initiated in the R/3 System are transmitted to the R/2 System. WM movement types, that initiate communication to the R/2 Inventory Management system, are maintained via the activity key 001 in the R/2 System assignment table (see R/3 _ R/2 Processes). To send data about picked quantities back to the R/2 Shipping system, you must make an entry with the corresponding activity key 002.

To maintain this assignment table, choose Define decentralized link to R/2 in the Interfaces section of the Warehouse Management IMG and then Individual Processing from the list of objects.

Defining Communication Indicators
From the assignment table described above, you can set an indicator that determines whether the communication of data to the R/2 System will take place immediately or depending upon each material. To set the indicators, position the cursor on the desired line and choose Detail. The system displays the detail screen for movement type links to the activity key. In the "Assignment" section of the screen, the communication number is displayed along with three fields:

  • Source items
  • Destination items
  • Differences

For each of these fields, there are three possibilities for defining communication indicators "Blank" no communication takes place
"1" A communication record is set up immediately for transmission to R/2.
This indicator is generally used for critical or perishable materials.
"2" material dependent - Another indicator in the material master record (Message to IM) is activated. This second indicator determines whether a communication record is to be set up immediately or whether an accumulated document is to be created by starting a program. You use indicator "2", for example, for materials that are handled infrequently or materials for which there is generally sufficient stock on hand.

Goods Receipt Posted First in R/3
Goods receipts from production are stored in the R/3 WM system initially without reference to a document posted in R/2. In the assignment table (see above), a corresponding entry (movement type 803) has been created for this purpose. For this example, you want to store 40 pallets from production that are filled with a specified material.

Procedure in R/3
To create the transfer order in the R/3 System

  1. Choose Logistics _ Logistics Execution _ Internal Whse Processes _ Stock Transfer _ Create Transfer Order _ No Source Object from the SAP menu.
  2. As a minimum, you must enter the warehouse number, movement type 803, material quantity, material number, and plant on the first screen. Choose ENTER.
  3. Complete the creation and confirmation of the transfer order.When you confirm the goods movement, a queue is created in the R/3 System.

How Communication Indicators Affect the Transfer
As described under "Linking Activity Keys to Movement Types" above, the communication indicators affect how and when the transmission of communication documents to the R/2 System take place. The following information applies to the transfer order created for the 40 pallets of material in the example:

  • If you use the communication indicator "1" for the Source item field (immediate confirmation and transfer of a communication document to R/2), no quant is built in the goods receipt (GR) area. Instead, one communication document is created for each pallet resulting in 40 communication documents.
  • If you use the communication indicator "2" for the Source item field, and you have identified the material as a non-critical material, the process is cumulative and negative quants are created in the GR area. In this case, data for all 40 pallets is contained in one communication document for the negative quant in the GR area.

Queue Handling in the R/3 System
The queue information display in the R/3 System is similar to the management information displayed using transaction TMQM in the R/2 System.

To retrieve the queue information in the R/3 System

  1. Choose Logistics Logistics Execution Internal Whse Processes R/2-R/3 Link Queue Edit from the SAP menu.
  2. To retrieve all queues in the system, enter * and choose Display.
    (You can also indicate the full queue ID name or a generic name. For example, WM* indicates all queues that begin with WM.)
  3. The status indicators on this screen are of significance:
    E = Error
    F = Finished
    These indicate whether the transmission of a queue was successful or in error.

  4. For additional information about a particular queue, double-click the mouse on a queue ID line.
    In the Modus field, "B" indicates a batch process and "M" indicates manual processing for the transaction.
  5. To start manual transmission of information, return to the screen displayed in step 2 and choose Execute.
  6. For information about the processing of the queue, choose Goto _ Log from the menu bar.

Creating a New Queue
From the queue maintenance screen, you can create a new queue or copy an existing queue.

Receiving Communication Documents in R/2
The communication process for transactions initiated in the R/3 System which results in the receipt of communication documents in the R/2 System is described in R/3 → R/2 Processes. The basic set-up and communication document handling is similar to that for transactions which transmit communication documents from R/2 to R/3.

R/2 System Setup
For R/3 → R/2 processes, entries in table 340C in the R/2 System link R/3 plants and warehouse numbers to the company code, plant and storage location in the R/2 System.

Linking R/3 Movement Types to R/2 Transactions and Movement Types
You must enter each R/3 movement type that initializes the transmission of data to the R/2 System in table 341C. In this table, transactions and movement types are assigned that are required for postings in the R/2 Inventory Management system.

Table 341C in R/2
R/3 ® R/2 Movement Type/Transaction Linkage

R/3 ® R/2 Movement Type/Transaction Linkage

For example, if table 341C is set up as illustrated in the table above, when a goods receipt without a purchase order (movement type 803) is posted in the R/3 Warehouse Management system, a communication document is created and transmitted which initiates transaction TL11 using movement type 501 in the R/2 Inventory Management system.

Analysis Tool in the R/2 System
When a communication document is received from the R/3 System, various checks take place. If the checks find an error, the status record is marked "in error". If the file is received successfully, the status record is marked as "completed". If the process is interrupted, the communication document is marked with the status "open". This status can be displayed using the analysis tool.

Using the R/2 Analysis Tool
You use the analysis tool in the R/2 System in basically the same manner as the analysis tool in the R/3 System described earlier in this section.
To display the R/2 analysis tool

  1. Use transaction TQ90 (enter ntq90 in the ok line and choose ENTER).
  2. Enter a record number or a range of record numbers and/or a date/time interval on the initial screen. Choose F13.
    The global display in the R/2 System is the same as the display in the R/3 described under The Analysis Tool.
  3. To retrieve more information about a specific group of communication documents move the cursor to that number group and choose F2.
    For communication documents with errors, the corresponding error message is also displayed with the list.
  4. To display a list of communication records in a specific communication document, move the cursor to the desired document and choose F2.
  5. To display detailed information about a specific communication record, move the cursor to a record in the list and choose F2 again.

Reposting Communication Documents in R/2
When errors occur during the transmission of communication documents from the R/3 system to the R/2 host, once you correct the errors you must repost the corresponding communication documents in the R/2 System. You can identify errors (technical or logical) using the same procedures available for the R/3 System (see the flow chart under Receiving Communication Documents in R/3).Once errors have been analyzed and corrected, you repost communication documents in the R/2 System using transaction TQ92.

Reposting from the Analysis Tool
This transaction can be started from the analysis tool (transaction TQ90) which is described in the previous section. From the global display in the analysis tool (see Step 2 above)

  1. Move the cursor to a group of communication documents from the Incorrect column and choose F2.
    The system displays an overview of the communication documents with errors. The corresponding error message is also displayed for each communication document in the list.
  2. After you have corrected the error, move the cursor to the appropriate communication number and choose F13.
  3. To repost the communication document in the foreground, choose F13.
    To repost the communication document in the background, choose F14.

Reposting Directly
To repost specific communication documents individually, you use transaction TQ92. Once you have entered the number of the corrected communication document in the Communication document field, the procedure is the same as described above beginning with step 3a.

Mail Control in the R/2 System
As in the R/3 System, when a communication document is received with errors in the R/2 System, a normal or express mail message can be sent to the user responsible (see Mail Control in the R/3 System.)

Assigning Mail Recipients
To assign users to receive mail messages for specific tasks in the R/2 System, you make entries in table 349M. In this table you enter the R/3 warehouse number, record type, recipient and whether or not an express mail message is to be sent.

There is no table, as in the R/3 System, which determines whether or not a Mail message is to be sent. You can, however, modify some logging and additional functions in the data section of the receiving program (ML18KTOP). To enter this program you use transaction TM38. The parameters are in a so-called modification part at the end of the include. If you modify any of these parameters in your system, please be aware that you may have to rework this Include after an official SAP system update.

PART 3: Additional Information
This section contains the following topics:
Reorganization of Communication Records
Polling of R/2 Data
IMS Connection for the WM R/2 - R/3 Interface

Reorganization of Communication Records
Tables LDK00, LDK07, LDK09, DVK03 and DVK04 contain documents and records resulting from R/3 transactions in the R/2 System. Communication documents that accumulate as a result of the interface of the R/3 WM system to the R/2 host can be deleted if they meet the following conditions:

  • Communication documents are processed (processing status X).
  • Processing date occurs before the selection date.

Reorganization report RLRE0LDK reads all LDK00 records that have been processed that are older than the selection date. Afterwards, it selects the dependent records and deletes them from the data base. After the dependent records have been deleted, the status record itself is deleted.

Polling of R/2 Data
Normally, data created in the R/2 host that is stored in the DOUT file is transferred by the R/2 System to the R/3 System. However, it is also possible for R/2 data to be retrieved by the target (R/3) system. To do this, the R/3 System polls the R/2 data. This capability is of particular significance for the DC system on the host, which does not support a complete APPC interface such as DCAM in BS2000 and IMS. Polling was imbedded in the existing functions of the R/2 <-> R/3 interface. In order to start the data transfer from the R/3 System, the R/2 System must take all necessary parameters in the R/3 System into consideration. The R/2 System is displayed as a queue with the queue management function (choose System Services Queue from any R/3 menu bar). All parameters of the R/2 System must be defined in the queue. For each queue in the R/2 System, a queue must be defined in the R/3 System which describes the same R/2 System.

From the queue management transaction, polling is then started in the same way as the transfer of data from R/3 to R/2. The triggered entry is marked as active and the number of records transferred is updated in the log. If there is an error, the queue is marked with the status "E" (error) and the error is noted in the log. In addition, a message with an error notice is sent to the corresponding queue. When polling is started, the R/2 queue must be passed to the R/2 System as a parameter. The R/2 queue must therefore be defined in R/3 with all parameters. This definition is then carried out in an include "RLDLVS90". In order to start the polling process, a driver is needed in the R/3 System. The driver was created as a report "RLDLVS20". This report must also be entered as a driver in the queue that is defined for the R/2 System.

IMS Connection for the WM R/2 - R/3 Interface
In the IMS environment, no complete APPC interface is workable. It is only possible to send a Mail message from the R/2 System. This possibility was used to pass a specific R/3 C-Program (IMSASYNC) from the R/2 System with the queue ID of the activated queue. The IMSASYNC program then passes this information on in a "usage report". The name of the report is taken from the queue ID; the form routine must be called IMSASYNC.

In the new IMSASYNC routine, the queue ID is received and afterwards the polling of the data in this queue is initiated. Polling of the data from a queue means that the transfer of data from R/2 is requested through the R/3 System. For polling, not only the queue ID is needed, but also the parameters of the R/2 System that is to be accessed. The corresponding R/2 System is then determined based on the data from the include RLDLVS90 via the queue ID. In the include RLDLVS90, the definition of the R/2 queue results as well as the assignment of the R/2 queue to the R/2 System, which was then listed as the R/3 queue.


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

SAP WM Topics