Data Element list used by SAP ABAP Table DCENACTCHK (Control string for checking the lock object activation prog.)
SAP ABAP Table 
DCENACTCHK (Control string for checking the lock object activation prog.) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
 |
|
|||
| 1 |  Data Element |
DCENBT0001 | Test: Do all base tables belong to lock object | |
| 2 | Data Element |
DCENBT0002 | Test: Is primary table consistent? | |
| 3 | Data Element |
DCENBT0003 | Test: Are all base tables active? | |
| 4 | Data Element |
DCENBT0004 | Test: Do any base tables occur twice? | |
| 5 | Data Element |
DCENBT0005 | Test: Are lock modes defined only for base tables | |
| 6 | Data Element |
DCENBT0006 | Test: Do all base tables of lock object have allowed type | |
| 7 | Data Element |
DCENBT0007 | Test: Are TABPOS entries correct | |
| 8 | Data Element |
DCENBT0009 | Test: Is a lock mode defined for each base table | |
| 9 | Data Element |
DCENBT0010 | Test if all entered lock modes are valid | |
| 10 | Data Element |
DCENDT0008 | Test: Can at least one base table be locked? | |
| 11 | Data Element |
DCENFD0001 | Test: Do all fields belong to the lock object? | |
| 12 | Data Element |
DCENFD0002 | Test: Does lock object have at least one lock parameter? | |
| 13 | Data Element |
DCENFD0004 | Test: Do lock parameters belong to base table fields? | |
| 14 | Data Element |
DCENFD0005 | Test: Does each field belong to at least one lock parameter? | |
| 15 | Data Element |
DCENFF0002 | Test: Have foreign keys been changed? | |
| 16 | Data Element |
DCENFF0003 | Test: Have only foreign keys to base tables been changed? | |
| 17 | Data Element |
DCENFF0004 | Test: Is foreign key table above check table? | |
| 18 | Data Element |
DCENFF0005 | Test: Do fields from base tables max. of one for. key fields | |
| 19 | Data Element |
DCENFK0001 | Test: Do all lock parameters belong to key fields? | |
| 20 | Data Element |
DCENFK0002 | Test: Does the foreign key dependency really exist? | |
| 21 | Data Element |
DCENFK0003 | Test: Has foreign key dependency been entered correctly? | |
| 22 | Data Element |
DCENFK0004 | Test: Is predecessor table base table? | |
| 23 | Data Element |
DCENFK0005 | Test: Do lock parameters not belong to a check field | |
| 24 | Data Element |
DCENFK0006 | Test: Are all foreign key fields key fields? | |
| 25 | Data Element |
DCENGP0001 | Test if total length per argument is =< 120 | |
| 26 | Data Element |
DCENGP0002 | Test if each lock parameter locks at least one table | |
| 27 | Data Element |
DCENGP0003 | Test, if all lock fields have allowed type | |
| 28 | Data Element |
DCENGP0004 | Test if interface of lock function module is narrow enough | |
| 29 | Data Element |
DCENGP0005 | Test if all lock fields have a valid type | |
| 30 | Data Element |
DCENHD0001 | Test: Does lock object name correspond to that in header | |
| 31 | Data Element |
DCENHD0002 | Test: Does lock object header have aggregate type 'E' | |
| 32 | Data Element |
DCENHD0003 | Test: Does the lock object exist? | |
| 33 | Data Element |
DCENHD0004 | Test: Is name of lock object allowable? | |
| 34 | Data Element |
DCENNM0001 | Test: Are names of the lock parameters valid field names? | |
| 35 | Data Element |
DCENNM0002 | Test: Does name of lock parameter not start with 'X_' | |
| 36 | Data Element |
DCENNM0003 | Test: Does name of lock parameter not start with 'MODE_' | |
| 37 | Data Element |
DCENNM0004 | Test: Do all lock parameters have different names? | |
| 38 | Data Element |
DCENNM0005 | Check for name conflict lock parameters - base tables | |
| 39 | Data Element |
DCENNM0006 | Check whether the lock parameters are not invalid |
