SAP MESSAGING Function Module for Output Determination Using the Condition Technique

Search SAP Function Modules

MESSAGING is a standard messaging SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Output Determination Using the Condition Technique 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 messaging FM, simply by entering the name MESSAGING into the relevant SAP transaction such as SE37 or SE38.

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

Function MESSAGING 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 'MESSAGING'"Output Determination Using the Condition Technique
  EXPORTING
*  APPLIKATION =  "Application
   MSG_OBJKY =  "Object Key
   SCHEMA =  "actually a required field; optiona
*  GRUPPENVERARBEITUNG =  "
*  PI_OBJTYPE =  "
*  PI_ITEM = ' ' "
*  PROTOCOL_ACCESS = 'X' "

 IMPORTING
   PE_UNPROCESSED_OUTPUT =  "

TABLES
   MSG_PART =  "

EXCEPTIONS
   APPLIKATION_NICHT_VORHANDEN = 1    SCHEMA_NICHT_VORHANDEN = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV61B_001 WFMC: Find Fax Number
EXIT_SAPLV61B_002 WFMC: Set Print Parameters

IMPORTING Parameters details for MESSAGING

APPLIKATION - Application

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

MSG_OBJKY - Object Key

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

SCHEMA - actually a required field; optiona

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

GRUPPENVERARBEITUNG -

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

PI_OBJTYPE -

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

PI_ITEM -

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

PROTOCOL_ACCESS -

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

EXPORTING Parameters details for MESSAGING

PE_UNPROCESSED_OUTPUT -

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

TABLES Parameters details for MESSAGING

MSG_PART -

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

EXCEPTIONS details

APPLIKATION_NICHT_VORHANDEN - Application Does Not Exist

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

SCHEMA_NICHT_VORHANDEN -

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

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

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