SAP BBP_CREATE_CONTACT_USER Function Module for SAP-GP. Anlegen Benutzer zu Ansprechpartner









BBP_CREATE_CONTACT_USER is a standard bbp create contact user 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 Benutzer zu 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 user FM, simply by entering the name BBP_CREATE_CONTACT_USER 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): Normal Function Module
Update:



Function BBP_CREATE_CONTACT_USER 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_USER'"SAP-GP. Anlegen Benutzer zu Ansprechpartner
  EXPORTING
*  IV_PARTNER_COMPANY =  "Partnernummer der Firma zu der die Ansprechpartnerbeziehung besteht
*  IS_LOGONDATA =  "LogonDaten (gültig von - bis)
*  IS_USERDEFAULTS =  "Benutzer Default-Werte (Datum-/Dezimalpunkt-Format)
*  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_PARTNER_CONTACT =  "Partnernummer des Ansprechpartners
*  IS_DATA =  "Zentrale Daten zum Ansprechpartner
*  IS_DATA_PERSON =  "Personendaten zum Ansprechpartner
*  IS_PERS_ADDR =  "Adresse zum Ansprechpartner
*  IS_CONT_ADDR =  "SAP-GP, AP-Bez.: BAPI-Struktur für zentrale Daten
*  IS_CONT_ADDR3 =  "Ansprechpartner-(Dienst-)Adresse
*  IS_PASSWORD =  "Password für den Ansprechpartner
   IS_USERNAME =  "Benutzerkennung

 IMPORTING
   EV_PERSON_ID =  "Zentrale Person

TABLES
*  ACT_GROUPS =  "Aktivitätsgruppen (Rollen) zum Benutzer
*  IT_ADTEL =  "Telefonnummern (Ansprechpartner)
*  IT_ADFAX =  "Faxnummern (Ansprechpartner)
*  IT_ADSMTP =  "e-mail-Adressen (Ansprechpartner)
*  ET_RETURN =  "Error/Messages Return Struktur

EXCEPTIONS
   PASSWORD_MISSING = 1    ERROR_CREATING_CENTRAL_PERSON = 2    ERROR_ASSIGNING_CP_TO_USER = 3    ERROR_MESSAGE_PASSED = 4    ACTIVITY_GROUP_MISSING = 5    USER_NAME_MISSING = 6    DIFFERENT_USER_ASSIGNED = 7    USER_ALREADY_ASSIGNED = 8    ERROR_READING_ADDRESS = 9
.



IMPORTING Parameters details for BBP_CREATE_CONTACT_USER

IV_PARTNER_COMPANY - Partnernummer der Firma zu der die Ansprechpartnerbeziehung besteht

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

IS_LOGONDATA - LogonDaten (gültig von - bis)

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

IS_USERDEFAULTS - Benutzer Default-Werte (Datum-/Dezimalpunkt-Format)

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

IV_XXS_CHECK - 'X' bedeutet dass XXS-Überprüfung laufen soll

Data type: XFELD
Default: 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: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PARTNER_CONTACT - Partnernummer des Ansprechpartners

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

IS_DATA - Zentrale Daten zum Ansprechpartner

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

IS_DATA_PERSON - Personendaten zum Ansprechpartner

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

IS_PERS_ADDR - Adresse zum Ansprechpartner

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

IS_CONT_ADDR - SAP-GP, AP-Bez.: BAPI-Struktur für zentrale Daten

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

IS_CONT_ADDR3 - Ansprechpartner-(Dienst-)Adresse

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

IS_PASSWORD - Password für den Ansprechpartner

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

IS_USERNAME - Benutzerkennung

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

EXPORTING Parameters details for BBP_CREATE_CONTACT_USER

EV_PERSON_ID - Zentrale Person

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

TABLES Parameters details for BBP_CREATE_CONTACT_USER

ACT_GROUPS - Aktivitätsgruppen (Rollen) zum Benutzer

Data type: BAPIAGR
Optional: Yes
Call by Reference: Yes

IT_ADTEL - Telefonnummern (Ansprechpartner)

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

IT_ADFAX - Faxnummern (Ansprechpartner)

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

IT_ADSMTP - e-mail-Adressen (Ansprechpartner)

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

ET_RETURN - Error/Messages Return Struktur

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

EXCEPTIONS details

PASSWORD_MISSING - IS_PASSWORD = initial

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

ERROR_CREATING_CENTRAL_PERSON - CRM_BUPA_CREATECENTRALPERSON mit Fehler beendet

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

ERROR_ASSIGNING_CP_TO_USER - CRM_CENTRALPERSON_ASSIGN_USER mit Fehler beendet

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

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)

USER_NAME_MISSING - In IS_USERNAME wurde keine Benutzerkennung übergeben

Data type:
Optional: No
Call by Reference: Yes

DIFFERENT_USER_ASSIGNED - Ein anderer Benutzer ist dem Mitarbeiter bereits zugeordnet

Data type:
Optional: No
Call by Reference: Yes

USER_ALREADY_ASSIGNED - Der Benutzer dem Mitarbeiter bereits zugeordnet

Data type:
Optional: No
Call by Reference: Yes

ERROR_READING_ADDRESS - Fehler beim Lesen der Adresse zum Partner

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CREATE_CONTACT_USER 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_person_id  TYPE PERSONID, "   
lv_password_missing  TYPE PERSONID, "   
lv_iv_partner_company  TYPE BU_PARTNER, "   
lv_is_logondata  TYPE BAPILOGOND, "   
lv_is_userdefaults  TYPE BAPIDEFAUL, "   
lv_iv_xxs_check  TYPE XFELD, "   SPACE
lv_iv_no_commit  TYPE XFELD, "   SPACE
lt_it_adtel  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_iv_partner_contact  TYPE BU_PARTNER, "   
lv_error_creating_central_person  TYPE BU_PARTNER, "   
lv_is_data  TYPE BAPIBUS1006_CENTRAL, "   
lt_it_adfax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_error_assigning_cp_to_user  TYPE BAPIADFAX, "   
lt_it_adsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_is_data_person  TYPE BAPIBUS1006_CENTRAL_PERSON, "   
lv_error_message_passed  TYPE BAPIBUS1006_CENTRAL_PERSON, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_is_pers_addr  TYPE BAPIBUS1006_ADDRESS, "   
lv_activity_group_missing  TYPE BAPIBUS1006_ADDRESS, "   
lv_is_cont_addr  TYPE BAPIBUS1006002_CENTRAL, "   
lv_user_name_missing  TYPE BAPIBUS1006002_CENTRAL, "   
lv_is_cont_addr3  TYPE BAPIBUS1006002_ADDRESS, "   
lv_different_user_assigned  TYPE BAPIBUS1006002_ADDRESS, "   
lv_is_password  TYPE BAPIPWD, "   
lv_user_already_assigned  TYPE BAPIPWD, "   
lv_is_username  TYPE BAPIBNAME, "   
lv_error_reading_address  TYPE BAPIBNAME. "   

  CALL FUNCTION 'BBP_CREATE_CONTACT_USER'  "SAP-GP. Anlegen Benutzer zu Ansprechpartner
    EXPORTING
         IV_PARTNER_COMPANY = lv_iv_partner_company
         IS_LOGONDATA = lv_is_logondata
         IS_USERDEFAULTS = lv_is_userdefaults
         IV_XXS_CHECK = lv_iv_xxs_check
         IV_NO_COMMIT = lv_iv_no_commit
         IV_PARTNER_CONTACT = lv_iv_partner_contact
         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_PERSON_ID = lv_ev_person_id
    TABLES
         ACT_GROUPS = lt_act_groups
         IT_ADTEL = lt_it_adtel
         IT_ADFAX = lt_it_adfax
         IT_ADSMTP = lt_it_adsmtp
         ET_RETURN = lt_et_return
    EXCEPTIONS
        PASSWORD_MISSING = 1
        ERROR_CREATING_CENTRAL_PERSON = 2
        ERROR_ASSIGNING_CP_TO_USER = 3
        ERROR_MESSAGE_PASSED = 4
        ACTIVITY_GROUP_MISSING = 5
        USER_NAME_MISSING = 6
        DIFFERENT_USER_ASSIGNED = 7
        USER_ALREADY_ASSIGNED = 8
        ERROR_READING_ADDRESS = 9
. " BBP_CREATE_CONTACT_USER




ABAP code using 7.40 inline data declarations to call FM BBP_CREATE_CONTACT_USER

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


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!