SAP BUS_SAVE Function Module for









BUS_SAVE is a standard bus save 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 save FM, simply by entering the name BUS_SAVE 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_SAVE 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_SAVE'"
EXPORTING
* I_OBJAP = ' ' "Application Object
* I_XUPDTASK = 'X' "
* I_XINIT_MEMORY = 'X' "

IMPORTING
EV_MESSAGE_SEVERITY = "

TABLES
* T_KEY = "
* ET_MESSAGE = "CBP: Message for each object
.



IMPORTING Parameters details for BUS_SAVE

I_OBJAP - Application Object

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

I_XUPDTASK -

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

I_XINIT_MEMORY -

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

EXPORTING Parameters details for BUS_SAVE

EV_MESSAGE_SEVERITY -

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

TABLES Parameters details for BUS_SAVE

T_KEY -

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

ET_MESSAGE - CBP: Message for each object

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

Copy and paste ABAP code example for BUS_SAVE 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_t_key  TYPE STANDARD TABLE OF BUSSKEY, "   
lv_i_objap  TYPE TBZ1-OBJAP, "   SPACE
lv_ev_message_severity  TYPE SYSUBRC, "   
lt_et_message  TYPE STANDARD TABLE OF BUS0MSG1, "   
lv_i_xupdtask  TYPE BOOLE-BOOLE, "   'X'
lv_i_xinit_memory  TYPE BOOLE-BOOLE. "   'X'

  CALL FUNCTION 'BUS_SAVE'  "
    EXPORTING
         I_OBJAP = lv_i_objap
         I_XUPDTASK = lv_i_xupdtask
         I_XINIT_MEMORY = lv_i_xinit_memory
    IMPORTING
         EV_MESSAGE_SEVERITY = lv_ev_message_severity
    TABLES
         T_KEY = lt_t_key
         ET_MESSAGE = lt_et_message
. " BUS_SAVE




ABAP code using 7.40 inline data declarations to call FM BUS_SAVE

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).
DATA(ld_i_objap) = ' '.
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xupdtask).
DATA(ld_i_xupdtask) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xinit_memory).
DATA(ld_i_xinit_memory) = 'X'.
 


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!