MDC_MODEL - Messages In Context Of MDC Model
 The following messages are stored in message class MDC_MODEL: Messages In Context Of MDC Model.
It is part of development package MDC_MODEL in software component CA-MDG-CMP-AF. This development package consists of objects that can be grouped under "Master Data Consolidation: Data Model".
 It is part of development package MDC_MODEL in software component CA-MDG-CMP-AF. This development package consists of objects that can be grouped under "Master Data Consolidation: Data Model".
| Message Nr ▲ | Message Text | 
|---|---|
| 000 | You have no authority to work with the process | 
| 001 | Exactly one table should be marked as ROOT TABLE for BO Type &1 | 
| 002 | One table should be marked for BO Type &1 | 
| 003 | Mark one table as ROOT TABLE for each BO Type | 
| 004 | Specifying source keys necessitates explicit package numbering | 
| 005 | BO &1 does not support process goal "Consolidat. for Central Maintenance" | 
| 006 | Append name &1 is not unique | 
| 007 | There is already a structure named &1 | 
| 008 | Choose a target package first | 
| 009 | Artifacts successfully created | 
| 010 | Data-handover while reading from current step for table &1 is not allowed | 
| 011 | Reading records from table &1 in package &2 failed due to an SQL error | 
| 012 | Saving records to table &1 in package &2 failed due to an SQL error | 
| 013 | Determining source keys from table &1 for package &2 failed | 
| 014 | Handover into table &1 for package &2 requires process ID | 
| 015 | Saving into table &1 for package &2 requires process ID | 
| 016 | Sequencing best record groups failed for package &1 | 
| 017 | Tables for model &1 maintained inaccurately | 
| 018 | No status available for this source record | 
| 019 | There are multiple active records in one match-group | 
| 020 | You have no authority to generate artifacts | 
| 021 | Deleting records from table &1 in package &2 failed due to an SQL error | 
| 022 | Fatal error: inconsistency of key mapping, match groups and source status | 
| 023 | Initializing process &1 at &2 | 
| 024 | Finalizing process &1 at &2 | 
| 025 | Instantiating of consolidation model failed | 
| 026 | Deleting records by worklists failed due to an SQL error | 
| 027 | Splitting records by worklists failed due to an SQL error | 
| 028 | Splitting records by worklists failed due to duplicate records error | 
| 029 | Starting hallmarking modified records of table &1 at &2 | 
| 030 | Hallmarking modified records of table &1 finished at &2 | 
| 031 | Starting hallmarking modified fields of table &1 at &2 | 
| 032 | Hallmarking modified fields of table &1 finished at &2 | 
| 033 | BRF+ application &1 could not be locked | 
| 034 | Object &1 successfully activated | 
| 035 | Created BRF+ application &1 | 
| 036 | Application &1 registered on &2 in system &3, package &4 | 
| 037 | No table of this model is allowing for BRF+ | 
| 038 | Table &1 allows for BRF+, but this is only allowed for process tables | 
| 039 | Field list only needed for process-relevant tables | 
| 040 | Worklist is invalid or does not exist | 
| 041 | Table &1 is already assigned to model &2 | 
| 042 | Model changes could not be included into transporting request &1 | 
| 043 | Activating active table(s) failed | 
| 044 | Applying templates (e.g. creating source and process tables) failed | 
| 045 | Creating BRF+ artifacts failed | 
| 046 | Generating model class or data access class failed | 
| 047 | Model &1 does not have a root table assigned | 
| 048 | Root table &1 of model &2 must have exactly 1 key field besides client | 
| 049 | Altering root table for model &1 is not allowed | 
| 050 | Deletion of active models is not allowed | 
| 051 | Model &1 does not exist | 
| 052 | Deletion not allowed due to possible invalidation of model &1 | 
| 053 | Artifact &1 (&2) could not be deleted | 
| 054 | Table &1 does not exist | 
| 055 | You have no authority to change this record | 
| 056 | BRF+ application does not exist or is inactive | 
| 057 | You have no authority to create BRF+ artifacts | 
| 058 | You have no authority to change records | 
| 059 | Handing over records to next step lead to duplicate entries in table "&1" | 
| 060 | Creation of Gateway model &1 failed | 
| 061 | Creation of Gateway service &1 failed | 
| 062 | Assignment of Gateway model to Gateway service failed | 
| 063 | Matching could not be completed due to active records being locked | 
| 064 | Business Object &1 does not support process goal "&2" | 
| 065 | Conflict found for ID &1 in table &2, field '&3', value '&4' | 
| 066 | Configured key mapping &1 field not in process table &2 | 
| 067 | Inconsistent temporary reference ID &1; could not be retrieved | 
| 068 | Temp. reference for &1 &2 (&3-&4) ignored for validation | 
| 069 | No active ID for source reference &1 &2 exists (&3-&4) - retry required | 
| 070 | Source record for reference ID &1 does not exist within package | 
| 071 | Processing error, consistency check failed | 
| 072 | Improve all Records only supports direct activation | 
| 073 | A record with the same key already exists | 
| 074 | Records must not be removed during reliable processing | 
| 075 | Deletion not allowed for "&1" (&2) or one of its children | 
| 076 | Deletion of records without mapping not allowed for "&1" (&2) | 
| 077 | Keeping Class Name for purpose "&1" must not be empty | 
| 078 | "&1" is not a valid Keeping Class for purpose "&2" | 
| 080 | Keeper of fabric with purpose "&1" is not available | 
| 081 | No corresponding process object exists, table "&1" might be switched off | 
| 083 | New customer ID could not be determined for reference &1 in loop mode | 
| 084 | New supplier ID could not be determined for reference &1 in loop mode | 
| 085 | New customer ID could not be determined for source ID &1 in loop mode | 
| 086 | New supplier ID could not be determined for source &1 in loop mode | 
| 087 | Keeper class &1 must inherit from &2 | 
| 088 | |
| 089 | Keeper class must not be empty | 
| 091 | Dependencies of reference fields could not be resolved | 
| 100 | Names of model table &1 and active table &2 of BO &3 are not identical | 
| 101 | Table &1 of BO &4 contains unsupported data type &2 for key field &3 |