SAP LMBP_STEP_MESSAGE_DISPLAY Function Module for Display user's message

Search SAP Function Modules

LMBP_STEP_MESSAGE_DISPLAY is a standard lmbp step message 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 user's message 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 message display FM, simply by entering the name LMBP_STEP_MESSAGE_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_MESSAGE_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_MESSAGE_DISPLAY'"Display user's message
  EXPORTING
*  I_MSGTY = 'I' "
*  IS_TRPRP =  "Transaction properties
*  I_MSGNO =  "
*  I_MSGID =  "
*  I_MSGV1 =  "
*  I_MSGV2 =  "
*  I_MSGV3 =  "
*  I_MSGV4 =  "
*  I_MESSAGE =  "Message for the resource
*  IS_RLMBP =  "Screen properties

 IMPORTING
   O_ANSWER =  "Answer: Yes or No

.

IMPORTING Parameters details for LMBP_STEP_MESSAGE_DISPLAY

I_MSGTY -

Data type:
Default: 'I'
Optional: Yes
Call by Reference: Yes

IS_TRPRP - Transaction properties

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

I_MSGNO -

Data type:
Optional: Yes
Call by Reference: Yes

I_MSGID -

Data type:
Optional: Yes
Call by Reference: Yes

I_MSGV1 -

Data type:
Optional: Yes
Call by Reference: Yes

I_MSGV2 -

Data type:
Optional: Yes
Call by Reference: Yes

I_MSGV3 -

Data type:
Optional: Yes
Call by Reference: Yes

I_MSGV4 -

Data type:
Optional: Yes
Call by Reference: Yes

I_MESSAGE - Message for the resource

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

IS_RLMBP - Screen properties

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

EXPORTING Parameters details for LMBP_STEP_MESSAGE_DISPLAY

O_ANSWER - Answer: Yes or No

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

Copy and paste ABAP code example for LMBP_STEP_MESSAGE_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.

ABAP code using 7.40 inline data declarations to call FM LMBP_STEP_MESSAGE_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