SAP OBJECT_CHECK_DPR_OBJLNK Function Module for NOTRANSL: Prüfung, cProjectselement vorhanden - für Klassifizierung (sonst
OBJECT_CHECK_DPR_OBJLNK is a standard object check dpr objlnk SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfung, cProjectselement vorhanden - für Klassifizierung (sonst 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 object check dpr objlnk FM, simply by entering the name OBJECT_CHECK_DPR_OBJLNK into the relevant SAP transaction such as SE37 or SE38.
Function Group: OLR3_DMS_WORK
Program Name: SAPLOLR3_DMS_WORK
Main Program: SAPLOLR3_DMS_WORK
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_CHECK_DPR_OBJLNK 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 'OBJECT_CHECK_DPR_OBJLNK'"NOTRANSL: Prüfung, cProjectselement vorhanden - für Klassifizierung (sonst.
EXPORTING
* CALLED_FROM = 1 "
* LANGUAGE = SY-LANGU "
* LOCK = ' ' "
* SINGLE = ' ' "
* I_AUTH_CHK = ' ' "
IMPORTING
FAULT_TEXT = "
MESSAGE_TYPE = "
NO_AUTH = "
TABLES
OTAB = "Classification
EXCEPTIONS
FOREIGN_LOCK = 1 OBJECT_NOT_FOUND = 2 SYSTEM_FAILURE = 3
IMPORTING Parameters details for OBJECT_CHECK_DPR_OBJLNK
CALLED_FROM -
Data type:Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGUAGE -
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOCK -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SINGLE -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AUTH_CHK -
Data type: RMCLF-KREUZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OBJECT_CHECK_DPR_OBJLNK
FAULT_TEXT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTH -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OBJECT_CHECK_DPR_OBJLNK
OTAB - Classification
Data type: RMCLOBTXOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OBJECT_CHECK_DPR_OBJLNK 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: | ||||
| lt_otab | TYPE STANDARD TABLE OF RMCLOBTX, " | |||
| lv_fault_text | TYPE RMCLOBTX, " | |||
| lv_called_from | TYPE RMCLOBTX, " 1 | |||
| lv_foreign_lock | TYPE RMCLOBTX, " | |||
| lv_language | TYPE SY-LANGU, " SY-LANGU | |||
| lv_message_type | TYPE SY, " | |||
| lv_object_not_found | TYPE SY, " | |||
| lv_lock | TYPE SY, " SPACE | |||
| lv_no_auth | TYPE SY, " | |||
| lv_system_failure | TYPE SY, " | |||
| lv_single | TYPE SY, " SPACE | |||
| lv_i_auth_chk | TYPE RMCLF-KREUZ. " SPACE |
|   CALL FUNCTION 'OBJECT_CHECK_DPR_OBJLNK' "NOTRANSL: Prüfung, cProjectselement vorhanden - für Klassifizierung (sonst |
| EXPORTING | ||
| CALLED_FROM | = lv_called_from | |
| LANGUAGE | = lv_language | |
| LOCK | = lv_lock | |
| SINGLE | = lv_single | |
| I_AUTH_CHK | = lv_i_auth_chk | |
| IMPORTING | ||
| FAULT_TEXT | = lv_fault_text | |
| MESSAGE_TYPE | = lv_message_type | |
| NO_AUTH | = lv_no_auth | |
| TABLES | ||
| OTAB | = lt_otab | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| OBJECT_NOT_FOUND = 2 | ||
| SYSTEM_FAILURE = 3 | ||
| . " OBJECT_CHECK_DPR_OBJLNK | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_CHECK_DPR_OBJLNK
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_called_from) | = 1. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| DATA(ld_lock) | = ' '. | |||
| DATA(ld_single) | = ' '. | |||
| "SELECT single KREUZ FROM RMCLF INTO @DATA(ld_i_auth_chk). | ||||
| DATA(ld_i_auth_chk) | = ' '. | |||
Search for further information about these or an SAP related objects