Ansicht
Dokumentation

RLINVE00 - Test Report for IDOC Receipt: Entry of Inventory Count for WM-System

ABAP Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Purpose

You can use this report to test the inventory interface between an external system and the WM system. The entry of data with the help of a mobile data entry device is simulated in the system.

The system takes the data from the existing inventory documents. In this way, it can simulate the receipt of the IDoc WMIVID01 in the system. Careful in the productive system: a document is really posted!

The standard chain of activities for WM inventory (Creating inventory documents - Printing the documents - Entering the count results - Posting the count - Possibly recounting - Clearing the differences in the warehouse and IM system) is interrupted during printing. The data is not printed but transmitted to a subsystem. The count could take place using mobile data entry devices. The external system transmits the data. This data is posted in the SAP System. Then processing picks up again in the above chain. The data is transmitted by the report RLLI0405. The report RLINVE00 simulates the re-transmission of the count data from the external system to the SAP system.

For documentation on this data transmission, refer to the report RLLI0405.

The following test options are provided in this report:

• Testing via the ALE interface

The IDocs created in this report are transmitted to the function module 'INBOUND_IDOC_PROCESS'. Further processing is the same as for the standard interface from the external system through the ALE layer, that is, IDocs are created. The respective application function module for processing IDocs is automatically called, and, if an error occurs, the workflow is activated.

So that the data receipt from ALE can be processed, you must define the partner profile for the external system to be tested and the message type WMINVE. In the report selection, you must enter the external system as the sender system. You must select the logical name of the SAP system in which this test is taking place as the receiving system. This name is defined in the client table as the logical system.

Additionally, this test can take place in background processing. For this purpose, select the option "In Background Task".

• Testing entry of counted data directly

The created IDocs are transmitted directly for processing from this report to the application function module (L_IDOC_INPUT_WMINVE). The individual count items are posted at the end of the processing and a log with the data is issued. This data is passed back, during normal processing, from this function module to the ALE layer. This type of testing is appropriate to use if processing is to be tested within the application since there is no diversion through ALE. In this case, no IDoc is created either. In this way, the application logic can be tested independently of the communication logic.

To activate this type of test, select the option "Call processing directly". .

Careful: Testing this interface can cause changes to the database. If processing is successful, the goods movements defined in the IDocs are executed.

Prerequisites

The data is transmitted in an interim structure WMIVID01. The target data of the inventory bins in the inventory documents serves as the basis for the IDoc processing.

If you have several IDocs, however, the transmitting system may only call the SAP system using an IDo. It can do this as often as required.

Output

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.

Length: 3733 Date: 20240531 Time: 114458     sap01-206 ( 91 ms )