SAP BBP_SUS_BUPA_REGID_CREATE Function Module for Create Register User as Default Amind User









BBP_SUS_BUPA_REGID_CREATE is a standard bbp sus bupa regid create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Register User as Default Amind User 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 sus bupa regid create FM, simply by entering the name BBP_SUS_BUPA_REGID_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_SUS_BUPA_REGID_CREATE 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_BUPA_REGID_CREATE'"Create Register User as Default Amind User
  EXPORTING
   IV_SUPPL =  "
*  IS_CENTRAL =  "Vom Geschäftspartnertyp unabhängige allgemeine Daten des GP
*  IS_CENTRALORG =  "SAP-GP: BAPI-Struktur für Organisationsdaten
*  IS_ADDRESS =  "
*  IV_ADDR_ID =  "Adreßnummer
*  IV_NO_EMAIL =  "Feld zum Ankreuzen

 IMPORTING
   EV_REGID =  "Charakterfeld der Länge 12

TABLES
*  IT_ADTEL =  "
*  IT_ADFAX =  "
*  IT_ADSMTP =  "
*  IT_VENMAP =  "MappingTabelle PartnerGUID - R/3 Nummer
*  ET_RETURN =  "Return Parameter
.



IMPORTING Parameters details for BBP_SUS_BUPA_REGID_CREATE

IV_SUPPL -

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

IS_CENTRAL - Vom Geschäftspartnertyp unabhängige allgemeine Daten des GP

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

IS_CENTRALORG - SAP-GP: BAPI-Struktur für Organisationsdaten

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

IS_ADDRESS -

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

IV_ADDR_ID - Adreßnummer

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

IV_NO_EMAIL - Feld zum Ankreuzen

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

EXPORTING Parameters details for BBP_SUS_BUPA_REGID_CREATE

EV_REGID - Charakterfeld der Länge 12

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

TABLES Parameters details for BBP_SUS_BUPA_REGID_CREATE

IT_ADTEL -

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

IT_ADFAX -

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

IT_ADSMTP -

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

IT_VENMAP - MappingTabelle PartnerGUID - R/3 Nummer

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

ET_RETURN - Return Parameter

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

Copy and paste ABAP code example for BBP_SUS_BUPA_REGID_CREATE 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_ev_regid  TYPE CHAR58, "   
lt_it_adtel  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_iv_suppl  TYPE BU_PARTNER, "   
lt_it_adfax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_is_central  TYPE BAPIBUS1006_CENTRAL, "   
lt_it_adsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_is_centralorg  TYPE BAPIBUS1006_CENTRAL_ORGAN, "   
lt_it_venmap  TYPE STANDARD TABLE OF VENMAP, "   
lv_is_address  TYPE BAPIBUS1006_ADDRESS, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_addr_id  TYPE AD_ADDRNUM, "   
lv_iv_no_email  TYPE XFELD. "   

  CALL FUNCTION 'BBP_SUS_BUPA_REGID_CREATE'  "Create Register User as Default Amind User
    EXPORTING
         IV_SUPPL = lv_iv_suppl
         IS_CENTRAL = lv_is_central
         IS_CENTRALORG = lv_is_centralorg
         IS_ADDRESS = lv_is_address
         IV_ADDR_ID = lv_iv_addr_id
         IV_NO_EMAIL = lv_iv_no_email
    IMPORTING
         EV_REGID = lv_ev_regid
    TABLES
         IT_ADTEL = lt_it_adtel
         IT_ADFAX = lt_it_adfax
         IT_ADSMTP = lt_it_adsmtp
         IT_VENMAP = lt_it_venmap
         ET_RETURN = lt_et_return
. " BBP_SUS_BUPA_REGID_CREATE




ABAP code using 7.40 inline data declarations to call FM BBP_SUS_BUPA_REGID_CREATE

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!