SAP BAPI_USER_WP_PERS_DATA_SAVE Function Module for Writing the WP Personalization Data for a User
BAPI_USER_WP_PERS_DATA_SAVE is a standard bapi user wp pers data save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Writing the WP Personalization Data for a 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 bapi user wp pers data save FM, simply by entering the name BAPI_USER_WP_PERS_DATA_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: WP_EXCHANGE
Program Name: SAPLWP_EXCHANGE
Main Program:
Appliation area:
Release date: 09-May-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_USER_WP_PERS_DATA_SAVE 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 'BAPI_USER_WP_PERS_DATA_SAVE'"Writing the WP Personalization Data for a User.
EXPORTING
ID = "User Name
COUNTRY = "Country Key
DRDIALOG = "Drag&Relate: Dialog for Relate
TABLES
* MINIPERS_TAB = "Personalization Information on MiniApps
* GEN_PERS_TBL = "Table for General Workplace Personalization Data
* LANG_DEFLT = "Return Structure for Workplace Language Settings
* LPORDER_TAB = "Sequence of Roles in LaunchPad
* CHANNEL_TAB = "BAPI Structure: Channel Occupation (Serialized)
* FAVO_TABC = "BAPI Structure: Favorites (Table SMEN_BUFFC)
* FAVO_TABI = "BAPI Structure: Favorites (Table SMEN_BUFFI)
* RETURN = "Return Parameter
IMPORTING Parameters details for BAPI_USER_WP_PERS_DATA_SAVE
ID - User Name
Data type: BAPIWPUSRP-USERIDOptional: No
Call by Reference: No ( called with pass by value option)
COUNTRY - Country Key
Data type: BAPIWPUSRP-COUNTRYOptional: No
Call by Reference: No ( called with pass by value option)
DRDIALOG - Drag&Relate: Dialog for Relate
Data type: BAPIWPUSRP-DRDIALOGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_USER_WP_PERS_DATA_SAVE
MINIPERS_TAB - Personalization Information on MiniApps
Data type: BAPIWPUSRMOptional: Yes
Call by Reference: No ( called with pass by value option)
GEN_PERS_TBL - Table for General Workplace Personalization Data
Data type: BAPIWPUSRGOptional: Yes
Call by Reference: No ( called with pass by value option)
LANG_DEFLT - Return Structure for Workplace Language Settings
Data type: BAPIWPUSRLOptional: Yes
Call by Reference: No ( called with pass by value option)
LPORDER_TAB - Sequence of Roles in LaunchPad
Data type: BAPIWPUSROOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANNEL_TAB - BAPI Structure: Channel Occupation (Serialized)
Data type: BAPIWPCHANOptional: Yes
Call by Reference: Yes
FAVO_TABC - BAPI Structure: Favorites (Table SMEN_BUFFC)
Data type: BAPIWPSMBCOptional: Yes
Call by Reference: Yes
FAVO_TABI - BAPI Structure: Favorites (Table SMEN_BUFFI)
Data type: BAPIWPSMBIOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_USER_WP_PERS_DATA_SAVE 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_id | TYPE BAPIWPUSRP-USERID, " | |||
| lt_minipers_tab | TYPE STANDARD TABLE OF BAPIWPUSRM, " | |||
| lv_country | TYPE BAPIWPUSRP-COUNTRY, " | |||
| lt_gen_pers_tbl | TYPE STANDARD TABLE OF BAPIWPUSRG, " | |||
| lv_drdialog | TYPE BAPIWPUSRP-DRDIALOG, " | |||
| lt_lang_deflt | TYPE STANDARD TABLE OF BAPIWPUSRL, " | |||
| lt_lporder_tab | TYPE STANDARD TABLE OF BAPIWPUSRO, " | |||
| lt_channel_tab | TYPE STANDARD TABLE OF BAPIWPCHAN, " | |||
| lt_favo_tabc | TYPE STANDARD TABLE OF BAPIWPSMBC, " | |||
| lt_favo_tabi | TYPE STANDARD TABLE OF BAPIWPSMBI, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_USER_WP_PERS_DATA_SAVE' "Writing the WP Personalization Data for a User |
| EXPORTING | ||
| ID | = lv_id | |
| COUNTRY | = lv_country | |
| DRDIALOG | = lv_drdialog | |
| TABLES | ||
| MINIPERS_TAB | = lt_minipers_tab | |
| GEN_PERS_TBL | = lt_gen_pers_tbl | |
| LANG_DEFLT | = lt_lang_deflt | |
| LPORDER_TAB | = lt_lporder_tab | |
| CHANNEL_TAB | = lt_channel_tab | |
| FAVO_TABC | = lt_favo_tabc | |
| FAVO_TABI | = lt_favo_tabi | |
| RETURN | = lt_return | |
| . " BAPI_USER_WP_PERS_DATA_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_USER_WP_PERS_DATA_SAVE
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 USERID FROM BAPIWPUSRP INTO @DATA(ld_id). | ||||
| "SELECT single COUNTRY FROM BAPIWPUSRP INTO @DATA(ld_country). | ||||
| "SELECT single DRDIALOG FROM BAPIWPUSRP INTO @DATA(ld_drdialog). | ||||
Search for further information about these or an SAP related objects