ACMDT_OBJSTATUS - ACM: Messages for the Object-Status of Designtime-Objects
The following messages are stored in message class ACMDT_OBJSTATUS: ACM: Messages for the Object-Status of Designtime-Objects.
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 | &1&2&3&4 |
| 001 | DCL source has no persisted ABAP artifacts (role/aggregate) |
| 002 | Foreign lock exist! Object status monitor cannot be started |
| 003 | Start checking all objects (use buffer = '&1') |
| 004 | Creation time of ABAP artifacts is earlier than changing time of DCL |
| 005 | DCL source has no corresponding text/description |
| 006 | Orphaned DCL source text: '&1' (language=&2) |
| 007 | Role has no corresponding DCL source |
| 008 | Rule references to an invalid authorization view |
| 009 | Condition (in rule &1) has no link to an access condition |
| 010 | Condition (in rule &1) references to an invalid access condition |
| 011 | Rule is orphaned |
| 012 | DT condition is orphaned |
| 013 | Entity '&1' is invalid (does not exist in table: DD02B) |
| 014 | SQL view '&1' (related to entity '&2') doesn't exist in the database |
| 015 | Entity '&1' has parameters (parameters are supported by the database) |
| 016 | Entity '&1' has parameters (parameters are not supported by the database) |
| 017 | SQL view '&1' (entity &2) not exists because parameters are not supported |
| 018 | Repairing of object '&1' (level=&2) not necessary (required level=&3) |
| 019 | Repairing of object '&1' not possible. No sub object ID was specified |
| 020 | Repairing of object '&1' not possible. No sub object table was specified |
| 021 | Repairing of object '&1' not possible. Sub object '&2' doesn't exist |
| 022 | Repairing of object '&1' failed: &2&3&4 |
| 023 | Object statuses of type: DCL cannot be repaired here. Use ADT instead |
| 024 | Role with ID=&1 cannot be regenerated, because it does not exist |
| 025 | Role &1 has manually adapted aspect values and so cannot be regenerated |
| 026 | User role assignments for role &1 cannot be deleted:&2&3&4 |
| 027 | User &1 cannot be assigned to role &2: &3&4 |
| 028 | Do you really want to repair '&1' (main object: &2 - status type: &3) |
| 029 | '&1' (main object: &2 - status type: &3) successfully repaired |
| 030 | Role contains no rules |
| 031 | '&1' (sub object table: &2 - status type: &3) successfully repaired |
| 032 | Repairing of object '&1' not possible. No sub object name was specified |
| 033 | Entity '&1' (status type: DDIC) cannot be repaired here. Use ADT instead |
| 034 | DDL source '&1' is invalid (does not exist in table: DDDDLSRC) |
| 035 | DDL source '&1' not exists in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4) |
| 036 | Entity '&1' not exists in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4) |
| 037 | SQL view '&1' not exists in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4) |
| 038 | DDL source '&1' is orphaned in table: DDDDLSRC |
| 039 | DDL source '&1' is orphaned in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4 |
| 040 | Entity '&1' is orphaned in table DD02B |
| 041 | Entity '&1' is orphaned in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4) |
| 042 | SQL view '&1' is orphaned in the database |
| 043 | SQL view '&1' is orphaned in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4) |
| 044 | Authorizationview ID=&1 cannot be regenerated, because it does not exist |
| 045 | No business entity can be determined for Authorizationview: &1 |
| 046 | Business entity &1 (related to Authorizationview &2) no longer exists |
| 047 | Business entity &1 has &2 keyfields, but its related Authview &3 has &4 |
| 048 | Keyfield &1 of business entity &2 does not exist in its Authview &3 |
| 049 | Business entity &1 has other parameters than its related Authview &2 |
| 050 | AC-Field &1 of AuthView &2 does not exist anymore in business entity &3 |
| 051 | Parameterstring of business entity &1 cannot be build: &2&3&4 |
| 052 | Viewdefinition of Authview &1 is not valid anymore: &2&3&4 |
| 053 | Entity &1 has &2 keys, its related Authview &3 has &4 in ACMACAVIEWDETAIL |
| 054 | Keyfield &1 of Entity &2 doesn't exist in ACMACAVIEWDETAIL of Authview &3 |
| 055 | Error deleting Authorizationview '&1': &2&3&4 |
| 056 | Error deleting AC-Condition: &1&2&3&4 |
| 057 | Changing CDS entity &1 made some of the following DCL roles inconsistent |
| 058 | Please adapt and re-activate those inconsistent DCL roles |
| 059 | Changing associations/paths of entity &1 made some DCL roles inconsistent |
| 060 | Authorizationview: &1 successfully regenerated |
| 061 | Do you really want to repair the &1 marked objects? |
| 062 | Authorizationview has no link to a rule/access condition |
| 063 | Authorizationview has no detail entries |
| 064 | Authview detail (ID=&1) references to an invalid aspect (ASPECT_ID=&2) |
| 065 | Authorizationview detail entry (ID = &1) is orphaned |
| 066 | Authorizationview field entry (ID = &1) is orphaned |
| 067 | Access condition has no link to an Authorizationview |
| 068 | Access condition has no link to a designtime condition |
| 069 | Access condition of type FIELDVIEW has no field entries |
| 070 | AC field (ID=&1) references to an invalid aspect (ASPECT_ID=&2) |
| 071 | Object cannot be repaired here. Repair role '&1' instead (type: DDIC) |
| 072 | Object cannot be repaired here. Repair Authview '&1' instead (type: DDIC) |
| 073 | &1 of &2 erroneous objects could be repaired successfully |
| 074 | Aggregate has no corresponding DCL source |
| 075 | Aggregate contains neither aspects nor PFCG mappings |
| 076 | Aspect (type: PFCG_AUTH) has no related AC-Field or Authview-Detail |
| 077 | Aspect (type: PFCG_AUTH) has no link to a PFCG-Aspect entry |
| 078 | PFCG-Aspect entry is invalid (ID <> ASPECT_ID) |
| 079 | PFCG-Aspect has no detail entries |
| 080 | PFCG-Aspect detail (ID=&1) references to an invalid PFCG-Mapping (&2) |
| 081 | PFCG-Aspect entry (ID = &1) is orphaned |
| 082 | PFCG-Aspect detail entry (ID = &1) is orphaned |
| 083 | Aspect with ID=&1 cannot be regenerated, because it does not exist |
| 084 | Aspect &1 is not of type: PFCG_AUTH but of type: &2 |
| 085 | Aspect &1 cannot be regenerated, because it has no related AC-Condition |
| 086 | Aspect &1 is corrupt, because it has more than one related AC-Condition |
| 087 | AC-Condition of Aspect &1 cannot be parsed: &2&3&4 |
| 088 | Repairing of '&1' not possible. Corresp. Aspect-PFCG '&2' doesn't exist |
| 089 | Aspect &1 cannot be regenerated, because related role &2 doesn't exist |
| 090 | PFCG-Aspect has &1 detail entries, its related AC-Condition has &2 |
| 091 | PFCG-Aspect has auth.object &1, but its PFCG mapping has auth.object &2 |
| 092 | Aspect has no link to a aggregate or has an invalid aspect-type |
| 093 | Aspect has none or more than one related Aspectviews |
| 094 | Error deleting Aspect '&1': &2&3&4 |
| 095 | Repairing of aspect '&1' not possible. No related aggregate exists |
| 096 | Aspectview entry (ID = &1) is orphaned |
| 097 | Aspectview '&1' cannot be regenerated, because its aspect does not exist |
| 098 | PFCG-Mapping has no related Aggregate (Access Policy) |
| 099 | PFCG-Mapping has no detail entries |
| 100 | PFCG-Mapping has no corresponding hierarchy key entries |
| 101 | PFCG-Mapping detail entry (ID = &1) is orphaned |
| 102 | Hierarchy-key entry (ID = &1; Entity = &2) is orphaned |
| 103 | PFCG-Mapping with ID=&1 cannot be regenerated, because it does not exist |
| 104 | PFCG-Mapping &1 cannot be regenerated because it aggregate doesn't exist |
| 105 | No hierarchy view entity can be determined for PFCG-Mapping: &1 |
| 106 | Hierarchy view entity &1 (related to PFCG-Mapping &2) no longer exists |
| 107 | Hierarchy view &1 has &2 IDs/keys in real but &3 keys in ACMHIERARCHYKEY |
| 108 | ID/Keyfield &1 of hierarchy entity &2 doesn't exist in ACMHIERARCHYKEY |
| 109 | Field &1 of PFCG-Mapping &2 does not exist anymore in hierarchy view &3 |
| 110 | PFCG-Mapping &1 cannot be repaired. Check hierarchy view &2 manually |
| 111 | Hierarchy metadata table has no related 'Generated hierarchy-view' |
| 112 | Hierarchy metadata table has no detail entries (representative keys) |
| 113 | Hierarchy metadata detail has no link-entries to an AC-Condition |
| 114 | Hierarchy AC-Condition link-entry contains invalid AC-Condition ID: &1 |
| 115 | Hierarchy AC-Condition link-entry is orphaned |
| 116 | AC-Condition contains a hierarchy but has no hierarchy link-entry |
| 117 | Hierarchy AC-Condition link-entry has no hierarchy metadata detail entry |
| 118 | Hierarchy metadata detail has no related hierarchy metadata table entry |
| 119 | Internal hierarchy metadata inconsistency. &1 |
| 120 | Cannot repair hierarchy metadata (ID=&1) - no linked AC-Condition found |
| 121 | No hierarchy view entity can be determined |
| 122 | Hierarchy view entity &1 does no longer exist |
| 123 | Hierarchy field &1 does not exist anymore in hierarchy view &2 |
| 124 | Hierarchy-Metadata ID=&1 cannot be regenerated because it does not exist |
| 125 | Hierarchy-Metadata: &1 cannot be repaired automatically |
| 126 | No dimension view entity can be determined |
| 127 | Dimension view entity &1 does no longer exist |
| 128 | No analytical view entity (=info cube) can be determined |
| 129 | Analytical view entity &1 (=info cube) does no longer exist |
| 130 | Field &1 does not exist anymore in analytical view &2 (=info cube) |
| 131 | Determine all ACM database tables |
| 132 | Get all orphaned ACM authorization views |
| 133 | Get all orphaned ACM aspect views |
| 134 | Do you want to delete all entries from &1 ACM artifact tables? |
| 135 | Cleaning of ACM artifact tables and artifact views finished |
| 136 | Cleaning of ACM artifact tables was cancelled |
| 137 | Do you want to delete &1 orphaned ACM artifact views? |
| 138 | Cleaning of orphaned ACM artifact views was cancelled |
| 139 | Deleting entries of ACM artifact table: &1 |
| 140 | Deleting orphaned ACM authorization view: &1 |
| 141 | Deleting orphaned ACM aspect view: &1 |
| 142 | Orphaned protection view: '&1' |
| 143 | Determine all ACM hierarchy rank tables |
| 144 | Deleting ACM hierarchy rank table: &1 |
| 145 | DCL source has no corresponding protection view(s) |
| 146 | Cleaning of ACM artifact tables and artifact views finished with errors |
| 147 | DCL &1 could not be repaired automatically. Use ADT to check and adapt |
| 148 | Orphaned DCL metadata entry for DCL: '&1' |
| 149 | DCL source has no or an inconsistent metadata entry |
| 150 | Do you really want to delete the &1 marked entries? |
| 151 | Do you really want to delete the marked entry? |
| 152 | &1 object status result entries deleted |
| 153 | &1 unversioned entries with ID='&2' in database table &3 |
| 154 | Version '&1' is not the only active version |
| 155 | Version '&1' has invalid state |
| 156 | Generation of version '&1' has been canceled. |
| 157 | All table entries are related to a version |
| 158 | Version &1 is consistent |
| 159 | Runtime content has no runtime condition |
| 160 | Runtime condition has no runtime restriction |
| 161 | Runtime restriction has no mapping to design time |
| 162 | Designtime mapping to non-existent restriction |
| 163 | Designtime mapping to non-existent role |
| 164 | Initial load required (see long text) |
| 165 | DCL metadata for DCL &1 is missing |
| 166 | Accesspolicy name in DCL is different from DCL metadata |
| 167 | Aspect &1 is missing in DCL metadata |
| 168 | PFCG mapping &1 is missing in DCL metadata |
| 169 | Role name in DCL is different from DCL metadata |
| 170 | Entity &1 is missing in DCL metadata |
| 171 | Number of entities differs from metadata (&1) to parsed data (&2) |
| 172 | Entity &1 has the erroneous ACM status: &2 |
| 173 | Checking main object: &1 (&2/&3) [&4] |
| 174 | Checking orphaned objects of main object: &1 [&2] |
| 175 | Access Condition references to an invalid CTE (CTE_ID=&1) |
| 176 | Error (&1) |
| 177 | Warning (&1) |
| 178 | Info (&1) |
| 179 | Object is consistent |
| 180 | CTE column value contains an aspect (XPRA 2021 did not run successfully) |
| 181 | CTE column value has no corresponding Access Condition |
| 182 | Repairing of object '&1' not possible. No object ID was specified |
| 183 | Repairing object &1/&2 (main object type: &3) |
| 184 | Unknown object database table: &1 |
| 185 | Object could not be repaired &1 |
| 186 | Only &1 of &2 objects could be repaired &3 |
| 187 | Do you really want to repair the marked object? |
| 188 | Object has been repaired |
| 189 | All &1 of &2 objects could be repaired (or were already fixed) |
| 190 | Access Condition has no corresponding CTE column value |
| 191 | Current object status monitor results retrieved |
| 192 | This object is not repairable |
| 193 | Finished checking all objects [retrieved results: &1 / &2 / &3 / &4] |
| 194 | Start repairing &1 objects |
| 195 | Repairing of object '&1' not possible. It cannot be read from database |
| 196 | CTE column value references to an invalid column name (COLNAME_ID=&1) |
| 197 | CTE belongs to an invalid CDS entity: &1 |
| 198 | CTE of type: AUTHV has no corresponding CTE columnname |
| 199 | CTE of type: AUTHV/HEADV has no corresponding BASEV CTE |
| 200 | CTE of type: BASEV has no corresponding CTE key entry |
| 201 | CTE of type: AUTHV has no corresponding AC condition |
| 202 | CTE of type: ASPV has no corresponding aspect |
| 203 | Keys of entity: &1 could not be read from DDIC (&2) |
| 204 | The keys of the entity differ from the keys of the CTE |
| 205 | The field USING_DISTINCT is filled wrongly ('&1' instead of '&2') |
| 206 | Check of mainobject: &1 --> [red/yellow/grey] = [&2] |
| 207 | Cannot read keys of entity: &1 (&2&3&4) |
| 208 | Cannot read associations of entity: &1 (&2&3&4) |
| 209 | The parameters of the entity differ from the parameters of the CTE |
| 210 | CTE keys are no longer in use |
| 211 | CTE parameters are no longer in use |
| 212 | CTE2CTE entry has no corresponding CTE |
| 213 | CTE2CTE entry has no corresponding predecessor CTE |
| 214 | Type conflict: entity column [&1] vs. CTE column [&2] |
| 215 | The CTE column name is no valid column of entity: &1 |
| 216 | CTE column name has no corresponding CTE |
| 217 | &1 unversioned entry with ID='&2' in database table &3 |
| 218 | Mapping detail has no corresponding PFCG mapping |
| 219 | CTE column name part has no corresponding CTE column name |
| 220 | Cannot read NAMETAB entry of entity: &1 (&2&3&4) |
| 221 | CDS entity has no status entry in ACMENTITYSTATUS |
| 222 | CDS entity has an erroneous status entry in ACMENTITYSTATUS (&1) |
| 223 | CDS entity is no longer access control protected |
| 224 | CDS entity has DCLs but is flagged as "Access control not allowed" |
| 225 | CDS entity is flagged as "Access control allowed" but has no DCL |
| 226 | Entity status entry refers to an invalid CDS entity |
| 227 | All CDS entities have an erroneous status entry in ACMENTITYSTATUS (&1) |
| 228 | data was read from internal buffer |
| 229 | Inherit metadata entry inherits from role which has no artifacts |
| 230 | Entity metadata entry refers to an invalid CDS entity (&1) |
| 231 | The cardinality of the CTE column part association is wrong (&1 vs. &2) |
| 232 | Entity metadata entry has no corresponding DCL metadata entry |
| 233 | Invalid repair action: &1 for object type: &2 |
| 234 | CDS entity is flagged as "Has no DCLs" but has related metadata entries |
| 235 | CDS entity is flagged as "Has DCLs" but has no related metadata entries |
| 236 | Runtime header entry references to an invalid CTE (CTE_ID = &1) |
| 237 | Runtime header entry belongs to an invalid CDS entity: &1 |
| 238 | Trying to repair subobject '&1' in table '&2' with action '&3' |
| 239 | Repairing no longer necessary. Object was already fixed |
| 240 | ACM version mismatch (persisted:&1 - current:&2). Repairing not possible |
| 241 | Currently used brutto memory: &1 MB |
| 242 | User &1 has not enough autorizations to get memory usage information |
| 243 | Used brutto memory before getting the object status results: &1 MB |
| 244 | Runtime condition entry references to an invalid CTE (CTE_ID = &1) |
| 245 | Runtime condition references to an invalid designtime condition (ID=&1) |
| 246 | Runtime condition entry references to an invalid PFCG_AUTH aspect (&1) |
| 247 | Runtime column entry has the invalid position: 0 |
| 248 | Runtime column entry has no related CTE column value entry |
| 249 | Runtime condition has no corresponding runtime header |
| 250 | Runtime column has no corresponding runtime condition |
| 251 | CTE column value has no related PFCG aspect detail |
| 252 | Runtime column entry has no related PFCG aspect detail entry |
| 253 | Aspect of type: PFCG_AUTH has no related PFCG aspect |
| 254 | Aspect of type: PFCG_AUTH has no corresponding access condition |
| 255 | PFCG aspect has no related PFCG aspect details |
| 256 | Number of CTE column values and PFCG aspect details differ [&1/&2] |
| 257 | PFCG aspect has no corresponding aspect |
| 258 | Runtime header is no 'functional grant' and has no CTE |
| 259 | CTEs of viewtype: &1 cannot be repaired |
| 260 | PFCG aspect detail references to an invalid PFCG mapping (ID=&1) |
| 261 | PFCG aspect detail has the invalid position: 0 |
| 262 | PFCG aspect detail has no related CTE column value |
| 263 | PFCG aspect detail has no corresponding PFCG aspect |
| 264 | CTE column value has deprecated data (XPRA 2021 didn't run successfully) |
| 265 | Productive DCL has no ABAP artifacts because of a syntax error |
| 266 | Non-productive DCL has no ABAP artifacts because of a syntax error |
| 267 | Productive DCL has no ABAP artifacts |
| 268 | Non-productive DCL has no ABAP artifacts |
| 269 | DCL has no corresponding metadata entry |
| 270 | DCL text has no corresponding DCL |
| 271 | Main object: &1 (of type: &2) no longer exist |
| 272 | Productive DCL has no active version |
| 273 | Non-productive DCL has no active version |
| 274 | ACMTST DCL has no ABAP artifacts |
| 275 | Runtime header entry is orphaned (has no related designtime rule) |
| 276 | CTE of type: BASEV has no corresponding CTE of type: AUTHV/CONDV |
| 277 | CTE of type: HEADV has no corresponding runtime header |
| 278 | DCL metadata entry of type "aggregate" has no aspect metadata entry |
| 279 | Aspect metadata entry has no corresponding DCL metadata entry |
| 280 | DCL metadata entry references to an invalid/inactive DCL |
| 281 | DCL metadata entry of type "role" has no related entity metadata entry |
| 282 | ACMTST test framework objects shall be deleted via transaction: SACMINT |
| 283 | Trying to delete unversioned entries with ID='&1' in table '&2' |
| 284 | Repairing of object '&1' not possible. No database table was specified |
| 285 | Deleting entries from table '&1' results in OpenSQL error: &2&3&4 |
| 286 | Repairing no longer necessary. Objects were already fixed |
| 287 | Deleting '&1' results in error: &2&3&4 |
| 288 | Repairing not possible. Repair the related orphaned object '&1' first |
| 289 | Repair action: &1 for object type: &2 and ID: &3 failed |
| 290 | Aspects of type: &1 cannot be repaired |
| 291 | Repairing not possible. DCLs cannot be determined. Repair orphans first! |
| 292 | Role has no DCL metadata entry |
| 293 | Role's timestamp differs from the timestamp of the active DCL |
| 294 | Parsed inherit metadata and persisted inherit metadata differ |
| 295 | Parsed entity metadata and persisted entity metadata differ |
| 296 | Role contains no rules (empty role) |
| 297 | Rule belongs to an invalid CDS entity: &1 |
| 298 | Role has no corresponding DCL source: &1 |
| 299 | Rule has no related entity metadata entry |
| 300 | Rule has no related runtime header entry |
| 301 | Rule has no corresponding role |
| 302 | DT-condition has no corresponding rule |
| 303 | DT-condition has no related AC-condition (ACCONDITION=&1) |
| 304 | DT-condition has no related runtime condition |
| 305 | Parsed aspect metadata and persisted aspect metadata differ |
| 306 | CTE belongs to an invalid database table: &1 |
| 307 | DCL cannot be parsed. Probably it become syntactically wrong |
| 308 | Aspect metadata entry refers to an invalid CDS entity (&1) |
| 309 | Parsed DCL metadata and persisted DCL metadata differ |
| 310 | DCL metadata entry of type "aggregate" has no pfcgmapping metadata entry |
| 311 | Inherit metadata entry has no corresponding DCL metadata entry |
| 312 | Inherit metadata entry inherits from an invalid CDS entity (&1) |
| 313 | PFCG mapping metadata entry has no corresponding DCL metadata entry |
| 314 | Parsed PFCG mapping metadata and persisted PFCG mapping metadata differ |
| 315 | PFCG mapping metadata entry refers to an invalid CDS entity (&1) |
| 316 | Aggregate has no DCL metadata entry |
| 317 | Aggregate has no corresponding DCL source: &1 |
| 318 | Aggregates's timestamp differs from the timestamp of the active DCL |
| 319 | Aggregate contains no aspects or PFCG mappings (empty aggregate) |
| 320 | CTE column name has the invalid column name type: &1 |
| 321 | CTE column name of type: &1 has no related PFCG mapping detail |
| 322 | CTE column name is related to an invalid PFCG mapping detail (ID=&1) |
| 323 | Aggregate has another name than its related DCL |
| 324 | Role has another name than its related DCL |
| 325 | PFCG mapping has another name than its related access policy |
| 326 | More than one PFCG mapping metadata entries exist |
| 327 | PFCG mapping has no mapping metadata entry |
| 328 | PFCG mapping contains an invalid datasource entity: &1 |
| 329 | PFCG mapping contains no details (empty mapping) |
| 330 | PFCG mapping contains an invalid hierarchy entity: &1 |
| 331 | PFCG mapping has deprecated data (XPRA 2021 did not run successfully) |
| 332 | PFCG mapping contains an invalid PFCG authorization object: &1 |
| 333 | Aggregate contains more than one sub entry (aspect/PFCG mapping) |
| 334 | PFCG mapping has no corresponding aggregate |
| 335 | PFCG mapping has an invalid parent type: &1 |
| 336 | PFCG mapping has the invalid position: &1 |
| 337 | Mapping field name is no valid field of entity: &1 |
| 338 | Authorization field &1 is no valid field of authorization object &2 |
| 339 | PFCG mapping metadata entry (&1) could not be inserted |
| 340 | PFCG aspect contains an invalid PFCG authorization object: &1 |
| 341 | DCL &1 has no active version, so no metadata update can be done |
| 342 | CTE of type: PMAPV has no corresponding pfcg mapping |
| 343 | PFCG mapping has no related CTE of type: PMAPV |
| 344 | PFCG mapping has an invalid CTE-ID: &1 |
| 345 | Mapping detail has no related CTE-Colname entry |
| 346 | Mapping detail has more than 1 related CTE-Colname entries (&1) |
| 347 | Auth. object of PFCG aspect (&1) and of related PFCG mapping (&2) differ |
| 348 | Parsed role-aspect metadata and persisted role-aspect metadata differ |
| 349 | Role-aspect metadata entry refers to an invalid aspect (&1) |
| 350 | Role-aspect metadata entry has no corresponding DCL metadata entry |
| 351 | Parsed role-mapping metadata and persisted role-mapping metadata differ |
| 352 | Role-mapping metadata entry refers to an invalid PFCG mapping (&1) |
| 353 | Role-mapping metadata entry has no corresponding DCL metadata entry |
| 354 | Invalid filter value &1 of field &2 in object &3 (productive entity) |
| 355 | Invalid filter value &1 of field &2 in object &3 (non-productive entity) |
| 356 | DCL has syntactical or semantical error(s) |
| 357 | Mapping output field name is no valid field of entity: &1 |
| 358 | Mapping output entry has no related CTE-Colname entry |
| 359 | Mapping output entry has more than 1 related CTE-Colname entries (&1) |
| 360 | Mapping output entry has no corresponding PFCG mapping |
| 361 | CTE column name of type: &1 has no related PFCG mapping output entry |
| 362 | CTE column name is related to an invalid PFCG mapping output entry (&1) |
| 363 | Start deleting ABAP artifacts of &1 DCL(s) |
| 364 | Start generating ABAP artifacts of &1 DCL(s) |
| 365 | Runtime column entry refers to an invalid Colmap-CTE ID (&1) |
| 366 | ACM ranktable '&1' is obsolete (PGMID=&2; OBJ=&3; DEVCLASS=&4) |
| 367 | Obsolete generated hierarchy ID entry exists |
| 368 | Obsolete generated hierarchy view entry exists |
| 369 | Obsolete hierarchy key entry exists |
| 370 | Obsolete hierarchy data accondition entry exists |
| 371 | Obsolete hierarchy data detail entry exists |
| 372 | Obsolete hierarchy data table entry exists |
| 373 | Keyfield &1 of entity &2 has a DCL-forbidden datatype &3 |
| 374 | Aspect column entry has no corresponding Aspect |
| 375 | Artifact's timestamp differs from the timestamp of the productive DCL |
| 376 | Artifact's timestamp differs from the timestamp of the non-productive DCL |
| 377 | Number of CTE column values and generic aspect columns differ [&1/&2] |
| 378 | Access condition references to an invalid aspect (ASPECT_ID=&1) |
| 379 | CTE column value (position = &1) has no related generic aspect column |
| 380 | Cannot get runtime-delivered CTE expression: &1&2&3&4 |
| 381 | The persisted and the runtime-delivered CTE expression differ (DTAUTHV) |
| 382 | CTE column value references to previously-existing aspect: USER |
| 383 | Aspect has invalid type: &1 |
| 384 | Generic aspect has no aspect metadata entry |
| 385 | Generic aspect has no corresponding aggregate |
| 386 | Generic aspect has another name than its related access policy |
| 387 | Generic aspect contains an invalid entity: &1 |
| 388 | Generic aspect has no related CTE of type: ASPV |
| 389 | Generic aspect has an invalid CTE-ID: &1 |
| 390 | Generic aspect has an invalid parent type: &1 |
| 391 | Generic aspect has the invalid position: &1 |
| 392 | Generic aspect contains &1 columns of type: USER |
| 393 | Generic aspect contains no columns of type: OUTPUT |
| 394 | Aspect column references to an invalid CTE column name (ID=&1) |
| 395 | Runtime condition entry references to an invalid GENERIC aspect (&1) |
| 396 | Aspect column has the invalid column type: &1 |
| 397 | Full authorization operator (&1) and value (&2) do not match |
| 398 | Non-productive DCL has syntactical or semantical error(s) |
| 399 | CTE of type: '&1' is orphaned |
| 400 | The persisted association target '&1' differs from the real target '&2' |
| 401 | CTE column is representing a path but has no CTE column part |
| 402 | Invalid parameter name '&1' of DCL function '&2' |
| 403 | DCL function parameter '&1' is of invalid type '&2' |
| 404 | DCL function parameter '&1' has invalid rollname '&2' |
| 405 | CTE column is representing a DCL function but it has no parameter(s) |
| 406 | CTE column is representing invalid DCL function '&1' |
| 407 | CTE column name function parameter has no corresponding CTE column name |
| 408 | Runtime conditions has no comparison operator (COMP_OPER) |
| 409 | CTE column name has no related aspect column entry |
| 410 | DCL has syntactical or semantical warning(s) |
| 411 | CDS entity has an inconsistent NAMETAB entry |
| 412 | CTE2CTE entry has a designtime CTE as successor |