SAP MM_ARRANG_CHECK_REGU_CUSTSETT Function Module for NOTRANSL: Regulierungsanforderung pruefen Kundenabrechnung

Search SAP Function Modules

MM_ARRANG_CHECK_REGU_CUSTSETT is a standard mm arrang check regu custsett 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: Regulierungsanforderung pruefen Kundenabrechnung 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 mm arrang check regu custsett FM, simply by entering the name MM_ARRANG_CHECK_REGU_CUSTSETT into the relevant SAP transaction such as SE37 or SE38.

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

Function MM_ARRANG_CHECK_REGU_CUSTSETT 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 'MM_ARRANG_CHECK_REGU_CUSTSETT'"NOTRANSL: Regulierungsanforderung pruefen Kundenabrechnung
  EXPORTING
   I_WBTYP =  "Settlement Request: Payment Type
   I_WRTYP =  "Entry category: payment
   I_LFTYP =  "Agency Business: Billing Category
   I_WDTYP =  "Agency Business: Document Category
   I_RFBSK =  "Status for Transfer to Accounting
   I_WRART =  "Agency Business: Payment Type

 IMPORTING
   E_READ_SUBRC =  "Return Value, Return Value after ABAP Statements
   E_TMZR =  "Agency Business: Payment Types

EXCEPTIONS
   INVALID_WRART = 1 

.

IMPORTING Parameters details for MM_ARRANG_CHECK_REGU_CUSTSETT

I_WBTYP - Settlement Request: Payment Type

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

I_WRTYP - Entry category: payment

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

I_LFTYP - Agency Business: Billing Category

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

I_WDTYP - Agency Business: Document Category

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

I_RFBSK - Status for Transfer to Accounting

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

I_WRART - Agency Business: Payment Type

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

EXPORTING Parameters details for MM_ARRANG_CHECK_REGU_CUSTSETT

E_READ_SUBRC - Return Value, Return Value after ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

E_TMZR - Agency Business: Payment Types

Data type: TMZR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_WRART - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

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

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