SAP LMBP_STEP_DISPLAY Function Module for Display transaction step









LMBP_STEP_DISPLAY is a standard lmbp step display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display transaction step 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 display FM, simply by entering the name LMBP_STEP_DISPLAY 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_DISPLAY 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_DISPLAY'"Display  transaction step
  EXPORTING
   IS_RLMBP =  "Additional fields in Mobile Presentation
*  IS_TRPRP =  "Transaction properties

 IMPORTING
   O_ERROR =  "Presentation error code
   OS_RLMBP =  "Additional fields in Mobile Presentation
   OS_TRPRP =  "Transaction properties

CHANGING
*  CT_MOVE =  "Move
*  CT_ACTUAL =  "Tasks actual data
*  CT_DO =  "Operation
*  CT_STEP_VERIF =  "Verification profile
*  CT_FCODE_PROFILE =  "Pushbutton profile
   CT_PARAM =  "Parameters
*  CT_DATA =  "
.



IMPORTING Parameters details for LMBP_STEP_DISPLAY

IS_RLMBP - Additional fields in Mobile Presentation

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

IS_TRPRP - Transaction properties

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

EXPORTING Parameters details for LMBP_STEP_DISPLAY

O_ERROR - Presentation error code

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

OS_RLMBP - Additional fields in Mobile Presentation

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

OS_TRPRP - Transaction properties

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

CHANGING Parameters details for LMBP_STEP_DISPLAY

CT_MOVE - Move

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

CT_ACTUAL - Tasks actual data

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

CT_DO - Operation

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

CT_STEP_VERIF - Verification profile

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

CT_FCODE_PROFILE - Pushbutton profile

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

CT_PARAM - Parameters

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

CT_DATA -

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

Copy and paste ABAP code example for LMBP_STEP_DISPLAY 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_ct_move  TYPE LMBPT_IT_MOVE, "   
lv_o_error  TYPE LMBP_ERROR, "   
lv_is_rlmbp  TYPE RLMBP, "   
lv_is_trprp  TYPE LMBPT_TRPRP, "   
lv_os_rlmbp  TYPE RLMBP, "   
lv_ct_actual  TYPE LMBPT_IT_ACTUAL, "   
lv_ct_do  TYPE LMBPT_IT_DO, "   
lv_os_trprp  TYPE LMBPT_TRPRP, "   
lv_ct_step_verif  TYPE LMBPT_IT_VERIF_PROFILE, "   
lv_ct_fcode_profile  TYPE LMBPT_IT_PB_PROFILE, "   
lv_ct_param  TYPE LMBPT_IT_PARAM, "   
lv_ct_data  TYPE ABAP_FUNC_PARMBIND_TAB. "   

  CALL FUNCTION 'LMBP_STEP_DISPLAY'  "Display transaction step
    EXPORTING
         IS_RLMBP = lv_is_rlmbp
         IS_TRPRP = lv_is_trprp
    IMPORTING
         O_ERROR = lv_o_error
         OS_RLMBP = lv_os_rlmbp
         OS_TRPRP = lv_os_trprp
    CHANGING
         CT_MOVE = lv_ct_move
         CT_ACTUAL = lv_ct_actual
         CT_DO = lv_ct_do
         CT_STEP_VERIF = lv_ct_step_verif
         CT_FCODE_PROFILE = lv_ct_fcode_profile
         CT_PARAM = lv_ct_param
         CT_DATA = lv_ct_data
. " LMBP_STEP_DISPLAY




ABAP code using 7.40 inline data declarations to call FM LMBP_STEP_DISPLAY

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!