SAP BBP_CHECK_PARTNER_EXIST Function Module for









BBP_CHECK_PARTNER_EXIST is a standard bbp check partner exist 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 check partner exist FM, simply by entering the name BBP_CHECK_PARTNER_EXIST 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_CHECK_PARTNER_EXIST 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_CHECK_PARTNER_EXIST'"
EXPORTING
IS_PARTNER_OPI = "
IV_IDENT_CATEGORY = "

IMPORTING
PARTNER_EXIST = "
EV_PARTNER = "
EV_PARTNER_GUID = "
.



IMPORTING Parameters details for BBP_CHECK_PARTNER_EXIST

IS_PARTNER_OPI -

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

IV_IDENT_CATEGORY -

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

EXPORTING Parameters details for BBP_CHECK_PARTNER_EXIST

PARTNER_EXIST -

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

EV_PARTNER -

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

EV_PARTNER_GUID -

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

Copy and paste ABAP code example for BBP_CHECK_PARTNER_EXIST 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_partner_exist  TYPE XFELD, "   
lv_is_partner_opi  TYPE BBP_WS_OPI_ITEM_S, "   
lv_ev_partner  TYPE BU_PARTNER, "   
lv_iv_ident_category  TYPE BU_ID_CATEGORY, "   
lv_ev_partner_guid  TYPE BU_PARTNER_GUID. "   

  CALL FUNCTION 'BBP_CHECK_PARTNER_EXIST'  "
    EXPORTING
         IS_PARTNER_OPI = lv_is_partner_opi
         IV_IDENT_CATEGORY = lv_iv_ident_category
    IMPORTING
         PARTNER_EXIST = lv_partner_exist
         EV_PARTNER = lv_ev_partner
         EV_PARTNER_GUID = lv_ev_partner_guid
. " BBP_CHECK_PARTNER_EXIST




ABAP code using 7.40 inline data declarations to call FM BBP_CHECK_PARTNER_EXIST

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!