SAP BBP_PARTNER_OPI_EXT Function Module for









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

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



Function BBP_PARTNER_OPI_EXT 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_PARTNER_OPI_EXT'"
EXPORTING
IV_ROOT_NODE = "
* IV_DO_NOT_CREATE_BP = "
* IV_PURCH_ORG = "
IV_BU_ROLE = "

IMPORTING
PARTNER_GUID = "
PARTNER_ID = "
PARTNER_NAME1 = "
EV_NEW_VENDOR = "
EV_NOT_RELEASED = "
ES_DATA = "
ES_DATA_ORGAN = "
ES_ADDRESS = "
ES_FRG0010 = "

CHANGING
CS_PARTNER_OPI = "

TABLES
* ET_ADTEL = "
* ET_ADFAX = "
* ET_ADSMTP = "
* ET_FRG0061 = "
* ET_RETURN = "

EXCEPTIONS
AUTHORITY_CHECK_ERROR = 1 PARTNER_CREATE_ERROR = 2
.



IMPORTING Parameters details for BBP_PARTNER_OPI_EXT

IV_ROOT_NODE -

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

IV_DO_NOT_CREATE_BP -

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

IV_PURCH_ORG -

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

IV_BU_ROLE -

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

EXPORTING Parameters details for BBP_PARTNER_OPI_EXT

PARTNER_GUID -

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

PARTNER_ID -

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

PARTNER_NAME1 -

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

EV_NEW_VENDOR -

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

EV_NOT_RELEASED -

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

ES_DATA -

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

ES_DATA_ORGAN -

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

ES_ADDRESS -

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

ES_FRG0010 -

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

CHANGING Parameters details for BBP_PARTNER_OPI_EXT

CS_PARTNER_OPI -

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

TABLES Parameters details for BBP_PARTNER_OPI_EXT

ET_ADTEL -

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

ET_ADFAX -

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

ET_ADSMTP -

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

ET_FRG0061 -

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

ET_RETURN -

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

EXCEPTIONS details

AUTHORITY_CHECK_ERROR -

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

PARTNER_CREATE_ERROR -

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

Copy and paste ABAP code example for BBP_PARTNER_OPI_EXT 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_et_adtel  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_iv_root_node  TYPE OBJEKTID, "   
lv_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_cs_partner_opi  TYPE BBP_WS_OPI_ITEM_S, "   
lv_authority_check_error  TYPE BBP_WS_OPI_ITEM_S, "   
lt_et_adfax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_partner_id  TYPE BU_PARTNER, "   
lv_iv_do_not_create_bp  TYPE XFELD, "   
lv_partner_create_error  TYPE XFELD, "   
lt_et_adsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_iv_purch_org  TYPE BBP_PROC_ORG, "   
lv_partner_name1  TYPE BU_NAMEOR1, "   
lt_et_frg0061  TYPE STANDARD TABLE OF BBPM_BUT_FRG0061, "   
lv_iv_bu_role  TYPE BU_ROLE, "   
lv_ev_new_vendor  TYPE BOOLE-BOOLE, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_ev_not_released  TYPE BU_XNOT_RELEASED, "   
lv_es_data  TYPE BAPIBUS1006_CENTRAL, "   
lv_es_data_organ  TYPE BAPIBUS1006_CENTRAL_ORGAN, "   
lv_es_address  TYPE BAPIBUS1006_ADDRESS, "   
lv_es_frg0010  TYPE BBPT_BUS_FRG0010. "   

  CALL FUNCTION 'BBP_PARTNER_OPI_EXT'  "
    EXPORTING
         IV_ROOT_NODE = lv_iv_root_node
         IV_DO_NOT_CREATE_BP = lv_iv_do_not_create_bp
         IV_PURCH_ORG = lv_iv_purch_org
         IV_BU_ROLE = lv_iv_bu_role
    IMPORTING
         PARTNER_GUID = lv_partner_guid
         PARTNER_ID = lv_partner_id
         PARTNER_NAME1 = lv_partner_name1
         EV_NEW_VENDOR = lv_ev_new_vendor
         EV_NOT_RELEASED = lv_ev_not_released
         ES_DATA = lv_es_data
         ES_DATA_ORGAN = lv_es_data_organ
         ES_ADDRESS = lv_es_address
         ES_FRG0010 = lv_es_frg0010
    CHANGING
         CS_PARTNER_OPI = lv_cs_partner_opi
    TABLES
         ET_ADTEL = lt_et_adtel
         ET_ADFAX = lt_et_adfax
         ET_ADSMTP = lt_et_adsmtp
         ET_FRG0061 = lt_et_frg0061
         ET_RETURN = lt_et_return
    EXCEPTIONS
        AUTHORITY_CHECK_ERROR = 1
        PARTNER_CREATE_ERROR = 2
. " BBP_PARTNER_OPI_EXT




ABAP code using 7.40 inline data declarations to call FM BBP_PARTNER_OPI_EXT

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ev_new_vendor).
 
 
 
 
 
 
 


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!