ISU_SAMPLE_R512 SAP Function module - Determine Budget Billing Amount for Payment Scheme

ISU_SAMPLE_R512 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISU_SAMPLE_R512 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EA61PS_EVENT
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_SAMPLE_R512 - ISU SAMPLE R512

CALL FUNCTION 'ISU_SAMPLE_R512' "Determine Budget Billing Amount for Payment Scheme
  EXPORTING
    x_obj =                     " isu25_paymentscheme  Payment Scheme Object
    x_ever =                    " ever          Contract, for which the Amount Is to Be Determined
    x_payfreq =                 " e_payfreq     Pay frequency
    x_paydate =                 " e_paydate     Payment Day
    x_edatum =                  " sy-datum      Creation/Adjustment Date
    x_emode =                   " e_mode        2 = Change, 3 = Create
    x_pending =                 " c             X = Payment Scheme Is Provisional
  TABLES
    xt_eabpl =                  " eabpl         Old Sample Lines and Lines with Extrapolation Amount
    xt_billtot =                " eps_bfa_amount  Invoice Amounts
    yt_eabpl_complete =         " eabpl         New Sample Lines
  EXCEPTIONS
    DATA_ERROR = 1              "               Data Error
    INPUT_ERROR = 2             "               Data invalid
    SYSTEM_ERROR = 3            "               Program error
    .  "  ISU_SAMPLE_R512

ABAP code example for Function Module ISU_SAMPLE_R512

The ABAP code below is a full code listing to execute function module ISU_SAMPLE_R512 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_xt_eabpl  
 
 TYPE STANDARD TABLE OF EABPL,"TABLES PARAM
wa_xt_eabpl
 
 LIKE LINE OF it_xt_eabpl
,
it_xt_billtot  
 
 TYPE STANDARD TABLE OF EPS_BFA_AMOUNT,"TABLES PARAM
wa_xt_billtot
 
 LIKE LINE OF it_xt_billtot
,
it_yt_eabpl_complete  
 
 TYPE STANDARD TABLE OF EABPL,"TABLES PARAM
wa_yt_eabpl_complete
 
 LIKE LINE OF it_yt_eabpl_complete
.


DATA(ld_x_obj) = 'Check type of data required'.

DATA(ld_x_ever) = 'Check type of data required'.

DATA(ld_x_payfreq) = 'Check type of data required'.

DATA(ld_x_paydate) = 'Check type of data required'.

DATA(ld_x_edatum) = '20210129'.

DATA(ld_x_emode) = '20210129'.

DATA(ld_x_pending) = '20210129'.
 

"populate fields of struture and append to itab
append wa_xt_eabpl to it_xt_eabpl.
 

"populate fields of struture and append to itab
append wa_xt_billtot to it_xt_billtot.
 

"populate fields of struture and append to itab
append wa_yt_eabpl_complete to it_yt_eabpl_complete.
.

CALL FUNCTION 'ISU_SAMPLE_R512'
  EXPORTING
    x_obj =                      ld_x_obj
    x_ever =                     ld_x_ever
    x_payfreq =                  ld_x_payfreq
    x_paydate =                  ld_x_paydate
    x_edatum =                   ld_x_edatum
    x_emode =                    ld_x_emode
    x_pending =                  ld_x_pending
  TABLES
    xt_eabpl =                   it_xt_eabpl
    xt_billtot =                 it_xt_billtot
    yt_eabpl_complete =          it_yt_eabpl_complete
  EXCEPTIONS
    DATA_ERROR =                 1
    INPUT_ERROR =                2
    SYSTEM_ERROR =               3
    .  "  ISU_SAMPLE_R512

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_x_obj
 
 TYPE ISU25_PAYMENTSCHEME ,
it_xt_eabpl
 
 TYPE STANDARD TABLE OF EABPL ,
wa_xt_eabpl
 
 LIKE LINE OF it_xt_eabpl,
ld_x_ever
 
 TYPE EVER ,
it_xt_billtot
 
 TYPE STANDARD TABLE OF EPS_BFA_AMOUNT ,
wa_xt_billtot
 
 LIKE LINE OF it_xt_billtot,
ld_x_payfreq
 
 TYPE E_PAYFREQ ,
it_yt_eabpl_complete
 
 TYPE STANDARD TABLE OF EABPL ,
wa_yt_eabpl_complete
 
 LIKE LINE OF it_yt_eabpl_complete,
ld_x_paydate
 
 TYPE E_PAYDATE ,
ld_x_edatum
 
 TYPE SY-DATUM ,
ld_x_emode
 
 TYPE E_MODE ,
ld_x_pending
 
 TYPE C .


ld_x_obj = '20210129'. 

"populate fields of struture and append to itab
append wa_xt_eabpl to it_xt_eabpl.
ld_x_ever = '20210129'. 

"populate fields of struture and append to itab
append wa_xt_billtot to it_xt_billtot.
ld_x_payfreq = '20210129'. 

"populate fields of struture and append to itab
append wa_yt_eabpl_complete to it_yt_eabpl_complete.
ld_x_paydate = '20210129'.
ld_x_edatum = '20210129'.
ld_x_emode = '20210129'.
ld_x_pending = '20210129'.