Writing a Report


A report must be written for each BAPI that can be used in the DX Workbench, in order to support the analysis phase. It is needed to generate IDocs for existing objects in a file. In particular, it generates IDocs for a BAPI call whose parameters have been filled with data from an existing object.


The following conventions apply to the report interface:

·        A parameter for the receiver of the IDoc is a required import parameter, in addition to the fields for selecting the objects.

·        Because the DX Workbench uses this report to write the IDocs to a special file, the receivers are passed on automatically as soon as the report is called. As a result, this field must be defined with “parameters: receiver like tbdlst-logsys no-display.” or select-options: receiver for tbdlst-logsys no-display.

·        Additional, optional parameters may be present, but they are not used by the DX Workbench.

The flow logic of the report is written as follows:

·        The report first collects all the relevant data for the objects the user has selected. This can be performed, for example, using the corresponding GetDetail() BAPIs for the objects.

·        It then calls the generated ALE outbound function module to generate the IDoc (also see Generating the BAPI-ALE Interface) with the data collected above. This generates outbound IDocs in the database.

If the user has already maintained outbound partner agreements and a file port, then these outbound IDocs are written to an outbound file – where the DX Workbench finds them and converts them to inbound IDocs, which are available to analyze the underlying structures (also see Analyzing SAP Structures).


·        The report must have parameter RECEIVER of type TBDLST-LOGSYS.

·        The report does not determine ALE receivers.
No receiver determination may be performed, because although the DX Workbench requires customizing of partner agreement and port, it does not require a logical system to be assigned to the current client.