SADL_GW_DT_CDS - Messages CDS Checks
The following messages are stored in message class SADL_GW_DT_CDS: Messages CDS Checks.
It is part of development package SADL_GW_DT_SECONDARY_GENERAL in software component BC-ESI-ESF-GW. This development package consists of objects that can be grouped under "General Secondary Handler for Checks".
It is part of development package SADL_GW_DT_SECONDARY_GENERAL in software component BC-ESI-ESF-GW. This development package consists of objects that can be grouped under "General Secondary Handler for Checks".
Message Nr ▲ | Message Text |
---|---|
000 | CDS Modeling Check (SADL/BOPF) |
001 | Join &1 is not allowed. |
002 | Calculated field &1 is not allowed. |
003 | Association &1 is exposed multiple times. |
004 | Data source &1 is not a transactional CDS view. |
005 | Do not use the element &1 in the association definition. |
006 | Do not use the association &1. |
007 | Do not use the path expression closed using the element &1. |
008 | Do not use the virtual element &1 in the association definition. |
009 | &1: Annotation &2 is missing. Add the annotation to the CDS view. |
010 | Do not use annotation &1 on subnode. |
011 | Annotation '@ObjectModel.semanticKey' is required for UUID-based models. |
012 | Semantic key element &1 is unknown or hidden. |
013 | The syntax of the semantic key is invalid. |
014 | Transient field &1 requires the annotation '@ObjectModel.readOnly'. |
015 | Remove the annotation &1. |
016 | Association #TO_COMPOSITION_PARENT in CDS view &1 is missing. |
017 | Association #TO_COMPOSITION_ROOT in CDS view &1 is missing. |
018 | Enter a valid primary key for CDS view &1. |
019 | The composition does not use consistent primary keys. |
020 | CDS view &1: Association &2 may use fields of target primary key only. |
021 | Key fields of association &2 are missing in CDS view &1. |
022 | CDS view &1: Association to child &2 must use primary key of CDS view &1. |
023 | Composition of CDS view &1 contains duplicate views. |
024 | Association #TO_COMPOSITION_PARENT in CDS view &1 defined multiple times |
025 | Association #TO_COMPOSITION_ROOT in CDS view &1 defined multiple times |
027 | CDS view &1 is not a consumption view. |
028 | Annotation 'ObjectModel.writeDraftPersistence' is missing in CDS view &1. |
029 | CDS view &1 cannot be draft-enabled due to underlying transactional view. |
031 | CDS view &1: Association to child &2 is missing. |
032 | Element &1 has inherited the annotation &2 and cannot be exposed. |
033 | Key field &1 must not be annotated as &2. |
034 | Element &1 cannot be used in annotation &2 because of annotation &3. |
035 | Annotation '&1: &2' must not be used here. |
036 | The draft table &1 exists for this CDS view and must not be renamed. |
037 | Syntax of CDS view &1 is not supported. Correct the syntax. |
038 | Key fields must be identical to key fields in transactional CDS view. |
039 | The target of the composition association &1 must be a consumption view. |
040 | Composition association &1 must not be used with a filter. |
041 | Specialization &1 of composition association can only have &2 conditions. |
042 | Aggregation and grouping is not allowed in consumption CDS view. |
043 | Statement 'select distinct' is not allowed in consumption CDS view. |
044 | Statements of type 'union' are not allowed in consumption CDS view &1. |
045 | Foreign key association &1 may use fields of target primary key only. |
046 | Foreign key association &1 is not exposed in the CDS view &2. |
047 | Inherited foreign key association &1 is not exposed in the CDS view &2. |
048 | Foreign key association &1 is not found. Check the association alias. |
049 | Element &2 and 'on' condition of foreign key association &1 do not match. |
050 | Target of foreign key association &1 has syntax error or does not exist. |
051 | Annotation &1&2 is used more than once. |
052 | CDS view &1 must not contain draft-specific fields. |
053 | CDS views with parameters are not supported. |
054 | CDS views cannot be analytical and transactional at the same time. |
055 | &1: The type of element &2 must be compatible with data element &3. |
056 | Field &1 must be exposed because it is used in annotation &2 at field &3. |
057 | Where-condition in consumption view can only have operator: &1. |
058 | Where-condition of view &1 does not match filter of association &2. |
060 | CDS view &1 is not root of the composition. |
061 | CDS view &1 is not a child of &2. |
062 | Association name &1 must be identical to &2. |
063 | Prefix &1 for Association &2 is longer than &3 characters. |
064 | Prefix &1 for Association &2 is used more than once. |
065 | Prefix is missing for Association &1. |
066 | Target &1 of Association &2 is not draft 2.0 enabled. |
067 | Association &1 is missing in BO view &2. |
068 | For Textnode, element &1 must be a key field. |
069 | Annotation &1 is used multiple times. |
070 | The root of a composition cannot be of type '&'. |
071 | Association &1 is not draft-enabled in transactional view &2. |
072 | CDS view &1 with annotation &2 must not be draft enabled. |
073 | Annotation &1 requires annotation &2 or &3. |
074 | At least one element of annotation &1 or &2 must be a key element. |
075 | Entityset Name '&1' not given or exeeds 30 Characters |
076 | Used in annotation '&1' element '&2' is not a part of CDS-View '&3'. |
077 | ETag-Handling will not be supported totally |
078 | Value &1 for annotation &2 is not allowed. |
079 | Value &1 is not supported. |
080 | Provide default values for hidden parameter &1 |
081 | DB hint &1 is not on the allowlist. |
082 | Editable field &1 must not be read-only |
083 | Referenced field &1 must be read-only |
084 | Referenced field &1 must be exposed in the view |
085 | Editable field &1 is the same as referenced field |
086 | &1: Element &2 is typed incorrectly for this annotation |
087 | &1: Element &2 must be annotated with &3 |
088 | valueHelpDefinition: Element '&1' for value help '&2' is invalid |
089 | Annotation is not correctly defined for DB hints |
090 | valueHelpDefinition: Value Help &1 does not exists |
099 | =>&1&2&3&4 |