SAP DPSPP_GET_ALL_CUST_SALESAREAS Function Module for Dealer Portal Spare Parts: Collect Customer Sales Area Information









DPSPP_GET_ALL_CUST_SALESAREAS is a standard dpspp get all cust salesareas 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: Collect Customer Sales Area Information 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 all cust salesareas FM, simply by entering the name DPSPP_GET_ALL_CUST_SALESAREAS into the relevant SAP transaction such as SE37 or SE38.

Function Group: DPSPPUI01
Program Name: SAPLDPSPPUI01
Main Program: SAPLDPSPPUI01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DPSPP_GET_ALL_CUST_SALESAREAS 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_ALL_CUST_SALESAREAS'"Dealer Portal Spare Parts: Collect Customer Sales Area Information
EXPORTING
IF_USERID = "Customer Number
IV_DEST = "DP SPP: Dealer Portal RFC Backend Destination

IMPORTING
ET_CUSTOMER_SALESAREA = "table type for sales area and texts
ET_RETURN = "Return parameter table
.



IMPORTING Parameters details for DPSPP_GET_ALL_CUST_SALESAREAS

IF_USERID - Customer Number

Data type: SY-UNAME
Optional: No
Call by Reference: Yes

IV_DEST - DP SPP: Dealer Portal RFC Backend Destination

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

EXPORTING Parameters details for DPSPP_GET_ALL_CUST_SALESAREAS

ET_CUSTOMER_SALESAREA - table type for sales area and texts

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

ET_RETURN - Return parameter table

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

Copy and paste ABAP code example for DPSPP_GET_ALL_CUST_SALESAREAS 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_if_userid  TYPE SY-UNAME, "   
lv_et_customer_salesarea  TYPE DPSPPT_CUSTSTR, "   
lv_iv_dest  TYPE DPSPP_RFC_DESTINATION, "   
lv_et_return  TYPE BAPIRET2_T. "   

  CALL FUNCTION 'DPSPP_GET_ALL_CUST_SALESAREAS'  "Dealer Portal Spare Parts: Collect Customer Sales Area Information
    EXPORTING
         IF_USERID = lv_if_userid
         IV_DEST = lv_iv_dest
    IMPORTING
         ET_CUSTOMER_SALESAREA = lv_et_customer_salesarea
         ET_RETURN = lv_et_return
. " DPSPP_GET_ALL_CUST_SALESAREAS




ABAP code using 7.40 inline data declarations to call FM DPSPP_GET_ALL_CUST_SALESAREAS

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 UNAME FROM SY INTO @DATA(ld_if_userid).
 
 
 
 


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!