SAP VENDOR_MASTER_DATA_SELECT_17 Function Module for Determine Partner of a Vendor According to Partner Role









VENDOR_MASTER_DATA_SELECT_17 is a standard vendor master data select 17 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Partner of a Vendor According to Partner Role 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 vendor master data select 17 FM, simply by entering the name VENDOR_MASTER_DATA_SELECT_17 into the relevant SAP transaction such as SE37 or SE38.

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



Function VENDOR_MASTER_DATA_SELECT_17 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 'VENDOR_MASTER_DATA_SELECT_17'"Determine Partner of a Vendor According to Partner Role
EXPORTING
PI_LIFNR = "Vendor
PI_EKORG = "Purchasing Organization
* PI_LTSNR = ' ' "Vendor Subrange
* PI_WERKS = ' ' "Plant
PI_PARVW = "Partner Role
* PI_PREFETCH = 'X' "

IMPORTING
PE_PARTNER = "

TABLES
* T_E_WYT3 = "

EXCEPTIONS
PARAMETER_MISSING = 1 NO_ENTRY_FOUND = 2 NO_PARTNER_FOUND = 3 NO_EXISTING_MASTER_DATA = 4
.



IMPORTING Parameters details for VENDOR_MASTER_DATA_SELECT_17

PI_LIFNR - Vendor

Data type: WYT3-LIFNR
Optional: No
Call by Reference: No ( called with pass by value option)

PI_EKORG - Purchasing Organization

Data type: WYT3-EKORG
Optional: No
Call by Reference: No ( called with pass by value option)

PI_LTSNR - Vendor Subrange

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

PI_WERKS - Plant

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

PI_PARVW - Partner Role

Data type: WYT3-PARVW
Optional: No
Call by Reference: No ( called with pass by value option)

PI_PREFETCH -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for VENDOR_MASTER_DATA_SELECT_17

PE_PARTNER -

Data type: KRED_PART
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for VENDOR_MASTER_DATA_SELECT_17

T_E_WYT3 -

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

EXCEPTIONS details

PARAMETER_MISSING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_ENTRY_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_PARTNER_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_EXISTING_MASTER_DATA -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for VENDOR_MASTER_DATA_SELECT_17 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_pi_lifnr  TYPE WYT3-LIFNR, "   
lt_t_e_wyt3  TYPE STANDARD TABLE OF WYT3, "   
lv_pe_partner  TYPE KRED_PART, "   
lv_parameter_missing  TYPE KRED_PART, "   
lv_pi_ekorg  TYPE WYT3-EKORG, "   
lv_no_entry_found  TYPE WYT3, "   
lv_pi_ltsnr  TYPE WYT3-LTSNR, "   SPACE
lv_no_partner_found  TYPE WYT3, "   
lv_pi_werks  TYPE WYT3-WERKS, "   SPACE
lv_no_existing_master_data  TYPE WYT3, "   
lv_pi_parvw  TYPE WYT3-PARVW, "   
lv_pi_prefetch  TYPE C. "   'X'

  CALL FUNCTION 'VENDOR_MASTER_DATA_SELECT_17'  "Determine Partner of a Vendor According to Partner Role
    EXPORTING
         PI_LIFNR = lv_pi_lifnr
         PI_EKORG = lv_pi_ekorg
         PI_LTSNR = lv_pi_ltsnr
         PI_WERKS = lv_pi_werks
         PI_PARVW = lv_pi_parvw
         PI_PREFETCH = lv_pi_prefetch
    IMPORTING
         PE_PARTNER = lv_pe_partner
    TABLES
         T_E_WYT3 = lt_t_e_wyt3
    EXCEPTIONS
        PARAMETER_MISSING = 1
        NO_ENTRY_FOUND = 2
        NO_PARTNER_FOUND = 3
        NO_EXISTING_MASTER_DATA = 4
. " VENDOR_MASTER_DATA_SELECT_17




ABAP code using 7.40 inline data declarations to call FM VENDOR_MASTER_DATA_SELECT_17

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 LIFNR FROM WYT3 INTO @DATA(ld_pi_lifnr).
 
 
 
 
"SELECT single EKORG FROM WYT3 INTO @DATA(ld_pi_ekorg).
 
 
"SELECT single LTSNR FROM WYT3 INTO @DATA(ld_pi_ltsnr).
DATA(ld_pi_ltsnr) = ' '.
 
 
"SELECT single WERKS FROM WYT3 INTO @DATA(ld_pi_werks).
DATA(ld_pi_werks) = ' '.
 
 
"SELECT single PARVW FROM WYT3 INTO @DATA(ld_pi_parvw).
 
DATA(ld_pi_prefetch) = 'X'.
 


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!