SAP FRE_POOP_CHK_READ_DATA Function Module for Read Purchase order data
FRE_POOP_CHK_READ_DATA is a standard fre poop chk read data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Purchase order data 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 fre poop chk read data FM, simply by entering the name FRE_POOP_CHK_READ_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRE_SUPPORT_TOOLS
Program Name: SAPLFRE_SUPPORT_TOOLS
Main Program: SAPLFRE_SUPPORT_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FRE_POOP_CHK_READ_DATA 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 'FRE_POOP_CHK_READ_DATA'"Read Purchase order data.
EXPORTING
* IF_ONLY_OPEN_PO = 'X' "Read Opend Purchase Orders only
* IT_ART_SITE = "Article site combination - F&R relevant
* IRT_AEDAT = "Creation Date Range (Only using Article Site combination)
* IRT_ORDNO = "Order Proposal Document Number Range
* IRT_EBELN = "Purchasing Document Number Range
* IRT_UPTYP = "Unterpositionstyp Einkaufsbeleg
* I_STRUCT = "Additional check for components
CHANGING
CT_OPI = "Purchase Order data - FRE_CHECK_PO_OP
* CT_CPS = "Change pointer data
EXCEPTIONS
CHECK_INPUT = 1
IMPORTING Parameters details for FRE_POOP_CHK_READ_DATA
IF_ONLY_OPEN_PO - Read Opend Purchase Orders only
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_ART_SITE - Article site combination - F&R relevant
Data type: FRE_WERKS_MATNR_TTYOptional: Yes
Call by Reference: No ( called with pass by value option)
IRT_AEDAT - Creation Date Range (Only using Article Site combination)
Data type: FRE_ERDAT_RTTYOptional: Yes
Call by Reference: No ( called with pass by value option)
IRT_ORDNO - Order Proposal Document Number Range
Data type: FRE_ORDNO_RTTYOptional: Yes
Call by Reference: No ( called with pass by value option)
IRT_EBELN - Purchasing Document Number Range
Data type: FRE_EBELN_RTTYOptional: Yes
Call by Reference: No ( called with pass by value option)
IRT_UPTYP - Unterpositionstyp Einkaufsbeleg
Data type: FRE_UPTYP_RTTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_STRUCT - Additional check for components
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FRE_POOP_CHK_READ_DATA
CT_OPI - Purchase Order data - FRE_CHECK_PO_OP
Data type: FRE_POOP_CHK_DATA_OPI_TTYOptional: No
Call by Reference: No ( called with pass by value option)
CT_CPS - Change pointer data
Data type: FRE_POOP_CHK_PO_KEY_TTYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CHECK_INPUT - Check Input Parameters
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FRE_POOP_CHK_READ_DATA 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_ct_opi | TYPE FRE_POOP_CHK_DATA_OPI_TTY, " | |||
| lv_check_input | TYPE FRE_POOP_CHK_DATA_OPI_TTY, " | |||
| lv_if_only_open_po | TYPE XFELD, " 'X' | |||
| lv_ct_cps | TYPE FRE_POOP_CHK_PO_KEY_TTY, " | |||
| lv_it_art_site | TYPE FRE_WERKS_MATNR_TTY, " | |||
| lv_irt_aedat | TYPE FRE_ERDAT_RTTY, " | |||
| lv_irt_ordno | TYPE FRE_ORDNO_RTTY, " | |||
| lv_irt_ebeln | TYPE FRE_EBELN_RTTY, " | |||
| lv_irt_uptyp | TYPE FRE_UPTYP_RTTY, " | |||
| lv_i_struct | TYPE CHAR1. " |
|   CALL FUNCTION 'FRE_POOP_CHK_READ_DATA' "Read Purchase order data |
| EXPORTING | ||
| IF_ONLY_OPEN_PO | = lv_if_only_open_po | |
| IT_ART_SITE | = lv_it_art_site | |
| IRT_AEDAT | = lv_irt_aedat | |
| IRT_ORDNO | = lv_irt_ordno | |
| IRT_EBELN | = lv_irt_ebeln | |
| IRT_UPTYP | = lv_irt_uptyp | |
| I_STRUCT | = lv_i_struct | |
| CHANGING | ||
| CT_OPI | = lv_ct_opi | |
| CT_CPS | = lv_ct_cps | |
| EXCEPTIONS | ||
| CHECK_INPUT = 1 | ||
| . " FRE_POOP_CHK_READ_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FRE_POOP_CHK_READ_DATA
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_if_only_open_po) | = 'X'. | |||
Search for further information about these or an SAP related objects