SAP PAYMENTREQUEST_INTERACTION Function Module for List for Release, Payment, Cancelation

Search SAP Function Modules

PAYMENTREQUEST_INTERACTION is a standard paymentrequest interaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for List for Release, Payment, Cancelation 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 paymentrequest interaction FM, simply by entering the name PAYMENTREQUEST_INTERACTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: 2021
Program Name: SAPL2021
Main Program: SAPL2021
Appliation area:
Release date: 26-Nov-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function PAYMENTREQUEST_INTERACTION 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 'PAYMENTREQUEST_INTERACTION'"List for Release, Payment, Cancelation
  EXPORTING
*  RELEASEPOST =  "Release Payment Request for Posting
*  RELEASEPAY =  "Release Payment Request for Payment
*  PAY =  "Payment Request is to be Paid
*  CANCEL =  "Payment Request is to be Canceled
*  VARIANT =  "Layout (External Use)

 IMPORTING
   RETURN =  "Return Parameter

TABLES
   REQUESTID =  "Selection of Payment Request Key
*  RNG_DEFAULT_FIELDS =  "Range for Default Fields for the Display
   REQUESTID_ACTION =  "Key Number of the Payment Requests to be Released

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPL2021_001 User Exit for Creation BAPI: Check
EXIT_SAPL2021_002 User Exit for Creation BAPI: Processing
EXIT_SAPL2021_003 User Exit for GetList BAPI: Check
EXIT_SAPL2021_004 User Exit for GetList BAPI: Restrict Selection
EXIT_SAPL2021_005 User Exit for Cancel BAPI: Check
EXIT_SAPL2021_006 User Exit for Cancel BAPI: Update Customer Data
EXIT_SAPL2021_007 User Exit for Post BAPI: Check
EXIT_SAPL2021_008 User Exit for Post BAPI: Update Customer Data
EXIT_SAPL2021_009 User Exit for Release BAPI: Check
EXIT_SAPL2021_010 User Exit for Release BAPI: Update Customer Data

IMPORTING Parameters details for PAYMENTREQUEST_INTERACTION

RELEASEPOST - Release Payment Request for Posting

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

RELEASEPAY - Release Payment Request for Payment

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

PAY - Payment Request is to be Paid

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

CANCEL - Payment Request is to be Canceled

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

VARIANT - Layout (External Use)

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

EXPORTING Parameters details for PAYMENTREQUEST_INTERACTION

RETURN - Return Parameter

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

TABLES Parameters details for PAYMENTREQUEST_INTERACTION

REQUESTID - Selection of Payment Request Key

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

RNG_DEFAULT_FIELDS - Range for Default Fields for the Display

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

REQUESTID_ACTION - Key Number of the Payment Requests to be Released

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

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

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