USMD_EDITION_GENERAL - Message Class for Edition
The following messages are stored in message class USMD_EDITION_GENERAL: Message Class for Edition.
It is part of development package USMD_EDITION_GENERAL in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data Governance Editions General".
It is part of development package USMD_EDITION_GENERAL in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data Governance Editions General".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Enter an edition number |
| 002 | Enter an edition name |
| 003 | Enter an edition type |
| 004 | Specify a valid-from date (or a valid-from period) for the edition |
| 005 | Specify at least one valid-from date |
| 006 | Specify at least one valid-to period |
| 007 | Edition &1 does not exist |
| 008 | Edition is not updated |
| 009 | Edition &1 is already released |
| 010 | Specify an edition type or an edition |
| 011 | Edition type &1 is retired and cannot be used to create editions |
| 012 | Edition &1 still has open change requests |
| 013 | Editions for all change requests must belong to same edition type |
| 014 | Special characters &1 are not allowed for edition name |
| 015 | Edition status is mandatory |
| 016 | There is no valid edition type for entity type &1 |
| 017 | Edition type must be the same for source and target edition |
| 018 | New edition must have status 'in process' |
| 019 | Edition is already released |
| 020 | Change request is mandatory |
| 021 | Change request &1 details are not available |
| 022 | Change request &1 is already in status &2 |
| 023 | Change request &1 could not be locked |
| 024 | Technical error |
| 025 | No edition is assigned to change request &1 |
| 026 | Target edition must differ from source edition for change request |
| 027 | Change request &1 contains one or more hierarchies; cannot be rescheduled |
| 028 | Change request &1 is moved to edition &2 |
| 029 | Objects in change request &1 have conflicting changes if moved to &2 |
| 030 | Cannot delete; entity &2 (entity type &1) is used in a future edition |
| 031 | Upgrade to new edition logic started |
| 032 | Upgrade to new edition logic completed |
| 033 | Upgrade to new edition logic failed |
| 034 | Upgrade to new edition logic started for data model &1 |
| 035 | Upgrade to new edition logic completed for data model &1 |
| 036 | Upgrade to new edition logic failed for data model &1 |
| 037 | Upgrade to new edition logic started for entity type &1 |
| 038 | Upgrade to new edition logic completed for entity type &1 |
| 039 | Upgrade to new edition logic failed for entity type &1 |
| 040 | Upgrade failed; edition types have different timeframes for entity &1 |
| 041 | Edition type &1 does not exist |
| 042 | Upgrade to new edition logic not possible |
| 043 | &1 Editions have been replicated |
| 044 | Edition upgrade for model &1 is not completed |
| 045 | Cannot upgrade editions: Zero Downtime Maintenance in process |
| 046 | Backup table &1 created for model &2 entity type &3 table &4 |
| 047 | Backup to table &1 failed for model &2 entity type &3 table &4 |