DMC_AP - MWB: AP specific messages
The following messages are stored in message class DMC_AP: MWB: AP specific messages.
It is part of development package CNV_DMCM in software component CA-LT. This development package consists of objects that can be grouped under "Data Mapping and Conversion: Maintenance".
It is part of development package CNV_DMCM in software component CA-LT. This development package consists of objects that can be grouped under "Data Mapping and Conversion: Maintenance".
Message Nr ▲ | Message Text |
---|---|
000 | Remote service destination is not available |
001 | Semantic descriptor of field &1 (structure &2) has been removed |
002 | &1 needs to be synchronized before action can be executed |
003 | Leading field information of semantic descriptor successfully replaced |
004 | The service connection type must be provided |
005 | Field can contain only alphanumeric values |
006 | Rule missing for structure &1 |
007 | System and Mapping Type need to be provided |
008 | Table &1 is not available; ATTENTION: switch to local migration tables |
009 | Table &1 and &2 are empty |
010 | Start of messages related to extended error handling |
011 | At least one of the processes started for record &1 is still running |
012 | End of Messages related to Extended Error Handling |
013 | &1 messages sent: &1 successful, &2 errors and &3 were in process |
014 | Table &1 and &2 have different structures |
015 | &1 is locked; screen will be opened in display mode |
016 | project &1 not accessible |
017 | Not all structures have been maintained in View Modeler and Rule Modeler |
018 | There is no subproject with same migration object to copy View Modeling |
020 | Messages 20-40 are reserved for field mapping |
021 | Reference field &1 does not have a rule call |
022 | &1 is locked; maintenance of attributes not allowed |
023 | Duplicates have been found and also deleted; review remaining entries |
024 | &1 does already exist in &2 |
025 | Field length and length of the semantic descriptor are deviating |
026 | Migration Scenario &1 does not yet exist |
027 | Exporting parameters and certain importing parameters cannot be deleted |
028 | Precalculation is not possible for reading type 'INDX-Cluster' |
029 | This function is not available at present |
030 | Sem. descr.s with single-usage-attribute can not be splitted |
031 | Semantic Descriptor does not exist on database |
032 | Data Preparation is only valid on Migration Object level |
033 | The &1 does not exist |
034 | Specify &1 identifier |
035 | Different data types between receiver field and semantic descriptor |
040 | Messages 20-40 are reserved for field mapping |
041 | Proxy interface might not be available |
042 | Parameter &1: &2 is not a valid value for codelist &3 |
043 | The new semantic descriptor &1 has been assigned to the field |
044 | Maintain description |
045 | Please map reference field with sender field or maintain fixed value &1 |
046 | Maintenance of &1 is not possible for this receiver field |
047 | Business object &1 not known |
048 | Node &1 of business object &2 not known |
049 | Service Interface &1 does not exist |
050 | Rule Modeling for field is incomplete; action not permitted |
051 | No suitable values have been found |
052 | Error saving assigment of a semantic descriptor |
053 | Data type of semantic descriptor has been adapted |
054 | Usage of semantic descriptor has been deleted due to changed data type |
055 | &1 is invalid for &2; please use F4 help |
056 | Maintain description of variant |
057 | Rule set element is already in use; change will affect other mig.objects |
058 | No subtype defined for sender connection type |
059 | No subtype defined for receiver connection type |
060 | Query &1 of node &2 of business object &3 not known |
061 | A semantic descriptor hasn't been assigned to this field yet |
062 | Template does not yet exist for additions of semantic descriptor |
063 | Please place cursor on importing parameter |
064 | Search field &1 not valid for query &2 |
065 | The specified selections are not valid for query &1 |
066 | Code list &1 does not exist |
067 | Semantic Descriptor cannot be assigned (invalid data type/field length) |
070 | Logical port & to KTP document host is not available |
071 | Sem. Descr. does not provide Business Object, Node and Query Information |