DMC_RT_GEN - DMC: Nachrichten der Generierungfunktionen
The following messages are stored in message class DMC_RT_GEN: DMC: Nachrichten der Generierungfunktionen.
It is part of development package CNV_DMCR in software component CA-LT. This development package consists of objects that can be grouped under "Data Mapping and Conversion: Runtime".
It is part of development package CNV_DMCR in software component CA-LT. This development package consists of objects that can be grouped under "Data Mapping and Conversion: Runtime".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No valid reference was transferred to the migration object |
| 001 | Error while generating RFC module &2; RC = &1 |
| 002 | No foreign key relations were maintained for structure &1. |
| 003 | Runtime objects for &1 were generated |
| 004 | Class is no longer in use |
| 005 | Syntax error in function module &1 |
| 006 | RFC connection error &1 in function module &2 of function group &3 |
| 007 | RFC system error &1 in function module &2 in function group &3 |
| 008 | Error while processing runtime objects for &1 |
| 009 | Target structure &1 is not mapped to any source structure |
| 010 | Error message: &1&2&3&4 |
| 011 | RFC connection error (destination &1, function module &2) |
| 012 | RFC system error (destination &1, function module &2) |
| 013 | Error while generating module &1; return code &2 |
| 014 | Function group name overruns area: &1 does not lie between &2 and &3 |
| 015 | No valid function group name could be found |
| 016 | Function group &1 could not be created |
| 017 | No valid function module name could be created |
| 018 | Event &1 is not defined |
| 019 | Error during concatenation of &1 &2 &3: Target string is too long |
| 020 | Invalid parameter value for 1036 conversion |
| 021 | Reactivate the referenced DDIC structure |
| 022 | Undefined pseudocode was used: &1 |
| 023 | Missing formal/ actual parameter assignment! Field &1 |
| 024 | Missing formal/ actual parameter assignment for event &1 |
| 025 | Missing formal/ actual parameter assignment in migration object |
| 026 | &1 of ST program &2 failed |
| 027 | Invalid XML file: &1 |
| 028 | No information for business object &1 is available in XML file &1 |
| 029 | Structure information not available for business object |
| 030 | Specified structure &1 does not exist |
| 031 | No field list exists for the specified structure: &1 |
| 032 | Field &1 does not exist in structure &2 |
| 033 | XML synchronization stopped due to incorrect XSD file |
| 034 | XML parse failed due to incorrect XSD file |
| 035 | &1 sync started for migration object &2 |
| 036 | Activation of ST program &1 failed |
| 037 | ROWID selection only possible for migrat. objects with exactly one table |
| 038 | Wrong STREE_TYPE &1 for structure &2 |
| 039 | Parent and child component do not match |
| 040 | Unknown class specified for generation of &1 module |
| 041 | Runtime object invalid. Automatic regeneration was scheduled |
| 042 | no structure left that is not set to read-only |
| 043 | Incorrect or missing migration object GUID in DMC_MT_TABLES |
| 044 | Migration object &1 is not assigned to mass transfer &2 |
| 045 | Parallelization not possible due to non-character-like key field |
| 046 | No counter field found for INDX declustering in DDIC object &1 |
| 047 | RAW fields longer than 32 bytes can't be used as selection field |
| 048 | Initial write behaviour &1 was changed by rule to &2 |
| 049 | Function module &1 does not have a suitable return parameter &2 |
| 050 | Use of a non-released rule: &1 |
| 051 | System specific ident not found |
| 052 | Migration object &1; incorrect definition of cluster table in target syst |
| 053 | Relation &1 <- &2. Default WHERE clause can not be generated. |
| 054 | Invalid foreign key relationship detected for migration object &1 |
| 055 | Migration object &1; incorrect definition of cluster table |
| 056 | Runtime Object identifier not found for migration object &1 |
| 057 | No root structure found for migration object &1 |
| 058 | No valid runtime objects found for migration object &1 |
| 059 | Generated runtime objects of migration object &1 have been deleted |
| 060 | Function group &1 could not be created |
| 061 | Function module could not be inserted in function group &1 |
| 062 | Function module &1 could not be deleted |
| 063 | Cannot delete runtime objects for object &1: object is in process |
| 070 | No table type parameter in function module, therefore no mass processing |
| 100 | ***Mass Generation*** |
| 101 | Start of mass data transfer for ID &1 on &2 at &3 |
| 102 | End of mass data transfer for ID &1 on &2 at &3 |
| 103 | Start creation of migration object &1 |
| 104 | End creation of migration object &1 |
| 105 | &1: No selection parameter was specified |
| 106 | &1 (reading type &2): No access plan calculator was generated |
| 107 | Table &1 is excluded from generation due to table class &2 |
| 108 | Invalid event: &1 is not supported |
| 109 | Mass processing: Start of definition phase for ID &1 on &2 at &3 |
| 110 | Mass processing: End of definition phase for ID &1 on &2 at &3 |
| 111 | Mass processing: Start of generation for ID &1 on &2 at &3 |
| 112 | Mass processing: End of generation for ID &1 on &2 at &3 |
| 113 | Runtime objects for conversion object &1 were generated on &2 at &3 |
| 114 | Start of processing for table &1 |
| 115 | Start generation of the runtime objects for migration object &1 |
| 116 | For table &1, no TABCLASS has been specified in DMC_MT_TABLES! |
| 117 | Error while determining FMID |
| 118 | Function module &1 of function group &2 for migr.object &3 already exists |
| 119 | Begin of deletion of run time objects for mass transfer &1 on &2 at &3 |
| 120 | End of deletion of runtime objects for mass data transfer &1 on &2 at &3 |
| 121 | Start delete function for migration object &1 |
| 122 | Select at least one step |
| 123 | List of tables for mass data transfer &1 was created |
| 124 | Syntax error: &1&2&3&4 |
| 125 | Template function module &1 does not exist |
| 126 | Include name creation failed for migration object &1 |
| 127 | &1: The migration object &3 is not the owner of function group &2 |
| 128 | Structure &1 not suitable for OLO_GEN_DEL behaviour |
| 129 | &1: Error while resolving relationship between sender and receiver struc. |
| 130 | Error while reading Shadow DDIC for structure &1 |
| 131 | No include has been sepcified to fill application select structures |
| 132 | The functionality you are trying to use is not supported in the sender |
| 133 | ABAP Dictionary differences detected for object &1 |
| 134 | Not authorized to use function &1 with RFC connection &2 |
| 135 | Logging table missing for DDNTT |
| 136 | Can't generate runtime object;structure &1 not mapped to any src. struct. |
| 137 | No more objects to process |
| 138 | Read only sender structure &1 is mapped to receiver structure &2 |
| 139 | Sender container of migration object &1 contains more than two structures |
| 140 | Receiver container of mig. obj. &1 contains more/less than one structure |
| 200 | No valid entry in Unicode control tables for &1 |
| 201 | Category 1 but no access to the language key for &1 |
| 202 | Error when determining code page for &1 |
| 220 | Loading existing migration object &1 failed |
| 221 | Data aging field &1 does not exist in source system table &2 |
| 222 | Data aging field &1 has an invalid data type; data type must be DATS |
| 223 | Start of processing for file &1 |
| 224 | End of processing for file &1 |
| 300 | Template program '&1' missing |
| 301 | Syntax error in program '&1' (&2, &3) |
| 302 | Context missing in program '&1' : '&2' |
| 303 | Generated program '&1' could not be deleted |
| 401 | Module type &1 not valid for remote runtime object generation |
| 402 | Error when reading the metadata for remote runtime object generation |
| 403 | Action not possible (system upgrade in process); try again later |
| 404 | Error while selecting data for &1 (include &2) |