CNV_DMC_MC - Migration Object Modeler
The following messages are stored in message class CNV_DMC_MC: Migration Object Modeler.
It is part of development package CNV_DMC_MC_GENERICS in software component CA-LT. This development package consists of objects that can be grouped under "Migration Object Modeler: Generic Objects".
It is part of development package CNV_DMC_MC_GENERICS in software component CA-LT. This development package consists of objects that can be grouped under "Migration Object Modeler: Generic Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Changes are only allowed for customer fields |
| 002 | Function is not supported for context &1 |
| 003 | Filling the hit list failed. Value request aborted |
| 004 | Foreign key maint. is not possible if struct. does not exist in database |
| 005 | Function not possible; select dependent structure |
| 006 | Specify a field |
| 007 | Field name '&' must be unique |
| 008 | Field name can only contain letters, numbers, or underscore characters |
| 009 | Specify a datatype for field '&1' |
| 010 | Data type '&1' does not exist for field '&2' |
| 011 | Length must be greater than 0 for field '&1' |
| 012 | Decimal places must be empty or '0' for field '&1' |
| 013 | Decimals length must be smaller than field length |
| 014 | Error while displaying input help (F4 help) |
| 015 | Cannot delete field; only customer fields can be deleted |
| 016 | Select exactly one row |
| 017 | Field name '&' must start with a letter |
| 018 | A namespace prefix can contain a maximum of 10 characters |
| 019 | Namespace must contain between 3 and 8 characters after the character '/' |
| 020 | Field name '&' cannot only consist of a namespace prefix |
| 021 | Field name '&' contains an incorrect number of '/' characters |
| 022 | Namespace prefix must start with the character '/' |
| 023 | Cannot determine whether field &1 is visible, not visible, or required |
| 024 | Rule name too long; maximum length for rules is &1 |
| 025 | Rule name too long; predefined maximum length for rule is &1 |
| 026 | Rule &1 does not have a valid namespace; name must start with Y or Z |
| 027 | Rule &1 cannot start with a namespace prefix (the character �/�) |
| 028 | Technical error: Getting selected tree node key failed |
| 029 | Technical error: Creation of TEXTEDIT_HEADER object failed |
| 030 | Technical error: Creation of TEXTEDIT_FOOTER object failed |
| 031 | Technical error: Creation of TEXTEDIT_BODY object failed |
| 032 | Technical error: Unknown User Command '&1' |
| 033 | &1: Use single quotation marks for literals, for example 'literal' |
| 034 | &1: Data type/length of fields do not match; note that data may be lost |
| 035 | &1: Foreign key field '&2' does not exist |
| 036 | Enter a valid project name |
| 037 | Project name '&' does not exist |
| 038 | Migration object ID '&' must be unique |
| 039 | Enter a migration object ID |
| 040 | Enter a function module |
| 041 | Function module '&1' does not exist |
| 042 | Enter a description |
| 043 | Object ID can only contain letters,numbers,or underscore characters |
| 044 | Select exactly one row |
| 045 | Object ID too long; maximum length for Object ID is 14 |
| 046 | Migration object ID '&' cannot be used; enter a new migration object ID |
| 047 | Function not supported |
| 048 | Enter a translation object ident |
| 049 | Tranlation Object ID must be unique |
| 050 | Project name must be unique |
| 051 | Project not found |
| 052 | Migration object '&1' created successfully |
| 053 | The migration object is locked by user '&1'. Change mode is not possible |
| 054 | Migration object '&1' is not part of project &2 |
| 055 | Migration object '&1' does not exist |
| 056 | Migration object name must be unique |
| 057 | Source structure '&1' created |
| 058 | Field name '&' not unique |
| 059 | Length of data type '&1' must be '&2' |
| 060 | Decimals of data type '&1' must be '&2' |
| 061 | Enter a & |
| 062 | No more files left: Translation object values deleted for project &1 |
| 063 | Files deleted for migration object &1, access plan &2 |
| 064 | Key fields must be placed at the top of the table |
| 065 | Translation Object '&1' does not exist |
| 066 | &1 '&2' is invalid |
| 067 | The name &1 already exists at &2 level; choose another name |
| 068 | The name &1 already exists at migration object level; choose another name |
| 069 | The name &1 already exists at subproject level; choose another name |
| 070 | The name &1 already exists at project level; choose another name |
| 071 | Keyfield &1 must be at the top |
| 072 | Data type '&1' not supported for field '&2'; choose another data type |
| 073 | Name &1 not permitted; choose another name |
| 074 | Cannot switch to edit mode; rule is not based on free code |
| 075 | Project '&1' created successfully |
| 076 | Project name too long; length cannot exceed &1 |
| 077 | Project name can only contain letters,numbers,or underscore characters |
| 078 | A project with the same name already exists; choose another name |
| 079 | Name must start with a valid namespace ('Y' or 'Z' or '/<namespace>/') |
| 080 | Incorrect number of '/' characters; expected format is '/<namespace>/' |
| 081 | Project name '&1' cannot only consist of a namespace prefix |
| 082 | Mig. Obj. must start with a valid namespace:'Y' or 'Z' or '/<namespace>/' |
| 083 | Migration Object ID '&1' cannot only consist of a namespace prefix |
| 084 | Incorrect number of '/' characters; expected format is '/<namespace>/' |
| 085 | Project name can only contain letters, numbers, and characters '/' or '_' |
| 086 | Create Project canceled |
| 087 | Create Migration Object canceled |
| 088 | Migration Object ID must start with 'Z_' |
| 089 | Staging migration objects can only be copied into staging projects |
| 090 | The top level of the object list is already being displayed |
| 091 | Cannot move fields; only one field can be moved at a time |
| 092 | Mapping of target field "&1" of structure "&2" is incomplete |
| 093 | Source field "&1" of structure "&2" is not mapped |
| 094 | Errors in the delivered coding; contact SAP for support |
| 095 | Decimals length must be between 0 and 14 for field '&1' |
| 096 | For data type '&1', field Length must not contain a value for field '&2' |
| 097 | & is not a migration object that uses staging tables |
| 098 | & is not a migration object that uses files |
| 099 | The code for the rule may contains errors |
| 100 | Assigned rule will not be used; see long text |
| 101 | There are variables that have not been checked; see long text |
| 102 | Cannot assign rule; rules can only be assigned to events and fields |
| 103 | Cannot assign rule; source structure is not mapped to a target structure |
| 104 | Cannot display tooltip; Structure Field &1 has no tooltip |
| 105 | Cannot display tooltip; field &1 does not exist |
| 106 | Cannot assign rule; rules can only be assigned to events |
| 107 | Select an option for the target structure |
| 108 | Target structure type '&1' does not exist |
| 109 | Cannot check target values for domain &1; check the domain |
| 110 | Cannot use domain; there is no field for the domain in the value table &1 |
| 111 | &1 is not a valid domain; specify a valid domain |
| 112 | No field selected |
| 113 | Key field &1 of &3 will be excluded from the staging table; see long text |
| 114 | Cannot copy project to project &1; &1 was created in a different client |
| 115 | Cannot copy into project &1; project &1 was created in a different client |
| 116 | Object already displayed in object browser |
| 117 | Feature not supported for this level |
| 118 | Simulation Result for &1 |
| 119 | Select a node first. |
| 120 | Cannot use this option at this level; select a non-root structure node. |
| 121 | All required fields should be filled |
| 122 | It is not possible to use this report for this object; see long text |
| 123 | It is not possible to assign rules to this field |
| 124 | It is not possible to assign rules to this field |
| 125 | It is not possible to remove rules from this field |
| 126 | Cannot simulate migration object; project &1 has the status "Finished" |
| 127 | Cannot reset transfer status; project &1 has the status "Finished" |
| 128 | Cannot change client for project; project &1 has the status "Finished" |
| 129 | Structure &1 must contain at least one visible key field |
| 130 | Cannot simulate the import of data from a staging table; see long text |
| 131 | Cannot generate runtime object; see long text |
| 132 | Cannot synchronize structures; see long text |