ACM - Message-Class for all ACM functions/exceptions
The following messages are stored in message class ACM: Message-Class for all ACM functions/exceptions.
It is part of development package SACM_COMMON in software component BC-SEC-AUT-DCL. This development package consists of objects that can be grouped under "Common Objects for Access Control Management".
It is part of development package SACM_COMMON in software component BC-SEC-AUT-DCL. This development package consists of objects that can be grouped under "Common Objects for Access Control Management".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | &1 |
| 002 | &1 &2 |
| 003 | &1 &2 &3 |
| 004 | &1 &2 &3 &4 |
| 005 | By parsing DCL &1, no DCL type could be determined |
| 006 | By parsing DCL &1, no artifact name could be determined |
| 007 | Hierarchy BADI cannot be retrieved: &1&2&3&4 |
| 008 | Invalid DCL source name &1 or no active DCL source exists |
| 009 | Unique secondary key violation for database table &1 |
| 010 | Unknown error occurred for database table &1 |
| 011 | ACM Parser: DCL source name &1 already exists |
| 012 | ACM Parser: DCL source name &1 does not exist |
| 013 | Aggregate with ID=&1 does not exist |
| 014 | Unique key violation for database table &1 |
| 015 | &1 &2&3&4 |
| 016 | &1 &2&3&4 |
| 017 | ACM Parser: End of DCL source reached |
| 018 | Aggregate &1 does not exist |
| 019 | Aspect &1 is already defined in aggregate &2 |
| 020 | Duplicate aspects defined in aggregate &1 |
| 021 | Association &1 of entity &2 is invalid |
| 022 | Wrong no. of open (&1) and close (&2) brackets after assoc. &3 |
| 023 | "]" is located before "[" after association "&1" |
| 024 | Invalid number of spaces (&1) in bracket expression of associaton &2 |
| 025 | Invalid literal &1 after association &2; expected keyword &3 |
| 026 | Invalid field &1 of entity &2 |
| 027 | Invalid aspect &1 |
| 028 | Invalid number of spaces (&1) in AC field expression &2 |
| 029 | Invalid entity &1 |
| 030 | Deletion of role &1 aborted by the user |
| 031 | To be deleted aspect &1 is assigned to a role |
| 032 | Aggregate &1 already defined in DCL &2 |
| 033 | Role &1 already defined in DCL &2 |
| 034 | Aspect &1 is used in &2 roles; do you really want to change its content? |
| 035 | DCL source name &1 does not exist |
| 036 | Expression "= ASPECT" not found in canonical PFCGAUTH-Path (&1) |
| 037 | "&1" is no valid PFCG authorization object |
| 038 | "&1" is no valid PFCG authorization field of authorization object: "&2" |
| 039 | DCL source name &1 has no ABAP artifacts (i.e. is not active) |
| 040 | Role &1 is assigned to &2 user(s). Activation will delete all assignments |
| 041 | Cannot change the fieldtype of aspect &1 because it is (probably) in use |
| 042 | An Aspect must not have the name "&1" |
| 043 | SQL-View &1 of entity &2 does not exist in the database (see tx: SE14) |
| 044 | Cannot generate unique table name |
| 045 | To be deleted PFCG mapping &1 is assigned to a role |
| 046 | Unknown parameter datatype &1 used in entity &2 |
| 047 | Mapping &1 is used in &2 roles; do you really want to change its content? |
| 048 | Duplicate PFCG mappings defined in aggregate &1 |
| 049 | No AC-Condition/Rule exists for authorization view "&1" (ID = &2) |
| 050 | Invalid PFCG mapping &1 |
| 051 | Mapping &1 with object &2 cannot be used in ASPECT PFCG_AUTH(&3, ...) |
| 052 | Invalid entity &1 for PFCG mapping &2 |
| 053 | Invalid path expression: "&1" (it contains no '.') |
| 054 | Association "&1" has a maximum cardinality > 1. This is not allowed |
| 055 | Invalid character '&1' in path expression: "&2" |
| 056 | Keyfield &1 of entity &2 is of DCL-forbidden type: String/XString |
| 057 | Role &1 is a productive role, but only local roles can be deleted |
| 058 | Cannot read TADIR entry of role: &1 |
| 059 | DCL source &1 has inconsistent metadata; activate DDL/DCL to resolve |
| 060 | Cannot delete DCL &1; system upgrade is running; try again later |
| 061 | Automatic repair of DCL source &1 failed; correct it manually |
| 062 | Entity &1 should have been checked before! - &2&3&4 |
| 063 | Error while trying to get information from SQL View &1 |
| 064 | Inconsistent internal data |
| 065 | Field &1 of entity &2 can only be used once within PFCG mapping &3 |
| 066 | Authorization field &1 of authorization object &2 can only be used once |
| 067 | Hierarchy &1 has an identifying field &2 which must be mapped |
| 068 | Mainobject: "&1: &2" is currenty locked by user: &3. Try again later! |
| 069 | Cannot get hierarchy field information from BADI for dimension &1 |
| 070 | Hierarchy Rank-Table: &1 does not exist |
| 071 | Stored Rank-Table name &1 and calculated Rank-Table name &2 differ |
| 072 | Cannot create/update hierarchy Rank-Table &1 (RC=&2) |
| 073 | Cannot activate hierarchy Rank-Table &1 (RC=&2) |
| 074 | Cannot write hierarchy Rank-Table &1 into TADIR (RC=&2) |
| 075 | Condition contains more than one PFCG Mapping |
| 076 | Cannot get hierarchy field information for hierarchy view &1 |
| 077 | Cannot get hierarchy id information from BADI for hierarchy view &1 |
| 078 | Cannot get table information for table: &1 (RC=&2) |
| 079 | Aggregate inserted |
| 080 | Aspect and corresponding Aspectview &1 persisted (insert mode = '&2') |
| 081 | DDL source of Aspectview &1 persisted into DDIC/database |
| 082 | Viewdefinition of Aspectview &1 successfully checked |
| 083 | DDL source of Aspectview &1 deleted from DDIC and database |
| 084 | Aspectview &1 written into TADIR (DDLS+STOB+VIEW) |
| 085 | All mapping-fields of PFCG authorization object &1 successfully checked |
| 086 | Hierarchy entity &1 and its &2 mapping-field(s) successfully checked |
| 087 | PFCG mapping &1 (&2 details) inserted |
| 088 | &1 hierarchy key(s) persisted |
| 089 | Aggregate deleted |
| 090 | Aspect and corresponding Aspectview &1 deleted |
| 091 | PFCG mapping and its sub entries deleted |
| 092 | Before creating ABAP artifacts, delete the existing ones first (&1) |
| 093 | PFCG mapping &1 is already defined in aggregate &2 |
| 094 | Aggregate does not exist and therefore cannot be deleted |
| 095 | User role assignments deleted |
| 096 | Mapping role assignment deleted |
| 097 | Role with &1 rule(s) and &2 condition(s) deleted |
| 098 | Before creating aggregate ABAP artifacts, delete the &1 related roles |
| 099 | After creating aggregate ABAP artifacts, recreate the &1 related roles |
| 100 | Deleting rule number: &1 (functional rule) |
| 101 | Deleting rule number: &1 (instance-based rule) |
| 102 | Rule number: &1 deleted |
| 103 | DDL source of authorization view deleted from DDIC and database |
| 104 | A Role to this DCL does not exist and therefore cannot be deleted |
| 105 | Trying to delete DT-Condition number: &1 |
| 106 | DT-Condition number: &1 deleted |
| 107 | AC-Condition deleted |
| 108 | Trying to delete AC-Condition |
| 109 | PFCG_AUTH aspect deleted |
| 110 | Related PFCG_AUTH aspect &1 is still in use and cannot be deleted |
| 111 | Authorizationview &1 deleted |
| 112 | Related Authorizationview is still in use and cannot be deleted |
| 113 | Link-entry between AC-Condition and hierarchy metadata deleted (ID=&1) |
| 114 | Related hierarchy data detail (&1) is still in use and cannot be deleted |
| 115 | Hierarchy data detail (metadata detail) &1 deleted |
| 116 | Related hierarchy metadata (&1/&2) is still in use and cannot be deleted |
| 117 | Hierarchy data table (metadata header) &1 / &2 deleted |
| 118 | Related AC-Condition is still in use and cannot be deleted |
| 119 | Trying to delete Authorizationview -- with keys/values: "&1/&2" |
| 120 | Authorizationview deleted |
| 121 | DDL source of Aspectview &1 activated |
| 122 | No Authorizationviews changed --> No DDL source activation necessary |
| 123 | DDL source of the authorization view activated |
| 124 | Trying to delete role |
| 125 | Role deleted |
| 126 | Role created with &1 rule(s) and &2 condition(s) |
| 127 | Mapping role assignment created |
| 128 | Trying to insert &1 'Generated hierarchy views' (+data) in new tasks |
| 129 | Trying to insert role |
| 130 | Inserting rule number: &1 (functional rule) |
| 131 | Inserting rule number: &1 (instance-based rule) |
| 132 | Check if fieldview exists and create it if not existent |
| 133 | Fieldview already exists and can be re-used |
| 134 | DDL source of authorization view persisted into DDIC/database |
| 135 | Authorization view and its details persisted (inserted) |
| 136 | Authorizationview written into TADIR (DDLS+STOB+VIEW) |
| 137 | Rule number: &1 inserted |
| 138 | Trying to insert DT-Condition number: &1 |
| 139 | A related AC-Condition already exists and must not be inserted |
| 140 | DT-Condition number: &1 inserted |
| 141 | Trying to insert AC-Condition of column type: &1 |
| 142 | AC-Condition inserted |
| 143 | AC-Field refers to a 'normal' aspect with name: &1 |
| 144 | AC-Field refers to a generic aspect |
| 145 | AC-Field refers to a fix-filter-condition (without an aspect) |
| 146 | The AC-Condition refers to a 'normal' (non PFCG_AUTH) pathview |
| 147 | The AC-Condition refers to a PFCG_AUTH pathview |
| 148 | The AC-Condition refers to a 'normal' (non PFCG_AUTH) fieldview |
| 149 | The AC-Condition refers to a PFCG_AUTH fieldview |
| 150 | The PFCG_AUTH aspect used in this AC-Condition contains no fieldmapping |
| 151 | There is already a PFCG_AUTH aspect with canonical expression: &1&2&3&4 |
| 152 | Trying to insert PFCG_AUTH aspect with canonical expression: &1&2&3&4 |
| 153 | PFCG_AUTH aspect inserted |
| 154 | The AC-Condition contains a PFCG-Mapping to hierarchy view: &1 |
| 155 | AC-Condition hierarchy info: Analytical view=&1 / Representative key=&2 |
| 156 | Read hierarchy metadata header information from BADI-class: &1 |
| 157 | Hierarchy metadata header successfully checked |
| 158 | Hierarchy metadata details successfully checked |
| 159 | Link between AC-Condition and hierarchy metadata already exists (ID=&1) |
| 160 | Hierarchy metadata detail already exists for analytic view/field: &1/&2 |
| 161 | Hierarchy metadata header already exists for hierarchy/dimension: &1/&2 |
| 162 | Hierarchy metadata header (&1/&2) inserted |
| 163 | &1 hierarchy metadata detail entries inserted |
| 164 | Link between AC-Condition and hierarchy metadata inserted |
| 165 | Viewdefinition of authorization view successfully checked |
| 166 | Trying to insert authorization view |
| 167 | Internal table '&1' doesn't contain an entry with "contains_aspect=X" |
| 168 | DDIC Open-SQL error: &1&2&3&4 |
| 169 | Trying to regenerate hierarchy metadata for access condition |
| 170 | ABAP artifacts generation failed --> Delete all artifacts of role &1 |
| 171 | ABAP artifacts generation failed --> Delete all artifacts of aggregate &1 |
| 172 | Only &1 of &2 log entries could be persisted |
| 173 | &1 fields on the left side, but the PFCG mapping has &2 output fields |
| 174 | Hierarchy information: datasource type = '&1'; datasource name = '&2' |
| 175 | Getting hierarchy information for entity &1 and field &2 failed |
| 176 | Using prefix &1, elements &2 and &3 yield the same prefixed name &4 |
| 179 | Generate ABAP artifacts of DCL: &1 |
| 180 | Delete ABAP artifacts of DCL: &1 |
| 181 | Categorizing &1 DCL(s) |
| 182 | Updating the metadata of &1 DCL(s) |
| 183 | Executing the 'After Import' method for &1 DCLs |
| 184 | Execution of the 'After Import' method finished |
| 185 | Categorizing DCLs - number of existing roles: &1 |
| 186 | Categorizing DCLs - number of deleted roles: &1 |
| 187 | Categorizing DCLs - number of existing aggregates: &1 |
| 188 | Categorizing DCLs - number of deleted aggregates: &1 |
| 189 | Categorizing DCLs - number of DCLs which cannot be categorized: &1 |
| 190 | Updating metadata for DCLs of type: Role (&1 modified; &2 deleted) |
| 192 | Updating metadata for DCLs of type: Aggregate (&1 modified; &2 deleted) |
| 193 | Processing DCLs of type: &1 |
| 194 | After skipping ACMTST DCLs - number existing roles: &1 |
| 195 | After skipping ACMTST DCLs - number existing aggregates: &1 |
| 196 | Trying to delete the ABAP artifacts for the DCL (&1/&2) |
| 197 | After removing descendants (metadata pruning) - number existing roles &1 |
| 198 | Categorizing DCLs - DCL: '&1' cannot be categorized |
| 199 | Error when deleting artifacts (more details in the log of the DCL) |
| 200 | ABAP artifacts of the DCL successfully deleted (&1/&2) |
| 201 | Warning when deleting artifacts (more details in the log of the DCL) |
| 202 | Trying to generate the ABAP artifacts for the DCL (&1/&2) |
| 203 | Number of modified DCLs before metadata update: &1 |
| 204 | Number of modified DCLs after metadata update: &1 |
| 205 | Error when generating artifacts (details in the log of the DCL) (&1/&2) |
| 206 | ABAP artifacts of the DCL successfully generated (&1/&2) |
| 207 | Warning when generating artifacts (details in the log of the DCL)(&1/&2) |
| 208 | Executing the 'XPRA Initial Load' report for &1 DCLs |
| 209 | Execution of the 'XPRA Initial Load' report finished |
| 210 | Executing the 'Initial Load' report for &1 DCLs |
| 211 | Execution of the 'Initial Load' report finished |
| 212 | Execution finished after deletion (Flag 'delete only' was set) |
| 213 | Changed metadata of DCL &1 (&2/&3) |
| 214 | Deleted metadata of DCL &1 |
| 216 | <-- Reference to the related log root entry |
| 217 | DCL &1 is currenty locked by user: &2. Try again later! |
| 218 | Trying to generate the ABAP artifacts for DCL |
| 219 | ABAP artifacts for DCL successfully generated |
| 220 | DCL parser started |
| 221 | Role parser started |
| 222 | Aggregate parser started |
| 223 | Create/Insert ABAP artifacts of aggregate |
| 224 | Trying to delete the ABAP artifacts for the DCL |
| 225 | ABAP artifacts could not be generated because of an error |
| 226 | ABAP artifacts for DCL deleted |
| 227 | ABAP artifacts for DCL could not be deleted because of an error |
| 228 | DCL inherits to &1 other DCL(s) |
| 229 | DCL handler started |
| 230 | DCL handler ended |
| 231 | &1 DCL(s) cause an infinite loop; deleting artifacts of the DCL(s) |
| 232 | Objects for request &1 could not be read |
| 233 | DDL source &1 was processed in ACM after import method |
| 234 | DCL source &1 was added in ACM after import method |
| 235 | Cannot get the metadata of the DCL |
| 237 | The metadata are current |
| 238 | Executing the 'After Import' for transport request: &1 |
| 239 | Execution of the 'After Import' for transport request: &1 finished |
| 240 | Transport request contains the ACM after import post processing DDL |
| 241 | Transport request contains &1 DDL(s) |
| 242 | The &1 DDL(s) are used in &2 DCL(s), which have to be processed now |
| 243 | Generate ABAP artifacts of DCL: &1 (&2/&3) |
| 244 | Delete ABAP artifacts of DCL: &1 (&2/&3) |
| 245 | Starting the ABAP artifacts deep-cleaner |
| 246 | ABAP artifacts deep-cleaner finished |
| 247 | Deleted all entries of &1 ACM artifact tables |
| 248 | &1 orphaned ACM DDIC view(s) found |
| 249 | &1 orphaned ACM DDIC view(s) deleted |
| 250 | The metadata of DCL &1 are current |
| 251 | Changed the metadata of DCL &1 |
| 252 | Created the metadata of DCL &1 |
| 253 | Deleted the metadata of DCL &1 |
| 254 | Orphaned ACM DDIC view '&1' could not be deleted |
| 255 | Upgrade running: Changes in ACM are locked (decision taken by rule &1) |
| 256 | This function cannot be executed in dialog mode |
| 257 | Initial load for access controls will be performed as background job |
| 258 | There are no DCLs to be processed. Quit processing |
| 259 | Executing the 'XPRA Metadata Update' report for &1 DCLs |
| 260 | Execution of the 'XPRA Metadata Update' report finished |
| 261 | &1 DCL(s) cause an infinite loop; their metadata were not updated |
| 262 | DCL metadata updated |
| 265 | ABAP artifacts generation failed and was rolled back |
| 266 | Inconsistency in method: &1. Invalid type=&2 / name=&3 |
| 267 | Inconsistency in method: &1. Current type=&2 / supplied type=&3 |
| 268 | Inconsistency in method: &1. Current name=&2 / supplied name=&3 |
| 269 | ABAP artifacts deletion failed and was rolled back |
| 270 | ACM generator starts to check the DCL |
| 271 | ACM generator successfully checked the DCL |
| 272 | ACM generator quit processing because an error was found |
| 273 | Invalid resource type: &1 |
| 274 | Role generator started |
| 275 | The related CTE (type=&1) already exists and must not be inserted |
| 276 | Trying to insert CTE (view type: &1) |
| 277 | CTE inserted (view type: &1; column type: '&2') |
| 278 | Trying to delete CTE (view type: &1; column type: '&2') |
| 279 | The to be deleted CTE (ID=&1) does not exist in the database |
| 280 | CTE (view type: &1; column type: '&2') deleted |
| 281 | CTE cannot be build because for entity: &1 no keys were defined |
| 282 | Related CTE is still in use and cannot be deleted |
| 283 | CTE of type=&1 has not changed. No update required |
| 284 | Error when trying to generate the CTE. The DCL has syntactical errors |
| 285 | CTE check could not be executed (check dump with ID=&1 in ST22) |
| 286 | Trying to delete AC-Condition (old version with DDIC views) |
| 287 | Trying to update CTE (view type: &1) |
| 288 | CTE updated (view type: &1; column type: '&2') |
| 289 | Processing CTE (view type: &1) |
| 290 | Update expression for related CTE (view type: &1; column type: '&2') |
| 291 | Check AC-Condition of column type: &1 and its CTEs, aspects, mappings |
| 292 | A related AC-Condition does not exist and must be inserted |
| 293 | Aggregate generator started |
| 294 | An aggregate to this DCL does not exist and therefore cannot be deleted |
| 295 | Entity with parameters are not allowed in aspects (aspect=&1; entity=&2) |
| 296 | Trying to delete aspect |
| 297 | Aspect deleted |
| 298 | Trying to insert aspect of type: &1 |
| 299 | Aspect of type: &1 inserted |
| 300 | AC-Condition deleted (old version with DDIC views) |
| 301 | Creating new version with ID prefix '&1' |
| 302 | Generate successfull. Activate version '&1'.Delete all other content. |
| 303 | Initial load run detected. Generating copy of artefacts into version '&1' |
| 304 | Trying to delete rule number: &1 (old version with DDIC views) |
| 305 | Rule number: &1 deleted (old version with DDIC views) |
| 306 | Trying to delete aspect (old version with DDIC views) |
| 307 | Aspect deleted (old version with DDIC views) |
| 308 | Cannot generate artifacts (CTE version conflict). Delete artifacts first! |
| 309 | Using hierarchy BADI-class: &1 |
| 310 | Mandatory PFCG mapping content: &1 is initial |
| 311 | Trying to insert PFCG mapping |
| 312 | Trying to delete PFCG mapping |
| 313 | Trying to delete aggregate |
| 314 | No corresponding hierarchy data exist. No further deletion necessary |
| 316 | The determined CTE merge type of the condition is: &1 |
| 317 | Cannot determine the CTE merge type of the condition |
| 318 | CTE &1 has the invalid merge type: &2 |
| 319 | CTE cannot be build because the path does not end with an aspect |
| 320 | DDIC API error. Cannot get header data for entity: &1 |
| 321 | Internal error. Condition with index &1 does not exist |
| 322 | The CTE already has a column for entity field: &1 |
| 323 | CTE column name entry: &1 is no longer in use and was deleted |
| 324 | CTE column type was adapted. Old value: '&1'; new value: '&2' |
| 325 | CTE expression was adapted. Old length: &1; new length: &2 |
| 326 | Built CTE expression |
| 327 | Check CTE expression |
| 328 | Error when checking CTE in line: &1 for word: &2 |
| 329 | Hierarchy BADI class: &1 returned inconsistent data (&2 vs &3) |
| 330 | DDIC API error. Cannot get parameter data for entity: &1 |
| 331 | Parameter &1 of entity &2 has unknown/invalid type: '&3' |
| 332 | Filter &1 has unknown/invalid type: '&2' |
| 333 | Internal error. Table IT_PATHDETAIL_FILTERS does not have &1 entries |
| 334 | Deletion of the metadata of the DCL failed, sy-subrc: &1 |
| 335 | Deletion of the metadata of the DCL &1 failed |
| 336 | Change of the metadata of the DCL failed, sy-subrc: &1 |
| 337 | Change of the metadata of the DCL &1 failed |
| 338 | Creation of the metadata of the DCL failed, sy-subrc: &1 |
| 339 | Creation of the metadata of the DCL &1 failed |
| 340 | CDS entity being processed |
| 341 | DCL metadata incorrect: DCL &1 does not contain entity &2 |
| 342 | Getting the NAMETAB entry for entity: &1 failed |
| 343 | First stack element is not the supplied instance (Stack is inconsistent) |
| 344 | Buffer entries for entity: &1 in view: &2 invalidated |
| 345 | Buffer for entity: &1 in view: &2 could not be invalidated (rc=&3) |
| 346 | Complete buffer for view: &1 invalidated |
| 347 | Complete buffer for view: &1 could not be invalidated (rc=&2) |
| 348 | Entity identified for NAMETAB update + buffer invalidation (phase: &1)&2 |
| 349 | Entity identified for NAMETAB update (phase: &1)&2 |
| 350 | Writing the NAMETAB entry for entity: &1 failed |
| 351 | NAMETAB for this entity updated (Access Control Exists = '&1') |
| 352 | Dedicated entity: &1 identified for buffer invalidation (view: &2) |
| 353 | This CTE expression was already checked before within this role |
| 354 | To be checked CTE program (syntax check) has no errors |
| 355 | Check CTE expression for entity &1 with dedicated DDL API |
| 356 | No CTE exist to this runtime header entry |
| 357 | DCL was removed from list. It will be generated by its parent DCL: &1 |
| 358 | NAMETAB of DDL &1 is inconsistent (Tx: SE11-->Utilities-->Runtime Object) |
| 359 | CDS entity &1 no longer existent and so deleted from ACMENTITYSTATUS |
| 360 | Start to delete all entries of ACM artifact tables |
| 361 | The keyfields of entity &1 could not be determined |
| 362 | &1 entity metadata entries deleted |
| 363 | &1. entity metadata entry inserted: [&2 / &3] |
| 364 | Entity metadata entry [&1 / &2] already exists and must not be inserted |
| 365 | Metadata update failed for DCL &1 |
| 366 | Trying to manually update the NAMETAB entry for CDS entity: &1 |
| 367 | Cannot get Rank-Table fields for hierarchy &1 and dimension &2 |
| 368 | Field '&1' of hierarchy view &2 was not found in PFCG mapping (ID=&3) |
| 369 | Field '&1' of hierarchy view &2 was not found in the Rank-Table |
| 370 | Ranktable field &1 nor part of PFCG mapping neither of the dimension key |
| 371 | Number of DCL-entity tuples to be checked for NAMETAB update: &1 |
| 372 | Invalid hierarchy datasource type: '&1' |
| 373 | Hierarchy datasource name not filled |
| 374 | Datatype inconsistency: Field &1 differs in entity &2 and &3 |
| 375 | Deleted DCL has no deletable metadata |
| 376 | DCL &1 has inheritance cycle. Elements: &2&3&4 |
| 377 | --> inheriting from role &1 |
| 378 | Cannot read DTCTE expressions from ACM runtime: &1&2&3&4 |
| 379 | Resource: &1 does not contain a Designtime-CTE of type: DTAUTHV |
| 380 | &1: More than &2 DCLs to process. Using SHDB parallelization framework. |
| 381 | &1: Less than &2 DCLs to process. No parallelization required. |
| 382 | &1: Package &2: Processed &3 |
| 383 | Package &1: DCL &2 generated successfully |
| 384 | Package &1: DCL &2 generated with error (retrying in post-processing) |
| 385 | More than &1 DCLs to process. Using SHDB parallelization framework. |
| 386 | Less than &1 DCLs to process. No parallelization required. |
| 387 | Result of parallel processing: &1 successful, &2 warnings, &3 errors |
| 388 | Starting serial generation of the &1 DCLs with error/warning |
| 389 | Package &1: DCL &2 generated with warning (retrying in post-processing) |
| 390 | Internal error: PFCG mapping: &1 has no output entry on position &2 |
| 391 | DCL prepared for metadata update (delete-flag='&1') |
| 392 | Metadata persistency: &1/&2 successfully deleted |
| 393 | Metadata persistency: &1/&2 successfully inserted |
| 394 | Activation of &1 failed. Review root cause in SACMDCLS --> "Log Entries". |
| 395 | DCL metadata cannot be determined |
| 396 | ACM generator was not called. No ABAP artifacts were deleted |
| 397 | A redefinition for entity '&1' already exists in rule &2 of DCL '&3' |
| 398 | Rule artifact for CDS entity generated (role: &1) |
| 399 | Dialog text object '&1' does not exist for languages '&2' and '&3' |
| 400 | CTE of type: '&1' was not deleted as it is still in use by another rule |
| 401 | CTE of type: '&1' was deleted |
| 402 | CTE of type: '&1' was inserted |
| 403 | CTE of type: '&1' was updated |
| 404 | Delete ABAP artifacts because an error has occurred at generating |
| 405 | DCL collected into GENERATE buffer (status: &1) |
| 406 | DCL collected into GENERATE buffer (old status: &1; next status: &2) |
| 407 | Collected DCL in GENERATE buffer was already generated |
| 408 | DCL (and one child) collected into GENERATE buffer (status: &1) |
| 409 | DCL (and &2 children) collected into GENERATE buffer (status: &1) |
| 410 | Process collected DCL (status=&1) at SUBMIT: Start generate artifacts |
| 411 | Package &1: Descendant of &2 has already status: &3 in GENERATE buffer |
| 412 | Package &1: Descendant of &2 collected into GENERATE buffer (status: &3) |
| 413 | Package &1: DCL collected into GENERATE buffer (status: &2) |
| 414 | A specified aspect is too long for persisting (details: &1) |
| 415 | NAMETAB flag was already correctly set (Access Control Exists = '&1') |
| 416 | Trying to update the NAMETAB entry for CDS entity &1 from DCL &2 |
| 417 | Successfully updated the NAMETAB entry for CDS entity &1 from DCL &2 |
| 418 | Update NAMETAB entry for CDS entity &1 from DCL &2 failed |