SAP ABAP Message Class SDCBO (Dictionary BO Texts)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-DIC (Application Component) ABAP Dictionary
⤷
SDCBO (Package) RDL Artefacts
⤷
⤷
Attributes
| Message class | SDCBO | |
| Short Description | Dictionary BO Texts | |
| Changed On | 20140121 | |
| Last Changed At | 105103 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Table & for BO structure &, node & could not be written | The short text describes the object sufficiently | ||
| 2 | Table & for BO structure &, node & could not be activated | The short text describes the object sufficiently | ||
| 3 | Table & for BO structure &, node & was activated with warnings | The short text describes the object sufficiently | ||
| 4 | Table & for BO structure &, node & was activated successfully | The short text describes the object sufficiently | ||
| 5 | BO structure & was activated successfully | The short text describes the object sufficiently | ||
| 6 | BO structure & was activated with warnings | The short text describes the object sufficiently | ||
| 7 | BO structure & could not be activated | The short text describes the object sufficiently | ||
| 8 | Runtime object for & could not be generated | The short text describes the object sufficiently | ||
| 9 | Runtime object for & could not be written | The short text describes the object sufficiently | ||
| 10 | Type information could not be updated | The short text describes the object sufficiently | ||
| 11 | Incorrect object type &: name check not possible | The short text describes the object sufficiently | ||
| 12 | Activating BO structure & | The short text describes the object sufficiently | ||
| 13 | Activating dependent BO structure & | The short text describes the object sufficiently | ||
| 14 | Activating BO structure & (active version) | The short text describes the object sufficiently | ||
| 15 | Activating tables for BO structure nodes | The short text describes the object sufficiently | ||
| 16 | Name of DB table for structured object &, node & cannot be determined | The short text describes the object sufficiently | ||
| 17 | & & could not be entered in task & | The short text describes the object sufficiently | ||
| 18 | Package missing. TADIR entry will not be written for table &. | The short text describes the object sufficiently | ||
| 19 | Append & for structured obj. &, node & could not be written | The short text describes the object sufficiently | ||
| 20 | Package missing. TADIR entry will not be written for append & | The short text describes the object sufficiently | ||
| 21 | BO parent structure & information for append & could not be read | The short text describes the object sufficiently | ||
| 22 | BO parent struct. & informat. for append & does not exist as active ver. | The short text describes the object sufficiently | ||
| 23 | Append & was not found (deleted or not yet active) | The short text describes the object sufficiently | ||
| 24 | Activate & & | The short text describes the object sufficiently | ||
| 25 | & & for structured object &, node & could not be activated | The short text describes the object sufficiently | ||
| 26 | & & for structured object &, node & was activated with warning messages | The short text describes the object sufficiently | ||
| 27 | & & for structured object &, node & was activated successfully | The short text describes the object sufficiently | ||
| 28 | Node &: No attributes exist | The short text describes the object sufficiently | ||
| 29 | Inconsistency in node source data, node &, append & | The short text describes the object sufficiently | ||
| 30 | Table & is not client-specific | The short text describes the object sufficiently | ||
| 31 | (Internal) node & was deleted; attributes still exist though | The short text describes the object sufficiently | ||
| 32 | (Append) node & was deleted; attributes still exist though | The short text describes the object sufficiently | ||
| 33 | No more attributes exist, but node & still exists | The short text describes the object sufficiently | ||
| 34 | No more external attributes exist, but node & exists externally | The short text describes the object sufficiently | ||
| 35 | Node & was removed from the structured object, DB table & will be deleted | The short text describes the object sufficiently | ||
| 36 | Node & was reoved from append &; DB table & will be deleted | The short text describes the object sufficiently | ||
| 37 | Node &: Name of DB table (&->&) was changed. Deleting table &. | The short text describes the object sufficiently | ||
| 38 | Node &: Alternative key & deleted; index & will be deleted from DB tab. & | The short text describes the object sufficiently | ||
| 39 | Node &: External attribute & is deleted (append & will be deleted) | The short text describes the object sufficiently | ||
| 40 | Node & changed from external to internal; old DB table & will be deleted | The short text describes the object sufficiently | ||
| 41 | Append & for table & will be deleted | The short text describes the object sufficiently | ||
| 42 | Index & of table & will be deleted | The short text describes the object sufficiently | ||
| 43 | Node &: Name of append struct.(&->&) is changed. Deleting app. struct. &. | The short text describes the object sufficiently | ||
| 44 | Node & was changed from external to internal. Deleting append struct. &. | The short text describes the object sufficiently | ||
| 45 | Invalid read status: & | The short text describes the object sufficiently | ||
| 46 | Metadata of structured object & could not be read | The short text describes the object sufficiently | ||
| 47 | Metadata (version 4) does not exist | The short text describes the object sufficiently | ||
| 48 | ============= Messages for Checks of a Structured Object ================ | The short text describes the object sufficiently | ||
| 49 | Incorrect object type &: name check not possible | The short text describes the object sufficiently | ||
| 50 | At least one node must be specified for the structured object | The short text describes the object sufficiently | ||
| 51 | For each node of a structured object, maintain at least one attribute | The short text describes the object sufficiently | ||
| 52 | Checking structured object & | The short text describes the object sufficiently | ||
| 53 | Structured object & has been checked successfully | The short text describes the object sufficiently | ||
| 54 | Structured object was checked, resulted in warning messages | The short text describes the object sufficiently | ||
| 55 | Structured object has errors | The short text describes the object sufficiently | ||
| 56 | The nodes of the structured object have no attributes | The short text describes the object sufficiently | ||
| 57 | Node & has attributes and does not exist in the list of nodes | The short text describes the object sufficiently | ||
| 58 | Impermissible or unknown type & | The short text describes the object sufficiently | ||
| 59 | & & does not exist or is not active | The short text describes the object sufficiently | ||
| 60 | & is not a built-in type | The short text describes the object sufficiently | ||
| 61 | BO structure header is missing | The short text describes the object sufficiently | ||
| 62 | Depth information is not correct or type 7 has no fields | The short text describes the object sufficiently | ||
| 63 | No DB table name exists for node & -> will be generated | The short text describes the object sufficiently | ||
| 64 | Value & is not allowed for & (allowed values &) | The short text describes the object sufficiently | ||
| 65 | Name of database field missing for node attribute &-& | The short text describes the object sufficiently | ||
| 66 | (Information for &-& is not consistent) | The short text describes the object sufficiently | ||
| 67 | Attribute &-& will be adopted in DB table; only scalar types possible | The short text describes the object sufficiently | ||
| 68 | Attribute name & appears multiple times in node & | The short text describes the object sufficiently | ||
| 69 | Association name & appears multiple times in node & | The short text describes the object sufficiently | ||
| 70 | Node & association &: & is not a node attribute | The short text describes the object sufficiently | ||
| 71 | Node & associat.&: & is not a node attribute of target BO/DO structure & | The short text describes the object sufficiently | ||
| 72 | Node & associat. &: & is not a node attribute (may exist in target BO &) | The short text describes the object sufficiently | ||
| 73 | Node & assoc.& field &: Type information source and target is different | The short text describes the object sufficiently | ||
| 74 | & is not a valid data type | The short text describes the object sufficiently | ||
| 75 | Node & association &: target field & is not a node attribute | The short text describes the object sufficiently | ||
| 76 | & & already exists globally as object of another type: | The short text describes the object sufficiently | ||
| 77 | Node name & appears multiple times in BO structure & | The short text describes the object sufficiently | ||
| 78 | Node & comes from an append (&) | The short text describes the object sufficiently | ||
| 79 | Append &: node & is deleted in BO structure. Adapt append accordingly! | The short text describes the object sufficiently | ||
| 80 | Node & is deleted in BO structure &. Adapt append accordingly! | The short text describes the object sufficiently | ||
| 81 | BO structure information could not be added | The short text describes the object sufficiently | ||
| 82 | Append information could not be added | The short text describes the object sufficiently | ||
| 83 | Name of appender is missing | The short text describes the object sufficiently | ||
| 84 | Node & is external in parent node &; was already defined in append <> & | The short text describes the object sufficiently | ||
| 85 | Node & is internal in parent node &; was possibly introduced new there | The short text describes the object sufficiently | ||
| 86 | Append & node &: source is undefined. Check append. | The short text describes the object sufficiently | ||
| 87 | Node source is inconsistent because only partially available (node &) | The short text describes the object sufficiently | ||
| 88 | Field &, node &: No name found for Dictionary table/structure | The short text describes the object sufficiently | ||
| 89 | Field name & for use in DB table exists multiple times in node & | The short text describes the object sufficiently | ||
| 90 | Association & for node & will be deleted | The short text describes the object sufficiently | ||
| 91 | Node & was imported from append &; must be deleted in append | The short text describes the object sufficiently | ||
| 92 | Node & is still being enhanced by append & | The short text describes the object sufficiently | ||
| 93 | Association &: DO as target can only be used in embedding assistant | The short text describes the object sufficiently | ||
| 94 | Association & is an embedding assistant: specify prefix | The short text describes the object sufficiently | ||
| 95 | Embedding assist. &: prefix & must not be concatenated for definition | The short text describes the object sufficiently | ||
| 96 | Embedding assistant &: prefix appears multiple times | The short text describes the object sufficiently | ||
| 97 | No embedding assistant found for this prefix in BO structure & | The short text describes the object sufficiently | ||
| 98 | No embedding assistant found for this prefix in dependent object & | The short text describes the object sufficiently | ||
| 99 | Tables for RBAM checks must both be specified | The short text describes the object sufficiently | ||
| 100 | No RBAM tables can be maintained for BO structure appends | The short text describes the object sufficiently | ||
| 101 | RBAM check is either through ACL assistant or through ACLROOT/ENTRY table | Space: object requires documentation |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in | 803 |