SAP PVSMC_MESSAGE_COLLECT Function Module for NOTRANSL: Nachricht in den Nachrichtensammler stellen

Search SAP Function Modules

PVSMC_MESSAGE_COLLECT is a standard pvsmc message collect SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Nachricht in den Nachrichtensammler stellen 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 pvsmc message collect FM, simply by entering the name PVSMC_MESSAGE_COLLECT into the relevant SAP transaction such as SE37 or SE38.

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

Function PVSMC_MESSAGE_COLLECT 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 'PVSMC_MESSAGE_COLLECT'"NOTRANSL: Nachricht in den Nachrichtensammler stellen
  EXPORTING
   MSGTY =  "Message Type
*  PROBCLASS = ' ' "Application log: Message problem class
   MSGID =  "Message Class
   MSGNO =  "Message Number
*  MSGV1 =  "Message Variable 1
*  MSGV2 =  "Message Variable 2
*  MSGV3 =  "Message Variable 3
*  MSGV4 =  "Message Variable 4
*  MSGTY_LIMIT_MIN =  "Message Type
*  DETLEVEL = ' ' "Application Log: Level of detail

 IMPORTING
   EX_MSG_HANDLER =  "Generic Type

EXCEPTIONS
   MESSAGE_NOT_COLLECTED = 1 

.

IMPORTING Parameters details for PVSMC_MESSAGE_COLLECT

MSGTY - Message Type

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

PROBCLASS - Application log: Message problem class

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

MSGID - Message Class

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

MSGNO - Message Number

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

MSGV1 - Message Variable 1

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

MSGV2 - Message Variable 2

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

MSGV3 - Message Variable 3

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

MSGV4 - Message Variable 4

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

MSGTY_LIMIT_MIN - Message Type

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

DETLEVEL - Application Log: Level of detail

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

EXPORTING Parameters details for PVSMC_MESSAGE_COLLECT

EX_MSG_HANDLER - Generic Type

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

EXCEPTIONS details

MESSAGE_NOT_COLLECTED - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

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

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