SAP FM_PAYTR_READ_DOCUMENTS_FI Function Module for
FM_PAYTR_READ_DOCUMENTS_FI is a standard fm paytr read documents fi 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 fm paytr read documents fi FM, simply by entering the name FM_PAYTR_READ_DOCUMENTS_FI into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMPA
Program Name: SAPLFMPA
Main Program: SAPLFMPA
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_PAYTR_READ_DOCUMENTS_FI 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 'FM_PAYTR_READ_DOCUMENTS_FI'".
EXPORTING
* I_RC_ACTIVE = ' ' "
* I_PERFORM_AVC = ' ' "
* I_PERFORM_V2 = ' ' "
* I_ARCH_DONE = ' ' "
* I_ARCH_RUN_MODE = ' ' "
CHANGING
* C_FLG_R2 = "
TABLES
T_FI_KEYS = "
T_HEADER = "
T_ITEMS = "
* T_RAGL1 = "
* T_CLEARED_ITEMS = "
* T_TRANSFER = "Documents to Be Transferred
* T_TRANSFER_DOCS = "Documents to Be Transferred
EXCEPTIONS
FI_HEADER_MISSING = 1
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_SAPLFMPA_001 RFFMS200: Fill User Dimension
EXIT_SAPLFMPA_002 RFFMS200: Deactivate Conversion of Credit Memos
EXIT_SAPLFMPA_003 RFFMS200: Activating the V2 update
EXIT_SAPLFMPA_004 RFFMS200: Payment Records for Credit Memos not Statistical
EXIT_SAPLFMPA_005 RFFMS200: Activate Conversion of 60-50 Invoices
EXIT_SAPLFMPA_006 RFFMS200: Deactivate Conversion of Overpayments
IMPORTING Parameters details for FM_PAYTR_READ_DOCUMENTS_FI
I_RC_ACTIVE -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PERFORM_AVC -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PERFORM_V2 -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ARCH_DONE -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ARCH_RUN_MODE -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FM_PAYTR_READ_DOCUMENTS_FI
C_FLG_R2 -
Data type: COptional: Yes
Call by Reference: Yes
TABLES Parameters details for FM_PAYTR_READ_DOCUMENTS_FI
T_FI_KEYS -
Data type: FMPA_T_FI_HEADER_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
T_HEADER -
Data type: FMPA_T_FI_HEADER_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
T_ITEMS -
Data type: FMPA_T_FI_ITEM_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
T_RAGL1 -
Data type: RAGL1Optional: Yes
Call by Reference: No ( called with pass by value option)
T_CLEARED_ITEMS -
Data type: FMPA_T_FI_HEADER_TYPEOptional: Yes
Call by Reference: Yes
T_TRANSFER - Documents to Be Transferred
Data type: FMPA_T_TRANSFER_DOCSOptional: Yes
Call by Reference: Yes
T_TRANSFER_DOCS - Documents to Be Transferred
Data type: FMPA_T_TRANSFER_DOCSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FI_HEADER_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FM_PAYTR_READ_DOCUMENTS_FI 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_c_flg_r2 | TYPE C, " | |||
| lt_t_fi_keys | TYPE STANDARD TABLE OF FMPA_T_FI_HEADER_TYPE, " | |||
| lv_i_rc_active | TYPE C, " SPACE | |||
| lv_fi_header_missing | TYPE C, " | |||
| lt_t_header | TYPE STANDARD TABLE OF FMPA_T_FI_HEADER_TYPE, " | |||
| lv_i_perform_avc | TYPE C, " SPACE | |||
| lt_t_items | TYPE STANDARD TABLE OF FMPA_T_FI_ITEM_TYPE, " | |||
| lv_i_perform_v2 | TYPE C, " SPACE | |||
| lt_t_ragl1 | TYPE STANDARD TABLE OF RAGL1, " | |||
| lv_i_arch_done | TYPE C, " SPACE | |||
| lv_i_arch_run_mode | TYPE C, " SPACE | |||
| lt_t_cleared_items | TYPE STANDARD TABLE OF FMPA_T_FI_HEADER_TYPE, " | |||
| lt_t_transfer | TYPE STANDARD TABLE OF FMPA_T_TRANSFER_DOCS, " | |||
| lt_t_transfer_docs | TYPE STANDARD TABLE OF FMPA_T_TRANSFER_DOCS. " |
|   CALL FUNCTION 'FM_PAYTR_READ_DOCUMENTS_FI' " |
| EXPORTING | ||
| I_RC_ACTIVE | = lv_i_rc_active | |
| I_PERFORM_AVC | = lv_i_perform_avc | |
| I_PERFORM_V2 | = lv_i_perform_v2 | |
| I_ARCH_DONE | = lv_i_arch_done | |
| I_ARCH_RUN_MODE | = lv_i_arch_run_mode | |
| CHANGING | ||
| C_FLG_R2 | = lv_c_flg_r2 | |
| TABLES | ||
| T_FI_KEYS | = lt_t_fi_keys | |
| T_HEADER | = lt_t_header | |
| T_ITEMS | = lt_t_items | |
| T_RAGL1 | = lt_t_ragl1 | |
| T_CLEARED_ITEMS | = lt_t_cleared_items | |
| T_TRANSFER | = lt_t_transfer | |
| T_TRANSFER_DOCS | = lt_t_transfer_docs | |
| EXCEPTIONS | ||
| FI_HEADER_MISSING = 1 | ||
| . " FM_PAYTR_READ_DOCUMENTS_FI | ||
ABAP code using 7.40 inline data declarations to call FM FM_PAYTR_READ_DOCUMENTS_FI
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.| DATA(ld_i_rc_active) | = ' '. | |||
| DATA(ld_i_perform_avc) | = ' '. | |||
| DATA(ld_i_perform_v2) | = ' '. | |||
| DATA(ld_i_arch_done) | = ' '. | |||
| DATA(ld_i_arch_run_mode) | = ' '. | |||
Search for further information about these or an SAP related objects