SAP BBP_MS_USER_VENDOR_CHANGE Function Module for Ändern eines Benutzers einer verkaufenden Firma in MarketSet









BBP_MS_USER_VENDOR_CHANGE is a standard bbp ms user vendor change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ändern eines Benutzers einer verkaufenden Firma in MarketSet 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 ms user vendor change FM, simply by entering the name BBP_MS_USER_VENDOR_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_MS_USER_VENDOR_CHANGE 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_MS_USER_VENDOR_CHANGE'"Ändern eines Benutzers einer verkaufenden Firma in MarketSet
  EXPORTING
   IV_USERNAME =  "Benutzername im Benutzerstamm
   IS_PASSWORD =  "Kennwort eines SAP-Benutzers
   IV_TPID =  "ID Partnergesellschaft
   IS_LOGON_DATA =  "Benutzer: Übergabestruktur Logondaten
*  IS_ADDRESS =  "BAPI-Referenzstruktur für Adressen (Ansprechpartner)
*  IS_ADDRESS_X =  "BAPI-Change-Referenzstruktur für Adressen (Ansprechpartner)
*  IS_USERDEFAULTS =  "User: Fixed Values Transfer Structure
*  IS_USERDEFAULTS_X =  "User: Change parameters for fixed value transfer structure
*  IS_LOGON_DATA_X =  "User: Logon Data Transfer Structure

 IMPORTING
   ET_RETURN =  "
.



IMPORTING Parameters details for BBP_MS_USER_VENDOR_CHANGE

IV_USERNAME - Benutzername im Benutzerstamm

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

IS_PASSWORD - Kennwort eines SAP-Benutzers

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

IV_TPID - ID Partnergesellschaft

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

IS_LOGON_DATA - Benutzer: Übergabestruktur Logondaten

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

IS_ADDRESS - BAPI-Referenzstruktur für Adressen (Ansprechpartner)

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

IS_ADDRESS_X - BAPI-Change-Referenzstruktur für Adressen (Ansprechpartner)

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

IS_USERDEFAULTS - User: Fixed Values Transfer Structure

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

IS_USERDEFAULTS_X - User: Change parameters for fixed value transfer structure

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

IS_LOGON_DATA_X - User: Logon Data Transfer Structure

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

EXPORTING Parameters details for BBP_MS_USER_VENDOR_CHANGE

ET_RETURN -

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

Copy and paste ABAP code example for BBP_MS_USER_VENDOR_CHANGE 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_et_return  TYPE BAPIRET2_T, "   
lv_iv_username  TYPE BAPIBNAME-BAPIBNAME, "   
lv_is_password  TYPE BAPIPWD, "   
lv_iv_tpid  TYPE SMUM_TPID, "   
lv_is_logon_data  TYPE BAPILOGOND, "   
lv_is_address  TYPE BAPIADDR3, "   
lv_is_address_x  TYPE BAPIADDR3X, "   
lv_is_userdefaults  TYPE BAPIDEFAUL, "   
lv_is_userdefaults_x  TYPE BAPIDEFAX, "   
lv_is_logon_data_x  TYPE BAPILOGONX. "   

  CALL FUNCTION 'BBP_MS_USER_VENDOR_CHANGE'  "Ändern eines Benutzers einer verkaufenden Firma in MarketSet
    EXPORTING
         IV_USERNAME = lv_iv_username
         IS_PASSWORD = lv_is_password
         IV_TPID = lv_iv_tpid
         IS_LOGON_DATA = lv_is_logon_data
         IS_ADDRESS = lv_is_address
         IS_ADDRESS_X = lv_is_address_x
         IS_USERDEFAULTS = lv_is_userdefaults
         IS_USERDEFAULTS_X = lv_is_userdefaults_x
         IS_LOGON_DATA_X = lv_is_logon_data_x
    IMPORTING
         ET_RETURN = lv_et_return
. " BBP_MS_USER_VENDOR_CHANGE




ABAP code using 7.40 inline data declarations to call FM BBP_MS_USER_VENDOR_CHANGE

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 BAPIBNAME FROM BAPIBNAME INTO @DATA(ld_iv_username).
 
 
 
 
 
 
 
 
 


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!