SAP BBP_PROD_CND_BADI_ENQUEUE Function Module for FB to Set BAdI Product Attribute Lock









BBP_PROD_CND_BADI_ENQUEUE is a standard bbp prod cnd badi enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FB to Set BAdI Product Attribute Lock 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 prod cnd badi enqueue FM, simply by entering the name BBP_PROD_CND_BADI_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PROD_CND_BADI_ENQUEUE 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_PROD_CND_BADI_ENQUEUE'"FB to Set BAdI Product Attribute Lock
  EXPORTING
   FLT_VAL =  "Data Element and Context Name
   I_MAINT_CONTEXT_DATA =  "
   I_INSTANCE =  "
   IS_WORKING_SET_ITEM_INT =  "
   IT_FIELDNAME_ROLLNAME =  "Field and Data Element Names
   I_COLLECT_ENQUEUE =  "Boolean Variable

 IMPORTING
   E_WAS_EXECUTED =  "Boolean Variable
   E_RESULT =  "Return Value of ABAP Statements

CHANGING
   CT_MNT_APPLICATION_LOG =  "Entries in Application Log in Condition Maintenance

EXCEPTIONS
   EXC_STOP_WORK = 1
.



IMPORTING Parameters details for BBP_PROD_CND_BADI_ENQUEUE

FLT_VAL - Data Element and Context Name

Data type: /SAPCND/ROLLNAME_CONTEXTNAME
Optional: No
Call by Reference: No ( called with pass by value option)

I_MAINT_CONTEXT_DATA -

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

I_INSTANCE -

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

IS_WORKING_SET_ITEM_INT -

Data type: ANY
Optional: No
Call by Reference: Yes

IT_FIELDNAME_ROLLNAME - Field and Data Element Names

Data type: /SAPCND/T_FIELDNAME_ROLLNAME
Optional: No
Call by Reference: Yes

I_COLLECT_ENQUEUE - Boolean Variable

Data type: /SAPCND/BOOLEAN
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BBP_PROD_CND_BADI_ENQUEUE

E_WAS_EXECUTED - Boolean Variable

Data type: /SAPCND/BOOLEAN
Optional: No
Call by Reference: No ( called with pass by value option)

E_RESULT - Return Value of ABAP Statements

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

CHANGING Parameters details for BBP_PROD_CND_BADI_ENQUEUE

CT_MNT_APPLICATION_LOG - Entries in Application Log in Condition Maintenance

Data type: /SAPCND/T_MNT_APPLICATION_LOG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

EXC_STOP_WORK -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_PROD_CND_BADI_ENQUEUE 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_flt_val  TYPE /SAPCND/ROLLNAME_CONTEXTNAME, "   
lv_exc_stop_work  TYPE /SAPCND/ROLLNAME_CONTEXTNAME, "   
lv_e_was_executed  TYPE /SAPCND/BOOLEAN, "   
lv_ct_mnt_application_log  TYPE /SAPCND/T_MNT_APPLICATION_LOG, "   
lv_e_result  TYPE SYSUBRC, "   
lv_i_maint_context_data  TYPE DATA, "   
lv_i_instance  TYPE DATA, "   
lv_is_working_set_item_int  TYPE ANY, "   
lv_it_fieldname_rollname  TYPE /SAPCND/T_FIELDNAME_ROLLNAME, "   
lv_i_collect_enqueue  TYPE /SAPCND/BOOLEAN. "   

  CALL FUNCTION 'BBP_PROD_CND_BADI_ENQUEUE'  "FB to Set BAdI Product Attribute Lock
    EXPORTING
         FLT_VAL = lv_flt_val
         I_MAINT_CONTEXT_DATA = lv_i_maint_context_data
         I_INSTANCE = lv_i_instance
         IS_WORKING_SET_ITEM_INT = lv_is_working_set_item_int
         IT_FIELDNAME_ROLLNAME = lv_it_fieldname_rollname
         I_COLLECT_ENQUEUE = lv_i_collect_enqueue
    IMPORTING
         E_WAS_EXECUTED = lv_e_was_executed
         E_RESULT = lv_e_result
    CHANGING
         CT_MNT_APPLICATION_LOG = lv_ct_mnt_application_log
    EXCEPTIONS
        EXC_STOP_WORK = 1
. " BBP_PROD_CND_BADI_ENQUEUE




ABAP code using 7.40 inline data declarations to call FM BBP_PROD_CND_BADI_ENQUEUE

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!