PURCH_WERE SAP (GR/IR Data: Purchasing Documents for Condition Record) Structure details
Description: GR/IR Data: Purchasing Documents for Condition Record
Structure field list including key, data, relationships and ABAP select examples
PURCH_WERE 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 "GR/IR Data: Purchasing Documents for Condition Record" 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_PURCH_WERE TYPE PURCH_WERE.
The PURCH_WERE table consists of various fields, each holding specific information or linking keys about GR/IR Data: Purchasing Documents for Condition Record data available in SAP. These include KOPOS (Sequential number of the condition), EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), LIFNR (Vendor Account Number).. 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 PURCH_WERE 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 |
| KNUMH | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
| KOPOS | Sequential number of the condition | KOPOS | NUMC | 2 | NUM02 | ||||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| BSTMG | Purchase Order Quantity | BSTMG | QUAN | 13(3) | MENG13 | ||||
| WEMNG | Quantity of Goods Received | WEEMG | QUAN | 13(3) | MENG13 | ||||
| OWEMG | Open goods receipt quantity | OWEMG | QUAN | 13(3) | MENG13 | ||||
| OWEPZ | Open goods receipt (percentage) | OWEPZ | DEC | 5(2) | DEC3_2 | ||||
| REMNG | Quantity invoiced | REMNG | QUAN | 13(3) | MENG13 | ||||
| OREMG | Open invoice receipt quantity | OREMG | QUAN | 13(3) | MENG13 | ||||
| OREPZ | Open invoice receipt (percentage) | OREPZ | DEC | 5(2) | DEC3_2 | ||||
| ELIKZ | 'Delivery Completed' Indicator | ELIKZ | CHAR | 1 | XFELD | ||||
| MEINS | Purchase Order Unit of Measure | BSTME | UNIT | 3 | Assigned to domain | CUNIT | MEINS |
| Key field | Non-key field |
How do I retrieve data from SAP structure PURCH_WERE using ABAP code?
As PURCH_WERE 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 PURCH_WERE as there is no data to select.How to access SAP table PURCH_WERE
Within an ECC or HANA version of SAP you can also view further information about PURCH_WERE 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