BAPICUCFGM SAP (VAW: Configuration Data) Structure details
Description: VAW: Configuration Data
Structure field list including key, data, relationships and ABAP select examples
BAPICUCFGM 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 "VAW: Configuration Data" 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_BAPICUCFGM TYPE BAPICUCFGM.
The BAPICUCFGM table consists of various fields, each holding specific information or linking keys about VAW: Configuration Data data available in SAP. These include SD_DOC (Sales and Distribution Document Number), POSEX (External Item Number), CONFIG_ID (External Configuration ID (Temporary)), ROOT_ID (Instance Number in 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: Not classified
SAP BAPICUCFGM 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 |
| OPERATION | Function | MSGFN | CHAR | 3 | MSGFN | ||||
| SD_DOC | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| POSEX | External Item Number | CU_POSEX | CHAR | 6 | CHAR6 | ||||
| CONFIG_ID | External Configuration ID (Temporary) | CUXCFG_ID | CHAR | 6 | CHAR6 | ||||
| ROOT_ID | Instance Number in Configuration | CU_INST_ID | CHAR | 8 | CHAR8 | ||||
| SCE | CU: Only Information Transferred from SCE to Configuration | CUFLAG1 | CHAR | 1 | CUFLAG1 | ||||
| KBNAME | Knowledge-Base Object | KBOBJNAME | CHAR | 30 | Assigned to domain | KBOBJNAME | KBO | ||
| KBVERSION | Runtime Version of SCE Knowledge Base | RTVERSION | CHAR | 30 | CHAR30 | KBR | |||
| COMPLETE | General Indicator | CU_CHECKED | CHAR | 1 | CHAR1 | ||||
| CONSISTENT | General Indicator | CU_CHECKED | CHAR | 1 | CHAR1 | ||||
| CFGINFO | CU: Configuration BLOB (SCE) | CUBLOB | CHAR | 250 | CUBLOB | ||||
| KBPROFILE | Knowledge-Base Profile | CUX_KBPROFILE | CHAR | 30 | CHAR30 | ||||
| KBLANGUAGE | Configuration Language | CUX_KBLANGUAGE | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| CBASE_ID | Instance Number (Persistent) | CUX_PERSIST_ID | CHAR | 32 | CHAR32 | ||||
| CBASE_ID_TYPE | Type of Instance Number (Persistent) | CUX_PERSIST_ID_TYPE | CHAR | 1 | CUX_PERSIST_ID_TYPE |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPICUCFGM using ABAP code?
As BAPICUCFGM 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 BAPICUCFGM as there is no data to select.How to access SAP table BAPICUCFGM
Within an ECC or HANA version of SAP you can also view further information about BAPICUCFGM 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