SAP KBPS_MSG_HEADLINE Function Module for









KBPS_MSG_HEADLINE is a standard kbps msg headline 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 kbps msg headline FM, simply by entering the name KBPS_MSG_HEADLINE into the relevant SAP transaction such as SE37 or SE38.

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



Function KBPS_MSG_HEADLINE 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 'KBPS_MSG_HEADLINE'"
EXPORTING
APPLIK = "
* OBJNR = ' ' "
* POSIT = ' ' "
* GEBER = ' ' "

IMPORTING
MSGV1 = "
MSGV2 = "
MSGV3 = "
MSGV4 = "

TABLES
* I_BPAK = "
* I_MESG_REFERENCE = "
* E_HEADLINES = "
.



IMPORTING Parameters details for KBPS_MSG_HEADLINE

APPLIK -

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

OBJNR -

Data type: BPIN-OBJNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POSIT -

Data type: BPIN-POSIT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

GEBER -

Data type: BPIN-GEBER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for KBPS_MSG_HEADLINE

MSGV1 -

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

MSGV2 -

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

MSGV3 -

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

MSGV4 -

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

TABLES Parameters details for KBPS_MSG_HEADLINE

I_BPAK -

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

I_MESG_REFERENCE -

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

E_HEADLINES -

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

Copy and paste ABAP code example for KBPS_MSG_HEADLINE 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_msgv1  TYPE MESG-MSGV1, "   
lv_applik  TYPE BPIN-APPLIK, "   
lt_i_bpak  TYPE STANDARD TABLE OF BPAK, "   
lv_msgv2  TYPE MESG-MSGV2, "   
lv_objnr  TYPE BPIN-OBJNR, "   SPACE
lt_i_mesg_reference  TYPE STANDARD TABLE OF BPBU_T_REFERENCE, "   
lv_msgv3  TYPE MESG-MSGV3, "   
lv_posit  TYPE BPIN-POSIT, "   SPACE
lt_e_headlines  TYPE STANDARD TABLE OF MESG, "   
lv_geber  TYPE BPIN-GEBER, "   SPACE
lv_msgv4  TYPE MESG-MSGV4. "   

  CALL FUNCTION 'KBPS_MSG_HEADLINE'  "
    EXPORTING
         APPLIK = lv_applik
         OBJNR = lv_objnr
         POSIT = lv_posit
         GEBER = lv_geber
    IMPORTING
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
    TABLES
         I_BPAK = lt_i_bpak
         I_MESG_REFERENCE = lt_i_mesg_reference
         E_HEADLINES = lt_e_headlines
. " KBPS_MSG_HEADLINE




ABAP code using 7.40 inline data declarations to call FM KBPS_MSG_HEADLINE

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.

"SELECT single MSGV1 FROM MESG INTO @DATA(ld_msgv1).
 
"SELECT single APPLIK FROM BPIN INTO @DATA(ld_applik).
 
 
"SELECT single MSGV2 FROM MESG INTO @DATA(ld_msgv2).
 
"SELECT single OBJNR FROM BPIN INTO @DATA(ld_objnr).
DATA(ld_objnr) = ' '.
 
 
"SELECT single MSGV3 FROM MESG INTO @DATA(ld_msgv3).
 
"SELECT single POSIT FROM BPIN INTO @DATA(ld_posit).
DATA(ld_posit) = ' '.
 
 
"SELECT single GEBER FROM BPIN INTO @DATA(ld_geber).
DATA(ld_geber) = ' '.
 
"SELECT single MSGV4 FROM MESG INTO @DATA(ld_msgv4).
 


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!