SAP BBP_PD_CTR_UPDATE Function Module for









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

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



Function BBP_PD_CTR_UPDATE 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_CTR_UPDATE'"
  EXPORTING
*  I_PARK =  "
   I_HEADER =  "
*  I_SAVE =  "
*  IV_REJECT =  "
*  IT_ATTACH =  "
*  IT_CONDITIONS =  "
*  IV_WITH_CHANGE_APPROVAL = 'X' "

 IMPORTING
   E_CHANGED =  "
   ES_HEADER =  "

TABLES
*  I_ITEM =  "
*  I_EXCHRATE =  "
*  I_PARTNER =  "
*  I_LONGTEXT =  "
*  I_ORGDATA =  "
*  E_MESSAGES =  "
*  I_HCF =  "
*  I_ICF =  "
*  I_TOL =  "
*  I_DIS =  "
.



IMPORTING Parameters details for BBP_PD_CTR_UPDATE

I_PARK -

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

I_HEADER -

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

I_SAVE -

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

IV_REJECT -

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

IT_ATTACH -

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

IT_CONDITIONS -

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

IV_WITH_CHANGE_APPROVAL -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BBP_PD_CTR_UPDATE

E_CHANGED -

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

ES_HEADER -

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

TABLES Parameters details for BBP_PD_CTR_UPDATE

I_ITEM -

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

I_EXCHRATE -

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

I_PARTNER -

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

I_LONGTEXT -

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

I_ORGDATA -

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

E_MESSAGES -

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

I_HCF -

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

I_ICF -

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

I_TOL -

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

I_DIS -

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

Copy and paste ABAP code example for BBP_PD_CTR_UPDATE 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_i_item  TYPE STANDARD TABLE OF BBP_PDS_CTR_ITEM_ICU, "   
lv_i_park  TYPE XFELD, "   
lv_e_changed  TYPE XFELD, "   
lt_i_exchrate  TYPE STANDARD TABLE OF BBP_PDS_EXR, "   
lv_i_header  TYPE BBP_PDS_CTR_HEADER_U, "   
lv_es_header  TYPE BBP_PDS_CTR_HEADER_D, "   
lt_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lv_i_save  TYPE XFELD, "   
lt_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lv_iv_reject  TYPE XFELD, "   
lt_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lv_it_attach  TYPE BBPT_PDS_ATT_T, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lt_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_CTR, "   
lv_it_conditions  TYPE BBPT_PD_CND_ICU, "   
lt_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_CTR, "   
lv_iv_with_change_approval  TYPE XFELD, "   'X'
lt_i_tol  TYPE STANDARD TABLE OF BBP_PDS_TOL, "   
lt_i_dis  TYPE STANDARD TABLE OF BBP_PDS_DIS. "   

  CALL FUNCTION 'BBP_PD_CTR_UPDATE'  "
    EXPORTING
         I_PARK = lv_i_park
         I_HEADER = lv_i_header
         I_SAVE = lv_i_save
         IV_REJECT = lv_iv_reject
         IT_ATTACH = lv_it_attach
         IT_CONDITIONS = lv_it_conditions
         IV_WITH_CHANGE_APPROVAL = lv_iv_with_change_approval
    IMPORTING
         E_CHANGED = lv_e_changed
         ES_HEADER = lv_es_header
    TABLES
         I_ITEM = lt_i_item
         I_EXCHRATE = lt_i_exchrate
         I_PARTNER = lt_i_partner
         I_LONGTEXT = lt_i_longtext
         I_ORGDATA = lt_i_orgdata
         E_MESSAGES = lt_e_messages
         I_HCF = lt_i_hcf
         I_ICF = lt_i_icf
         I_TOL = lt_i_tol
         I_DIS = lt_i_dis
. " BBP_PD_CTR_UPDATE




ABAP code using 7.40 inline data declarations to call FM BBP_PD_CTR_UPDATE

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_iv_with_change_approval) = 'X'.
 
 
 


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!