USMD_GOV_API - Meldungen aus dem Governance API
The following messages are stored in message class USMD_GOV_API: Meldungen aus dem Governance API.
It is part of development package USMD_GOVERNANCE_API in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data Governance API".
It is part of development package USMD_GOVERNANCE_API in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data Governance API".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Error(s) during creation of governance process |
| 001 | &1 is an invalid or an inactive data model |
| 002 | Specify a change request type |
| 003 | Assign change request type &1 to data model &2 |
| 004 | Change request &1 does not exist |
| 005 | Specify a change request number |
| 006 | Blocking behavior &1 is invalid; only values 1, 2, or 3 are allowed |
| 007 | Entity type &1 for model &2 does not exist |
| 008 | Entity &1 cannot be blocked; only entity type 1 is supported |
| 009 | Change request &1 is not locked |
| 010 | Entity &1 is not locked |
| 011 | Status &1 of change request is invalid |
| 012 | Status of change request &1 does not permit changes |
| 013 | Error while reading entity &1 using the specified keys |
| 014 | Entity &1 does not belong to change request &2; check not possible |
| 015 | Entity &1 cannot be blocked; keys are invalid |
| 016 | Current user &1 is not an authorized processor of work item &2 |
| 017 | Entity &1 with this key already exists in the object list |
| 018 | Change request &1 does not agree with change request &2 in work item &3 |
| 019 | Change request &2 already contains entity &1 |
| 020 | Submitted structure is not suitable to entity &1 |
| 021 | Submitted method parameters are insufficient |
| 022 | Priority &1 of the change request is invalid |
| 023 | Reason '&1' of the change request is invalid |
| 024 | Reason for rejection '&1' of the change request is invalid |
| 025 | Specify the change request number or change request type |
| 026 | Change request &1 is not compatible to change request type &2 |
| 027 | Work item &1 is not compatible with change request &2 |
| 028 | More than one work item exists; select one work item |
| 029 | Object list of change request &1 cannot be changed |
| 030 | Entity type &1 is not contained in data model &2 |
| 031 | Entity type &1 cannot be processed with change request type &2 |
| 032 | Entity properties of entity type &1 do not allow deletion of entity |
| 040 | Edition &1 cannot be used with change request type &2 |
| 041 | Edition &1 for edition type &2 does not match data model &3 |
| 042 | Edition can not be changed |
| 043 | Change request type does not support editions |
| 044 | Specify an edition before specifying a replication timing |
| 045 | Replication timing cannot be changed |
| 046 | Replication timing not valid |
| 047 | Provide valid edition before writing data to the change request |
| 048 | Edition &1 of change request is different to edition &2 of the entity |
| 049 | Provide a valid edition for change request &1 |
| 050 | Edition &1 does not exist |
| 051 | Edition &1 is blocked or released. Choose a different one. |
| 070 | Derived data of entity type &1 is not in scope of change request &2 |
| 071 | A technical error occurred during the derivation of change request &1 |
| 072 | Derived data of &1 with key &2 is interlocked in change request &3 |
| 080 | &1 &2 cannot be processed in this change request |
| 081 | |
| 100 | You have submitted change request &1 |
| 101 | Change request &1 saved |
| 102 | Enter a reason for the rejection of the change request |
| 103 | Enter a priority |
| 104 | Enter a due date |
| 105 | Enter a reason |
| 200 | Inconsistency in structure of context attribute for &1 |
| 201 | Create a general context first |
| 300 | Enter all of the specified required fields |
| 301 | Select only those attachments you are allowed to delete |
| 302 | Select a work item and proceed with OK |
| 349 | |
| 350 | Hierarchy &1 in &2 hierarchy assignment is locked by change request &3 |
| 351 | &1 hierarchy assignment &2 to parent &3 is not locked |
| 352 | &1 hierarchy assignment &2 to parent &3 in version &4 is not locked |
| 353 | Hierarchy &1 in version &4 is locked by change request &3 |
| 354 | &1 is completely locked for &2 hierarchy assignment by change request &3 |