SAP BUS_CHANGE_DOCUMENT Function Module for









BUS_CHANGE_DOCUMENT is a standard bus change document 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 change document FM, simply by entering the name BUS_CHANGE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function BUS_CHANGE_DOCUMENT 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_CHANGE_DOCUMENT'"
EXPORTING
* I_OBJAP = "Application Object
* I_SORTK = '1' "Sort sequence
* I_XTECH = "
* I_POPUP = "
* I_XCHDOC = 'X' "
* I_XPLCHDOC = 'X' "
* I_XARCHIVE = "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
* I_XRAISE_EXCEPTION = ' ' "
* I_NO_OUTPUT = ' ' "

TABLES
* T_UDATE = "
* T_UNAME = "
* T_ABFLD = "
* T_SICHTTAB = "
* T_OBJECTID = "
* T_TABKEY = "Key of Table Line
* T_TABLEAUS1 = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for BUS_CHANGE_DOCUMENT

I_OBJAP - Application Object

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

I_SORTK - Sort sequence

Data type: BUS000FLDS-ABLSO
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XTECH -

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

I_POPUP -

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

I_XCHDOC -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XPLCHDOC -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XARCHIVE - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

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

I_XRAISE_EXCEPTION -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NO_OUTPUT -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BUS_CHANGE_DOCUMENT

T_UDATE -

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

T_UNAME -

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

T_ABFLD -

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

T_SICHTTAB -

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

T_OBJECTID -

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

T_TABKEY - Key of Table Line

Data type: BUS0TABKEYR
Optional: Yes
Call by Reference: Yes

T_TABLEAUS1 -

Data type: BUSCHGDOUT1
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - No documents found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUS_CHANGE_DOCUMENT 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:
lv_i_objap  TYPE TBZ1-OBJAP, "   
lt_t_udate  TYPE STANDARD TABLE OF BUS0DATER, "   
lv_not_found  TYPE BUS0DATER, "   
lv_i_sortk  TYPE BUS000FLDS-ABLSO, "   '1'
lt_t_uname  TYPE STANDARD TABLE OF BUS0NAMER, "   
lv_i_xtech  TYPE BUS000FLDS-XTECH, "   
lt_t_abfld  TYPE STANDARD TABLE OF BUS0ABFLDR, "   
lv_i_popup  TYPE C, "   
lt_t_sichttab  TYPE STANDARD TABLE OF BUS0SICHTR, "   
lv_i_xchdoc  TYPE BOOLE-BOOLE, "   'X'
lt_t_objectid  TYPE STANDARD TABLE OF BUS0AEND, "   
lt_t_tabkey  TYPE STANDARD TABLE OF BUS0TABKEYR, "   
lv_i_xplchdoc  TYPE BOOLE-BOOLE, "   'X'
lv_i_xarchive  TYPE BOOLE-BOOLE, "   
lt_t_tableaus1  TYPE STANDARD TABLE OF BUSCHGDOUT1, "   
lv_i_xraise_exception  TYPE BOOLE-BOOLE, "   SPACE
lv_i_no_output  TYPE BOOLE-BOOLE. "   SPACE

  CALL FUNCTION 'BUS_CHANGE_DOCUMENT'  "
    EXPORTING
         I_OBJAP = lv_i_objap
         I_SORTK = lv_i_sortk
         I_XTECH = lv_i_xtech
         I_POPUP = lv_i_popup
         I_XCHDOC = lv_i_xchdoc
         I_XPLCHDOC = lv_i_xplchdoc
         I_XARCHIVE = lv_i_xarchive
         I_XRAISE_EXCEPTION = lv_i_xraise_exception
         I_NO_OUTPUT = lv_i_no_output
    TABLES
         T_UDATE = lt_t_udate
         T_UNAME = lt_t_uname
         T_ABFLD = lt_t_abfld
         T_SICHTTAB = lt_t_sichttab
         T_OBJECTID = lt_t_objectid
         T_TABKEY = lt_t_tabkey
         T_TABLEAUS1 = lt_t_tableaus1
    EXCEPTIONS
        NOT_FOUND = 1
. " BUS_CHANGE_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM BUS_CHANGE_DOCUMENT

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 OBJAP FROM TBZ1 INTO @DATA(ld_i_objap).
 
 
 
"SELECT single ABLSO FROM BUS000FLDS INTO @DATA(ld_i_sortk).
DATA(ld_i_sortk) = '1'.
 
 
"SELECT single XTECH FROM BUS000FLDS INTO @DATA(ld_i_xtech).
 
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xchdoc).
DATA(ld_i_xchdoc) = 'X'.
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xplchdoc).
DATA(ld_i_xplchdoc) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xarchive).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xraise_exception).
DATA(ld_i_xraise_exception) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_no_output).
DATA(ld_i_no_output) = ' '.
 


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!