SAP BUPA_PARTNER_CONTACT_SEARCH Function Module for SAP BP, BAPI: Search Business Partner for Telephone, E-Mail, Address
BUPA_PARTNER_CONTACT_SEARCH is a standard bupa partner contact search SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAP BP, BAPI: Search Business Partner for Telephone, E-Mail, Address processing and below is the pattern details for this FM, 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 bupa partner contact search FM, simply by entering the name BUPA_PARTNER_CONTACT_SEARCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUBA_3
Program Name: SAPLBUBA_3
Main Program: SAPLBUBA_3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BUPA_PARTNER_CONTACT_SEARCH 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 'BUPA_PARTNER_CONTACT_SEARCH'"SAP BP, BAPI: Search Business Partner for Telephone, E-Mail, Address.
EXPORTING
* TELEPHONE = "Telephone number for determining caller
* E_MAIL = "Internet Mail (SMTP) Address Search Field
* BUSINESSPARTNER = "
* ADDRESS = "Address search parameter
TABLES
* COMPANIES = "Address Return Structure
* PERSONS = "Return structure for person with private address
* CONTACTS = "Return structure for the address of a person in a company
* RETURN = "
IMPORTING Parameters details for BUPA_PARTNER_CONTACT_SEARCH
TELEPHONE - Telephone number for determining caller
Data type: BAPIBUS1006_COMM-TELEPHONEOptional: Yes
Call by Reference: No ( called with pass by value option)
E_MAIL - Internet Mail (SMTP) Address Search Field
Data type: BAPIBUS1006_COMM-E_MAILOptional: Yes
Call by Reference: No ( called with pass by value option)
BUSINESSPARTNER -
Data type: BAPIBUS1006_HEAD-BPARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESS - Address search parameter
Data type: ADDR3_FINDOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BUPA_PARTNER_CONTACT_SEARCH
COMPANIES - Address Return Structure
Data type: BAPIBUS1006_COMPANY_ADDROptional: Yes
Call by Reference: No ( called with pass by value option)
PERSONS - Return structure for person with private address
Data type: BAPIBUS1006_PERSONAL_ADDROptional: Yes
Call by Reference: No ( called with pass by value option)
CONTACTS - Return structure for the address of a person in a company
Data type: BAPIBUS1006_CONTACT_ADDROptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BUPA_PARTNER_CONTACT_SEARCH 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_companies | TYPE STANDARD TABLE OF BAPIBUS1006_COMPANY_ADDR, " | |||
| lv_telephone | TYPE BAPIBUS1006_COMM-TELEPHONE, " | |||
| lv_e_mail | TYPE BAPIBUS1006_COMM-E_MAIL, " | |||
| lt_persons | TYPE STANDARD TABLE OF BAPIBUS1006_PERSONAL_ADDR, " | |||
| lt_contacts | TYPE STANDARD TABLE OF BAPIBUS1006_CONTACT_ADDR, " | |||
| lv_businesspartner | TYPE BAPIBUS1006_HEAD-BPARTNER, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_address | TYPE ADDR3_FIND. " |
|   CALL FUNCTION 'BUPA_PARTNER_CONTACT_SEARCH' "SAP BP, BAPI: Search Business Partner for Telephone, E-Mail, Address |
| EXPORTING | ||
| TELEPHONE | = lv_telephone | |
| E_MAIL | = lv_e_mail | |
| BUSINESSPARTNER | = lv_businesspartner | |
| ADDRESS | = lv_address | |
| TABLES | ||
| COMPANIES | = lt_companies | |
| PERSONS | = lt_persons | |
| CONTACTS | = lt_contacts | |
| RETURN | = lt_return | |
| . " BUPA_PARTNER_CONTACT_SEARCH | ||
ABAP code using 7.40 inline data declarations to call FM BUPA_PARTNER_CONTACT_SEARCH
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 TELEPHONE FROM BAPIBUS1006_COMM INTO @DATA(ld_telephone). | ||||
| "SELECT single E_MAIL FROM BAPIBUS1006_COMM INTO @DATA(ld_e_mail). | ||||
| "SELECT single BPARTNER FROM BAPIBUS1006_HEAD INTO @DATA(ld_businesspartner). | ||||
Search for further information about these or an SAP related objects