Int4 IFTT can be used for testing outbound integration scenarios using existing transactional documents. If Suppose the message for the integration platform is being triggered on the backend system via Output Control (NAST) then. Then, in that case, instead of creating the whole new document, it is enough to just replicate the output. The scope of the test is then like in the picture below:
...
In this process, the creation of the document itself is not being tested. Focus The focus of tests lies in the integration phrase 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 a template of the IFTT Automation Object template along with appropriate settings and parameters required for such comparison.
Please note that this is a 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:
...
Import/Export of int4 IFTT Configuration
The object consist of the following parameters:
Remark: The variables' names correspond to the key fields of the output control table (NAST), so they can’t be renamedyou can't rename them
Mandatory Variables
...
Variable processing:
...