WE19 IDoc testing tools Tutorial

1, WE19 Introduction

WE19 IDOC is a very common testing tools, it can be tested by simulation inbound and outbound IDOC, rather than through other systems IDOC actually sending a test. In tests using the WE19 can have need to change depending on the value of IDOC in each field, it is very convenient.

Tcode:WE19

2016-09-25_13-15-24

Templates can see there are many options on the WE19 interface, focusing on the following introduction:

  • IDoc (Existing IDoc) present: Enter an existing IDoc number, based on this test, IDoc in the value of the field has been filled with good.
  • Basic types (BasicTyp): Enter an IDoc type, which is an empty template, you need to enter their own field value IDoc
  • By Message Type: a message type input, and then select the message type IDoc type, it is an empty template

2016-09-25_13-27-35

  • No template (W / O template): no template, information about all of the IDoc are required to manually fill in the WE19, this use is relatively small.

2, the inbound standard (standard inbound) Test

Examples explain how to test the standard IDoc inbound, just find a inboud IDoc 0000000003832546 by IDOC WE02 monitoring tools in the system, this is one pair of quotation modified IDoc

2016-09-25_13-37-32

WE19, IDoc number entered just find the 0000000003832546 run

2016-09-25_13-39-58

Into the test interface, click the control record line or through the menu to enter the control record editing window,

2016-09-25_13-42-07

IDoc--Edit control record

2016-09-25_13-42-56

In the control record edit window, there is a default receiving end, the transmitting end, relevant information message, usually without modification,

When testing standard inbound (standard inbound), in addition to partner profile port of Sender and Receiver are free to fill in, other related fields to be filled out correctly, the system must exist.

2016-09-25_13-54-41

Receiver:

Port: SAP + <SID>, e.g. SAPDE1, wherein DE1 is the SID (system ID), can be seen in the lower right corner of the SAP system, this system is SAPDE1 port, not visible in the WE21

2016-09-25_13-49-47

Sender:

To partner profile presence in WE20, we test it is, it must be as follows,

Tcode:WE20

2016-09-25_13-59-17

Click the field value can be changed in the WE19, Purchase order date date of this modified embodiment of the quotation line item, modify 20160927 20160925,

2016-09-25_14-17-16

Then click on the button standard inbound

2016-09-25_14-18-56

Pop-up message box that prompts IDOC generation,

2016-09-25_14-20-11

You can view in WE02:

2016-09-25_14-21-25

By VA23, see the purchase order date Date of quotation of successfully modified.

2016-09-25_14-22-20

3, introverted function module (inbound function module) test

This is used to test inbound process (refer to the meaning of the term -> the SAP development entry the IDOC ) hanging function, but also with the above IDoc 3832546, WE20 can be seen process code,

2016-09-25_14-25-59

Double-click the process code to jump to the function interface, can also Tcode: WE42 View

2016-09-25_14-30-22

Click WE19 top inbound function module button in the pop-up window can be set debugging mode, front running and other models, and then click the green check mark, you can test the function, and finally generate IDoc.

2016-09-25_14-31-43

Also: Record control function within the module is set to standard inbound (standard inbound) of the same, in addition to partner profile port of Sender and Receiver are free to fill in, other related fields to be filled out correctly, the system must exist.

4, introverted file (inbound file)

Inbound file is used to generate inbound IDoc test file, there is a need to specify the port in WE21 true in the control record, partner profile receiver is the same as the above two tests are free to fill in, as follows:

2016-09-25_14-57-15

Click the inbound file button, enter idoc file name, select the relevant operating mode by clicking the green check mark,

2016-09-25_14-58-56

Tip IDoc file is successfully created,

2016-09-25_15-01-22

You can view idoc status in WE02

2016-09-25_15-03-25

You can also view IDoc files in the server path port EDI_OSC in, WE21:

2016-09-25_15-05-22

5, outbound processing standard (standard outbound processing)

Find an outbound IDoc by WE02, WE19 then reprocessed in

2016-09-25_16-06-14

sender's partner profile control record can be free to fill in, in addition to be filled true, fill in the following meaning to send an outbound idoc port A000000018 through SAPDE1 simulation.

2016-09-25_16-06-47

Click the button standard outbound processing, send outbound IDoc

2016-09-25_16-11-50

Tip outbound IDoc successfully sent to an external system,

2016-09-25_16-13-09

And displaying in the status bar IDoc number 3846148

2016-09-25_16-14-09

Can be seen in WE02, the

2016-09-25_16-15-00

Note: WE19 different test outbound and inbound, and the breakpoint is not provided in the associated process code corresponding to the function of the stop.

the above.

Guess you like

Origin www.cnblogs.com/lvdong18847870057/p/12550757.html