EBAN_ORD_CUST SAP (Changeable purchase request flds with customer exit in order) Structure details
Description: Changeable purchase request flds with customer exit in order
Related tables to EBAN_ORD_CUST
Access table EBAN_ORD_CUST
Structure field list including key, data, relationships and ABAP select examples
EBAN_ORD_CUST 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 "Changeable purchase request flds with customer exit in order" 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_EBAN_ORD_CUST TYPE EBAN_ORD_CUST.
The EBAN_ORD_CUST table consists of various fields, each holding specific information or linking keys about Changeable purchase request flds with customer exit in order data available in SAP. These include ABLAD (Unloading Point), BEDNR (Requirement Tracking Number), FLIEF (Fixed Vendor), BPUEB (Adopt Requisition Price in Purchase Order).. 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 EBAN_ORD_CUST 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 |
| WEMPF | Goods Recipient/Ship-To Party | WEMPF | CHAR | 12 | WEMPF | ||||
| ABLAD | Unloading Point | ABLAD | CHAR | 25 | TEXT25 | ||||
| BEDNR | Requirement Tracking Number | BEDNR | CHAR | 10 | CHAR10 | ||||
| FLIEF | Fixed Vendor | FLIEF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| BPUEB | Adopt Requisition Price in Purchase Order | BPUEB | CHAR | 1 | BPUEB | ||||
| LFDAT | Delivery date | LFDAT | DATS | 8 | DATUM | ||||
| BSART | Order Type (Purchasing) | BSART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
| 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 | |||
| AFNAM | Name of Requisitioner/Requester | AFNAM | CHAR | 12 | AFNAM | ||||
| IDNLF | Material Number Used by Vendor | IDNLF | CHAR | 35 | IDNEX | ||||
| FRGDT | Purchase Requisition Release Date | FRGDT | DATS | 8 | DATUM | ||||
| LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG |
| Key field | Non-key field |
How do I retrieve data from SAP structure EBAN_ORD_CUST using ABAP code?
As EBAN_ORD_CUST 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 EBAN_ORD_CUST as there is no data to select.How to access SAP table EBAN_ORD_CUST
Within an ECC or HANA version of SAP you can also view further information about EBAN_ORD_CUST 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