SAP BUPA_ROLE_ADD_2 Function Module for









BUPA_ROLE_ADD_2 is a standard bupa role add 2 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 bupa role add 2 FM, simply by entering the name BUPA_ROLE_ADD_2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: BUBA_4
Program Name: SAPLBUBA_4
Main Program: SAPLBUBA_4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BUPA_ROLE_ADD_2 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_ROLE_ADD_2'"
  EXPORTING
*  IV_PARTNER =  "Business Partner Number
*  IV_CREATE_CP =  "
*  IV_PARTNER_GUID =  "Business Partner GUID
*  IV_PARTNERROLECATEGORY =  "BP role category
*  IV_X_ALL_PARTNERROLES = ' ' "
*  IV_PARTNERROLE =  "BP Role
*  IV_DIFFTYPEVALUE =  "BP: Differentiation Type Value
*  IV_VALIDFROM =  "
*  IV_VALIDTO = '99991231' "
*  IV_X_SAVE = 'X' "

TABLES
*  ET_RETURN =  "Messages
.



IMPORTING Parameters details for BUPA_ROLE_ADD_2

IV_PARTNER - Business Partner Number

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

IV_CREATE_CP -

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

IV_PARTNER_GUID - Business Partner GUID

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

IV_PARTNERROLECATEGORY - BP role category

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

IV_X_ALL_PARTNERROLES -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PARTNERROLE - BP Role

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

IV_DIFFTYPEVALUE - BP: Differentiation Type Value

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

IV_VALIDFROM -

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

IV_VALIDTO -

Data type: BAPIBUS1006_BPROLE_VALIDITY-BPROLEVALIDTO
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_X_SAVE -

Data type: BAPI4001_1-SAVE_ADDR
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BUPA_ROLE_ADD_2

ET_RETURN - Messages

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

Copy and paste ABAP code example for BUPA_ROLE_ADD_2 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_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_iv_create_cp  TYPE BOOLE-BOOLE, "   
lv_iv_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_iv_partnerrolecategory  TYPE BU_PARTNERROLECAT, "   
lv_iv_x_all_partnerroles  TYPE BOOLE-BOOLE, "   SPACE
lv_iv_partnerrole  TYPE BU_PARTNERROLE, "   
lv_iv_difftypevalue  TYPE BU_DFVAL, "   
lv_iv_validfrom  TYPE BAPIBUS1006_BPROLE_VALIDITY-BPROLEVALIDFROM, "   
lv_iv_validto  TYPE BAPIBUS1006_BPROLE_VALIDITY-BPROLEVALIDTO, "   '99991231'
lv_iv_x_save  TYPE BAPI4001_1-SAVE_ADDR. "   'X'

  CALL FUNCTION 'BUPA_ROLE_ADD_2'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_CREATE_CP = lv_iv_create_cp
         IV_PARTNER_GUID = lv_iv_partner_guid
         IV_PARTNERROLECATEGORY = lv_iv_partnerrolecategory
         IV_X_ALL_PARTNERROLES = lv_iv_x_all_partnerroles
         IV_PARTNERROLE = lv_iv_partnerrole
         IV_DIFFTYPEVALUE = lv_iv_difftypevalue
         IV_VALIDFROM = lv_iv_validfrom
         IV_VALIDTO = lv_iv_validto
         IV_X_SAVE = lv_iv_x_save
    TABLES
         ET_RETURN = lt_et_return
. " BUPA_ROLE_ADD_2




ABAP code using 7.40 inline data declarations to call FM BUPA_ROLE_ADD_2

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 BOOLE FROM BOOLE INTO @DATA(ld_iv_create_cp).
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_x_all_partnerroles).
DATA(ld_iv_x_all_partnerroles) = ' '.
 
 
 
"SELECT single BPROLEVALIDFROM FROM BAPIBUS1006_BPROLE_VALIDITY INTO @DATA(ld_iv_validfrom).
 
"SELECT single BPROLEVALIDTO FROM BAPIBUS1006_BPROLE_VALIDITY INTO @DATA(ld_iv_validto).
DATA(ld_iv_validto) = '99991231'.
 
"SELECT single SAVE_ADDR FROM BAPI4001_1 INTO @DATA(ld_iv_x_save).
DATA(ld_iv_x_save) = 'X'.
 


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!