API_CITEM SAP (All Items in Configuration Structure) Structure details
Description: All Items in Configuration Structure
Structure field list including key, data, relationships and ABAP select examples
API_CITEM 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 "All Items in Configuration Structure" 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_API_CITEM TYPE API_CITEM.
The API_CITEM table consists of various fields, each holding specific information or linking keys about All Items in Configuration Structure data available in SAP. These include INSTS (Instance number within DDB (configuration)), FL_TRUE (Single-Character Indicator), CUOBJ (Configuration (internal object number)), CINST (Instance number within DDB (configuration)).. 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 API_CITEM 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 |
INSTP | Instance number within DDB (configuration) | CUINST | NUMC | 8 | NUMC8 | ||||
INSTS | Instance number within DDB (configuration) | CUINST | NUMC | 8 | NUMC8 | ||||
FL_TRUE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
CUOBJ | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX | |||
CINST | Instance number within DDB (configuration) | CUINST | NUMC | 8 | NUMC8 | ||||
KZMBW | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
POSNR | BOM Item Number | SPOSN | CHAR | 4 | NUMCV | SPOSN | |||
OBJTY | Object type (BOM item) | OBJTY | CHAR | 1 | Assigned to domain | OBJTY | |||
POSTP | Item Category (Bill of Material) | POSTP | CHAR | 1 | Assigned to domain | POSTP | |||
IDNRK | BOM component | IDNRK | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
KLART | Class Type | KLASSENART | CHAR | 3 | Assigned to domain | KLASSENART | KAR | ||
CLASS | Class number | KLASSE_D | CHAR | 18 | KLASSE | KLA | |||
DOKAR | Document Type | DOKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
DOKNR | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
QUANM | Component quantity | KMPMG | QUAN | 13(3) | MENGV13 | ||||
QUANR | Component quantity | KMPMG | QUAN | 13(3) | MENGV13 | ||||
ATAUT | Classification: Author | ATAUT | CHAR | 1 | ATAUT | ||||
ISPEC | Specialized manually | MSPEC | CHAR | 1 | MSPEC | ||||
INEW | Instance Inserted Manually | INEW | CHAR | 1 | INEW | ||||
IINST | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
FREE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
LOCKED | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
INCOMPLETE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
INCONSISTENT | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
IDNRK_MVAR | BOM component | IDNRK | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
IDNRK_INST | BOM component | IDNRK | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
NODE | Item is a Node | CU_NODE | CHAR | 1 | CU_NODE | ||||
TRUE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
IFIXI | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C |
Key field | Non-key field |
How do I retrieve data from SAP structure API_CITEM using ABAP code?
As API_CITEM 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 API_CITEM as there is no data to select.How to access SAP table API_CITEM
Within an ECC or HANA version of SAP you can also view further information about API_CITEM 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