SAP PRC_CHECK_LOCK Function Module for Prüfen, ob ein Sperrobjekt gesetzt ist
PRC_CHECK_LOCK is a standard prc check lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prüfen, ob ein Sperrobjekt gesetzt ist 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 prc check lock FM, simply by entering the name PRC_CHECK_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRC_PRICING_API
Program Name: SAPLPRC_PRICING_API
Main Program: SAPLPRC_PRICING_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRC_CHECK_LOCK 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 'PRC_CHECK_LOCK'"Prüfen, ob ein Sperrobjekt gesetzt ist.
EXPORTING
IV_PD_GUID = "GUID-Schlüssel des Preisfindungsbeleges (KNUMV)
* IV_BAL_LOG = "Anwendungs-Log: Handle eines Protokolls
IMPORTING
EV_PD_LOCKED = "Feld zum Ankreuzen
IMPORTING Parameters details for PRC_CHECK_LOCK
IV_PD_GUID - GUID-Schlüssel des Preisfindungsbeleges (KNUMV)
Data type: PRCT_PRIDOC_GUIDOptional: No
Call by Reference: Yes
IV_BAL_LOG - Anwendungs-Log: Handle eines Protokolls
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PRC_CHECK_LOCK
EV_PD_LOCKED - Feld zum Ankreuzen
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRC_CHECK_LOCK 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_iv_pd_guid | TYPE PRCT_PRIDOC_GUID, " | |||
| lv_ev_pd_locked | TYPE XFELD, " | |||
| lv_iv_bal_log | TYPE BALLOGHNDL. " |
|   CALL FUNCTION 'PRC_CHECK_LOCK' "Prüfen, ob ein Sperrobjekt gesetzt ist |
| EXPORTING | ||
| IV_PD_GUID | = lv_iv_pd_guid | |
| IV_BAL_LOG | = lv_iv_bal_log | |
| IMPORTING | ||
| EV_PD_LOCKED | = lv_ev_pd_locked | |
| . " PRC_CHECK_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM PRC_CHECK_LOCK
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