VMDS_WYT3_S SAP (Partner Functions) Structure details
Description: Partner Functions
Structure field list including key, data, relationships and ABAP select examples
VMDS_WYT3_S is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Partner Functions" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_VMDS_WYT3_S TYPE VMDS_WYT3_S.
The VMDS_WYT3_S table consists of various fields, each holding specific information or linking keys about Partner Functions data available in SAP. These include MANDT (Client), LIFNR (Account Number of Vendor or Creditor), EKORG (Purchasing Organization), LTSNR (Vendor Subrange).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP VMDS_WYT3_S structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| OLD_DATA | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | ALPHA | LIFNR | LIF | KRED_C | |
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | EKORG | EKO | |||
| LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | LTSNR | ||||
| WERKS | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
| PARVW | Partner Function | PARVW | CHAR | 2 | PARVW | PARVW | PAR | ||
| PARZA | Partner counter | PARZA | NUMC | 3 | PARZA | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| LIFN2 | Reference to other vendor | LIFN2 | CHAR | 10 | ALPHA | LIFNR | |||
| DEFPA | Default Partner | DEFPA | CHAR | 1 | XFELD | ||||
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| PARNR | Number of contact person | PARNR | NUMC | 10 | PARNR | VPA | |||
| NEW_DATA | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | ALPHA | LIFNR | LIF | KRED_C | |
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | EKORG | EKO | |||
| LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | LTSNR | ||||
| WERKS | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
| PARVW | Partner Function | PARVW | CHAR | 2 | PARVW | PARVW | PAR | ||
| PARZA | Partner counter | PARZA | NUMC | 3 | PARZA | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| LIFN2 | Reference to other vendor | LIFN2 | CHAR | 10 | ALPHA | LIFNR | |||
| DEFPA | Default Partner | DEFPA | CHAR | 1 | XFELD | ||||
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| PARNR | Number of contact person | PARNR | NUMC | 10 | PARNR | VPA | |||
| UPD | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure VMDS_WYT3_S using ABAP code?
As VMDS_WYT3_S is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on VMDS_WYT3_S as there is no data to select.How to access SAP table VMDS_WYT3_S
Within an ECC or HANA version of SAP you can also view further information about VMDS_WYT3_S and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects