SACM_DCLS - SACM DCL Source Editor
The following messages are stored in message class SACM_DCLS: SACM DCL Source Editor.
It is part of development package SACMDT_LM in software component BC-SEC-AUT-DCL. This development package consists of objects that can be grouped under "Designtime-Life-Cycle for Access Control Management".
It is part of development package SACMDT_LM in software component BC-SEC-AUT-DCL. This development package consists of objects that can be grouped under "Designtime-Life-Cycle for Access Control Management".
Message Nr ▲ | Message Text |
|---|---|
| 000 | |
| 001 | Use the ABAP Development Tools in Eclipse |
| 002 | There is no active version of the object &1 |
| 003 | There are &1 DCL sources of type &2 |
| 004 | &1&2&3&4 |
| 005 | &1 &2 &3 &4 |
| 006 | Description of DCL source &1 is too long; only &2 characters allowed |
| 007 | Description of DCL source &1 is empty |
| 008 | The name of the ABAP DCL source &1 is not valid |
| 009 | The name of the ABAP DCL source must not be empty |
| 010 | The name of the ABAP DCL source must not be longer than 40 characters |
| 011 | ABAP DCL source &1 already exists |
| 012 | The short text describing the ABAP DCL source is empty |
| 013 | The entity &1 is used in access control documents. Remove the usage. |
| 014 | The entity &1 is used in access control document &2 |
| 015 | No access control for entity &1, or use AccessControl.authorizationCheck |
| 016 | No Authorization Check Mode set. Default value #CHECK is used |
| 017 | The Authorization Check Mode does not allow access control by DCL |
| 019 | Unknown annotation value &1 for AccessControl.authorizationCheck |
| 020 | Use the ADT Tools in Eclipse to modify access control documents |
| 021 | The access control &1 has errors. Open it for more information |
| 022 | Unable to read depending DCL &1. Check correctness of the document |
| 023 | Result set is filtered by access control |
| 024 | Could not add &1 to transport request &2. &3 &4 |
| 025 | No transport request given. Could not add DCLs to transport request |
| 026 | Description of DCL source is too long; only &1 characters allowed |
| 027 | Update of TADIR for object &1 failed |
| 028 | Accesspolicy &1 already exists as subobject of &2 in system &3 |
| 029 | Role &1 already exists as subobject of &2 in system &3 (SAP Note 2561791) |
| 030 | Aspect &1 already exists as subobject of &2 in system &3 |
| 031 | PFCG mapping &1 already exists as subobject of &2 in system &3 |
| 032 | Inheritance chain contains a cycle: &1&2&3&4 |
| 033 | DDL secondary object handler started for activated DDL: &1 |
| 034 | DDL secondary object handler finished for activated DDL: &1 |
| 035 | The changes invalidated its authorization view. Must be fixed manually |
| 036 | The view definition is still syntactically correct |
| 037 | ACM object status monitor found no issues for this access condition |
| 038 | ACM object status monitor could not repair this authorization view |
| 039 | ACM object status monitor could repair this authorization view |
| 040 | DCL &1 added to transport request &2 |
| 041 | Could not add &1 to transport request &2. DCL already on request &3 |
| 042 | The changes invalidated the DCL. The DCL must be fixed manually |
| 043 | The DCL is still syntactically correct |
| 044 | ACM object status monitor found no issues for this CTE |
| 045 | ACM object status monitor could not repair this CTE |
| 046 | ACM object status monitor could repair this CTE |
| 047 | Entity has &1 related and also to-be-checked entity (including itself) |
| 048 | Entity has &1 related and also to-be-checked entities (including itself) |
| 049 | Check consistency of entity number: &1 |
| 050 | Entity is used in &1 DCL(s) |
| 051 | Starting checking the DCL definition |
| 052 | Finished checking the DCL definition |
| 053 | Entity is not used in any DCLs |
| 054 | No Authorization Check Mode set. Default value #NOT_REQUIRED is used |
| 055 | Deletion of workbench object for DCL &1 failed |
| 056 | No authorization to delete the Access Control &1 |