SAP CTBI_WRITE_MESSAGE Function Module for









CTBI_WRITE_MESSAGE is a standard ctbi write message 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 ctbi write message FM, simply by entering the name CTBI_WRITE_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function CTBI_WRITE_MESSAGE 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 'CTBI_WRITE_MESSAGE'"
  EXPORTING
   MSGID =  "
   MSGNO =  "
   MSGTY =  "
*  MSGV1 = ' ' "
*  MSGV2 = ' ' "
*  MSGV3 = ' ' "
*  MSGV4 = ' ' "
*  MSGV5 = ' ' "

 IMPORTING
   ERROR =  "
   MESSG =  "
   MSGLN =  "
.



IMPORTING Parameters details for CTBI_WRITE_MESSAGE

MSGID -

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

MSGNO -

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

MSGTY -

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

MSGV1 -

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

MSGV2 -

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

MSGV3 -

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

MSGV4 -

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

MSGV5 -

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

EXPORTING Parameters details for CTBI_WRITE_MESSAGE

ERROR -

Data type:
Optional: No
Call by Reference: Yes

MESSG -

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

MSGLN -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CTBI_WRITE_MESSAGE 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_error  TYPE STRING, "   
lv_msgid  TYPE SY-MSGID, "   
lv_messg  TYPE CLMESSAGE, "   
lv_msgno  TYPE SY-MSGNO, "   
lv_msgln  TYPE SY, "   
lv_msgty  TYPE SY-MSGTY, "   
lv_msgv1  TYPE SY, "   SPACE
lv_msgv2  TYPE SY, "   SPACE
lv_msgv3  TYPE SY, "   SPACE
lv_msgv4  TYPE SY, "   SPACE
lv_msgv5  TYPE SY. "   SPACE

  CALL FUNCTION 'CTBI_WRITE_MESSAGE'  "
    EXPORTING
         MSGID = lv_msgid
         MSGNO = lv_msgno
         MSGTY = lv_msgty
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
         MSGV5 = lv_msgv5
    IMPORTING
         ERROR = lv_error
         MESSG = lv_messg
         MSGLN = lv_msgln
. " CTBI_WRITE_MESSAGE




ABAP code using 7.40 inline data declarations to call FM CTBI_WRITE_MESSAGE

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 MSGID FROM SY INTO @DATA(ld_msgid).
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno).
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty).
 
DATA(ld_msgv1) = ' '.
 
DATA(ld_msgv2) = ' '.
 
DATA(ld_msgv3) = ' '.
 
DATA(ld_msgv4) = ' '.
 
DATA(ld_msgv5) = ' '.
 


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!