SAP EHPRC_CP_LB03_TRACE_MSG Function Module for

Search SAP Function Modules

EHPRC_CP_LB03_TRACE_MSG is a standard ehprc cp lb03 trace msg 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 ehprc cp lb03 trace msg FM, simply by entering the name EHPRC_CP_LB03_TRACE_MSG into the relevant SAP transaction such as SE37 or SE38.

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

Function EHPRC_CP_LB03_TRACE_MSG 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 'EHPRC_CP_LB03_TRACE_MSG'"
  EXPORTING
*  I_MSGTY = SY-MSGTY "
*  I_ALSORT =  "
*  I_MSGID = SY-MSGID "
*  I_MSGNO = SY-MSGNO "
*  I_MSGV1 = SY-MSGV1 "
*  I_MSGV2 = SY-MSGV2 "
*  I_MSGV3 = SY-MSGV3 "
*  I_MSGV4 = SY-MSGV4 "
*  I_DETLEVEL =  "
*  I_PROBCLASS =  "

 IMPORTING
   ES_BALMI =  "

CHANGING
*  XT_BALMI =  "

.

IMPORTING Parameters details for EHPRC_CP_LB03_TRACE_MSG

I_MSGTY -

Data type: BALMI-MSGTY
Default: SY-MSGTY
Optional: Yes
Call by Reference: Yes

I_ALSORT -

Data type: BALMI-ALSORT
Optional: Yes
Call by Reference: Yes

I_MSGID -

Data type: BALMI-MSGID
Default: SY-MSGID
Optional: Yes
Call by Reference: Yes

I_MSGNO -

Data type: BALMI-MSGNO
Default: SY-MSGNO
Optional: Yes
Call by Reference: Yes

I_MSGV1 -

Data type: BALMI-MSGV1
Default: SY-MSGV1
Optional: Yes
Call by Reference: Yes

I_MSGV2 -

Data type: BALMI-MSGV2
Default: SY-MSGV2
Optional: Yes
Call by Reference: Yes

I_MSGV3 -

Data type: BALMI-MSGV3
Default: SY-MSGV3
Optional: Yes
Call by Reference: Yes

I_MSGV4 -

Data type: BALMI-MSGV4
Default: SY-MSGV4
Optional: Yes
Call by Reference: Yes

I_DETLEVEL -

Data type: BALMI-DETLEVEL
Optional: Yes
Call by Reference: Yes

I_PROBCLASS -

Data type: BALMI-PROBCLASS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for EHPRC_CP_LB03_TRACE_MSG

ES_BALMI -

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

CHANGING Parameters details for EHPRC_CP_LB03_TRACE_MSG

XT_BALMI -

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

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

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