SAP BBP_PD_PO_UNLOCK Function Module for Entsperren Bestellung
BBP_PD_PO_UNLOCK is a standard bbp pd po unlock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Entsperren Bestellung 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 bbp pd po unlock FM, simply by entering the name BBP_PD_PO_UNLOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PD_PO
Program Name: SAPLBBP_PD_PO
Main Program: SAPLBBP_PD_PO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PD_PO_UNLOCK 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_PO_UNLOCK'"Entsperren Bestellung.
EXPORTING
* I_HEADER_GUID = "
* IV_OBJECT_ID = "CRM-Positionsobjekttyp
TABLES
* E_MESSAGES = "
IMPORTING Parameters details for BBP_PD_PO_UNLOCK
I_HEADER_GUID -
Data type: BBP_GUIDOptional: Yes
Call by Reference: Yes
IV_OBJECT_ID - CRM-Positionsobjekttyp
Data type: CRMD_ORDERADM_I-OBJECT_TYPEOptional: Yes
Call by Reference: Yes
TABLES Parameters details for BBP_PD_PO_UNLOCK
E_MESSAGES -
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_PD_PO_UNLOCK 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_object_id | TYPE CRMD_ORDERADM_I-OBJECT_TYPE. " |
|   CALL FUNCTION 'BBP_PD_PO_UNLOCK' "Entsperren Bestellung |
| EXPORTING | ||
| I_HEADER_GUID | = lv_i_header_guid | |
| IV_OBJECT_ID | = lv_iv_object_id | |
| TABLES | ||
| E_MESSAGES | = lt_e_messages | |
| . " BBP_PD_PO_UNLOCK | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PD_PO_UNLOCK
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_TYPE FROM CRMD_ORDERADM_I INTO @DATA(ld_iv_object_id). | ||||
Search for further information about these or an SAP related objects