SAP SD_PARTNER_GET_SOURCE_PARTNER Function Module for NOTRANSL: Bestimmt 'Quellpartner', in dessen KNVP der Eingabe-Partner vorh
SD_PARTNER_GET_SOURCE_PARTNER is a standard sd partner get source partner SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Bestimmt 'Quellpartner', in dessen KNVP der Eingabe-Partner vorh 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 sd partner get source partner FM, simply by entering the name SD_PARTNER_GET_SOURCE_PARTNER into the relevant SAP transaction such as SE37 or SE38.
Function Group: V02P
Program Name: SAPLV02P
Main Program: SAPLV02P
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SD_PARTNER_GET_SOURCE_PARTNER 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 'SD_PARTNER_GET_SOURCE_PARTNER'"NOTRANSL: Bestimmt 'Quellpartner', in dessen KNVP der Eingabe-Partner vorh.
EXPORTING
I_KUNNR = "
I_PARVW = "
I_PARVW_SOURCE = "
I_VKORG = "
I_VTWEG = "
I_SPART = "
* I_CALL_BAPI = "Checkbox
IMPORTING
E_KUNNR = "
EXCEPTIONS
NO_PARTNER_FOUND = 1 NO_PARTNER_SELECTED = 2
IMPORTING Parameters details for SD_PARTNER_GET_SOURCE_PARTNER
I_KUNNR -
Data type: KNVP-KUNN2Optional: No
Call by Reference: No ( called with pass by value option)
I_PARVW -
Data type: KNVP-PARVWOptional: No
Call by Reference: No ( called with pass by value option)
I_PARVW_SOURCE -
Data type: KNVP-PARVWOptional: No
Call by Reference: No ( called with pass by value option)
I_VKORG -
Data type: KNVP-VKORGOptional: No
Call by Reference: No ( called with pass by value option)
I_VTWEG -
Data type: KNVP-VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
I_SPART -
Data type: KNVP-SPARTOptional: No
Call by Reference: No ( called with pass by value option)
I_CALL_BAPI - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_PARTNER_GET_SOURCE_PARTNER
E_KUNNR -
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_PARTNER_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PARTNER_SELECTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_PARTNER_GET_SOURCE_PARTNER 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_e_kunnr | TYPE KNA1-KUNNR, " | |||
lv_i_kunnr | TYPE KNVP-KUNN2, " | |||
lv_no_partner_found | TYPE KNVP, " | |||
lv_i_parvw | TYPE KNVP-PARVW, " | |||
lv_no_partner_selected | TYPE KNVP, " | |||
lv_i_parvw_source | TYPE KNVP-PARVW, " | |||
lv_i_vkorg | TYPE KNVP-VKORG, " | |||
lv_i_vtweg | TYPE KNVP-VTWEG, " | |||
lv_i_spart | TYPE KNVP-SPART, " | |||
lv_i_call_bapi | TYPE XFELD. " |
  CALL FUNCTION 'SD_PARTNER_GET_SOURCE_PARTNER' "NOTRANSL: Bestimmt 'Quellpartner', in dessen KNVP der Eingabe-Partner vorh |
EXPORTING | ||
I_KUNNR | = lv_i_kunnr | |
I_PARVW | = lv_i_parvw | |
I_PARVW_SOURCE | = lv_i_parvw_source | |
I_VKORG | = lv_i_vkorg | |
I_VTWEG | = lv_i_vtweg | |
I_SPART | = lv_i_spart | |
I_CALL_BAPI | = lv_i_call_bapi | |
IMPORTING | ||
E_KUNNR | = lv_e_kunnr | |
EXCEPTIONS | ||
NO_PARTNER_FOUND = 1 | ||
NO_PARTNER_SELECTED = 2 | ||
. " SD_PARTNER_GET_SOURCE_PARTNER |
ABAP code using 7.40 inline data declarations to call FM SD_PARTNER_GET_SOURCE_PARTNER
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 KUNNR FROM KNA1 INTO @DATA(ld_e_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). | ||||
Search for further information about these or an SAP related objects