DB Validation Rulesets

Backend Testing allows to validate database entries for the specified tables in the backend ABAP system. During full end-to-end testing within SAP Landscape of an application interface, the final document that Int4 Suite created in the SAP backend will be checked against the reference document stored during test cases creation. From the technical point of view, the validation is performed by comparing the selected database tables and table fields of both documents: the reference and the new one created during the test case execution. We make a business document’s database model representation and choose the tables, relations, and fields we want to be compared to achieve this.
Database Validation Rulesets can be reused by multiple automation objects.

Basic Information

You can access the Database Validation Rulesets by opening the Database Validation Rulesets tile.

Open

In the Database Validation Rulesets you can create or preview existing validation rulesets.
To create the validation rulesets, click Create button and then provide Ruleset ID and Description.

Steps

Open

To add the main table name click on the Create button and provide the name of the table that has to be validated.
In case you want to add a child table which entries are determined based on the keys from the main table select the row with a main table name click Create substep button.

Example
When records for reference and the newly created document will be fetched from the VBAK table (Sales Order Header) by variables, the entries from table VBPA (Partners) will be fetched based on the key field (VBELN) of the selected VBAK entry.

Then entries from VBAP will be fetched again based on the key field of the selected VBAK entry (VBELN field).

Finally, the entries from VBEP (schedule lines) will be fetched based on keys of records fetched for the VBAP table (VBELN and POSNR).

See the next chapter Selection Criteria to see how this selection works in detail.

Selection Criteria

Selection criteria are used to fetch relevant records from tables specified in the Steps step. For each table, it must be specified how the rows should be selected based on values stored in variables or fetched from records from preceding steps. Technically the configuration is used to prepare WHERE conditions for database queries. The queries that will be generated will be used to fetch references and newly created documents.

To add a selection criteria select the table for which you want to add them in the Steps section and in the Selection Criteria section click the Add button.

Example 1
Fetch headers of reference and newly created sales order based on variable PO from the Automation Object where DB Rulesets will be used

The variable PO in the automation Object is configured to fetch from reference XML or EDI file the field that contained the purchase order number.
Then the variable was regenerated with a new value from the IFTT number range and substituted into the new XML.

Example 2

Fetch all order items for the Sales Order that is chosen in Example 1 based on the VBELN (Sales Order Number) field.

Comparison Details

The comparison of reference and the new document is based on table and field level.
Finally, when the definition contains tables and the logic of how rows from the tables will be fetched, it is time to specify fields from each table that is compared.

To add a Comparison Details in the edit mode select the table from the Steps section and then click the Add button.

Example
Example fields to be compared in the VBAK table

Joins

Join tables are used to configure SQL join conditions to filter the selected data for the current step table configuration. You can still validate the table entries of the join table. However, it must be declared in a parent step, or a proper predefined database view should be used in the current step instead of the database table. The joined table might also be used for selection criteria as well as for additional fields to compare.

Sorting Criteria

Sorting Criteria is an optional configuration for the comparison of the tables. Suppose you want to make sure that reference and new records are compared in a specific sequence. In that case, you can select fields and sorting direction here. If the configuration is not maintained, no action will be performed.

Matching Criteria

Matching Criteria is an optional configuration for tables that contain multiple items (like sales order items). When reference and new records are compared, they will be first matched by the field specified here.

If no matching criteria are defined, items are compared based on an index ( first position from an original document with the first position from a new document, etc. ). It can lead to false-negative results if the new document's positions are posted in a different order.

Example Sales Order Item matching based on the line item number (POSEX)

Deletion of Duplicates

Deletion of Duplicates is an optional configuration for the DB Ruleset Details.

Suppose you want to make sure that unique records (based on fields' value) are compared. In that case, you can select fields for value comparison here. Records will be compared one by one, and only the first record with the same value will be kept for further processing. You can define the order of the records in the Sorting Criteria configuration. If the configuration is not maintained, no action will be performed.