SAP LMBP_STEP_PUSH Function Module for Append transaction step to the presentation flow stack









LMBP_STEP_PUSH is a standard lmbp step push SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Append transaction step to the presentation flow stack processing and below is the pattern details for this FM, 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 lmbp step push FM, simply by entering the name LMBP_STEP_PUSH into the relevant SAP transaction such as SE37 or SE38.

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



Function LMBP_STEP_PUSH 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 'LMBP_STEP_PUSH'"Append transaction step to the presentation flow stack
  EXPORTING
*  I_INIFLG =  "Flag of the beginning of transaction
   IS_RLMBP =  "Additional fields in Mobile Presentation
*  IT_MENU =  "Menu
*  IT_MOVE =  "Move
*  IT_ACTUAL =  "Actual tasks data
*  IT_DO =  "Operation
*  IT_STEP_VERIF =  "Verification profile
   IT_PARAM =  "Parameters
*  IT_DATA =  "

 IMPORTING
   O_PUSHED =  "General Flag

CHANGING
   CS_TRPRP =  "Transaction properties
*  CT_STEP =  "Steps stack
.



IMPORTING Parameters details for LMBP_STEP_PUSH

I_INIFLG - Flag of the beginning of transaction

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

IS_RLMBP - Additional fields in Mobile Presentation

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

IT_MENU - Menu

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

IT_MOVE - Move

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

IT_ACTUAL - Actual tasks data

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

IT_DO - Operation

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

IT_STEP_VERIF - Verification profile

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

IT_PARAM - Parameters

Data type: LMBPT_IT_PARAM
Optional: No
Call by Reference: Yes

IT_DATA -

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

EXPORTING Parameters details for LMBP_STEP_PUSH

O_PUSHED - General Flag

Data type: FLAG
Optional: No
Call by Reference: Yes

CHANGING Parameters details for LMBP_STEP_PUSH

CS_TRPRP - Transaction properties

Data type: LMBPT_TRPRP
Optional: No
Call by Reference: Yes

CT_STEP - Steps stack

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

Copy and paste ABAP code example for LMBP_STEP_PUSH 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_cs_trprp  TYPE LMBPT_TRPRP, "   
lv_i_iniflg  TYPE LMBP_FLAG_INI_TRANS, "   
lv_o_pushed  TYPE FLAG, "   
lv_ct_step  TYPE LMBPT_IT_SCRSTACK, "   
lv_is_rlmbp  TYPE RLMBP, "   
lv_it_menu  TYPE LMBPT_IT_MENU, "   
lv_it_move  TYPE LMBPT_IT_MOVE, "   
lv_it_actual  TYPE LMBPT_IT_ACTUAL, "   
lv_it_do  TYPE LMBPT_IT_DO, "   
lv_it_step_verif  TYPE LMBPT_IT_VERIF_PROFILE, "   
lv_it_param  TYPE LMBPT_IT_PARAM, "   
lv_it_data  TYPE ABAP_FUNC_PARMBIND_TAB. "   

  CALL FUNCTION 'LMBP_STEP_PUSH'  "Append transaction step to the presentation flow stack
    EXPORTING
         I_INIFLG = lv_i_iniflg
         IS_RLMBP = lv_is_rlmbp
         IT_MENU = lv_it_menu
         IT_MOVE = lv_it_move
         IT_ACTUAL = lv_it_actual
         IT_DO = lv_it_do
         IT_STEP_VERIF = lv_it_step_verif
         IT_PARAM = lv_it_param
         IT_DATA = lv_it_data
    IMPORTING
         O_PUSHED = lv_o_pushed
    CHANGING
         CS_TRPRP = lv_cs_trprp
         CT_STEP = lv_ct_step
. " LMBP_STEP_PUSH




ABAP code using 7.40 inline data declarations to call FM LMBP_STEP_PUSH

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.

 
 
 
 
 
 
 
 
 
 
 
 


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!