SAP JV_COLLECT_MESSAGE Function Module for Joint Venture Error Message Handling - Collection of Messages

Search SAP Function Modules

JV_COLLECT_MESSAGE is a standard jv collect message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Joint Venture Error Message Handling - Collection of Messages 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 jv collect message FM, simply by entering the name JV_COLLECT_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

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

Function JV_COLLECT_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 'JV_COLLECT_MESSAGE'"Joint Venture Error Message Handling - Collection of Messages
  EXPORTING
   MSGID =  "Message Identification Class
   MSGNO =  "Message Number - as defined in T100
   STATUS =  "Error Status:(A)bend,(E)rror,(W)arning,(I)nfo
*  VAR1 = ' ' "First variable to enter into the message
*  VAR2 = ' ' "Second variable to enter into the message
*  VAR3 = ' ' "Third message to enter into the message
*  VAR4 = ' ' "Fourth message to enter into the message

 IMPORTING
   MAX_SEVERITY =  "Maximum severity of recorded messages currently
   E_ACMESG =  "

EXCEPTIONS
   INCOMPLETE = 1 

.

IMPORTING Parameters details for JV_COLLECT_MESSAGE

MSGID - Message Identification Class

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

MSGNO - Message Number - as defined in T100

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

STATUS - Error Status:(A)bend,(E)rror,(W)arning,(I)nfo

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

VAR1 - First variable to enter into the message

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

VAR2 - Second variable to enter into the message

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

VAR3 - Third message to enter into the message

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

VAR4 - Fourth message to enter into the message

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

EXPORTING Parameters details for JV_COLLECT_MESSAGE

MAX_SEVERITY - Maximum severity of recorded messages currently

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

E_ACMESG -

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

EXCEPTIONS details

INCOMPLETE - Input Parameters are invalid

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

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

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