SAP SMD_PHIO_LOCK_CHECK Function Module for Check document lock in smdchko
SMD_PHIO_LOCK_CHECK is a standard smd phio lock check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check document lock in smdchko 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 smd phio lock check FM, simply by entering the name SMD_PHIO_LOCK_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SMD_MISC
Program Name: SAPLSMD_MISC
Main Program: SAPLSMD_MISC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SMD_PHIO_LOCK_CHECK 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 'SMD_PHIO_LOCK_CHECK'"Check document lock in smdchko.
EXPORTING
I_PHIO = "Phio to be checked in table smdchko
IMPORTING
ES_LOCK = "lock entry in smdchko
ES_FILE = "File Name of Last Check-Out
IMPORTING Parameters details for SMD_PHIO_LOCK_CHECK
I_PHIO - Phio to be checked in table smdchko
Data type: SDOKOBJECTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SMD_PHIO_LOCK_CHECK
ES_LOCK - lock entry in smdchko
Data type: SMDCHKOOptional: No
Call by Reference: Yes
ES_FILE - File Name of Last Check-Out
Data type: SMDCHKFOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SMD_PHIO_LOCK_CHECK 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_i_phio | TYPE SDOKOBJECT, " | |||
| lv_es_lock | TYPE SMDCHKO, " | |||
| lv_es_file | TYPE SMDCHKF. " |
|   CALL FUNCTION 'SMD_PHIO_LOCK_CHECK' "Check document lock in smdchko |
| EXPORTING | ||
| I_PHIO | = lv_i_phio | |
| IMPORTING | ||
| ES_LOCK | = lv_es_lock | |
| ES_FILE | = lv_es_file | |
| . " SMD_PHIO_LOCK_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM SMD_PHIO_LOCK_CHECK
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.Search for further information about these or an SAP related objects