Page Comparison

...

In the migration projects, It can happen that field names or structure of the payload may change (e.g., IDocs generated in SAP S/4HANA and previous SAP ECC systems). The new interface can also generate values in a different waydifferently. Int4 IFTT by default compares the node alphabetically, but the issue can occur when the order of the same nodes will be are different (for example, IDOC qualifiers)
In such a case, in order to compare the reference and current output, we should follow the procedure described below.

...

Let's take an example where we want to do make an IDOC comparison. In order to do an validation of To validate the IDoc segments, including possible changes (segments may have been renamed, new ones may have been added or deleted), we need to perform an appropriate transformation for both the reference and the current message. For this purpose, we can take advantage of the XSLT transformation functionality.

In our example, we need to test IDoc's, that are IDocs generated with a diffferent different segment order than before (the message is still the same , but contains a different sorting sequence for some of the segments). In this case we We will use the XSLT transformation (shown below), which adds qualified to the parent node name. With this approach, the comparison of IDoc segments is correct even if some node values are different and we . We can also easily compare missing or additional nodes.

...

Please note , that the presented approach can serve as a template and depending . Depending on the case, the XSLT transformation (shown above) should be modified accordingly, so that the . The output in new interface solutions can be properly appropriately compared, including any relevant (also customer-specific) changes.