Data Element list used by SAP ABAP Table DDTBFDCHK (Control String for Table Checks (Fields))
SAP ABAP Table
DDTBFDCHK (Control String for Table Checks (Fields)) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | DCIDEL0001 | Test: Are fields to be deleted reference fields? | ||
| 2 | DCIDEL0002 | Test: Are fields to be deleted used in aggregate? | ||
| 3 | DCILTY0001 | Test: Is use of type VARC correct? | ||
| 4 | DCILTY0003 | Test: Is use of type LCHR correct? | ||
| 5 | DCILTY0004 | Test: Is use of type LRAW correct? | ||
| 6 | DCILTY0005 | Test: Does more than one LONG field exist? | ||
| 7 | DCINNU0001 | Authorization check for the not null flag | ||
| 8 | DCINNU0002 | Test of the length restriction of NOT NULL fields | ||
| 9 | DCIPOO0001 | Test: Do pooled tables have keys of an allowed data type ? | ||
| 10 | DCIPOO0002 | Test: Is key of a pooled table too long? | ||
| 11 | DCIPOO0003 | Test: Are the fields of a pooled table too long? | ||
| 12 | DCIPOO0004 | Length check for special logical pooled tables | ||
| 13 | DCIREF0001 | Test: Do reference table and reference field exist? | ||
| 14 | DCIREF0002 | Reference table is table to be activated | ||
| 15 | DCIREF0003 | Reference table is a different table | ||
| 16 | DCITES0001 | Test: Is key field number OK for generic buffering? | ||
| 17 | DCITES0002 | Test: Is the table to be logged too long? | ||
| 18 | DCIVAL0001 | Test: Does the KEYFLAG have an allowed value? | ||
| 19 | DCIVAL0002 | Test: Does the MANDATORY flag have an allowed value? | ||
| 20 | DCIVAL0003 | Test: Is the value for the INCLUDE level allowed? | ||
| 21 | DCIVAL0004 | Test: Does the NOT NULL flag have an allowed value? | ||
| 22 | DCKEYC0001 | Test: Does key field exist? | ||
| 23 | DCKEYC0002 | Test: Are there too many key fields? | ||
| 24 | DCKEYC0003 | Test: Do key fields belong together ? | ||
| 25 | DCKEYC0004 | Test: Is key located at the start? | ||
| 26 | DCKEYC0005 | Test: Is the key too long? | ||
| 27 | DCKEYC0006 | Test: Does key have a maximum of 120 bytes ? | ||
| 28 | DCSAAN0001 | Test: Does name exist? | ||
| 29 | DCSAAN0002 | Test: Is name too long? | ||
| 30 | DCSAAN0003 | Test: Does name contain blanks? | ||
| 31 | DCSAAN0004 | Test: Does name contain '-'? | ||
| 32 | DCSAAN0005 | Test: Does name start with a letter? | ||
| 33 | DCSAAN0006 | Open | ||
| 34 | DCSAAN0007 | Test: Does name contain only allowed characters? | ||
| 35 | DCSAAN0008 | Test: Is 2nd or 3rd char. of name an underscore? | ||
| 36 | DCSAAN0009 | Test: Is name reserved? | ||
| 37 | DCTBFD0001 | Test: Duplicate field names | ||
| 38 | DCTBFD0002 | Test: Do fields use active data elements? | ||
| 39 | DCTBFD0003 | Test: Is client field (if it exists) in first position? | ||
| 40 | DCTBFD0004 | Test: Is data type correct? | ||
| 41 | DCTBFD0005 | Test: Are key fields unchanged? | ||
| 42 | DCTBFD0006 | Test: Is data type VARC used? | ||
| 43 | DCTBFD0007 | Test: Is table too long for the database ? | ||
| 44 | DCTBFD0008 | Test: Are fields of types CHAR and DEC too long? | ||
| 45 | DCTBFD0009 | Cluster table test: Is key correct? | ||
| 46 | DCTBFD0010 | Open | ||
| 47 | DCTBFD0011 | Test: Is translation-relevance meaningful ? | ||
| 48 | DCTBFD0012 | Test: Does the table contain any fields? | ||
| 49 | DCTBFD0013 | Test: Is SAP field in customer namespace? | ||
| 50 | DCTBFD0014 | Test: Is customer field in SAP namespace? | ||
| 51 | DCTBFD0015 | Test: Is field from special development in SAP table ? |