MDC_SANITY_MODEL - Model Sanity Messages
The following messages are stored in message class MDC_SANITY_MODEL: Model Sanity Messages.
It is part of development package MDC_MODEL_OP in software component CA-MDG-CMP-AF. This development package consists of objects that can be grouped under "Master Data Consolidation: Data Model On Premise".
It is part of development package MDC_MODEL_OP in software component CA-MDG-CMP-AF. This development package consists of objects that can be grouped under "Master Data Consolidation: Data Model On Premise".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Checks need a BO type to run |
| 001 | Model for BO type &1 could not be accessed |
| 002 | No table objects are available, check model setup |
| 003 | Table object &1 could not be accessed |
| 004 | Table object &1 does not return a table name for type "&2" |
| 005 | Table object &1 returned &2 as table name for type "&3" (&4) |
| 006 | Table object &1 unexpectedly returned &2 as table name for type "&3" (&4) |
| 007 | Model &1 passed instantiation test successfully |
| 008 | Client field of table object &1 should be &2, was &3 (type "&4") |
| 009 | Field &2 of table object &1 has no explicit properties |
| 010 | Source ID field &1-&2 contradicts multiple IDs returned by model |
| 011 | Neither table object &1, nor its model specify a source ID field |
| 012 | Table object &1 issues LOB data for &2, needs LOB handler |
| 013 | Process table &1 misses required field &2, consider regenerating artifact |
| 014 | Table object &1 exhibits field &2 for status "&3", but not for "&4" |
| 015 | Field &2 of table object &1 renders too long name for gateway access |