SAP FMCA_TRM_ESOA_PAYMENTS_GET Function Module for
FMCA_TRM_ESOA_PAYMENTS_GET is a standard fmca trm esoa payments get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fmca trm esoa payments get FM, simply by entering the name FMCA_TRM_ESOA_PAYMENTS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_TRM_ESOA_F4
Program Name: SAPLFMCA_TRM_ESOA_F4
Main Program: SAPLFMCA_TRM_ESOA_F4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FMCA_TRM_ESOA_PAYMENTS_GET 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 'FMCA_TRM_ESOA_PAYMENTS_GET'".
EXPORTING
I_GPART = "Business Partner Number
* I_DATE_LOW = "Posting Date in the Document
* I_DATE_HIGH = "Posting Date in the Document
* I_FBNUM = "Number of Form Bundle
* I_ABTYP_PS = "Revenue Type
* I_PERSL = "Key for Period Assignment
IMPORTING
ET_PAYMENTS = "Payment Information for TRM Web Service
ET_ITEMS = "Cleared Items for TRM Web Service
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for FMCA_TRM_ESOA_PAYMENTS_GET
I_GPART - Business Partner Number
Data type: GPART_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_LOW - Posting Date in the Document
Data type: BUDATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_HIGH - Posting Date in the Document
Data type: BUDATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FBNUM - Number of Form Bundle
Data type: FBNUM_PSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ABTYP_PS - Revenue Type
Data type: ABTYP_PS_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PERSL - Key for Period Assignment
Data type: PERSL_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMCA_TRM_ESOA_PAYMENTS_GET
ET_PAYMENTS - Payment Information for TRM Web Service
Data type: FMCA_SOA_PAYINFO_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_ITEMS - Cleared Items for TRM Web Service
Data type: FMCA_SOA_CLEARED_ITEMS_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMCA_TRM_ESOA_PAYMENTS_GET 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_gpart | TYPE GPART_KK, " | |||
| lv_et_payments | TYPE FMCA_SOA_PAYINFO_T, " | |||
| lv_et_items | TYPE FMCA_SOA_CLEARED_ITEMS_T, " | |||
| lv_i_date_low | TYPE BUDAT, " | |||
| lv_et_return | TYPE BAPIRETTAB, " | |||
| lv_i_date_high | TYPE BUDAT, " | |||
| lv_i_fbnum | TYPE FBNUM_PS, " | |||
| lv_i_abtyp_ps | TYPE ABTYP_PS_KK, " | |||
| lv_i_persl | TYPE PERSL_KK. " |
|   CALL FUNCTION 'FMCA_TRM_ESOA_PAYMENTS_GET' " |
| EXPORTING | ||
| I_GPART | = lv_i_gpart | |
| I_DATE_LOW | = lv_i_date_low | |
| I_DATE_HIGH | = lv_i_date_high | |
| I_FBNUM | = lv_i_fbnum | |
| I_ABTYP_PS | = lv_i_abtyp_ps | |
| I_PERSL | = lv_i_persl | |
| IMPORTING | ||
| ET_PAYMENTS | = lv_et_payments | |
| ET_ITEMS | = lv_et_items | |
| ET_RETURN | = lv_et_return | |
| . " FMCA_TRM_ESOA_PAYMENTS_GET | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_TRM_ESOA_PAYMENTS_GET
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