OLR3_R3_TS_REQ_DATA SAP (Fields for Puchase Requisition for External Activity) Structure details
Description: Fields for Puchase Requisition for External Activity
Related tables to OLR3_R3_TS_REQ_DATA
Access table OLR3_R3_TS_REQ_DATA
Structure field list including key, data, relationships and ABAP select examples
OLR3_R3_TS_REQ_DATA 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 "Fields for Puchase Requisition for External Activity" 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_OLR3_R3_TS_REQ_DATA TYPE OLR3_R3_TS_REQ_DATA.
The OLR3_R3_TS_REQ_DATA table consists of various fields, each holding specific information or linking keys about Fields for Puchase Requisition for External Activity data available in SAP. These include EBELP (Purchase Order Item Number), BSMNG (Quantity Ordered Against this Purchase Requisition), LFDAT (Item Delivery Date), FRGDT (Purchase Requisition Release Date).. 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 OLR3_R3_TS_REQ_DATA 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 |
| EBELN | Purchase Order Number | BSTNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | |
| EBELP | Purchase Order Item Number | BSTPO | NUMC | 5 | Assigned to domain | EBELP | |||
| BSMNG | Quantity Ordered Against this Purchase Requisition | BSMNG | QUAN | 13(3) | MENG13 | ||||
| LFDAT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| FRGDT | Purchase Requisition Release Date | FRGDT | DATS | 8 | DATUM | ||||
| BEDAT | Purchase Order Date | BEDAT | DATS | 8 | DATUM | ||||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| WERKS | Plant | EWERK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
| TXZ01 | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
| MENGE | Purchase Order Quantity | BSTMG | QUAN | 13(3) | MENG13 | ||||
| MEINS | Purchase Order Unit of Measure | BSTME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| WEDAT | Goods receipt posting date | WEBUD | DATS | 8 | DATUM | ||||
| WEMNG | Quantity of Goods Received | WEMNG | QUAN | 13(3) | MENG13 | ||||
| BADAT | Requisition (Request) Date | BADAT | DATS | 8 | DATUM | ||||
| FRGST | Release Strategy in Purchase Requisition | FRGST | CHAR | 2 | FRGST | ||||
| FRGGR | Release group | FRGGR | CHAR | 2 | Assigned to domain | FRGGR | |||
| FRGKZ | Release Indicator | FRGKZ | CHAR | 1 | Assigned to domain | FRGKZ | |||
| PASTRTERM | Inspection Start Date | QPRSTART | DATS | 8 | DATUM | ||||
| PAENDTERM | End Date of the Inspection | QPRENDE | DATS | 8 | DATUM | ||||
| VBEWERTUNG | Code Valuation | QBEWERTUNG | CHAR | 1 | QBEWERTUNG | ||||
| VCODE | Usage Decision Code | QVCODE | CHAR | 4 | Assigned to domain | QCODE | |||
| VCODEGRP | Code Group of the Usage Decision | QVGRUPPE | CHAR | 8 | Assigned to domain | QCODEGRP | CGP | ||
| QKENNZAHL | Quality Score | QKENNZAHL | DEC | 3 | QKENNZAHL | ||||
| VFOLGEAKTI | Follow-Up Action | QFOLGEAKTI | CHAR | 8 | Assigned to domain | QFOLGEAKTI | |||
| VDATUM | Date of Code Used for Usage Decision | QVEDATUM | DATS | 8 | DATUM | ||||
| VAEDATUM | Change Date of Usage Decision | QVAEDATUM | DATS | 8 | DATUM | ||||
| PRUEFLOS | Inspection Lot Number | QPLOS | NUMC | 12 | Assigned to domain | QPLOS | QLS | QALS | |
| CODE_GRUP | Combined Text for Code Group and Code | QCODE_GRUP | CHAR | 80 | QCHAR80 | ||||
| QKZ_TEXT | Short Text | QKURZTEXT | CHAR | 40 | QKURZTEXT | ||||
| VBEWERTUNG_TEXT | Explanatory short text | DDTEXT | CHAR | 60 | DDTEXT | ||||
| QKZVERF | Procedure for Calculating Quality Score | QKZVERF | CHAR | 2 | Assigned to domain | QKZVERF | |||
| VKATART | Catalog | QKATART | CHAR | 1 | Assigned to domain | QKATART | QKT | ||
| KTEXT_GRP | Short Description of the Code Group | QKTEXTGR | CHAR | 40 | QKURZTEXT | ||||
| KTEXT_QCD | Short Text for Code (Up to 40 Characters in Length) | QTXT_CODE | CHAR | 40 | QKURZTEXT | ||||
| VENT_TEXT | Short Text | QKURZTEXT | CHAR | 40 | QKURZTEXT |
| Key field | Non-key field |
How do I retrieve data from SAP structure OLR3_R3_TS_REQ_DATA using ABAP code?
As OLR3_R3_TS_REQ_DATA 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 OLR3_R3_TS_REQ_DATA as there is no data to select.How to access SAP table OLR3_R3_TS_REQ_DATA
Within an ECC or HANA version of SAP you can also view further information about OLR3_R3_TS_REQ_DATA 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