SAP ISU_SAMPLE_R530 Function Module for Execute Amount Checks

Search SAP Function Modules

ISU_SAMPLE_R530 is a standard isu sample r530 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute Amount Checks 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 isu sample r530 FM, simply by entering the name ISU_SAMPLE_R530 into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_SAMPLE_R530 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 'ISU_SAMPLE_R530'"Execute Amount Checks
  EXPORTING
   X_OBJ =  "
   XT_EABPLBASE =  "
   XT_EABPLADJ =  "
   X_AMOUNT =  "Amount in Transaction Currency with +/- Sign
*  X_CHNGDAT = SY-DATUM "Date
*  X_TERMTDAT = SY-DATUM "Date
   X_SINGLELINECOMP =  "Indicator
   X_ROLLIN =  "Indicator
   X_CHNGPROTECT =  "

 IMPORTING
   Y_LIMITFAIL =  "
   Y_PROTECTED =  "

CHANGING
*  XY_REASSESSFAIL = ' ' "Indicator

TABLES
*  XT_COMPLINES =  "Line Comparison Structure for Validation
*  XT_REFLINES =  "Line Comparison Structure for Validation

.

IMPORTING Parameters details for ISU_SAMPLE_R530

X_OBJ -

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

XT_EABPLBASE -

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

XT_EABPLADJ -

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

X_AMOUNT - Amount in Transaction Currency with +/- Sign

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

X_CHNGDAT - Date

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

X_TERMTDAT - Date

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

X_SINGLELINECOMP - Indicator

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

X_ROLLIN - Indicator

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

X_CHNGPROTECT -

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

EXPORTING Parameters details for ISU_SAMPLE_R530

Y_LIMITFAIL -

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

Y_PROTECTED -

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

CHANGING Parameters details for ISU_SAMPLE_R530

XY_REASSESSFAIL - Indicator

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

TABLES Parameters details for ISU_SAMPLE_R530

XT_COMPLINES - Line Comparison Structure for Validation

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

XT_REFLINES - Line Comparison Structure for Validation

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

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

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