SAP UCT8_MESSAGE Function Module for









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

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



Function UCT8_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 'UCT8_MESSAGE'"
  EXPORTING
   MSGID =  "Messages, Message Class
   MSGTY =  "Messages, Message Type
   MSGNO =  "Messages, Message Number
   MSGV1 =  "Messages, Message Variable
   MSGV2 =  "Messages, Message Variable
   MSGV3 =  "Messages, Message Variable
   MSGV4 =  "Messages, Message Variable

CHANGING
   CT_MESSAGE =  "Messages
.



IMPORTING Parameters details for UCT8_MESSAGE

MSGID - Messages, Message Class

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

MSGTY - Messages, Message Type

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

MSGNO - Messages, Message Number

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

MSGV1 - Messages, Message Variable

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

MSGV2 - Messages, Message Variable

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

MSGV3 - Messages, Message Variable

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

MSGV4 - Messages, Message Variable

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

CHANGING Parameters details for UCT8_MESSAGE

CT_MESSAGE - Messages

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

Copy and paste ABAP code example for UCT8_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_msgid  TYPE SYMSGID, "   
lv_ct_message  TYPE UC0_T_MESSAGE, "   
lv_msgty  TYPE SYMSGTY, "   
lv_msgno  TYPE SYMSGNO, "   
lv_msgv1  TYPE SYMSGV, "   
lv_msgv2  TYPE SYMSGV, "   
lv_msgv3  TYPE SYMSGV, "   
lv_msgv4  TYPE SYMSGV. "   

  CALL FUNCTION 'UCT8_MESSAGE'  "
    EXPORTING
         MSGID = lv_msgid
         MSGTY = lv_msgty
         MSGNO = lv_msgno
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
    CHANGING
         CT_MESSAGE = lv_ct_message
. " UCT8_MESSAGE




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

 
 
 
 
 
 
 
 


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!