Versions Compared

Old Version 7

changes.mady.by.user Izabela Bogorska

Saved on

compared with

New Version Current

changes.mady.by.user Michal Rohnka

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Below you will find the automation object’s required parameters and variables that will combine repeating the message in output control for the particular business document and capturing its final output message from the integration platform.

Configuration of an automation object:

  1. Create a standard automation object for outbound interface (based on the description for a particular test type)

  2. Setup an Additional Parameter:
    Name: Trigger the output from message control (NAST)
    Value: X

  3. Add variables that will allow to repeat the message and correlate output based on the final content

Variable Name

Variable Description

Variable processors

Comment

KAPPL

Output application

Action: Populate Variable Before execution
Var. Proc.: CONSTANT
Processing Parameter: {Application from NAST}

For example:
V1 for sales order,
V3 for Invoice etc.

KSCHL

Output Type

Constant as above. Parameter should contain Output Type key

For example:
RD00

PARNR

Partner

Constant as above. Parameter should contain Partner Name

Optional

PARVW

Partner Role

Constant as above. The parameter should contain Partner Role

Optional

SPRAS

Language

Constant as above. Parameter should contain Language

Optional

AENDE

Change message flag

Constant as above. Used for testing change messages.

Optional

NACHA

Message transmission medium

Constant as above

Optional

OBJKY

SAP Document number

Two actions:

  1. Read variable before execution | READ_MSG | {XPath or flat file expression}

  2. Locate new message using variable value | XPATH | {same XPath or flat file expression}

The same XPath expression should be used for both actions.

The variables' names must be the same. They are used to populate an output in the SAP S/4HANA backend automatically.
First, The OBJKY variable is used to read the business document number that the test case output was captured. Next, the new entry is added to output control, and the interface logic creates a new test message.
Finally, by the second action in the OBJKY variable, Int4 IFTT will search the integration platform and find a new message that was produced by the test case execution and contain the correct document number.

...