AEOI_API01 SAP (Interface for processing table AEOI using API) Structure details
Description: Interface for processing table AEOI using API
Structure field list including key, data, relationships and ABAP select examples
AEOI_API01 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 "Interface for processing table AEOI using API" 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_AEOI_API01 TYPE AEOI_API01.
The AEOI_API01 table consists of various fields, each holding specific information or linking keys about Interface for processing table AEOI using API data available in SAP. These include CHG_OBJTYP (Engineering Change Management Object), BOM_CAT (BOM Category), BOM_STD_OBJECT (Standard Object), BOM_USAGE (BOM Usage).. 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 AEOI_API01 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 |
ALT_DATE | Alternative date external key | AEDTN | CHAR | 18 | CHAR18 | ||||
CHG_OBJTYP | Engineering Change Management Object | AEOBJ | NUMC | 1 | Assigned to domain | AEOBJ | |||
BOM_CAT | BOM Category | CC_STLTY | CHAR | 1 | CC_STLTY | ||||
BOM_STD_OBJECT | Standard Object | CC_STOBJ | CHAR | 18 | CC_CHAR18 | ||||
BOM_USAGE | BOM Usage | CC_STLAN | CHAR | 1 | CC_STLAN | CC_STLAN | |||
CHGTYPEOBJ | Change Type for Object | CCOAA | NUMC | 3 | Assigned to domain | CCOAA | |||
DESCR_OBJ | Object management record description | OITXT | CHAR | 40 | TEXT40 | ||||
DOC_TYPE | Document Type | CC_DOKAR | CHAR | 3 | CC_DOKAR | CV2 | |||
DOC_NUMBER | Document number | CC_DOKNR | CHAR | 25 | ALPHA | CC_DOKNR | CV1 | ||
DOC_VERS | Document Version | CC_DOKVR | CHAR | 2 | CC_DOKVR | CV3 | |||
DOC_PART | Document Part | CC_DOKTL_D | CHAR | 3 | CC_DOKTL | CV4 | |||
EQUIPMENT | Equipment number | CC_EQUNR | CHAR | 18 | ALPHA | CC_EQUNR | CC_EQUI | ||
FUNC_LOC | Functional Location | CC_TPLNR | CHAR | 30 | CCTPL | CC_TPLNR | CC_IFLM | ||
MATERIAL | Material number | CCMATNR | CHAR | 18 | CCMAT | CCMATNR | MAT | CC_MAT1 | |
PLANT | Plant | CC_WERKS_D | CHAR | 4 | Assigned to domain | CC_WERKS | CC_WERKS | ||
PSP_ELEMENT | Work breakdown structure element (WBS element) | CC_PSP_PNR | CHAR | 24 | CHAR24 | ||||
PVS_GUID | Internal Identification for PVS Objects | CCPVS_GUID | RAW | 16 | SYSUUID | ||||
PVS_TYPE | PVS Type | CC_PVSTY | CHAR | 1 | CC_PVSTY | ||||
PVS_NODE | Engineering Change Management: iPPE Nodes | CC_PVS_PNODE | CHAR | 40 | CC_PVS_PNODE | ||||
PVS_CLASS_NUMBER | Class number | KLASSE_D | CHAR | 18 | KLASSE | KLA | |||
PVS_CLASS_TYPE | Class Type | KLASSENART | CHAR | 3 | Assigned to domain | KLASSENART | KAR | ||
PVS_VARIANT | Engineering Change Management (ECH): PVS variants | CC_PVS_POSVAR | CHAR | 8 | CC_PVS_POSVAR | ||||
SD_ORDER | Sales order | CC_VBELN | CHAR | 10 | ALPHA | CC_VBELN | AUN | CC_VBELN | |
SD_ORDER_I | Sales order item | CC_VBPOS | NUMC | 6 | CC_POSNR | APO | CC_VBPOS | ||
TEXTKEY | ECM: text key for APIs and IDOCs | CC_TEXTKEY | NUMC | 8 | CC_NUMC8 | ||||
TLIST_TYPE | Task List Type | CC_PLNTY | CHAR | 1 | Assigned to domain | CC_PLNTY | |||
TLIST_GRP | Key for Task List Group | CC_PLNNR | CHAR | 8 | ALPHA | CC_PLNNR | |||
OBJ_CHGLOCK | Indicator: object locked for changes | CCLCK | CHAR | 1 | XFELD | ||||
STATUS_PROF_OBJ | Status Profile | CC_J_STSMA | CHAR | 8 | CC_J_STSMA | ||||
FL_DELETE | Deletion Indicator | FLLKENZ | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure AEOI_API01 using ABAP code?
As AEOI_API01 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 AEOI_API01 as there is no data to select.How to access SAP table AEOI_API01
Within an ECC or HANA version of SAP you can also view further information about AEOI_API01 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