WPWYT3 SAP (Extended WYT3 structure (planned changes)) Structure details
Description: Extended WYT3 structure (planned changes)
Structure field list including key, data, relationships and ABAP select examples
WPWYT3 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 "Extended WYT3 structure (planned changes)" 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_WPWYT3 TYPE WPWYT3.
The WPWYT3 table consists of various fields, each holding specific information or linking keys about Extended WYT3 structure (planned changes) data available in SAP. These include UTIME (Time of Last Change), AENNR (Change Number), CHGFLAG (POS interface: flag for certain field changes), MANDT (Client).. 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: Not classified
SAP WPWYT3 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 |
DATUM | POS interface: date | WJDPOSDAT | DATS | 8 | DATUM | ||||
UTIME | Time of Last Change | UTIME | TIMS | 6 | UZEIT | ||||
AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
CHGFLAG | POS interface: flag for certain field changes | WJDPOSFLAG | CHAR | 1 | X | ||||
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | WYT1 | LTSNR | |||
WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
PARVW | Partner Function | PARVW | CHAR | 2 | TPAR | 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 | LFA1 | 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 |
Key field | Non-key field |
How do I retrieve data from SAP structure WPWYT3 using ABAP code?
As WPWYT3 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 WPWYT3 as there is no data to select.How to access SAP table WPWYT3
Within an ECC or HANA version of SAP you can also view further information about WPWYT3 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