Each Business Object is communicating with Connectors using unified template. Each transformation is receiving input in exactly the same format. Template is XML based file with below structure:
<?xml version="1.0" encoding="utf-8"?>
<asx:abap version="1.0" xmlns:asx="http://www.sap.com/abapxml">
<asx:values>
<BOA_INPUT>
<DOCUMENT_NUMBER>9100012345</DOCUMENT_NUMBER>
<INPUT_PAYLOAD><?xml version="1.0"?><customers><customer id="55000"><name>Dummy</name><address><street>100 Main</street><city>Dummy</city><zip>100</zip></address></customer></customers></INPUT_PAYLOAD>
<DESTINATION>MY_SYSTEM_RFC</DESTINATION>
<BO_PARAMETERS>
<_-INT4_-ST_BO_PARAMTER_VALUE>
<NAME>Param1</NAME>
<VALUE>1000</VALUE>
</_-INT4_-ST_BO_PARAMTER_VALUE>
<_-INT4_-ST_BO_PARAMTER_VALUE>
<NAME>Date_from</NAME>
<VALUE>2025-10-30</VALUE>
</_-INT4_-ST_BO_PARAMTER_VALUE>
<_-INT4_-ST_BO_PARAMTER_VALUE>
<NAME>Date_to</NAME>
<VALUE></VALUE>
</_-INT4_-ST_BO_PARAMTER_VALUE>
</BO_PARAMETERS>
<BO_JSON>{"test":"json"}</BO_JSON>
</BOA_INPUT>
</asx:values>
</asx:abap>
This template consists of few key components:
-
DOCUMENT_NUMBER - document number provided by Int4 Suite as input for Get Input, Get Reference Outputs and Get Result Outputs - main input to retrieve Business Object data from reference and test systems
-
INPUT_PAYLOAD - message payload prepared to be injected by connector to the test system. In case of multiple connections being executed for the single action, each connection will receive in this filed result of preceding connection.
Action Get Result Outputs receives payload produced by Execute Action in this field
-
DESTINATION - RFC Destination to be used to call the connector
-
BO_PARAMETERS - list of Business Object Parameters and their values
-
BO_JSON - JSON file define on Business Object