SAP EXIT_SAPMJV41_001 Function Module for Determine Further Output Partners









EXIT_SAPMJV41_001 is a standard exit sapmjv41 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Further Output Partners 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 exit sapmjv41 001 FM, simply by entering the name EXIT_SAPMJV41_001 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPMJV41_001 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 'EXIT_SAPMJV41_001'"Determine Further Output Partners
EXPORTING
F_JVTFEHLER = "

TABLES
PART = "
.



IMPORTING Parameters details for EXIT_SAPMJV41_001

F_JVTFEHLER -

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

TABLES Parameters details for EXIT_SAPMJV41_001

PART -

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

Copy and paste ABAP code example for EXIT_SAPMJV41_001 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:
lt_part  TYPE STANDARD TABLE OF MSGPA, "   
lv_f_jvtfehler  TYPE JVTFEHLER. "   

  CALL FUNCTION 'EXIT_SAPMJV41_001'  "Determine Further Output Partners
    EXPORTING
         F_JVTFEHLER = lv_f_jvtfehler
    TABLES
         PART = lt_part
. " EXIT_SAPMJV41_001




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMJV41_001

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!