IOEBAN SAP (Purchase requisition structure for order info.system) Structure details
Description: Purchase requisition structure for order info.system
Structure field list including key, data, relationships and ABAP select examples
IOEBAN 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 "Purchase requisition structure for order info.system" 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_IOEBAN TYPE IOEBAN.
The IOEBAN table consists of various fields, each holding specific information or linking keys about Purchase requisition structure for order info.system data available in SAP. These include BANFN (Purchase Requisition Number), BNFPO (Item Number of Purchase Requisition), BSART (Purchase Requisition Document Type), BSTYP (Purchasing Document Category).. 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 or numeric)
SAP IOEBAN 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| BANFN | Purchase Requisition Number | BANFN | CHAR | 10 | ALPHA | BANFN | BAN | MBAN_C | |
| BNFPO | Item Number of Purchase Requisition | BNFPO | NUMC | 5 | Assigned to domain | BNFPO | BAP | ||
| BSART | Purchase Requisition Document Type | BBSRT | CHAR | 4 | Assigned to domain | BSART | BBA | ||
| BSTYP | Purchasing Document Category | BSTYP | CHAR | 1 | BSTYP | ||||
| STATU | Processing status of purchase requisition | BANST | CHAR | 1 | BANST | ||||
| EKGRP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| TXZ01 | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| WERKS | Plant | EWERK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
| LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
| MATKL | Material Group | MATKL | CHAR | 9 | Assigned to domain | MATKL | MKL | S_WBWG | |
| MENGE | Purchase Requisition Quantity | BAMNG | QUAN | 13(3) | MENG13 | ||||
| MEINS | Purchase Requisition Unit of Measure | BAMEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| LFDAT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| FRGDT | Purchase Requisition Release Date | FRGDT | DATS | 8 | DATUM | ||||
| WEBAZ | Goods Receipt Processing Time in Days | WEBAZ | DEC | 3 | DEC3 | ||||
| PREIS | Price in Purchase Requisition | BAPRE | CURR | 11(2) | WERT11 | ||||
| PEINH | Price Unit | EPEIN | DEC | 5 | DEC5 | ||||
| PSTYP | Item Category in Purchasing Document | PSTYP | CHAR | 1 | Assigned to domain | PSTYP | |||
| KNTTP | Account Assignment Category | KNTTP | CHAR | 1 | Assigned to domain | KNTTP | KNT | ||
| WEPOS | Goods Receipt Indicator | WEPOS | CHAR | 1 | XFELD | ||||
| REPOS | Invoice Receipt Indicator | REPOS | CHAR | 1 | XFELD | ||||
| LIFNR | Desired Vendor | WLIEF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| FLIEF | Fixed Vendor | FLIEF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| KONNR | Number of Principal Purchase Agreement | KONNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | KTR | |
| KTPNR | Item Number of Principal Purchase Agreement | KTPNR | NUMC | 5 | Assigned to domain | EBELP | |||
| INFNR | Number of Purchasing Info Record | INFNR | CHAR | 10 | Assigned to domain | ALPHA | INFNR | INF | MEIN_C |
| 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 | |||
| BEDAT | Purchase Order Date | BEDAT | DATS | 8 | DATUM | ||||
| BSMNG | Quantity Ordered Against this Purchase Requisition | BSMNG | QUAN | 13(3) | MENG13 | ||||
| EBAKZ | Purchase Requisition Closed | EBAKZ | CHAR | 1 | XFELD | ||||
| BPUEB | Adopt Requisition Price in Purchase Order | BPUEB | CHAR | 1 | BPUEB | ||||
| FRGGR | Release group | FRGGR | CHAR | 2 | Assigned to domain | FRGGR | |||
| FRGKZ | Release Indicator | FRGKZ | CHAR | 1 | Assigned to domain | FRGKZ | |||
| FRGZU | Release status | FRGZU | CHAR | 8 | FRGZU | ||||
| FRGST | Release Strategy in Purchase Requisition | FRGST | CHAR | 2 | FRGST | ||||
| FRGRL | Release Not Yet Completely Effected | FRGRL | CHAR | 1 | XFELD | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS |
| Key field | Non-key field |
How do I retrieve data from SAP structure IOEBAN using ABAP code?
As IOEBAN 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 IOEBAN as there is no data to select.How to access SAP table IOEBAN
Within an ECC or HANA version of SAP you can also view further information about IOEBAN 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