SAP EXIT_SAPMJG01_011 Function Module for IS-M: Define Default Payment Method

Search SAP Function Modules

EXIT_SAPMJG01_011 is a standard exit sapmjg01 011 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Define Default Payment Method 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 sapmjg01 011 FM, simply by entering the name EXIT_SAPMJG01_011 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPMJG01_011 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_SAPMJG01_011'"IS-M: Define Default Payment Method
  EXPORTING
   JGTSADR_IN =  "Address Data
   KOART =  "Customer/Vendor Account Type
*  RJG01_IN =  "BP Screen Fields
*  JGTGPNR_IN =  "Business Partner
*  TJG39_IN =  "Business Partner Roles
*  KNVV_IN =  "Sales Data
*  KNB1_IN =  "Company Code Data

CHANGING
   ZWELS =  "PMethod

.

IMPORTING Parameters details for EXIT_SAPMJG01_011

JGTSADR_IN - Address Data

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

KOART - Customer/Vendor Account Type

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

RJG01_IN - BP Screen Fields

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

JGTGPNR_IN - Business Partner

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

TJG39_IN - Business Partner Roles

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

KNVV_IN - Sales Data

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

KNB1_IN - Company Code Data

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

CHANGING Parameters details for EXIT_SAPMJG01_011

ZWELS - PMethod

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

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

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