Capabilities and limitations

RFC and SAP business objects

In Tricentis TDM Studio there is a difference between functions and business objects with regard to the way that data are copied to SAP. Within Tricentis TDM Studio itself, the handling is identical. However, functions initiate a transaction that must be explicitly closed by another function which triggers a Commit. Otherwise no written datum will be visible in the SAP target system.

On the other hand, data written to SAP via a business object method are immediately visible in the SAP system because Tricentis TDM Studio automatically triggers a Commit after this method was called.

In the end it will depend your specific situation whether functions or business objects are preferred. Functions are usually advantageous when a batch of related data is copied where the whole batch would be invalidated if a single datum were not to be written, for instance due to an error or a network problem.

Limitations

The TDM Wizard for SAP BAPI can only generate functions, templates and tasks that work with BAPI functions and business objects which are implemented in SAP. IDoc interfaces are not supported.

The Wizard also supports all SAP ABAP data types, with the exception of internal tables (ITAB). Although functions or business objects with internal tables can be processed by the Wizard, the Wizard can not read data from these tables or write them to a target. All other fields in structures with an internal table will be correctly processed, though.

In addition, the Wizard can not generate templates or tasks that create files for a batch import. However, this can be achieved using the internal Tricentis TDM Studio tools and without involving a Wizard. The Wizard also does not generate any code that could trigger a batch import.