CNVMBTCHECK - Messages for PCL Checks
The following messages are stored in message class CNVMBTCHECK: Messages for PCL Checks.
It is part of development package CNV_MBT_MAIN in software component CA-LT. This development package consists of objects that can be grouped under "Main components of PCL for SLO Products".
It is part of development package CNV_MBT_MAIN in software component CA-LT. This development package consists of objects that can be grouped under "Main components of PCL for SLO Products".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Check &1 started at &2 &3 by &4 |
| 002 | Check &1 finished at &2 &3 by &4 |
| 003 | &1| Structure &2 does not exist in this migration object |
| 004 | &1| More than one top level structure in sender hierarchy |
| 005 | &1| More than one top level structure in receiver hierarchy |
| 006 | &1| No top level ( no tree ) for sender hierarchy |
| 007 | &1| No top level ( no tree ) for receiver hierarchy |
| 008 | &1| Structure &2 contains itself as parent |
| 009 | &1| Parent structure &2 for structure &3 is not a sender structure |
| 010 | &1| Parent structure &2 for structure &3 is not a receiver structure |
| 011 | &1| Structure contains itself as next structure |
| 012 | &1| Parent structure &2 for structure &3 is missing |
| 013 | &1| Next structure &2 for structure &3 is on the wrong level |
| 014 | &1| Next structure &2 for structure &3 is not a sender structure |
| 015 | &1| Next structure &2 for structure &3 is not a receiver structure |
| 016 | &1| Next structure &2 for structure &3 is missing |
| 017 | &1| Next structure definition is wrong and might cause an endless-loop |
| 018 | &1| One or more sender structures do not have a receiver assigned |
| 019 | &1| Receiver structure &2 is not assigned to a sender structure |
| 020 | &1| Structure &2 is not a receiver structure still assigned to a sender. |
| 021 | &1| Structure relationship not given for the sender structure &2 |
| 022 | &1| The given relationship type &3 for the structure &2 is wrong. |
| 023 | &1| Sender structure &2 is not assigned to the receiver structure &3 |
| 024 | &1| Rule &2 not having proper rule type. |
| 025 | &1| The rule import parameter &2 will not be available for this object. |
| 026 | &1| The selection-field &2 does not exist in top level structure. |
| 027 | &1| Table &2 is not active or does not exist in the receiver system. |
| 028 | &1| The field &2 is not active or missing in the receiver system |
| 029 | &1| Foreign key &2 does not exist in the parent structure on the sender. |
| 030 | &1| The foreign key &2 and the referring field &3 have diff. types |
| 031 | &1| Field &2 does not exist in the sender structure on sender system |
| 032 | &1| Include &2 has incorrect include type. |
| 033 | &1| Datatypes of sender field &2 and receiver field &3 do not match |
| 034 | &1| No receiver field or rule associated to the sender field &3-&2 |
| 035 | &1| Receiver field &3-&2 is not assigned a sender or rule. |
| 036 | &1| Datatype not mentioned for the rule parameter &2 of rule &3 |
| 037 | &1| For rule &2 the import parameter &3 is should be of type CHAR. |
| 038 | &1| Table &2 is not active or missing in the sender system |
| 039 | &1| The import parameter &2 of rule &3 is not long enough. |
| 040 | &1| structure type not specified for the structure &2. |
| 041 | &1| Rule &2 used in package &3 is not a field related rule |
| 042 | &1|No sender assinged to the receiver field &2. It will not be filled |
| 043 | &1| Field &2 will not be transferred; delete excl. flg. or rule |
| 044 | &1| Receiver field &2 and export parameter &3 have different types. |
| 045 | &1| Sender field &2 and the import parameter &3 have different types. |
| 046 | &1| Import param &2 and export param &3 have different types. |
| 047 | &1| &2 is not an import parameter but used as import parameter. |
| 048 | &1| No processing method specified for rule &2. |
| 049 | &1| Selfield not provided. |
| 050 | &1| Data Path not provided for the sender structure &2 |
| 051 | &1| the step rule &2 will not be used. |
| 052 | &1| No table information present for this migration object. |
| 053 | &1| Existence of selfield &2 not checked. (cluster/pool) |
| 054 | &1| Table &2 will not be checked for existence in sender. (cluster/pool) |
| 055 | &1| Receiver field &2 will not be checked for existence. (cluster/pool) |
| 056 | &1| Foreign key value &2 will not be checked. (cluster/pool) |
| 057 | &1| Sender field &2 does not exist in the given structure on sender. |
| 058 | &1| Sender field &2 will not be checked for existence. (cluster/pool) |
| 059 | &1| Table &2 will not be checked for existence in receiver.(cluster/pool) |
| 060 | &1| Foreign key &2 does not exist in the parent structure on sender. |
| 061 | |
| 062 | &1| Key for table &3 differs in sender and receiver. Check field &2. |
| 063 | Errors detected for migration object &1 : |
| 064 | &1| The assigned structure &2 is not a sender structure |
| 065 | &1| Rule &2 does not exist in package &3 |
| 066 | &1| Field &2 used as an import parameter for rule &3 does not exist |
| 067 | &1| Receiver table &1 is client dependent but sender table independent |
| 068 | &1| Sender table &1 is client dependent but receiver table independent |
| 069 | &1| Field &2 used as a child in the foreign key does not exist |