SAP BBP_VENDOR_SET Function Module for









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

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



Function BBP_VENDOR_SET 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_VENDOR_SET'"
EXPORTING
* IV_NO_COMMIT = ' ' "

IMPORTING
EV_ERROR = "

TABLES
IT_VENMAP = "
.



IMPORTING Parameters details for BBP_VENDOR_SET

IV_NO_COMMIT -

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

EXPORTING Parameters details for BBP_VENDOR_SET

EV_ERROR -

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

TABLES Parameters details for BBP_VENDOR_SET

IT_VENMAP -

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

Copy and paste ABAP code example for BBP_VENDOR_SET 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_ev_error  TYPE XFELD, "   
lt_it_venmap  TYPE STANDARD TABLE OF VENMAP, "   
lv_iv_no_commit  TYPE XFELD. "   SPACE

  CALL FUNCTION 'BBP_VENDOR_SET'  "
    EXPORTING
         IV_NO_COMMIT = lv_iv_no_commit
    IMPORTING
         EV_ERROR = lv_ev_error
    TABLES
         IT_VENMAP = lt_it_venmap
. " BBP_VENDOR_SET




ABAP code using 7.40 inline data declarations to call FM BBP_VENDOR_SET

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_no_commit) = ' '.
 


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!