ACM_SYNTAX - ACM: DCL Syntax Error Messages
The following messages are stored in message class ACM_SYNTAX: ACM: DCL Syntax Error Messages.
It is part of development package SACMDT_API in software component BC-SEC-AUT-DCL. This development package consists of objects that can be grouped under "Designtime-API for Access-Control-Management".
It is part of development package SACMDT_API in software component BC-SEC-AUT-DCL. This development package consists of objects that can be grouped under "Designtime-API for Access-Control-Management".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Syntax Check for DCL Sources |
| 001 | DCL source is empty |
| 002 | DCL source starts with a wrong keyword |
| 003 | Unexpected end of DCL source |
| 004 | Error during artifact generation: &1&2&3&4 |
| 005 | Cannot activate DCL; system upgrade is running; try again later |
| 006 | Parser was not able to identify authorization relevance |
| 007 | Unexpected structure of WHERE condition &1 |
| 008 | DCL source "&1" of type "ROLE" is already delivered |
| 009 | Unable to identify delivery status of DCL source "&1" of type "ROLE" |
| 010 | Parse DCL source &1 |
| 011 | Expected keyword missing &1 |
| 012 | Expected identifier missing &1 |
| 013 | Expected symbol missing &1 |
| 014 | Name of &1 too long; maximum length is &2 characters |
| 015 | Can not handle 'OR' with authorization relevant fields |
| 016 | Unexpected annotation &1 |
| 017 | &1 is only supported in combination with &2 |
| 018 | Number of entity fields and authorization object fields does not match |
| 019 | DCL source "&1" of type "AGGREGATE" is already delivered. |
| 020 | Unable to identify delivery status of DCL source "&1" of type "AGGREGATE" |
| 021 | DCL source "&1" of type "AGGREGATE" is already delivered. |
| 022 | Unknown delivery status of to-be-deleted DCL source "&1" of type "AGGR." |
| 023 | SQL-View &1 of entity &2 does not exist in the database (see tx: SE14) |
| 024 | Element &1 does not exist in entity &2 |
| 025 | Comparison operator "&1" is not supported at this position |
| 026 | No unique key was defined for entity &1 |
| 027 | All fields are defined as key fields for entity &1 |
| 029 | Use of keyword 'PFCG_MAPPING' is only allowed once per condition |
| 030 | &1 is no valid CDS entity |
| 031 | Name of authorization object &1 too long; maximum length is &2 characters |
| 032 | Name of authorization field &1 too long; maximum length is &2 characters |
| 033 | &1 is no valid authorization object |
| 034 | &1 is no valid authorization field of authorization object &2 |
| 035 | Field &1 of entity &2 has unsupported type &3 |
| 036 | Could not add DCL &1 to transport &2 |
| 037 | "&1" is no valid &2 literal: &3&4 |
| 038 | Literal "&1" of type &2 must be denoted with apostrophes |
| 039 | Literal &1 is of type &2, but contains non-numeric characters |
| 040 | Expected symbol missing &1 or &2 |
| 041 | The Auth. Check Mode of CDS entity &1 does not allow DCL access control |
| 042 | Literal "&1" has length &2, but the data type has maximum length &3 |
| 043 | Literal "&1" has length &2, but the data type has minimum length &3 |
| 044 | Operator LIKE is not permitted for data type &1 |
| 045 | An internal error during normalization of conditions occurred |
| 046 | Normalize two (or more) conditions in brackets is not yet supported |
| 047 | Use &1 or fewer sets of parentheses |
| 048 | Use exactly &1 terms within a set of parentheses |
| 049 | Cannot analyze path &1 &2 &3 &4. Check definition in DDL document |
| 050 | Feature not released. Remove usage of feature from DCL Document |
| 051 | Error during Enterprise Search update. Check CDS entity &1 in Editor |
| 052 | Cannot split argument "&1" of BETWEEN operator into "From" and "To" |
| 053 | Too many filters; Use &1 filters maximum |
| 054 | Expected keyword missing &1 or &2 |
| 055 | Role &1 does not exist or is not active |
| 056 | DCL Document for role &1 does not exist |
| 057 | @MappingRole is different from the inherited DCL &1 |
| 058 | Invalid association &1 of entity &2 |
| 059 | Rule without user dependent aspects |
| 060 | Infinite loop prevention. Activation aborted. Check inheritance of DCLs |
| 061 | Parent &1 role has more than &2 rule |
| 062 | Use exactly &1 inherit in a role |
| 063 | Syntax errors in child DCL &1. Execute syntax check on DCL &1 |
| 064 | Could not read active version of child DCL &1. Exception was &2 &3 &4 |
| 065 | Inherit from functional grant role &1 not allowed |
| 066 | Data error: Condition &1 contains more than one aspect |
| 067 | Data error: Condition &1 contains none or more than one field |
| 068 | Role &1 is used in role &2 in DCL &3 |
| 069 | Aspect &1 is used in role &2 in DCL &3 |
| 070 | DCL source contains syntax error |
| 071 | Remove duplicate field/value combinations in aspect pfcg_auth &1 &2 '&3' |
| 072 | Data error: Condition &1 contains an aspect of invalid type: &2 |
| 073 | Rename of role name loses inheritance and causes syntax errors in DCL &1 |
| 074 | DCL on Entity with AMDP functions not supported |
| 075 | "&1" is an invalid value for auth. field &2 of auth. object &3 |
| 076 | Inherit issue in role &1 of access control &3 (root cause follows) |
| 077 | Invalid aspect &1 |
| 078 | Entity &1 does not have a parameter &2 |
| 079 | Comparison between numerical and character-like types not allowed |
| 080 | &1 is longer than &2 |
| 081 | Statement not allowed in path filters |
| 082 | Path expressions not allowed in path filters |
| 083 | Path expressions only allowed for CDS. &1 is not a CDS entity |
| 084 | Type-incompatible comparison for field &1 |
| 085 | Parameters only allowed for associations to CDS entities |
| 086 | Token "&1" too long (at most &2 characters) |
| 087 | Condition term too long. Single terms can not be longer that 1333 chars |
| 088 | Invalid usage of data types RAW and STRING |
| 089 | Hierachy list needs to be matched to a PFCG_MAPPING |
| 090 | The left side needs to be matched with a PFCG field |
| 091 | Mapping field &1 was used more than once in the PFCG mapping |
| 092 | Resource "&1" is no valid hierarchy entity. Check the name and spelling |
| 093 | Resource "&1" is no valid datasource entity. Check the name and spelling |
| 094 | Forbidden condition inside a NOT-expression (see long text) |
| 095 | No &1 statement for entity &2 found in role &3 |
| 097 | Only one PFCG mapping per access policy is allowed |
| 098 | Name of the PFCG mapping (&1) and access policy (&2) differs |
| 099 | Name of the defined object (&1) must match the source document name (&2) |
| 100 | &2: Starting DCL AIM (user = &1) |
| 101 | &2: Deleting role from DCL &1 |
| 102 | &2: Deleting role (for regeneration) from DCL &1 |
| 103 | &2: Generating role from DCL &1 |
| 104 | &2: Regenerating role from DCL &1 |
| 105 | &2: Deleting aggregate from DCL &1 |
| 106 | &2: Deleting aggregate (for regeneration) from DCL &1 |
| 107 | &2: Generating aggregate from DCL &1 |
| 108 | &2: Regenerating aggregate from DCL &1 |
| 109 | DCL Source &1 contains invalid DCL type |
| 110 | &2: Error while generating DCL &1 (component &3, package &4) |
| 111 | &2: Warning while generating DCL &1 (component &3, package &4) |
| 112 | &2: Generation successfully terminated for DCL &1 |
| 113 | DCL PCA Task not executed because ZDM running. |
| 114 | DCL Initial Load: Could not get exclusive lock, return code &1 |
| 115 | DCL Initial Load: No DCLs, nothing to do |
| 116 | Client-Copy cleanup of all client-dependent tables done (client: &1) |
| 117 | Syntax errors in descendant DCL &1. Execute syntax check on DCL &1 |
| 118 | Invalid access policy name &1. There is already a role with this name |
| 119 | Reserved aspect name &1 must not be used |
| 120 | All generated ACM data and objects deleted |
| 121 | &2: Generating ABAP artifacts for DCL &1 (&3/&4) |
| 122 | &2: Deleting ABAP artifacts for DCL &1 (&3/&4) |
| 123 | &2: Error while deleting ABAP artifacts of DCL &1 |
| 124 | &2: Warning while deleting ABAP artifacts of DCL &1 |
| 125 | DCL After Import: Could not get exclusive lock |
| 126 | Parameter &1 of entity &2 is not bound |
| 127 | &1: Metadata for DCLs updated |
| 128 | &2: &1 DCL(s) cause an infinite loop; their metadata were not updated |
| 129 | DCL Source contains syntax warning |
| 130 | DCLs without annotation "@MappingRole: true" are not supported |
| 131 | For productive DCLs, only the following aspects are supported: &1 and &2 |
| 132 | Duplicate declaration of parameter &1 |
| 133 | REPLACING { ROOT WITH | PARAMETERS WITH ... } can be used at most once |
| 134 | DCL source &1 cannot be analyzed. No active version exists |
| 135 | Error while reading DCL source &1 |
| 136 | Unexpected annotation. Only &1 is supported |
| 137 | Annotation name &1 is used multiple times |
| 138 | Replacing a value with itself is imaginable, but pointless |
| 139 | Filter value replacement for field &1 chains value "&2" |
| 140 | No access control of entity &1 can be applied |
| 141 | Replacement of &1 does not apply to any inherited condition |
| 142 | Redundancy in ASPECT PFCG_AUTH: &1; see long text |
| 143 | Issue occurred in condition propagation from access control &1 to &2 |
| 144 | Entity &1 has no access controls from which to inherit |
| 145 | Start transaction SACMDCLS to review the status of access control &1 |
| 146 | Inheriting conditions from entity &1: Role &2 inapplicable |
| 147 | Object creation in access control parser terminated |
| 148 | The consecutive use of the same PFCG mapping &1 is not supported |
| 149 | The feature is not released for SAP Cloud Platform, ABAP environment |
| 150 | Entity &1 has parameters and cannot be used at this location |
| 151 | Datasource &1 for aspect &2 has no suitable auditing declaration |
| 152 | Field &1 of entity &2 not suitable for "aspect User" (type, length) |
| 153 | Entity &1 has type "&2" which is not supported by CDS access control |
| 154 | Uniqueness violation: A REDEFINITION- and another rule exist (entity=&1) |
| 155 | Target of ROOT WITH association (&1) must match INHERITING entity (&2) |
| 156 | Statement REDEFINITION is prohibited for SAP development |
| 157 | ROOT WITH ... INCLUDING PARAMETERS excludes PARAMETERS WITH |
| 158 | Number of entity fields (&1) and aspect fields (&2) does not match |
| 159 | Dedicated aspect &1 must be specified without brackets |
| 160 | A LIKE condition can only be used with character-like fields |
| 161 | Search pattern "&1" is too long |
| 162 | &1 cannot be converted to the type of the target (&2) |
| 163 | Invalid usage of host expression "&1" |
| 164 | Left side literal "&1" should be expressed as filter in ASPECT PFCG_AUTH |
| 165 | Rule &1 of this DCL supplied &2 conditions for inheritance (depth=&3) |
| 166 | Element &1&2 cannot be used in access conditions for CDS hierarchies |
| 167 | The access control type does not support language element &1 |
| 168 | The set of inherited conditions contains only VOID |
| 169 | REPLACING CONDITIONS prohibits further inheritance |
| 170 | REPLACING CONDITIONS ... WITH ... found an affected condition |
| 171 | Parameter bindings and path filters are not allowed at this location |
| 172 | Replacement value &1 is included in other replacement value &2 |
| 173 | Element &1 of entity &2 is a field and cannot have further path elements |
| 174 | Only fields of entity &1 can be used here (&2&3 is no field) |
| 175 | Only an association can be used here (&1&2 ends with a field) |
| 176 | Only a field or closed path can be used here (&1&2 ends with association) |
| 177 | REPLACING CONDITIONS can be used at most once for each of VOID/TRUE/FALSE |
| 178 | IF ALL CONDITIONS VOID THEN only together with CONDITIONS ... WITH VOID |
| 179 | Switchable authorization check scenario "&1" does not exist |
| 180 | Diverging scenario name for mapping &1 (role: "&2", mapping: "&3") |
| 181 | Entity &1 is not the base entity of the transactional projection view &2 |
| 182 | Unsupported statement in context of transactional projection view |
| 183 | To-be-protected entity &1 cannot inherit from itself (indefinite cycle!) |
| 184 | Usage of INHERITING CONDITIONS FROM SUPER requires REDEFINITION |
| 185 | COMBINATION MODE AND is not allowed for full access rules |
| 186 | Datatype "&1" cannot be converted/normalized to a string representation |
| 187 | REPLACING ELEMENT and ROOT WITH can not be used simultaneously |
| 188 | REPLACING ELEMENT is supported on transactional projection views only |
| 189 | &1 is not the alias of &2 |
| 190 | Exception occurred when reading required information from entity &1 |
| 191 | &1 of entity &2 is a virtual field |
| 192 | BYPASS WHEN cannot be used at this location |
| 193 | Rule won't apply to &1 because of the annotation setting of the entity |
| 194 | Rule won't apply to &1 because of redefinition in access control &2 |
| 195 | Rule won't apply to &1 because of functional grant in access control &2 |
| 196 | Element &1 does not exist in entity &2 (optional, runtime behavior &3) |
| 197 | Optional element &1 is not used |
| 198 | &1&2&3&4 is optional which excludes usage in PFCG mappings and aspects |
| 199 | Element &1 is used in an aspect and so not allowed as optional element |
| 200 | Optional element &1 was specified more than once |
| 201 | Paths/Filters are not allowed as optional elements (only fields+assocs.) |
| 202 | Element &1 is optional and so cannot be used together with: ROOT WITH |
| 203 | Element &1 is optional and cannot be used with: REPLACING ELEMENT |
| 204 | Error when inheriting from role &1: Association &2 does not exist |
| 205 | Feature "&1" is currently not supported for productive access controls |
| 206 | Use replacing option 'ROOT WITH' to inherit access conditions from &1 |
| 207 | Forbidden language element within a quantified condition |
| 208 | CDS entity &1 belongs to software component &2. Contact &3 before release |
| 209 | Usage of S_TABU_NAM in this language version requires empty left side |
| 210 | Usage of S_TABU_NAM in this language version demands filter on TABLE |
| 211 | This DCL function does not have a parameter "&1" |
| 212 | Invalid DCL function &1 |
| 213 | Message passed through inherit level &1 in role &2 for &3 reading role &4 |
| 214 | Condition inheritance using &1 reading role &2: &3 (&4) |
| 215 | Inheriting from own role (this rule will be excluded from selection) |
| 216 | Inheriting from own role is not possible for singleton inheritance |
| 217 | Inheriting from own entity (this rule will be excluded from selection) |
| 218 | &1&2&3 does not apply to any of the &4 considered replacement candidates |
| 219 | SAP Software Error: &1&2&3 (&4, English only) |
| 220 | Found at least two rules (roles &1 / &2) as REDEFINITION for entity |
| 221 | Statement contradicts the CDS access control grammar |
| 222 | For this entity type, ELEMENT WITH must point to a plain alias |
| 223 | "&1" is not accepted for usage in PREFIX WITH: &2&3&4 |
| 224 | Both arguments of ELEMENT WITH must have the same kind of termination |
| 225 | Conflict in trailing parameters or filters between source and target |
| 226 | Elements "&1&2" and "&3&4" violate constraint in quantified conditions |
| 227 | Optionality can only be declared for the first component of an element |
| 228 | Object &1 (&2) cannot be used in the documents ABAP language version |
| 229 | Full access rule in role &1 demotes inheritance errors to warnings |
| 230 | Replacement of element "&1&2" with host expression "&3&4" is not possible |
| 231 | Using VOID can cause a runtime error |
| 232 | The runtime value of &1 (type &2) may exceed the type of the target (&3) |
| 233 | The number of distinct "<Field> = <Value>" pairs is limited to 10 |
| 234 | &1 does not belong to the same software component as the access control |
| 235 | Aspect filter alias &1 is not unique |
| 236 | Aspect filter alias &1 is reserved |
| 237 | Element &1 is not defined as a filter of aspect &2 |
| 238 | Character sequence "&1" must not be used inside an aspect filter |
| 239 | Aspect filters must use filter elements |
| 240 | The use of inheritance is restricted in this language version |
| 241 | Element &1 must be declared as optional |
| 242 | Element &1 must be used in an access condition |