SAP LMBP_STEP_FETCH Function Module for Select next step of presentation device transaction









LMBP_STEP_FETCH is a standard lmbp step fetch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Select next step of presentation device transaction 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 fetch FM, simply by entering the name LMBP_STEP_FETCH 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_FETCH 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_FETCH'"Select next step of presentation device transaction
EXPORTING
I_APPLC = "Application
I_LOCAT = "Site
I_FROM_STEP = "Transaction step
I_FCODE = "Function code

IMPORTING
O_LINK = "Mobile transaction step flow

EXCEPTIONS
STEP_NOT_FOUND = 1
.



IMPORTING Parameters details for LMBP_STEP_FETCH

I_APPLC - Application

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

I_LOCAT - Site

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

I_FROM_STEP - Transaction step

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

I_FCODE - Function code

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

EXPORTING Parameters details for LMBP_STEP_FETCH

O_LINK - Mobile transaction step flow

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

EXCEPTIONS details

STEP_NOT_FOUND -

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

Copy and paste ABAP code example for LMBP_STEP_FETCH 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_o_link  TYPE LSTLN, "   
lv_i_applc  TYPE LMBP_APPLC, "   
lv_step_not_found  TYPE LMBP_APPLC, "   
lv_i_locat  TYPE LMBP_LOCAT, "   
lv_i_from_step  TYPE LMBP_STEP, "   
lv_i_fcode  TYPE LMBP_FCODE. "   

  CALL FUNCTION 'LMBP_STEP_FETCH'  "Select next step of presentation device transaction
    EXPORTING
         I_APPLC = lv_i_applc
         I_LOCAT = lv_i_locat
         I_FROM_STEP = lv_i_from_step
         I_FCODE = lv_i_fcode
    IMPORTING
         O_LINK = lv_o_link
    EXCEPTIONS
        STEP_NOT_FOUND = 1
. " LMBP_STEP_FETCH




ABAP code using 7.40 inline data declarations to call FM LMBP_STEP_FETCH

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!