Triggering the output from message control

Int4 IFTT can be used for testing outbound integration scenarios using existing transactional documents. Suppose the message for the integration platform is being triggered on the backend system via Output Control (NAST). Then, in that case, instead of creating the whole new document, it is enough to replicate the output. The scope of the test is then like in the picture below:

Open

In this process, the creation of the document itself is not being tested. The focus of tests lies in the integration phase ( for instance: IDOCs, User exits, BADIs, and middleware processing of the message), which is started from the triggering of the message control.

Configuration

This section describes the IFTT Automation Object template along with appropriate settings and parameters required for such comparison.

Please note that this is the same object for all interfaces, so you use the existing template that should be in your system. If not, you can import it from here:

Open

For details of how to import/export IFTT configuration objects, refer to page:

https://int4support.atlassian.net/wiki/spaces/IUM/pages/467697665

The object consist of the following parameters:

Remark: The variables' names correspond to the key fields of the output control table (NAST), so you can't rename them

Mandatory Variables

Open

Variable processing:

• KAPPL (Output application)

• KSCHL (Output type)

• OBJKY (Object key)

Optional Variables (If required ):

Variable processing:

• PARNR (Partner)

• PARVW (Partner Role)

• SPRAS (Language)

INT4 has prepared a generic configuration object for this scenario:

Test Case Creation

Test case creation is not different, than for the other test cases.

Interface type: 14/Backend/Trigger output should be used.

For details of how to create a test case, please refer to page: https://int4support.atlassian.net/wiki/spaces/IUM/pages/704905651