SAP BBP_PDSIG_CREATE Function Module for Creating metadata records









BBP_PDSIG_CREATE is a standard bbp pdsig create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creating metadata records 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 pdsig create FM, simply by entering the name BBP_PDSIG_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_PD_SIG
Program Name: SAPLBBP_PD_SIG
Main Program: SAPLBBP_PD_SIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function BBP_PDSIG_CREATE 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_PDSIG_CREATE'"Creating metadata records
EXPORTING
IV_SIG_GUID = "Globally Unique identifier
IV_SIG_IND = "Deletion Indicator SRM Purchasing Document
IV_SIGNED_AT = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
IV_OBJKEY = "Business Transaction Document ID
* IV_SET_GUID = "Set GUID

EXCEPTIONS
INVALID_DATA = 1
.



IMPORTING Parameters details for BBP_PDSIG_CREATE

IV_SIG_GUID - Globally Unique identifier

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

IV_SIG_IND - Deletion Indicator SRM Purchasing Document

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

IV_SIGNED_AT - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

IV_OBJKEY - Business Transaction Document ID

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

IV_SET_GUID - Set GUID

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

EXCEPTIONS details

INVALID_DATA - Data could not be inserted

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_PDSIG_CREATE 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_sig_guid  TYPE BBP_GUID, "   
lv_invalid_data  TYPE BBP_GUID, "   
lv_iv_sig_ind  TYPE BBP_DEL_IND, "   
lv_iv_signed_at  TYPE BBPTIMEST_PI, "   
lv_iv_objkey  TYPE BBP_BTD_ID, "   
lv_iv_set_guid  TYPE BBP_GUID. "   

  CALL FUNCTION 'BBP_PDSIG_CREATE'  "Creating metadata records
    EXPORTING
         IV_SIG_GUID = lv_iv_sig_guid
         IV_SIG_IND = lv_iv_sig_ind
         IV_SIGNED_AT = lv_iv_signed_at
         IV_OBJKEY = lv_iv_objkey
         IV_SET_GUID = lv_iv_set_guid
    EXCEPTIONS
        INVALID_DATA = 1
. " BBP_PDSIG_CREATE




ABAP code using 7.40 inline data declarations to call FM BBP_PDSIG_CREATE

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



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!