SAP BBP_PD_CTR_UPLOAD_WO_UPDATE Function Module for









BBP_PD_CTR_UPLOAD_WO_UPDATE is a standard bbp pd ctr upload wo 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 upload wo update FM, simply by entering the name BBP_PD_CTR_UPLOAD_WO_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_UPLOAD_WO_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_UPLOAD_WO_UPDATE'"
  EXPORTING
   IV_HEADER_GUID =  "
*  IV_DISP_VARIANT =  "
*  IT_FILE_OPTIONS =  "
   IT_DATA_CONTAINER =  "
*  IV_PAYMENT_SYSTEM =  "

 IMPORTING
   ES_HEADER_U =  "
   ET_TOL_U =  "
   ET_CONDITION_U =  "
   ET_ITEM_U =  "
   ET_PARTNER_U =  "
   ET_LONGTEXT_U =  "
   ET_ORGDATA_U =  "
   ET_HCF_U =  "
   ET_ICF_U =  "
   ET_DEP_U =  "

CHANGING
   CT_MESSAGES =  "
.



IMPORTING Parameters details for BBP_PD_CTR_UPLOAD_WO_UPDATE

IV_HEADER_GUID -

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

IV_DISP_VARIANT -

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

IT_FILE_OPTIONS -

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

IT_DATA_CONTAINER -

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

IV_PAYMENT_SYSTEM -

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

EXPORTING Parameters details for BBP_PD_CTR_UPLOAD_WO_UPDATE

ES_HEADER_U -

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

ET_TOL_U -

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

ET_CONDITION_U -

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

ET_ITEM_U -

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

ET_PARTNER_U -

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

ET_LONGTEXT_U -

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

ET_ORGDATA_U -

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

ET_HCF_U -

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

ET_ICF_U -

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

ET_DEP_U -

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

CHANGING Parameters details for BBP_PD_CTR_UPLOAD_WO_UPDATE

CT_MESSAGES -

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

Copy and paste ABAP code example for BBP_PD_CTR_UPLOAD_WO_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:
lv_ct_messages  TYPE BBPT_PD_MESSAGES, "   
lv_es_header_u  TYPE BBP_PDS_CTR_HEADER_U, "   
lv_iv_header_guid  TYPE BBP_GUID, "   
lv_et_tol_u  TYPE BBPT_PD_TOL, "   
lv_et_condition_u  TYPE BBPT_PD_CND_ICU, "   
lv_iv_disp_variant  TYPE BBP_DISP_VARIANT, "   
lv_et_item_u  TYPE BBPT_PD_CTR_ITEM_ICU, "   
lv_it_file_options  TYPE BBPT_FILE_OPTIONS, "   
lv_et_partner_u  TYPE BBPT_PDS_PARTNER, "   
lv_it_data_container  TYPE BBPT_DATA_CONTAINER, "   
lv_et_longtext_u  TYPE BBPT_PDS_LONGTEXT, "   
lv_iv_payment_system  TYPE LOGSYS, "   
lv_et_orgdata_u  TYPE BBPT_PDS_ORG, "   
lv_et_hcf_u  TYPE BBPT_PDS_HCF_CTR, "   
lv_et_icf_u  TYPE BBPT_PDS_ICF_CTR, "   
lv_et_dep_u  TYPE BBPT_PD_DIS. "   

  CALL FUNCTION 'BBP_PD_CTR_UPLOAD_WO_UPDATE'  "
    EXPORTING
         IV_HEADER_GUID = lv_iv_header_guid
         IV_DISP_VARIANT = lv_iv_disp_variant
         IT_FILE_OPTIONS = lv_it_file_options
         IT_DATA_CONTAINER = lv_it_data_container
         IV_PAYMENT_SYSTEM = lv_iv_payment_system
    IMPORTING
         ES_HEADER_U = lv_es_header_u
         ET_TOL_U = lv_et_tol_u
         ET_CONDITION_U = lv_et_condition_u
         ET_ITEM_U = lv_et_item_u
         ET_PARTNER_U = lv_et_partner_u
         ET_LONGTEXT_U = lv_et_longtext_u
         ET_ORGDATA_U = lv_et_orgdata_u
         ET_HCF_U = lv_et_hcf_u
         ET_ICF_U = lv_et_icf_u
         ET_DEP_U = lv_et_dep_u
    CHANGING
         CT_MESSAGES = lv_ct_messages
. " BBP_PD_CTR_UPLOAD_WO_UPDATE




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

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!