CNDOK SAP (Key Word Structure (Distinction between Networks and Orders)) Structure details
Dictionary Type: Structure
Description: Key Word Structure (Distinction between Networks and Orders)
Description: Key Word Structure (Distinction between Networks and Orders)
Structure field list including key, data, relationships and ABAP select examples
CNDOK 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 "Key Word Structure (Distinction between Networks and Orders)" 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_CNDOK TYPE CNDOK.
The CNDOK table consists of various fields, each holding specific information or linking keys about Key Word Structure (Distinction between Networks and Orders) data available in SAP. These include PLNNR (Standard network number), PLNAL (Alternative to a standard network), AUART (Network type), KSTEL (General costs element number).. 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 CNDOK 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 |
| AUFNR | Network number | NW_AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| PLNNR | Standard network number | CN_PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | STDN | |
| PLNAL | Alternative to a standard network | CN_PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| AUART | Network type | NW_AUART | CHAR | 4 | T003O | AUFART | |||
| KSTEL | General costs element number | CN_KSTEL | CHAR | 4 | NUMCV | VORNR | |||
| ARBEL | Work element number | CN_ARBEL | CHAR | 4 | NUMCV | VORNR | |||
| FRDEL | External processing element | CN_FRDEL | CHAR | 4 | NUMCV | VORNR | |||
| REFNR | Number of network to be copied | NW_REFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | AUKO | |
| ELEMENT | Activity element number (work/external/general costs) | CN_ELEMENT | CHAR | 4 | NUMCV | VORNR | |||
| AUFTRAG | Order number | CO_AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| RFS_KSTVRG | Sequence key for general costs activity (check) | RFS_KSTVRG | CHAR | 6 | Assigned to domain | CIM_RSCHL | |||
| RFS_EIGVRG | Sequence key for internally processed activity (check) | RFS_EIGVRG | CHAR | 6 | Assigned to domain | CIM_RSCHL | |||
| RFS_FRDVRG | Sequence key for externally processed activity (check) | RFS_FRDVRG | CHAR | 6 | Assigned to domain | CIM_RSCHL | |||
| RFS_KSTELM | Sequence key for general costs element (check) | RFS_KOSELM | CHAR | 6 | Assigned to domain | CIM_RSCHL | |||
| RFS_ARBELM | Sequence key for the work element (check) | RFS_ARBELM | CHAR | 6 | Assigned to domain | CIM_RSCHL | |||
| RFS_FRDELM | Sequence key for externally processed element (check) | RFS_FRDELM | CHAR | 6 | Assigned to domain | CIM_RSCHL | |||
| CN_VORNR | Activity number in network and standard network | CN_VORNR | CHAR | 4 | NUMCV | VORNR | |||
| NET_SHIFT | Scheduling indicator: Shift network | NET_SHIFT | CHAR | 1 | XFELD | ||||
| POSNR | Component item | NW_POSNR | CHAR | 4 | NUMCV | SPOSN | |||
| COPY_MLS | Indicator: Copy milestones | FLG_CO_MLS | CHAR | 1 | KREUZ | ||||
| VBELN | Sales Document | VBELN_VA | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| VPOSN | Sales Document Item | POSNR_VA | NUMC | 6 | Assigned to domain | POSNR | APO | ||
| TCJO1PLAN | Order values for orders in planning phase | TCJO1PLAN | CHAR | 1 | XFELD | ||||
| TCJO1FREI | Order value for orders being executed | TCJO1FREI | CHAR | 1 | XFELD | ||||
| TCJO1ABGL | Order value for closed orders | TCJO1ABGL | CHAR | 1 | XFELD | ||||
| TCJO1LOEKZ | Order value for orders with deletion indicators | TCJO1LOEKZ | CHAR | 1 | XFELD | ||||
| TCJO1ADDKZ | Appended plan update | TCJO1ADDKZ | CHAR | 1 | XFELD | ||||
| SUBNT | Subnetwork number | CN_SUBNT | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ||
| TCJO1DSPKZ | Order Plan Values as Assigned Funds in the Planning Phase | TCJO1DSPKZ | CHAR | 1 | XFELD | ||||
| CCDEF | Default values for entry lines in collective confirmation | CN_DEFAULT | CHAR | 3 | CHAR3 | ||||
| NLFZV | Activity related offset | CN_NLFZV | DEC | 3 | NLFZT | ||||
| SCHED_START | Scheduling aligned with activity start date | SCHED_START | CHAR | 1 | XFELD | ||||
| SCHED_END | Scheduling aligned with activity finish date | SCHED_END | CHAR | 1 | XFELD | ||||
| VBELV | Original Document | CN_VBELV | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
| CN_VERTN | Distribution key for general costs activities | CN_VERTN | CHAR | 8 | Assigned to domain | CR_VERTL | |||
| PLANCOST | Determine Plan Costs: 1/2/3 | CO_PCOST | CHAR | 1 | CO_PCOST | ||||
| KZEKL | Indicator: Unit costing exists | KZEKL | CHAR | 1 | XFELD | ||||
| CN_LTXA1 | Network activity description | CN_LTXA1 | CHAR | 40 | TEXT40 | ||||
| SCHED_INST | Schedule maintenance/service orders | CN_SCHINST | NUMC | 1 | CN_SCHINST | ||||
| GRP_PSP | Grouping WBS element | GRPSPNR | NUMC | 8 | Assigned to domain | KONPR | PS_POSNR | PSP | |
| NW_PLANCOST | Calculation of planned costs | CN_PCOST | CHAR | 1 | CN_PCOST | ||||
| LOSVG | Quantity of an external network activity | CN_LOSVG | QUAN | 13(3) | MENG13 | ||||
| EXT_AUFNR | Network number | NW_AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| PRCTYPE | Procurement Type | NW_PRCTYPE | CHAR | 40 | TEXT40 |
| Key field | Non-key field |
How do I retrieve data from SAP structure CNDOK using ABAP code?
As CNDOK 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 CNDOK as there is no data to select.How to access SAP table CNDOK
Within an ECC or HANA version of SAP you can also view further information about CNDOK 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