SAP BBP_PD_SC_LOCK Function Module for









BBP_PD_SC_LOCK is a standard bbp pd sc lock 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 bbp pd sc lock FM, simply by entering the name BBP_PD_SC_LOCK into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_PD_SC
Program Name: SAPLBBP_PD_SC
Main Program: SAPLBBP_PD_SC
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_PD_SC_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 'BBP_PD_SC_LOCK'"
EXPORTING
* I_HEADER_GUID = "
* IV_NO_DEQUEUE_AFTER_COMMIT = "
* IV_OBJECT_ID = "

TABLES
* E_MESSAGES = "
.



IMPORTING Parameters details for BBP_PD_SC_LOCK

I_HEADER_GUID -

Data type: BBP_GUID
Optional: Yes
Call by Reference: Yes

IV_NO_DEQUEUE_AFTER_COMMIT -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IV_OBJECT_ID -

Data type: CRMD_ORDERADM_H-OBJECT_ID
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for BBP_PD_SC_LOCK

E_MESSAGES -

Data type: BBP_PDS_MESSAGES
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BBP_PD_SC_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:
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_header_guid  TYPE BBP_GUID, "   
lv_iv_no_dequeue_after_commit  TYPE XFELD, "   
lv_iv_object_id  TYPE CRMD_ORDERADM_H-OBJECT_ID. "   

  CALL FUNCTION 'BBP_PD_SC_LOCK'  "
    EXPORTING
         I_HEADER_GUID = lv_i_header_guid
         IV_NO_DEQUEUE_AFTER_COMMIT = lv_iv_no_dequeue_after_commit
         IV_OBJECT_ID = lv_iv_object_id
    TABLES
         E_MESSAGES = lt_e_messages
. " BBP_PD_SC_LOCK




ABAP code using 7.40 inline data declarations to call FM BBP_PD_SC_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.

 
 
 
"SELECT single OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_id).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!