SAP OIUP_ARFC_SHADOW_SELECT Function Module for Select Shadow Data via ARFC (4.6C) - Not Used In ERP
OIUP_ARFC_SHADOW_SELECT is a standard oiup arfc shadow select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Select Shadow Data via ARFC (4.6C) - Not Used In ERP 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 oiup arfc shadow select FM, simply by entering the name OIUP_ARFC_SHADOW_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUP
Program Name: SAPLOIUP
Main Program: SAPLOIUP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUP_ARFC_SHADOW_SELECT 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 'OIUP_ARFC_SHADOW_SELECT'"Select Shadow Data via ARFC (4.6C) - Not Used In ERP.
EXPORTING
PRA_TABLE_NAME = "PDM Enabled PRA Table Name
PDM_GUID = "Unique 32 Byte GUID
WHERE_CLAUSE = "Where Clause
FOR_ALL_ENTRIES_ITAB = "FOR ALL ENTRIES ITAB
IMPORTING
NEARLINE_RECORDS_FETCHED = "Nearline Records Fetched
OIUP_PR_WCDVLH_ITAB = "OIUP_PR_WCDVLH Internal Table Type
OIUPH_RV_RJE_ITAB = "OIUPH_RV_RJE Internal Table Type
EXCEPTIONS
SYSTEM_CONFIG_READ_ERROR = 1
IMPORTING Parameters details for OIUP_ARFC_SHADOW_SELECT
PRA_TABLE_NAME - PDM Enabled PRA Table Name
Data type: TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PDM_GUID - Unique 32 Byte GUID
Data type: GUID_32Optional: No
Call by Reference: No ( called with pass by value option)
WHERE_CLAUSE - Where Clause
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
FOR_ALL_ENTRIES_ITAB - FOR ALL ENTRIES ITAB
Data type: OIUP_STRING_ITABOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIUP_ARFC_SHADOW_SELECT
NEARLINE_RECORDS_FETCHED - Nearline Records Fetched
Data type: SY-DBCNTOptional: No
Call by Reference: No ( called with pass by value option)
OIUP_PR_WCDVLH_ITAB - OIUP_PR_WCDVLH Internal Table Type
Data type: OIUP_PR_WCDVLH_ITABOptional: No
Call by Reference: No ( called with pass by value option)
OIUPH_RV_RJE_ITAB - OIUPH_RV_RJE Internal Table Type
Data type: OIUPH_RV_RJE_ITABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SYSTEM_CONFIG_READ_ERROR - Error Reading System / Configuration Information
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUP_ARFC_SHADOW_SELECT 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_pra_table_name | TYPE TABNAME, " | |||
| lv_nearline_records_fetched | TYPE SY-DBCNT, " | |||
| lv_system_config_read_error | TYPE SY, " | |||
| lv_pdm_guid | TYPE GUID_32, " | |||
| lv_oiup_pr_wcdvlh_itab | TYPE OIUP_PR_WCDVLH_ITAB, " | |||
| lv_where_clause | TYPE STRING, " | |||
| lv_oiuph_rv_rje_itab | TYPE OIUPH_RV_RJE_ITAB, " | |||
| lv_for_all_entries_itab | TYPE OIUP_STRING_ITAB. " |
|   CALL FUNCTION 'OIUP_ARFC_SHADOW_SELECT' "Select Shadow Data via ARFC (4.6C) - Not Used In ERP |
| EXPORTING | ||
| PRA_TABLE_NAME | = lv_pra_table_name | |
| PDM_GUID | = lv_pdm_guid | |
| WHERE_CLAUSE | = lv_where_clause | |
| FOR_ALL_ENTRIES_ITAB | = lv_for_all_entries_itab | |
| IMPORTING | ||
| NEARLINE_RECORDS_FETCHED | = lv_nearline_records_fetched | |
| OIUP_PR_WCDVLH_ITAB | = lv_oiup_pr_wcdvlh_itab | |
| OIUPH_RV_RJE_ITAB | = lv_oiuph_rv_rje_itab | |
| EXCEPTIONS | ||
| SYSTEM_CONFIG_READ_ERROR = 1 | ||
| . " OIUP_ARFC_SHADOW_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM OIUP_ARFC_SHADOW_SELECT
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 DBCNT FROM SY INTO @DATA(ld_nearline_records_fetched). | ||||
Search for further information about these or an SAP related objects