SAP BUS_DI_COMPLETE Function Module for









BUS_DI_COMPLETE is a standard bus di complete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bus di complete FM, simply by entering the name BUS_DI_COMPLETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BUSS
Program Name: SAPLBUSS
Main Program: SAPLBUSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BUS_DI_COMPLETE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BUS_DI_COMPLETE'"
EXPORTING
* I_XTEST = "Indicator: Test Run

TABLES
* I_ERROR = "Error Message Table
.



IMPORTING Parameters details for BUS_DI_COMPLETE

I_XTEST - Indicator: Test Run

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for BUS_DI_COMPLETE

I_ERROR - Error Message Table

Data type: BUSSPROT_X
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BUS_DI_COMPLETE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lt_i_error  TYPE STANDARD TABLE OF BUSSPROT_X, "   
lv_i_xtest  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'BUS_DI_COMPLETE'  "
    EXPORTING
         I_XTEST = lv_i_xtest
    TABLES
         I_ERROR = lt_i_error
. " BUS_DI_COMPLETE




ABAP code using 7.40 inline data declarations to call FM BUS_DI_COMPLETE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xtest).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!