SAP SDOK_PERSISTENT_RELOC_READ Function Module for
SDOK_PERSISTENT_RELOC_READ is a standard sdok persistent reloc read 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 sdok persistent reloc read FM, simply by entering the name SDOK_PERSISTENT_RELOC_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDCR
Program Name: SAPLSDCR
Main Program: SAPLSDCR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SDOK_PERSISTENT_RELOC_READ 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 'SDOK_PERSISTENT_RELOC_READ'".
EXPORTING
RELOC_ID = "Relocation
BLOCK_NUM = "
IMPORTING
DESCRIPT = "
CREA_TIME = "
STATE = "
DEST_CAT = "
DEST_REP = "
X_FAULTY = "
TABLES
* COMPONENT_INFO = "
* BAD_OBJECTS = "
EXCEPTIONS
NOT_EXISTING = 1
IMPORTING Parameters details for SDOK_PERSISTENT_RELOC_READ
RELOC_ID - Relocation
Data type: SDOKRELOC-RELOC_IDOptional: No
Call by Reference: No ( called with pass by value option)
BLOCK_NUM -
Data type: SDOKRELOC-BLOCK_NUMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SDOK_PERSISTENT_RELOC_READ
DESCRIPT -
Data type: SDOKRELOC-DESCRIPTOptional: No
Call by Reference: No ( called with pass by value option)
CREA_TIME -
Data type: SDOKRELOC-CREA_TIMEOptional: No
Call by Reference: No ( called with pass by value option)
STATE -
Data type: SDOKRELOC-STATEOptional: No
Call by Reference: No ( called with pass by value option)
DEST_CAT -
Data type: SDOKRELOC-DEST_CATOptional: No
Call by Reference: No ( called with pass by value option)
DEST_REP -
Data type: SDOKRELOC-DEST_REPOptional: No
Call by Reference: No ( called with pass by value option)
X_FAULTY -
Data type: SY-DATAROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SDOK_PERSISTENT_RELOC_READ
COMPONENT_INFO -
Data type: SDOKRLOCCMOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_OBJECTS -
Data type: SDOKERRKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_EXISTING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SDOK_PERSISTENT_RELOC_READ 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_descript | TYPE SDOKRELOC-DESCRIPT, " | |||
| lv_reloc_id | TYPE SDOKRELOC-RELOC_ID, " | |||
| lv_not_existing | TYPE SDOKRELOC, " | |||
| lt_component_info | TYPE STANDARD TABLE OF SDOKRLOCCM, " | |||
| lv_block_num | TYPE SDOKRELOC-BLOCK_NUM, " | |||
| lv_crea_time | TYPE SDOKRELOC-CREA_TIME, " | |||
| lt_bad_objects | TYPE STANDARD TABLE OF SDOKERRKEY, " | |||
| lv_state | TYPE SDOKRELOC-STATE, " | |||
| lv_dest_cat | TYPE SDOKRELOC-DEST_CAT, " | |||
| lv_dest_rep | TYPE SDOKRELOC-DEST_REP, " | |||
| lv_x_faulty | TYPE SY-DATAR. " |
|   CALL FUNCTION 'SDOK_PERSISTENT_RELOC_READ' " |
| EXPORTING | ||
| RELOC_ID | = lv_reloc_id | |
| BLOCK_NUM | = lv_block_num | |
| IMPORTING | ||
| DESCRIPT | = lv_descript | |
| CREA_TIME | = lv_crea_time | |
| STATE | = lv_state | |
| DEST_CAT | = lv_dest_cat | |
| DEST_REP | = lv_dest_rep | |
| X_FAULTY | = lv_x_faulty | |
| TABLES | ||
| COMPONENT_INFO | = lt_component_info | |
| BAD_OBJECTS | = lt_bad_objects | |
| EXCEPTIONS | ||
| NOT_EXISTING = 1 | ||
| . " SDOK_PERSISTENT_RELOC_READ | ||
ABAP code using 7.40 inline data declarations to call FM SDOK_PERSISTENT_RELOC_READ
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 DESCRIPT FROM SDOKRELOC INTO @DATA(ld_descript). | ||||
| "SELECT single RELOC_ID FROM SDOKRELOC INTO @DATA(ld_reloc_id). | ||||
| "SELECT single BLOCK_NUM FROM SDOKRELOC INTO @DATA(ld_block_num). | ||||
| "SELECT single CREA_TIME FROM SDOKRELOC INTO @DATA(ld_crea_time). | ||||
| "SELECT single STATE FROM SDOKRELOC INTO @DATA(ld_state). | ||||
| "SELECT single DEST_CAT FROM SDOKRELOC INTO @DATA(ld_dest_cat). | ||||
| "SELECT single DEST_REP FROM SDOKRELOC INTO @DATA(ld_dest_rep). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_x_faulty). | ||||
Search for further information about these or an SAP related objects