SAP Function Modules

SD_PARTNER_GET_SOURCE_PARTNER SAP Function module







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

Associated Function Group: V02P
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM SD_PARTNER_GET_SOURCE_PARTNER - SD PARTNER GET SOURCE PARTNER





CALL FUNCTION 'SD_PARTNER_GET_SOURCE_PARTNER' "
  EXPORTING
    i_kunnr =                   " knvp-kunn2
    i_parvw =                   " knvp-parvw
    i_parvw_source =            " knvp-parvw
    i_vkorg =                   " knvp-vkorg
    i_vtweg =                   " knvp-vtweg
    i_spart =                   " knvp-spart
*   i_call_bapi =               " xfeld
  IMPORTING
    e_kunnr =                   " kna1-kunnr
  EXCEPTIONS
    NO_PARTNER_FOUND = 1        "
    NO_PARTNER_SELECTED = 2     "
    .  "  SD_PARTNER_GET_SOURCE_PARTNER

ABAP code example for Function Module SD_PARTNER_GET_SOURCE_PARTNER





The ABAP code below is a full code listing to execute function module SD_PARTNER_GET_SOURCE_PARTNER 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_kunnr  TYPE KNA1-KUNNR .


SELECT single KUNN2
FROM KNVP
INTO @DATA(ld_i_kunnr).


SELECT single PARVW
FROM KNVP
INTO @DATA(ld_i_parvw).


SELECT single PARVW
FROM KNVP
INTO @DATA(ld_i_parvw_source).


SELECT single VKORG
FROM KNVP
INTO @DATA(ld_i_vkorg).


SELECT single VTWEG
FROM KNVP
INTO @DATA(ld_i_vtweg).


SELECT single SPART
FROM KNVP
INTO @DATA(ld_i_spart).

DATA(ld_i_call_bapi) = 'Check type of data required'. . CALL FUNCTION 'SD_PARTNER_GET_SOURCE_PARTNER' EXPORTING i_kunnr = ld_i_kunnr i_parvw = ld_i_parvw i_parvw_source = ld_i_parvw_source i_vkorg = ld_i_vkorg i_vtweg = ld_i_vtweg i_spart = ld_i_spart * i_call_bapi = ld_i_call_bapi IMPORTING e_kunnr = ld_e_kunnr EXCEPTIONS NO_PARTNER_FOUND = 1 NO_PARTNER_SELECTED = 2 . " SD_PARTNER_GET_SOURCE_PARTNER
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 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_kunnr  TYPE KNA1-KUNNR ,
ld_i_kunnr  TYPE KNVP-KUNN2 ,
ld_i_parvw  TYPE KNVP-PARVW ,
ld_i_parvw_source  TYPE KNVP-PARVW ,
ld_i_vkorg  TYPE KNVP-VKORG ,
ld_i_vtweg  TYPE KNVP-VTWEG ,
ld_i_spart  TYPE KNVP-SPART ,
ld_i_call_bapi  TYPE XFELD .


SELECT single KUNN2
FROM KNVP
INTO ld_i_kunnr.


SELECT single PARVW
FROM KNVP
INTO ld_i_parvw.


SELECT single PARVW
FROM KNVP
INTO ld_i_parvw_source.


SELECT single VKORG
FROM KNVP
INTO ld_i_vkorg.


SELECT single VTWEG
FROM KNVP
INTO ld_i_vtweg.


SELECT single SPART
FROM KNVP
INTO ld_i_spart.

ld_i_call_bapi = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SD_PARTNER_GET_SOURCE_PARTNER or its description.