SAP DPSPP_GET_PERS Function Module for Dealer Portal Spare Parts: Reading the Personalisation for a User
DPSPP_GET_PERS is a standard dpspp get pers SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dealer Portal Spare Parts: Reading the Personalisation 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 dpspp get pers FM, simply by entering the name DPSPP_GET_PERS into the relevant SAP transaction such as SE37 or SE38.
Function Group: DP_SPP_BCK
Program Name: SAPLDP_SPP_BCK
Main Program: SAPLDP_SPP_BCK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DPSPP_GET_PERS 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 'DPSPP_GET_PERS'"Dealer Portal Spare Parts: Reading the Personalisation for a User.
EXPORTING
* IV_UNAME = "User Name
* IV_FRONTEND = "Batch management indicator (internal)
IMPORTING
ES_PERS_SADATA = "VELO : Personalization data (Organisational data)
ET_RETURN = "frontend or backend error handling
IMPORTING Parameters details for DPSPP_GET_PERS
IV_UNAME - User Name
Data type: SYUNAMEOptional: Yes
Call by Reference: Yes
IV_FRONTEND - Batch management indicator (internal)
Data type: XCHAROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for DPSPP_GET_PERS
ES_PERS_SADATA - VELO : Personalization data (Organisational data)
Data type: DPSPP_PERSOptional: No
Call by Reference: Yes
ET_RETURN - frontend or backend error handling
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DPSPP_GET_PERS 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_iv_uname | TYPE SYUNAME, " | |||
| lv_es_pers_sadata | TYPE DPSPP_PERS, " | |||
| lv_et_return | TYPE BAPIRET2_T, " | |||
| lv_iv_frontend | TYPE XCHAR. " |
|   CALL FUNCTION 'DPSPP_GET_PERS' "Dealer Portal Spare Parts: Reading the Personalisation for a User |
| EXPORTING | ||
| IV_UNAME | = lv_iv_uname | |
| IV_FRONTEND | = lv_iv_frontend | |
| IMPORTING | ||
| ES_PERS_SADATA | = lv_es_pers_sadata | |
| ET_RETURN | = lv_et_return | |
| . " DPSPP_GET_PERS | ||
ABAP code using 7.40 inline data declarations to call FM DPSPP_GET_PERS
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