SAP BBP_API_PURCHREQ_UPD Function Module for









BBP_API_PURCHREQ_UPD is a standard bbp api purchreq upd 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 api purchreq upd FM, simply by entering the name BBP_API_PURCHREQ_UPD into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_API_PURCHREQ_UPD 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_API_PURCHREQ_UPD'"
  EXPORTING
*  IS_HEADER =  "
*  IT_ATTACH =  "
*  IT_ITEM =  "
*  IT_ACCOUNT =  "
*  IT_PARTNER =  "
*  IT_LONGTEXT =  "
*  IT_LIMIT =  "
*  IT_ORGDATA =  "
*  IT_TAX =  "

 IMPORTING
   ES_HEADER =  "
   ET_ATTACH =  "
   ET_ITEM =  "
   ET_ACCOUNT =  "
   ET_PARTNER =  "
   ET_LONGTEXT =  "
   ET_LIMIT =  "
   ET_ORGDATA =  "
.



IMPORTING Parameters details for BBP_API_PURCHREQ_UPD

IS_HEADER -

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

IT_ATTACH -

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

IT_ITEM -

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

IT_ACCOUNT -

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

IT_PARTNER -

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

IT_LONGTEXT -

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

IT_LIMIT -

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

IT_ORGDATA -

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

IT_TAX -

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

EXPORTING Parameters details for BBP_API_PURCHREQ_UPD

ES_HEADER -

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

ET_ATTACH -

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

ET_ITEM -

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

ET_ACCOUNT -

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

ET_PARTNER -

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

ET_LONGTEXT -

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

ET_LIMIT -

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

ET_ORGDATA -

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

Copy and paste ABAP code example for BBP_API_PURCHREQ_UPD 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_es_header  TYPE BBPS_PDEXT_SC_HEADER_D, "   
lv_is_header  TYPE BBPS_PDEXT_SC_HEADER_IU, "   
lv_et_attach  TYPE BBPT_PDS_ATT_T, "   
lv_it_attach  TYPE BBPT_PDEXT_ATTACH, "   
lv_et_item  TYPE BBPT_PD_SC_ITEM_ICU, "   
lv_it_item  TYPE BBPT_PDEXT_SC_ITEM_IU, "   
lv_et_account  TYPE BBPT_PDS_ACC, "   
lv_it_account  TYPE BBPT_PDEXT_ACC, "   
lv_et_partner  TYPE BBPT_PDS_PARTNER, "   
lv_it_partner  TYPE BBPT_PDEXT_PARTNER, "   
lv_et_longtext  TYPE BBPT_PD_LONGTEXT, "   
lv_it_longtext  TYPE BBPT_PDEXT_LONGTEXT, "   
lv_et_limit  TYPE BBPT_PD_LIMIT, "   
lv_it_limit  TYPE BBPT_PDEXT_LIMIT, "   
lv_et_orgdata  TYPE BBPT_PDS_ORG, "   
lv_it_orgdata  TYPE BBPT_PDEXT_ORG, "   
lv_it_tax  TYPE BBPT_PDEXT_TAX. "   

  CALL FUNCTION 'BBP_API_PURCHREQ_UPD'  "
    EXPORTING
         IS_HEADER = lv_is_header
         IT_ATTACH = lv_it_attach
         IT_ITEM = lv_it_item
         IT_ACCOUNT = lv_it_account
         IT_PARTNER = lv_it_partner
         IT_LONGTEXT = lv_it_longtext
         IT_LIMIT = lv_it_limit
         IT_ORGDATA = lv_it_orgdata
         IT_TAX = lv_it_tax
    IMPORTING
         ES_HEADER = lv_es_header
         ET_ATTACH = lv_et_attach
         ET_ITEM = lv_et_item
         ET_ACCOUNT = lv_et_account
         ET_PARTNER = lv_et_partner
         ET_LONGTEXT = lv_et_longtext
         ET_LIMIT = lv_et_limit
         ET_ORGDATA = lv_et_orgdata
. " BBP_API_PURCHREQ_UPD




ABAP code using 7.40 inline data declarations to call FM BBP_API_PURCHREQ_UPD

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!