CMDT_CD_CC SAP (Generic Master Record: Cost Center Enhancements - Data Part) Structure details
Description: Generic Master Record: Cost Center Enhancements - Data Part
Structure field list including key, data, relationships and ABAP select examples
CMDT_CD_CC 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 "Generic Master Record: Cost Center Enhancements - Data Part" 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_CMDT_CD_CC TYPE CMDT_CD_CC.
The CMDT_CD_CC table consists of various fields, each holding specific information or linking keys about Generic Master Record: Cost Center Enhancements - Data Part data available in SAP. These include KOSTL (Cost Center), BUKRS (Company Code), GSBER (Business Area), KOSAR (Cost Center 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 CMDT_CD_CC 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 |
KOKRS | Controlling Area | KOKRS | CHAR | 4 | Assigned to domain | CACCD | CAC | ||
KOSTL | Cost Center | KOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KOS | |
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
GSBER | Business Area | GSBER | CHAR | 4 | TGSB | GSBER | GSB | ||
KOSAR | Cost Center Category | KOSAR | CHAR | 1 | TKA05 | KOSAR | PCA_KOSAR | ||
PRCTR | Profit Center | PRCTR | CHAR | 10 | Assigned to domain | ALPHA | PRCTR | PRC | PRCTR_EMPTY |
FUNC_AREA | Functional Area | FKBER | CHAR | 16 | TFKB | FKBER | FBE | ||
ABTEI | Department | ABTEI | CHAR | 12 | ABTEI | ||||
CPI_TEMPL | Template for Activity-Independent Formula Planning | CCA_TEMPL_CPI | CHAR | 10 | COTPL | ABC_TEMPL | ABT | ||
CPD_TEMPL | Template for Activity-Dependent Formula Planning | CCA_TEMPL_CPD | CHAR | 10 | COTPL | ABC_TEMPL | ABT | ||
SCI_TEMPL | Template: Activity-Independent Allocation to Cost Center | CCA_TEMPL_SCI | CHAR | 10 | COTPL | ABC_TEMPL | ABT | ||
SCD_TEMPL | Template: Activity-Dependent Allocation to Cost Center | CCA_TEMPL_SCD | CHAR | 10 | COTPL | ABC_TEMPL | ABT | ||
KALSM | Costing Sheet | AUFKALSM | CHAR | 6 | T683 | KALSM | |||
BKZKP | Lock Indicator for Actual Primary Postings | BKZKP | CHAR | 1 | YNFLG | ||||
PKZKP | Lock Indicator for Plan Primary Costs | PKZKP | CHAR | 1 | YNFLG | ||||
BKZKS | Lock Indicator for Actual Secondary Costs | BKZKS | CHAR | 1 | YNFLG | ||||
BKZER | Lock Indicator for Actual Revenue Postings | BKZER | CHAR | 1 | YNFLG | ||||
BKZOB | Lock Indicator for Commitment Update | BKZOB | CHAR | 1 | YNFLG | ||||
PKZKS | Lock Indicator for Plan Secondary Costs | PKZKS | CHAR | 1 | YNFLG | ||||
PKZER | Lock Indicator for Planning Revenues | PKZER | CHAR | 1 | YNFLG | ||||
MGEFL | Indicator for Recording Consumption Quantities | MGEFL | CHAR | 1 | YNFLG | ||||
VNAME | Joint Venture | JV_NAME | CHAR | 6 | T8JV | ALPHA | JV_NAME | JVV | |
RECID | Recovery Indicator | JV_RECIND | CHAR | 2 | T8JJ | ALPHA | JV_RECIND | ||
ETYPE | Equity type | JV_ETYPE | CHAR | 3 | T8JG | ALPHA | JV_ETYPE | ||
JV_OTYPE | Joint Venture Object Type | JV_OTYPE | CHAR | 4 | ALPHA | JV_OTYPE | |||
JV_JIBCL | JIB/JIBE Class | JV_JIBCL | CHAR | 3 | T8J6A | JV_JIBCL | JIB | ||
JV_JIBSA | JIB/JIBE Subclass A | JV_JIBSA | CHAR | 5 | T8J6C | JV_JIBSA | JBS |
Key field | Non-key field |
How do I retrieve data from SAP structure CMDT_CD_CC using ABAP code?
As CMDT_CD_CC 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 CMDT_CD_CC as there is no data to select.How to access SAP table CMDT_CD_CC
Within an ECC or HANA version of SAP you can also view further information about CMDT_CD_CC 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