SPERS_RFC_USER_DATA_GET SAP Function module

SPERS_RFC_USER_DATA_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SPERS_RFC_USER_DATA_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SPERS_REMOTE
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM SPERS_RFC_USER_DATA_GET - SPERS RFC USER DATA GET

CALL FUNCTION 'SPERS_RFC_USER_DATA_GET' "
  EXPORTING
    p_pers_key = SPACE          " spers_key     Personalization Object Key
*   p_user = SY-UNAME           " uname         User Name
*   p_bypass_db_buffer = SPACE  " char1
* TABLES
*   p_data_table =              " spers_gdf
  EXCEPTIONS
    PERS_KEY_NOT_FOUND = 1      "
    GENERIC_TABLE_NOT_USED = 2  "
    USER_DOES_NOT_EXIST = 3     "               User Does Not Exist
    NO_DATA_FOUND = 4           "               Data Not Found
    .  "  SPERS_RFC_USER_DATA_GET

ABAP code example for Function Module SPERS_RFC_USER_DATA_GET

The ABAP code below is a full code listing to execute function module SPERS_RFC_USER_DATA_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_p_data_table  
 
 TYPE STANDARD TABLE OF SPERS_GDF,"TABLES PARAM
wa_p_data_table
 
 LIKE LINE OF it_p_data_table
.


DATA(ld_p_pers_key) = 'Check type of data required'.

DATA(ld_p_user) = 'Check type of data required'.

DATA(ld_p_bypass_db_buffer) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_p_data_table to it_p_data_table.
.

CALL FUNCTION 'SPERS_RFC_USER_DATA_GET'
  EXPORTING
    p_pers_key =                 ld_p_pers_key
*   p_user =                     ld_p_user
*   p_bypass_db_buffer =         ld_p_bypass_db_buffer
* TABLES
*   p_data_table =               it_p_data_table
  EXCEPTIONS
    PERS_KEY_NOT_FOUND =         1
    GENERIC_TABLE_NOT_USED =     2
    USER_DOES_NOT_EXIST =        3
    NO_DATA_FOUND =              4
    .  "  SPERS_RFC_USER_DATA_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_p_pers_key
 
 TYPE SPERS_KEY ,
it_p_data_table
 
 TYPE STANDARD TABLE OF SPERS_GDF ,
wa_p_data_table
 
 LIKE LINE OF it_p_data_table,
ld_p_user
 
 TYPE UNAME ,
ld_p_bypass_db_buffer
 
 TYPE CHAR1 .


ld_p_pers_key = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_p_data_table to it_p_data_table.
ld_p_user = 'Check type of data required'.
ld_p_bypass_db_buffer = 'Check type of data required'.