Processing Tests 

Use

The test programs allow you to skip certain sections of the processing chain between applications so that errors can be located. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an R/3 System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc interface and defining new IDoc types.

Features

The figure below shows the various test programs and the processing steps when they are used: For example, when using "Test from MC", an IDoc for outbound processing via the IDoc interface is generated from an existing message status record (which refers to the application data via an object key).

Function

Prerequisite

Result

Test tool

None

One or more inbound or outbound IDocs are generated, depending on the direction, and forwarded for processing.

Outbound Processing from MC

Message status record exists in Message Control, referring to the application object (for example, purchase order)

Outbound IDoc is generated. The IDoc is forwarded to the external system in accordance with the partner profile.

Outbound Processing from IDoc

Outbound IDoc status is 30

IDoc is forwarded to the external system.

Inbound Status File

The status must refer to an existing outbound IDoc.

The status values are appended to the relevant outbound IDoc as status records. Exception handling is triggered in accordance with the status value.

Inbound Processing: Modified Outbound File

File with one or more outbound IDocs exists in the operating system (port type "File")

IDoc is generated and forwarded for inbound processing (to application)

Inbound Processing: Original Inbound File

File with one or more inbound IDocs exists in operating system (port type "File")

IDoc is generated and forwarded for inbound processing (to application)

Activities

 

Graphic: Interaction of test tools in the processing flow