SAP SPERS_GET_DISTRIBUTION_DATA Function Module for









SPERS_GET_DISTRIBUTION_DATA is a standard spers get distribution data 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 spers get distribution data FM, simply by entering the name SPERS_GET_DISTRIBUTION_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function SPERS_GET_DISTRIBUTION_DATA 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 'SPERS_GET_DISTRIBUTION_DATA'"
EXPORTING
* P_USER = ' ' "User Name
* P_ROLE = ' ' "Role Name
* P_PERS_KEY = ' ' "Personalization Object Key

TABLES
P_DISTRIBUTION_DATA = "Intermediate format for distributing personalization data

EXCEPTIONS
OPERATION_FAILED = 1
.



IMPORTING Parameters details for SPERS_GET_DISTRIBUTION_DATA

P_USER - User Name

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

P_ROLE - Role Name

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

P_PERS_KEY - Personalization Object Key

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

TABLES Parameters details for SPERS_GET_DISTRIBUTION_DATA

P_DISTRIBUTION_DATA - Intermediate format for distributing personalization data

Data type: SPERS_DDF
Optional: No
Call by Reference: Yes

EXCEPTIONS details

OPERATION_FAILED - Data Read Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SPERS_GET_DISTRIBUTION_DATA 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_p_user  TYPE UNAME, "   SPACE
lv_operation_failed  TYPE UNAME, "   
lt_p_distribution_data  TYPE STANDARD TABLE OF SPERS_DDF, "   
lv_p_role  TYPE AGR_NAME, "   SPACE
lv_p_pers_key  TYPE SPERS_KEY. "   SPACE

  CALL FUNCTION 'SPERS_GET_DISTRIBUTION_DATA'  "
    EXPORTING
         P_USER = lv_p_user
         P_ROLE = lv_p_role
         P_PERS_KEY = lv_p_pers_key
    TABLES
         P_DISTRIBUTION_DATA = lt_p_distribution_data
    EXCEPTIONS
        OPERATION_FAILED = 1
. " SPERS_GET_DISTRIBUTION_DATA




ABAP code using 7.40 inline data declarations to call FM SPERS_GET_DISTRIBUTION_DATA

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.

DATA(ld_p_user) = ' '.
 
 
 
DATA(ld_p_role) = ' '.
 
DATA(ld_p_pers_key) = ' '.
 


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!