SAP TRCA_PAYMENTREQUEST_GETSTATUS Function Module for TR Interface: Determine Status of Payment Request
TRCA_PAYMENTREQUEST_GETSTATUS is a standard trca paymentrequest getstatus 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 Interface: Determine Status of Payment Request 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 trca paymentrequest getstatus FM, simply by entering the name TRCA_PAYMENTREQUEST_GETSTATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: TRCA013
Program Name: SAPLTRCA013
Main Program: SAPLTRCA013
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TRCA_PAYMENTREQUEST_GETSTATUS 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 'TRCA_PAYMENTREQUEST_GETSTATUS'"TR Interface: Determine Status of Payment Request.
EXPORTING
* I_KEYNO = "a) Schlüsselnummer
* I_OBJ_TYPE = "b1) Referenzvorgang (AWTYP)
* I_OBJ_KEY = "b2) Referenzschlüssel (AWKEY)
* I_OBJ_SYS = "b3) Logisches System (AWSYS)
EXCEPTIONS
NOT_FOUND = 1 IS_POSTED_PRELIMINARY = 2 IS_LOCKED_IN_PROPOSAL = 3 IS_BLOCKED_FOR_PAYMENT = 4 IS_RELEASED_ALREADY = 5 IS_PAID_ALREADY = 6 IS_REVERSED_ALREADY = 7 ERROR = 8
IMPORTING Parameters details for TRCA_PAYMENTREQUEST_GETSTATUS
I_KEYNO - a) Schlüsselnummer
Data type: PAYRQ-KEYNOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJ_TYPE - b1) Referenzvorgang (AWTYP)
Data type: AWTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJ_KEY - b2) Referenzschlüssel (AWKEY)
Data type: AWKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJ_SYS - b3) Logisches System (AWSYS)
Data type: AWSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Payment Request Not Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IS_POSTED_PRELIMINARY - Zahlungsanordnung ist vorerfasst
Data type:Optional: No
Call by Reference: Yes
IS_LOCKED_IN_PROPOSAL - Zahlungsanordnung ist durch einen Vorschlagslauf gesperrt
Data type:Optional: No
Call by Reference: Yes
IS_BLOCKED_FOR_PAYMENT - Zahlungsanordnung ist zur Zahlung gesperrt
Data type:Optional: No
Call by Reference: Yes
IS_RELEASED_ALREADY - Zahlungsanordnung ist bereits freigegeben
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IS_PAID_ALREADY - Zahlungsanordnung ist bereits bezahlt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IS_REVERSED_ALREADY - Zahlungsanordnung ist bereist storniert
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR - Release Not Possible
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRCA_PAYMENTREQUEST_GETSTATUS 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: | ||||
| lv_i_keyno | TYPE PAYRQ-KEYNO, " | |||
| lv_not_found | TYPE PAYRQ, " | |||
| lv_i_obj_type | TYPE AWTYP, " | |||
| lv_is_posted_preliminary | TYPE AWTYP, " | |||
| lv_i_obj_key | TYPE AWKEY, " | |||
| lv_is_locked_in_proposal | TYPE AWKEY, " | |||
| lv_i_obj_sys | TYPE AWSYS, " | |||
| lv_is_blocked_for_payment | TYPE AWSYS, " | |||
| lv_is_released_already | TYPE AWSYS, " | |||
| lv_is_paid_already | TYPE AWSYS, " | |||
| lv_is_reversed_already | TYPE AWSYS, " | |||
| lv_error | TYPE AWSYS. " |
|   CALL FUNCTION 'TRCA_PAYMENTREQUEST_GETSTATUS' "TR Interface: Determine Status of Payment Request |
| EXPORTING | ||
| I_KEYNO | = lv_i_keyno | |
| I_OBJ_TYPE | = lv_i_obj_type | |
| I_OBJ_KEY | = lv_i_obj_key | |
| I_OBJ_SYS | = lv_i_obj_sys | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| IS_POSTED_PRELIMINARY = 2 | ||
| IS_LOCKED_IN_PROPOSAL = 3 | ||
| IS_BLOCKED_FOR_PAYMENT = 4 | ||
| IS_RELEASED_ALREADY = 5 | ||
| IS_PAID_ALREADY = 6 | ||
| IS_REVERSED_ALREADY = 7 | ||
| ERROR = 8 | ||
| . " TRCA_PAYMENTREQUEST_GETSTATUS | ||
ABAP code using 7.40 inline data declarations to call FM TRCA_PAYMENTREQUEST_GETSTATUS
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 KEYNO FROM PAYRQ INTO @DATA(ld_i_keyno). | ||||
Search for further information about these or an SAP related objects