SD_INT_DPP_DETERMINE SAP Function module

SD_INT_DPP_DETERMINE 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 SD_INT_DPP_DETERMINE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: VPVA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SD_INT_DPP_DETERMINE - SD INT DPP DETERMINE

CALL FUNCTION 'SD_INT_DPP_DETERMINE' "
* EXPORTING
*   i_kunde =                   " knvv
*   i_boflag = 'O'              " char1
*   i_auart =                   " vbak-auart    Sales Document Type
*   i_kuagv =                   " kuagv
*   i_kuwev =                   " kuwev
*   i_vbak =                    " vbak
*   i_pvksm =                   " knvv-pvksm
*   i_prsdt =                   " vbkd-prsdt
*   i_tvta =                    " tvta          Organizational Unit: Sales Area(s)
  IMPORTING
    e_pvsm =                    " vbpvsm
    e_titel =                   " vpvcol
* TABLES
*   e_vbpv =                    " vbpvd         Client
  EXCEPTIONS
    E_INCOMPLETE = 1            "
    E_FB_NOT_FOUND = 2          "
    E_NO_SELECTION = 3          "
    E_NO_CUSTOMER = 4           "
    .  "  SD_INT_DPP_DETERMINE

ABAP code example for Function Module SD_INT_DPP_DETERMINE

The ABAP code below is a full code listing to execute function module SD_INT_DPP_DETERMINE 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:
ld_e_pvsm  
 
 TYPE VBPVSM
,
ld_e_titel  
 
 TYPE VPVCOL
,
it_e_vbpv  
 
 TYPE STANDARD TABLE OF VBPVD,"TABLES PARAM
wa_e_vbpv
 
 LIKE LINE OF it_e_vbpv
.


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

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

SELECT single AUART 
  FROM VBAK 
  INTO @DATA(ld_i_auart).


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

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

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

SELECT single PVKSM 
  FROM KNVV 
  INTO @DATA(ld_i_pvksm).

 

SELECT single PRSDT 
  FROM VBKD 
  INTO @DATA(ld_i_prsdt).


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

"populate fields of struture and append to itab
append wa_e_vbpv to it_e_vbpv.
.

CALL FUNCTION 'SD_INT_DPP_DETERMINE'
* EXPORTING
*   i_kunde =                    ld_i_kunde
*   i_boflag =                   ld_i_boflag
*   i_auart =                    ld_i_auart
*   i_kuagv =                    ld_i_kuagv
*   i_kuwev =                    ld_i_kuwev
*   i_vbak =                     ld_i_vbak
*   i_pvksm =                    ld_i_pvksm
*   i_prsdt =                    ld_i_prsdt
*   i_tvta =                     ld_i_tvta
  IMPORTING
    e_pvsm =                     ld_e_pvsm
    e_titel =                    ld_e_titel
* TABLES
*   e_vbpv =                     it_e_vbpv
  EXCEPTIONS
    E_INCOMPLETE =               1
    E_FB_NOT_FOUND =             2
    E_NO_SELECTION =             3
    E_NO_CUSTOMER =              4
    .  "  SD_INT_DPP_DETERMINE

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_e_pvsm
 
 TYPE VBPVSM ,
ld_i_kunde
 
 TYPE KNVV ,
it_e_vbpv
 
 TYPE STANDARD TABLE OF VBPVD ,
wa_e_vbpv
 
 LIKE LINE OF it_e_vbpv,
ld_e_titel
 
 TYPE VPVCOL ,
ld_i_boflag
 
 TYPE CHAR1 ,
ld_i_auart
 
 TYPE VBAK-AUART ,
ld_i_kuagv
 
 TYPE KUAGV ,
ld_i_kuwev
 
 TYPE KUWEV ,
ld_i_vbak
 
 TYPE VBAK ,
ld_i_pvksm
 
 TYPE KNVV-PVKSM ,
ld_i_prsdt
 
 TYPE VBKD-PRSDT ,
ld_i_tvta
 
 TYPE TVTA .


ld_i_kunde = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_e_vbpv to it_e_vbpv.
ld_i_boflag = 'Check type of data required'.

SELECT single AUART 
  FROM VBAK 
  INTO ld_i_auart.

ld_i_kuagv = 'Check type of data required'.
ld_i_kuwev = 'Check type of data required'.
ld_i_vbak = 'Check type of data required'.

SELECT single PVKSM 
  FROM KNVV 
  INTO ld_i_pvksm.


SELECT single PRSDT 
  FROM VBKD 
  INTO ld_i_prsdt.

ld_i_tvta = 'Check type of data required'.