SAP OBJECT_CHECK_PLOGI Function Module for
OBJECT_CHECK_PLOGI is a standard object check plogi 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 object check plogi FM, simply by entering the name OBJECT_CHECK_PLOGI into the relevant SAP transaction such as SE37 or SE38.
Function Group: DFOBJECTR3E_CLASS
Program Name: SAPLDFOBJECTR3E_CLASS
Main Program: /ISDFPS/SAPLBADI_DVS
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_CHECK_PLOGI 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_PLOGI'".
EXPORTING
* CALLED_FROM = 1 "
* LANGUAGE = SY-LANGU "
* LOCK = ' ' "
* SINGLE = ' ' "
* DATE_OF_CHANGE = "
* I_AUTH_CHK = ' ' "
IMPORTING
FAULT_TEXT = "
MEINS = "
MESSAGE_TYPE = "
NO_AUTH = "
DISTRIBUTION_LOCK = "
TABLES
OTAB = "
EXCEPTIONS
FOREIGN_LOCK = 1 OBJECT_NOT_FOUND = 2 SYSTEM_FAILURE = 3
IMPORTING Parameters details for OBJECT_CHECK_PLOGI
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)
DATE_OF_CHANGE -
Data type: RMCLF-DATUV1Optional: 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_PLOGI
FAULT_TEXT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MEINS -
Data type: MARA-MEINSOptional: 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)
DISTRIBUTION_LOCK -
Data type: T141-DLOCKOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OBJECT_CHECK_PLOGI
OTAB -
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: Yes
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OBJECT_CHECK_PLOGI 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_meins | TYPE MARA-MEINS, " | |||
| lv_language | TYPE SY-LANGU, " SY-LANGU | |||
| lv_object_not_found | TYPE SY, " | |||
| lv_lock | TYPE SY, " SPACE | |||
| lv_message_type | TYPE SY, " | |||
| lv_system_failure | TYPE SY, " | |||
| lv_single | TYPE SY, " SPACE | |||
| lv_no_auth | TYPE SY, " | |||
| lv_date_of_change | TYPE RMCLF-DATUV1, " | |||
| lv_distribution_lock | TYPE T141-DLOCK, " | |||
| lv_i_auth_chk | TYPE RMCLF-KREUZ. " SPACE |
|   CALL FUNCTION 'OBJECT_CHECK_PLOGI' " |
| EXPORTING | ||
| CALLED_FROM | = lv_called_from | |
| LANGUAGE | = lv_language | |
| LOCK | = lv_lock | |
| SINGLE | = lv_single | |
| DATE_OF_CHANGE | = lv_date_of_change | |
| I_AUTH_CHK | = lv_i_auth_chk | |
| IMPORTING | ||
| FAULT_TEXT | = lv_fault_text | |
| MEINS | = lv_meins | |
| MESSAGE_TYPE | = lv_message_type | |
| NO_AUTH | = lv_no_auth | |
| DISTRIBUTION_LOCK | = lv_distribution_lock | |
| TABLES | ||
| OTAB | = lt_otab | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| OBJECT_NOT_FOUND = 2 | ||
| SYSTEM_FAILURE = 3 | ||
| . " OBJECT_CHECK_PLOGI | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_CHECK_PLOGI
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 MEINS FROM MARA INTO @DATA(ld_meins). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| DATA(ld_lock) | = ' '. | |||
| DATA(ld_single) | = ' '. | |||
| "SELECT single DATUV1 FROM RMCLF INTO @DATA(ld_date_of_change). | ||||
| "SELECT single DLOCK FROM T141 INTO @DATA(ld_distribution_lock). | ||||
| "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