SAP BBP_SUS_USER_API Function Module for

Search SAP Function Modules

BBP_SUS_USER_API is a standard bbp sus user api 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 sus user api FM, simply by entering the name BBP_SUS_USER_API into the relevant SAP transaction such as SE37 or SE38.

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

Function BBP_SUS_USER_API 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_SUS_USER_API'"
  EXPORTING
*  IV_PARTNER1 =  "
*  IS_LOGONDATA =  "
*  IV_ADDRESS_NUMBER =  "
*  IV_ADDRESS_GUID =  "
*  IV_ORGUNIT =  "
*  IV_NO_COMMIT = ' ' "
*  IV_CREATE_USER = 'X' "
*  IV_PARTNER_GUID1 =  "
   IS_DATA =  "
   IS_DATA_PERSON =  "
   IS_PERS_ADDR =  "
   IS_CONT_ADDR =  "
   IS_CONT_ADDR3 =  "
*  IS_PASSWORD =  "
*  IS_USERNAME =  "

 IMPORTING
   EV_PARTNER =  "
   EV_PARTNER_GUID =  "
   EV_ADDRESS_NUMBER =  "
   EV_ADDRESS_GUID =  "
   EV_PERSON_ID =  "
   EV_POSITION =  "
   EV_REFERENCE_GUID =  "

TABLES
*  ACT_GROUPS =  "
*  IT_ADTEL =  "
*  IT_ADFAX =  "
*  IT_ADSMTP =  "
*  IT_PARTNER_ROLES =  "
*  IT_PERSMAP =  "
*  ET_RETURN =  "

EXCEPTIONS
   NO_PARTNER_DATA = 1    ERROR_CREATING_POSITION = 10    ACTIVITY_GROUP_MISSING = 11    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    ORGUNIT_NOT_FOUND = 9 

.

IMPORTING Parameters details for BBP_SUS_USER_API

IV_PARTNER1 -

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

IS_LOGONDATA -

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

IV_ADDRESS_NUMBER -

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

IV_ADDRESS_GUID -

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

IV_ORGUNIT -

Data type: HROBJECT-OBJID
Optional: Yes
Call by Reference: Yes

IV_NO_COMMIT -

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: Yes

IV_CREATE_USER -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_PARTNER_GUID1 -

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

IS_DATA -

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

IS_DATA_PERSON -

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

IS_PERS_ADDR -

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

IS_CONT_ADDR -

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

IS_CONT_ADDR3 -

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

IS_PASSWORD -

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

IS_USERNAME -

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

EXPORTING Parameters details for BBP_SUS_USER_API

EV_PARTNER -

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

EV_PARTNER_GUID -

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

EV_ADDRESS_NUMBER -

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

EV_ADDRESS_GUID -

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

EV_PERSON_ID -

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

EV_POSITION -

Data type: HROBJECT-OBJID
Optional: No
Call by Reference: Yes

EV_REFERENCE_GUID -

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

TABLES Parameters details for BBP_SUS_USER_API

ACT_GROUPS -

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

IT_ADTEL -

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

IT_ADFAX -

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

IT_ADSMTP -

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

IT_PARTNER_ROLES -

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

IT_PERSMAP -

Data type: PERSMAP
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

NO_PARTNER_DATA -

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

ERROR_CREATING_POSITION -

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

ACTIVITY_GROUP_MISSING -

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

PARTNER_MISMATCH -

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

ERROR_CREATING_BUPA -

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

USERNAME_MISSING -

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

PASSWORD_MISSING -

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

ERROR_CREATING_CENTRAL_PERSON -

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

ERROR_ASSIGNING_CP_TO_USER -

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

ERROR_MESSAGE_PASSED -

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

ORGUNIT_NOT_FOUND -

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

Copy and paste ABAP code example for BBP_SUS_USER_API 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.

ABAP code using 7.40 inline data declarations to call FM BBP_SUS_USER_API

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