SAP BBP_PRODUCT_PURCHASE_READ_API Function Module for









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

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



Function BBP_PRODUCT_PURCHASE_READ_API 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_PRODUCT_PURCHASE_READ_API'"
EXPORTING
* I_PRODUCT_GUID = "
* I_PRODUCT_ID = "
* I_PRODUCT_TYPE = ' ' "
* I_LANGUAGE = SY-LANGU "
* I_POPUP_SELECTION = ' ' "
* I_IGNORE_XNOSEARCH = ' ' "
* I_WITH_SHTEXT = ' ' "
* IV_LOGSYS = ' ' "

TABLES
* ET_PRODUCT_PURCHASE_DATA = "

EXCEPTIONS
NOT_FOUND = 1 WRONG_CALL = 2
.



IMPORTING Parameters details for BBP_PRODUCT_PURCHASE_READ_API

I_PRODUCT_GUID -

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

I_PRODUCT_ID -

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

I_PRODUCT_TYPE -

Data type: COMT_PRODUCT_TYPE
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_LANGUAGE -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

I_POPUP_SELECTION -

Data type: SY-MARKY
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_IGNORE_XNOSEARCH -

Data type: COMT_PRODUCT_XNOSEARCH
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_WITH_SHTEXT -

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

IV_LOGSYS -

Data type: COMT_LOGSYS
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for BBP_PRODUCT_PURCHASE_READ_API

ET_PRODUCT_PURCHASE_DATA -

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

EXCEPTIONS details

NOT_FOUND -

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

WRONG_CALL -

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

Copy and paste ABAP code example for BBP_PRODUCT_PURCHASE_READ_API 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_not_found  TYPE STRING, "   
lv_i_product_guid  TYPE COMT_PRODUCT_GUID, "   
lt_et_product_purchase_data  TYPE STANDARD TABLE OF BBPT_PRODUCT_PURCHASE_API_EXP, "   
lv_wrong_call  TYPE BBPT_PRODUCT_PURCHASE_API_EXP, "   
lv_i_product_id  TYPE COMT_PRODUCT_ID, "   
lv_i_product_type  TYPE COMT_PRODUCT_TYPE, "   SPACE
lv_i_language  TYPE SY-LANGU, "   SY-LANGU
lv_i_popup_selection  TYPE SY-MARKY, "   SPACE
lv_i_ignore_xnosearch  TYPE COMT_PRODUCT_XNOSEARCH, "   SPACE
lv_i_with_shtext  TYPE FLAG, "   SPACE
lv_iv_logsys  TYPE COMT_LOGSYS. "   SPACE

  CALL FUNCTION 'BBP_PRODUCT_PURCHASE_READ_API'  "
    EXPORTING
         I_PRODUCT_GUID = lv_i_product_guid
         I_PRODUCT_ID = lv_i_product_id
         I_PRODUCT_TYPE = lv_i_product_type
         I_LANGUAGE = lv_i_language
         I_POPUP_SELECTION = lv_i_popup_selection
         I_IGNORE_XNOSEARCH = lv_i_ignore_xnosearch
         I_WITH_SHTEXT = lv_i_with_shtext
         IV_LOGSYS = lv_iv_logsys
    TABLES
         ET_PRODUCT_PURCHASE_DATA = lt_et_product_purchase_data
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_CALL = 2
. " BBP_PRODUCT_PURCHASE_READ_API




ABAP code using 7.40 inline data declarations to call FM BBP_PRODUCT_PURCHASE_READ_API

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_i_product_type) = ' '.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_i_language).
DATA(ld_i_language) = SY-LANGU.
 
"SELECT single MARKY FROM SY INTO @DATA(ld_i_popup_selection).
DATA(ld_i_popup_selection) = ' '.
 
DATA(ld_i_ignore_xnosearch) = ' '.
 
DATA(ld_i_with_shtext) = ' '.
 
DATA(ld_iv_logsys) = ' '.
 


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!