SAP BBP_CREATE_CONTACT_PERSON Function Module for SAP-GP. Anlegen Ansprechpartner
BBP_CREATE_CONTACT_PERSON is a standard bbp create contact person 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-GP. Anlegen Ansprechpartner 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 bbp create contact person FM, simply by entering the name BBP_CREATE_CONTACT_PERSON into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PARTNER_MAINT
Program Name: SAPLBBP_PARTNER_MAINT
Main Program: SAPLBBP_PARTNER_MAINT
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_CREATE_CONTACT_PERSON 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_CREATE_CONTACT_PERSON'"SAP-GP. Anlegen Ansprechpartner.
EXPORTING
* IV_PARTNER1 = "Partnernummer der Organisation
* IS_LOGONDATA = "LogonDaten (gültig von - bis)
* IS_USERDEFAULTS = "Benutzer Default-Werte (Datum-/Dezimalpunkt-Format)
* IV_ADDRESS_NUMBER = "Adreßnummer des GP Company
* IV_ADDRESS_GUID = "AdreßGUID des GP Company
* IV_XXS_CHECK = ' ' "'X' bedeutet dass XXS-Überprüfung laufen soll
* IV_NO_COMMIT = ' ' "Bei IV_NO_COMMIT = 'X' wird vom Baustein kein COMMIT WROK ausgelöst
* IV_CREATE_USER = 'X' "Bei IV_CREATE_USER 'X' wird ein R/3 User angelegt oder zugeordnet
* IV_ASSIGN_USER = ' ' "Bei IV_ASSIGN_USER = 'X' wird ein bestehender Benutzer zugeordnet
* IS_CENTRAL_CUSTOMER_EXT = "EEW Extension of BUT000
* IV_PARTNER_GUID1 = "PartnerGUID der Organisation
IS_DATA = "Zentrale Daten zum Ansprechpartner
IS_DATA_PERSON = "Personendaten zum Ansprechpartner
IS_PERS_ADDR = "Adresse zum Ansprechpartner
IS_CONT_ADDR = "Zentrale Daten der Beziehung (Funktion, Abteilung, ..)
IS_CONT_ADDR3 = "Adresse der Beziehung (InhouseMail)
* IS_PASSWORD = "Password für den Ansprechpartner
* IS_USERNAME = "Benutzerkennung für den Ansprechpartner
IMPORTING
EV_PARTNER = "Partnernummer des Ansprechpartners
EV_PARTNER_GUID = "PartnerGUID des Ansprechpartners
EV_ADDRESS_NUMBER = "Adreßnummer des Ansprechpartners
EV_ADDRESS_GUID = "AdreßGUID des Ansprechpartners
EV_PERSON_ID = "Nummer des Ansprechpartners als Zentrale Person
EV_REFERENCE_GUID = "GUID des vorerfassten Partners
TABLES
* ACT_GROUPS = "Aktivitätsgruppen/Rollen
* IT_ADTEL = "Telefonnummern zum Ansprechpartner
* IT_ADFAX = "Faxnummern zum Ansprechpartner
* IT_ADSMTP = "Email-Adressen zum Ansprechpartner
* IT_PARTNER_ROLES = "Geschäftspartnerrollen
* IT_PERSMAP = "Mapping Information, Partnernummern in anderen Systemen
* ET_RETURN = "Error/Messages Return Struktur
EXCEPTIONS
NO_PARTNER_DATA = 1 PARTNER_MISMATCH = 2 ERROR_CREATING_BUPA = 3 USERNAME_MISSING = 4 PASSWORD_MISSING = 5 ERROR_CREATING_CENTRAL_PERSON = 6 ERROR_ASSIGNING_CP_TO_USER = 7 ERROR_MESSAGE_PASSED = 8 ACTIVITY_GROUP_MISSING = 9
IMPORTING Parameters details for BBP_CREATE_CONTACT_PERSON
IV_PARTNER1 - Partnernummer der Organisation
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IS_LOGONDATA - LogonDaten (gültig von - bis)
Data type: BAPILOGONDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_USERDEFAULTS - Benutzer Default-Werte (Datum-/Dezimalpunkt-Format)
Data type: BAPIDEFAULOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ADDRESS_NUMBER - Adreßnummer des GP Company
Data type: AD_ADDRNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ADDRESS_GUID - AdreßGUID des GP Company
Data type: BU_ADDRESS_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_XXS_CHECK - 'X' bedeutet dass XXS-Überprüfung laufen soll
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_COMMIT - Bei IV_NO_COMMIT = 'X' wird vom Baustein kein COMMIT WROK ausgelöst
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CREATE_USER - Bei IV_CREATE_USER 'X' wird ein R/3 User angelegt oder zugeordnet
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_ASSIGN_USER - Bei IV_ASSIGN_USER = 'X' wird ein bestehender Benutzer zugeordnet
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_CENTRAL_CUSTOMER_EXT - EEW Extension of BUT000
Data type: BUPA_CENTR_CUST_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARTNER_GUID1 - PartnerGUID der Organisation
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA - Zentrale Daten zum Ansprechpartner
Data type: BAPIBUS1006_CENTRALOptional: No
Call by Reference: No ( called with pass by value option)
IS_DATA_PERSON - Personendaten zum Ansprechpartner
Data type: BAPIBUS1006_CENTRAL_PERSONOptional: No
Call by Reference: No ( called with pass by value option)
IS_PERS_ADDR - Adresse zum Ansprechpartner
Data type: BAPIBUS1006_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
IS_CONT_ADDR - Zentrale Daten der Beziehung (Funktion, Abteilung, ..)
Data type: BAPIBUS1006002_CENTRALOptional: No
Call by Reference: No ( called with pass by value option)
IS_CONT_ADDR3 - Adresse der Beziehung (InhouseMail)
Data type: BAPIBUS1006002_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
IS_PASSWORD - Password für den Ansprechpartner
Data type: BAPIPWDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_USERNAME - Benutzerkennung für den Ansprechpartner
Data type: BAPIBNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_CREATE_CONTACT_PERSON
EV_PARTNER - Partnernummer des Ansprechpartners
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
EV_PARTNER_GUID - PartnerGUID des Ansprechpartners
Data type: BU_PARTNER_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_ADDRESS_NUMBER - Adreßnummer des Ansprechpartners
Data type: AD_ADDRNUMOptional: No
Call by Reference: No ( called with pass by value option)
EV_ADDRESS_GUID - AdreßGUID des Ansprechpartners
Data type: BU_ADDRESS_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_PERSON_ID - Nummer des Ansprechpartners als Zentrale Person
Data type: PERSONIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_REFERENCE_GUID - GUID des vorerfassten Partners
Data type: SYSUUID_COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_CREATE_CONTACT_PERSON
ACT_GROUPS - Aktivitätsgruppen/Rollen
Data type: BAPIAGROptional: Yes
Call by Reference: Yes
IT_ADTEL - Telefonnummern zum Ansprechpartner
Data type: BAPIADTELOptional: Yes
Call by Reference: Yes
IT_ADFAX - Faxnummern zum Ansprechpartner
Data type: BAPIADFAXOptional: Yes
Call by Reference: Yes
IT_ADSMTP - Email-Adressen zum Ansprechpartner
Data type: BAPIADSMTPOptional: Yes
Call by Reference: Yes
IT_PARTNER_ROLES - Geschäftspartnerrollen
Data type: BBPS_BUPA_ROLESOptional: Yes
Call by Reference: Yes
IT_PERSMAP - Mapping Information, Partnernummern in anderen Systemen
Data type: PERSMAPOptional: Yes
Call by Reference: Yes
ET_RETURN - Error/Messages Return Struktur
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_PARTNER_DATA - IV_PARTNER1 = IV_PARTNER_GUID1 = initial
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_MISMATCH - Select auf BUT000 mit Partner und GUID erfolglos
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_CREATING_BUPA - BUPA_CREATE_FROM_DATA mit Fehler beendet
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
USERNAME_MISSING - IS_USERNAME = initial
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PASSWORD_MISSING - IS_PASSWORD = initial
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_CREATING_CENTRAL_PERSON - BP_BUPA_CREATECENTRALPERSON mit Fehler beendet
Data type:Optional: No
Call by Reference: Yes
ERROR_ASSIGNING_CP_TO_USER - BP_CENTRALPERSON_ASSIGN_USER mit Fehler beendet
Data type:Optional: No
Call by Reference: Yes
ERROR_MESSAGE_PASSED - Message liegt in RETURN Struktur vor
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTIVITY_GROUP_MISSING - Keine Aktivitätsgruppe angegeben
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_CREATE_CONTACT_PERSON 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_act_groups | TYPE STANDARD TABLE OF BAPIAGR, " | |||
| lv_ev_partner | TYPE BU_PARTNER, " | |||
| lv_iv_partner1 | TYPE BU_PARTNER, " | |||
| lv_no_partner_data | TYPE BU_PARTNER, " | |||
| lv_is_logondata | TYPE BAPILOGOND, " | |||
| lv_is_userdefaults | TYPE BAPIDEFAUL, " | |||
| lv_iv_address_number | TYPE AD_ADDRNUM, " | |||
| lv_iv_address_guid | TYPE BU_ADDRESS_GUID, " | |||
| lv_iv_xxs_check | TYPE XFELD, " SPACE | |||
| lv_iv_no_commit | TYPE XFELD, " SPACE | |||
| lv_iv_create_user | TYPE XFELD, " 'X' | |||
| lv_iv_assign_user | TYPE XFELD, " SPACE | |||
| lv_is_central_customer_ext | TYPE BUPA_CENTR_CUST_EXT, " | |||
| lt_it_adtel | TYPE STANDARD TABLE OF BAPIADTEL, " | |||
| lv_ev_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_iv_partner_guid1 | TYPE BU_PARTNER_GUID, " | |||
| lv_partner_mismatch | TYPE BU_PARTNER_GUID, " | |||
| lv_is_data | TYPE BAPIBUS1006_CENTRAL, " | |||
| lt_it_adfax | TYPE STANDARD TABLE OF BAPIADFAX, " | |||
| lv_ev_address_number | TYPE AD_ADDRNUM, " | |||
| lv_error_creating_bupa | TYPE AD_ADDRNUM, " | |||
| lt_it_adsmtp | TYPE STANDARD TABLE OF BAPIADSMTP, " | |||
| lv_is_data_person | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
| lv_ev_address_guid | TYPE BU_ADDRESS_GUID, " | |||
| lv_username_missing | TYPE BU_ADDRESS_GUID, " | |||
| lv_ev_person_id | TYPE PERSONID, " | |||
| lv_is_pers_addr | TYPE BAPIBUS1006_ADDRESS, " | |||
| lt_it_partner_roles | TYPE STANDARD TABLE OF BBPS_BUPA_ROLES, " | |||
| lv_password_missing | TYPE BBPS_BUPA_ROLES, " | |||
| lt_it_persmap | TYPE STANDARD TABLE OF PERSMAP, " | |||
| lv_is_cont_addr | TYPE BAPIBUS1006002_CENTRAL, " | |||
| lv_ev_reference_guid | TYPE SYSUUID_C, " | |||
| lv_error_creating_central_person | TYPE SYSUUID_C, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_is_cont_addr3 | TYPE BAPIBUS1006002_ADDRESS, " | |||
| lv_error_assigning_cp_to_user | TYPE BAPIBUS1006002_ADDRESS, " | |||
| lv_is_password | TYPE BAPIPWD, " | |||
| lv_error_message_passed | TYPE BAPIPWD, " | |||
| lv_is_username | TYPE BAPIBNAME, " | |||
| lv_activity_group_missing | TYPE BAPIBNAME. " |
|   CALL FUNCTION 'BBP_CREATE_CONTACT_PERSON' "SAP-GP. Anlegen Ansprechpartner |
| EXPORTING | ||
| IV_PARTNER1 | = lv_iv_partner1 | |
| IS_LOGONDATA | = lv_is_logondata | |
| IS_USERDEFAULTS | = lv_is_userdefaults | |
| IV_ADDRESS_NUMBER | = lv_iv_address_number | |
| IV_ADDRESS_GUID | = lv_iv_address_guid | |
| IV_XXS_CHECK | = lv_iv_xxs_check | |
| IV_NO_COMMIT | = lv_iv_no_commit | |
| IV_CREATE_USER | = lv_iv_create_user | |
| IV_ASSIGN_USER | = lv_iv_assign_user | |
| IS_CENTRAL_CUSTOMER_EXT | = lv_is_central_customer_ext | |
| IV_PARTNER_GUID1 | = lv_iv_partner_guid1 | |
| IS_DATA | = lv_is_data | |
| IS_DATA_PERSON | = lv_is_data_person | |
| IS_PERS_ADDR | = lv_is_pers_addr | |
| IS_CONT_ADDR | = lv_is_cont_addr | |
| IS_CONT_ADDR3 | = lv_is_cont_addr3 | |
| IS_PASSWORD | = lv_is_password | |
| IS_USERNAME | = lv_is_username | |
| IMPORTING | ||
| EV_PARTNER | = lv_ev_partner | |
| EV_PARTNER_GUID | = lv_ev_partner_guid | |
| EV_ADDRESS_NUMBER | = lv_ev_address_number | |
| EV_ADDRESS_GUID | = lv_ev_address_guid | |
| EV_PERSON_ID | = lv_ev_person_id | |
| EV_REFERENCE_GUID | = lv_ev_reference_guid | |
| TABLES | ||
| ACT_GROUPS | = lt_act_groups | |
| IT_ADTEL | = lt_it_adtel | |
| IT_ADFAX | = lt_it_adfax | |
| IT_ADSMTP | = lt_it_adsmtp | |
| IT_PARTNER_ROLES | = lt_it_partner_roles | |
| IT_PERSMAP | = lt_it_persmap | |
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| NO_PARTNER_DATA = 1 | ||
| PARTNER_MISMATCH = 2 | ||
| ERROR_CREATING_BUPA = 3 | ||
| USERNAME_MISSING = 4 | ||
| PASSWORD_MISSING = 5 | ||
| ERROR_CREATING_CENTRAL_PERSON = 6 | ||
| ERROR_ASSIGNING_CP_TO_USER = 7 | ||
| ERROR_MESSAGE_PASSED = 8 | ||
| ACTIVITY_GROUP_MISSING = 9 | ||
| . " BBP_CREATE_CONTACT_PERSON | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CREATE_CONTACT_PERSON
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_xxs_check) | = ' '. | |||
| DATA(ld_iv_no_commit) | = ' '. | |||
| DATA(ld_iv_create_user) | = 'X'. | |||
| DATA(ld_iv_assign_user) | = ' '. | |||
Search for further information about these or an SAP related objects