SAP MAU2_CLEARING_OVERPAYMENT Function Module for TR Loans: FU Create Posting for MAUZ









MAU2_CLEARING_OVERPAYMENT is a standard mau2 clearing overpayment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TR Loans: FU Create Posting for MAUZ 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 mau2 clearing overpayment FM, simply by entering the name MAU2_CLEARING_OVERPAYMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function MAU2_CLEARING_OVERPAYMENT 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 'MAU2_CLEARING_OVERPAYMENT'"TR Loans: FU Create Posting for MAUZ
  EXPORTING
*  BLDAT = SY-DATUM "
*  EXPORT_BEPP = ' ' "
   I_TAB_BSID =  "Table Type for Table BSID
*  BTCI = 'X' "
*  BUDAT = SY-DATUM "
*  CALLT = ' ' "
*  MAPPE = SY-UNAME "
*  PROTOCOL = 'X' "
*  START_DAY = ' ' "
*  START_TIME = ' ' "
*  S_PRIMANOTA = ' ' "

CHANGING
*  X_NVORGANG = ' ' "Transaction Number
*  X_FLG_SINGLE_IP =  "General Flag

TABLES
   BEKI =  "
*  T_ADDBEPP =  "Additional Information on VDBEPP
*  T_VDBEKI_OLD =  "Flow Data: Document Header for Actual Record
*  T_ZEVRANL =  "Loans
   PAY_BSEG =  "
   T_TVZ01 =  "
   T_VDARL =  "
   UBEPI =  "
   UVERT_BEPP =  "
   LOANREF =  "
   T_TZPAB =  "
*  T_VDBEPP =  "Transaction Data - Plan Item

EXCEPTIONS
   POSTING_ERROR = 1    PROGRAM_ERROR = 2
.



IMPORTING Parameters details for MAU2_CLEARING_OVERPAYMENT

BLDAT -

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

EXPORT_BEPP -

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

I_TAB_BSID - Table Type for Table BSID

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

BTCI -

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

BUDAT -

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

CALLT -

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

MAPPE -

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

PROTOCOL -

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

START_DAY -

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

START_TIME -

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

S_PRIMANOTA -

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

CHANGING Parameters details for MAU2_CLEARING_OVERPAYMENT

X_NVORGANG - Transaction Number

Data type: VDBEPP-NVORGANG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_FLG_SINGLE_IP - General Flag

Data type: FLAG
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for MAU2_CLEARING_OVERPAYMENT

BEKI -

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

T_ADDBEPP - Additional Information on VDBEPP

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

T_VDBEKI_OLD - Flow Data: Document Header for Actual Record

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

T_ZEVRANL - Loans

Data type: VDARL
Optional: Yes
Call by Reference: Yes

PAY_BSEG -

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

T_TVZ01 -

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

T_VDARL -

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

UBEPI -

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

UVERT_BEPP -

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

LOANREF -

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

T_TZPAB -

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

T_VDBEPP - Transaction Data - Plan Item

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

EXCEPTIONS details

POSTING_ERROR -

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

PROGRAM_ERROR -

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

Copy and paste ABAP code example for MAU2_CLEARING_OVERPAYMENT 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_beki  TYPE STANDARD TABLE OF VDBEKI, "   
lv_bldat  TYPE SY-DATUM, "   SY-DATUM
lv_x_nvorgang  TYPE VDBEPP-NVORGANG, "   ' '
lv_posting_error  TYPE VDBEPP, "   
lt_t_addbepp  TYPE STANDARD TABLE OF ADDBEPP, "   
lv_export_bepp  TYPE ADDBEPP, "   ' '
lv_i_tab_bsid  TYPE TRTY_BSID, "   
lt_t_vdbeki_old  TYPE STANDARD TABLE OF VDBEKI, "   
lt_t_zevranl  TYPE STANDARD TABLE OF VDARL, "   
lv_btci  TYPE VDARL, "   'X'
lt_pay_bseg  TYPE STANDARD TABLE OF BSSBSEG, "   
lv_program_error  TYPE BSSBSEG, "   
lv_x_flg_single_ip  TYPE FLAG, "   
lv_budat  TYPE SY-DATUM, "   SY-DATUM
lt_t_tvz01  TYPE STANDARD TABLE OF TVZ01, "   
lv_callt  TYPE TVZ01, "   ' '
lt_t_vdarl  TYPE STANDARD TABLE OF VDARL, "   
lv_mappe  TYPE VDARL, "   SY-UNAME
lt_ubepi  TYPE STANDARD TABLE OF VDBEPI, "   
lv_protocol  TYPE VDBEPI, "   'X'
lt_uvert_bepp  TYPE STANDARD TABLE OF VDBEPP, "   
lt_loanref  TYPE STANDARD TABLE OF LOANREF, "   
lv_start_day  TYPE LOANREF, "   SPACE
lt_t_tzpab  TYPE STANDARD TABLE OF TZPAB, "   
lv_start_time  TYPE TZPAB, "   SPACE
lt_t_vdbepp  TYPE STANDARD TABLE OF VDBEPP, "   
lv_s_primanota  TYPE VDBEKI-RPNSUP. "   SPACE

  CALL FUNCTION 'MAU2_CLEARING_OVERPAYMENT'  "TR Loans: FU Create Posting for MAUZ
    EXPORTING
         BLDAT = lv_bldat
         EXPORT_BEPP = lv_export_bepp
         I_TAB_BSID = lv_i_tab_bsid
         BTCI = lv_btci
         BUDAT = lv_budat
         CALLT = lv_callt
         MAPPE = lv_mappe
         PROTOCOL = lv_protocol
         START_DAY = lv_start_day
         START_TIME = lv_start_time
         S_PRIMANOTA = lv_s_primanota
    CHANGING
         X_NVORGANG = lv_x_nvorgang
         X_FLG_SINGLE_IP = lv_x_flg_single_ip
    TABLES
         BEKI = lt_beki
         T_ADDBEPP = lt_t_addbepp
         T_VDBEKI_OLD = lt_t_vdbeki_old
         T_ZEVRANL = lt_t_zevranl
         PAY_BSEG = lt_pay_bseg
         T_TVZ01 = lt_t_tvz01
         T_VDARL = lt_t_vdarl
         UBEPI = lt_ubepi
         UVERT_BEPP = lt_uvert_bepp
         LOANREF = lt_loanref
         T_TZPAB = lt_t_tzpab
         T_VDBEPP = lt_t_vdbepp
    EXCEPTIONS
        POSTING_ERROR = 1
        PROGRAM_ERROR = 2
. " MAU2_CLEARING_OVERPAYMENT




ABAP code using 7.40 inline data declarations to call FM MAU2_CLEARING_OVERPAYMENT

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.

 
"SELECT single DATUM FROM SY INTO @DATA(ld_bldat).
DATA(ld_bldat) = SY-DATUM.
 
"SELECT single NVORGANG FROM VDBEPP INTO @DATA(ld_x_nvorgang).
DATA(ld_x_nvorgang) = ' '.
 
 
 
DATA(ld_export_bepp) = ' '.
 
 
 
 
DATA(ld_btci) = 'X'.
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_budat).
DATA(ld_budat) = SY-DATUM.
 
 
DATA(ld_callt) = ' '.
 
 
DATA(ld_mappe) = SY-UNAME.
 
 
DATA(ld_protocol) = 'X'.
 
 
 
DATA(ld_start_day) = ' '.
 
 
DATA(ld_start_time) = ' '.
 
 
"SELECT single RPNSUP FROM VDBEKI INTO @DATA(ld_s_primanota).
DATA(ld_s_primanota) = ' '.
 


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!