SAP Event Mesh Inbound

SAP Event Mesh Inbound is a test that will publish the message to SAP Event Mesh topic or queue.

Basic Information

Parameters

Parameter name	Description	Example
SAP Event Mesh Post to	Posting to Queue or Topic	Queue, Topic
SAP Event Mesh Topic Pattern	Topic name where the message should be published. Value help will show Topics that selected Queue subscribes to. Applicable only if ‘Topic’ was selected in ‘SAP Event Mesh Post to’ parameter.	int4suite/demo/em/ce/sap/s4/beh/salesorder/v1/SalesOrder/Created/v1
SAP Event Mesh QoS	Quality of Service for publishing messages. 0 - 204 http status code irrespective of whether the message is delivered or not. 1 - 204 http status code only for successfully published message	1, 0
SAP Event Mesh Message Expiration	Time to live for the message in milliseconds. Default value is 2592000000 ms (30 days).	2592000000
SAP Event Mesh Content Type	Header Content-Type parameter, used to indicate the media type of the message.	application/xml

Execution Settings

In this section there are common execution settings for all test cases.

Debug Log
This feature enables additional debugging messages to be included in the test execution log. Typically, this option is disabled, as a log with debugging information can become cluttered with details unnecessary for standard test execution. However, it proves invaluable during the initial phases of working with Int4 Suite, as it provides insights into each unsuccessful run and aids in identifying and resolving connectivity and security issues.

Display Wait Popup Before Validation
In specific scenarios, there may be a need for manual intervention between the message injection by Int4 Suite and the readiness for test validation. For instance, when an XML message is injected into SAP CPI, mapped to an IDoc, and subsequently transferred to SAP S/4, the IDoc may be processed automatically by the backend. However, certain configurations could hinder this automatic processing. In such cases, the tester must log into S/4 to manually request IDoc processing. The wait popup feature facilitates this by allowing Int4 Suite to send the message and display a popup before commencing backend data validation. This gives the tester time to complete the IDoc processing, return to Int4 Suite, and confirm the popup. Only after this confirmation will Int4 Suite proceed with data validations.

Delay Between Execution and Validation
Similar to the wait popup feature, these options allow for a delay to be configured between the initiation of the test run and/or between the injection of test case data and the validation of results. If it is anticipated that backend processing or integration platform mapping may require a considerable amount of time, this section allows for the configuration of such delays. As a result, Int4 Suite will pause before attempting to validate the integration platform and/or the backend, depending on the type of test being executed.

Variables

Variables are the container for values that can be used during testing. Each variable contains two values, the one that is calculated based on the reference message/document and the one that is calculated ad-hoc during test case execution.

There are various scenarios where variable processing can be beneficial:

• Updating document/message content before test execution

• Capturing data from document/message content after execution

• Matching documents based on variable content

• Passing data between test cases

For more details on Variables and their processing, read here: Variables & Variable processing

Create button allows variable creation.

Local Scripts

Local Scripts enable you to define custom scripts that are available within the context of the current Automation Object.

These scripts can be utilized in the following areas:

• Variable Processing

• Payload Processing

• Custom Validations

Please consult the Int4 Aster Documentation for details on the scripting language.

Custom Validations

Custom Validations offer enhanced flexibility for evaluating test case results by allowing the implementation of custom logic using ASTER Scripts.

Within the script, you can access test execution data using built-in Int4 Suite functions such as:

• GET_TC_VAR – to retrieve test case variables

• GET_VALIDATION_PAYLOADS – to access payloads used during validation

For the test case to be marked as successful, the script must return a _TRUE_ value.

Number Ranges

Int4 Suite uses own number ranges for data processing needs. Quite often, when sending test data to test systems again and again, the message can’t be exactly the same. For example, sending the same purchase order to generate sales order in S/4 could result in an error, if the system is configured to treat such situations as duplicates. Also, having a specific data field in the document might be mandatory to find another document - e.g. by generating an unique PO number for the Sales Order, we can find the newly created Sales Order in the database. The actual mechanics for such replacements of original document numbers or other values is described in the section Variables & Variable processing.

Below you will find information how to create a new number range.

The number range used to replace the source system document number should always be configured to not overwrite the original numbers. It means that documents generated by Int4 Suite should have their own subset of the original document number. Usually, it might be a subset of the upper limit of the original number range.

It is essential that automated testing with Int4 Suite doesn’t consume numbers that the source system will generate during manual testing. Additionally, if testing environment data is refreshed from the production system, more documents would be created in the testing environment. If the Int4 Suite number were configured in the same range, it would start creating duplicates.

For example, the original number range for document numbers from the source system is 560000 - 590000. It would be wise to set the Int4 Suite number range from 590000 to 600000. However, suppose the SAP backend system uses an external number range. It is essential to stay in the original range. In that case, the Int4 Suite number range may be set as 585000-590000, which gives space for 5000 testing documents. Using range from upper interval reduces the risk that the number will be overwritten.

Additionally, the good practice is to use prefixes or suffixes that will quickly separate source system documents and the ones created by Int4 Suite. It should always be used when there is no document number validation by the SAP backend.

Each Object Definition can contain an unlimited number of number ranges. This way, each variable declared in an object can use its specific number range.

Backend Systems

Backend systems in an Automation Object specify the SAP backend system (S/4HANA, ECC, or other ABAP-based systems) where to read a new document created by interface processing during test case execution. It also defines where the reference document was posted, serving as the source. The two documents will be compared in the test case results.

The given system line and source and target environment will be translated to the RFC destination in the runtime. Int4 Suite uses this RFC connection to execute dedicated function modules and retrieve data from the system’s database for comparison.

Find out more at Int4 Suite Internal Organization | Environments-and-System-Lines.

Depending on your testing scenario, both the current and reference system lines can be the same or different. For regression testing, they are typically the same, such as S/4HANA. The testing landscapes, however, may differ, e.g. Test and Production, where the system reads the reference from Production and the current document from Test. For migration scenarios, such as ECC to S/4HANA, the reference would usually be ECC, and the current would be S/4HANA.

External Links

External Links enable linking from Test Results and from Process Flow chart to business and system objects in external systems.

To link to external documents, the document reference (e.g. a number) must be captured by a Variable. The Variable number may be then used in link title and URL Template to construct a link to the document view. Based on Your Configuration , System Line might be specified, to create a link in the context of a specific business system.

Possible document links:

• Regular URL definition

• SAP Web GUI - following the template: /sap/bc/gui/sap/its/webgui?~transaction=*VA03 VBAK-VBELN={SO};DYNP_OKCODE=ENT2

• SAP GUI link - generated by Int4 Suite service: /sap/bc/int4/iftt/launcher/gui?~transaction=*VA03 VBAK-VBELN={SO};DYNP_OKCODE=ENT2

To generate SAP GUI/WebGUI links, the transaction code (e.g. VA03), selection screen parameters (e.g. VBAK-VBELN) and DynPro OK Code (e.g. ENT2) must be know. They are dependent on the specific SAP transaction. This information can be obtained from a functional expert or directly from SAP GUI by analyzing the fields on transaction screen.

Data Scrambling

Data scrambling enables to reduce or remove GDPR, privacy and security concerns when it comes to testing. When Int4 Suite is extracting the test data from existing messages or reports testing results, the visibility and availability of sensitive data could be an issue. To avoid this issue, sensitive data can be scrambled. Scrambling can occur at test case creation time and during the test execution. Actual behaviour of the scrambling engine is configured by a set of rules.