IFME_ENGINE - Incoming files - Engine
The following messages are stored in message class IFME_ENGINE: Incoming files - Engine.
It is part of development package ID-IFME-ENGINE in software component CA-GTF-CSC-DME. This development package consists of objects that can be grouped under "Incoming Files Mapping Engine".
It is part of development package ID-IFME-ENGINE in software component CA-GTF-CSC-DME. This development package consists of objects that can be grouped under "Incoming Files Mapping Engine".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Raw data was not supplied |
| 002 | Parser instance is not initialized |
| 003 | Raw data instance is not initialized |
| 004 | Inconsistent tree; Missing field node |
| 005 | Block is not initialized (&1) |
| 006 | Inconsistent tree; Missing field group node |
| 007 | Expected value in content starting value field (&1/&2) |
| 008 | Node is not initialized |
| 009 | Block content is not initialized (&1) |
| 010 | Length is not setup (&1) |
| 011 | Regular expression &1 returned no results |
| 012 | Delimiter not found (&1) |
| 014 | Processing started for format &1/&2. |
| 015 | There is a missing next mandatory node &1 (&2) |
| 016 | Parsing content based on starting value &1 and ending value &2 |
| 017 | Parsing content based on starting value &1 only |
| 018 | Parsing value with max length &1 |
| 019 | Parsing content based on delimiter &1 |
| 021 | Replacement value expected (&1) |
| 022 | Parsing was unsuccessful. Cannot continue to mapping phase |
| 023 | Mapper instance is not initialized |
| 024 | Error creating target structure |
| 025 | Field node expected (&1) |
| 026 | Parsing failed for node &1 (&2) |
| 027 | File was not parsed |
| 028 | Number of alternatives for node &2 (&3): &1 |
| 030 | Alternative &1 for node &2 (&3) |
| 031 | Alternative &1 chosen for node &2 (&3) |
| 032 | Alternative &1 failed for node &2 (&3) |
| 034 | Domain validation failed. |
| 035 | Unable to parse conditions for node &1 |
| 036 | Inconsistent tree (node: &1) |
| 037 | Invalid regular expression &1 |
| 038 | Node &1 not found |
| 040 | Currency not determined for field &1 (&2) currency field:&3 |
| 043 | Error when processing output value adjustment for node &1 |
| 044 | Not supported decimal format &1 for node &2 |
| 045 | Invalid decimal count in &1. Parsed &2, format requires &3. |
| 046 | Preparing to map into output structure &1 |
| 047 | No fields suitable for mapping were found |
| 050 | An internal error occurred during the engine run |
| 052 | Block for node &1 (&2) is inactive, will not be included in mapping |
| 053 | New line removed from &3 for node &1 (&2) |
| 055 | &1 (&2) is a valid candidate for mapping '&3' |
| 056 | Skipping subtree for node &1 (&2) |
| 059 | No more alternatives are available to try &1 (&2) |
| 060 | Parsing content based on ending value &1 only |
| 061 | Mandatory group is empty for node &1 (&2) |
| 062 | Group &1 has incorrect number of occurrences (Expected:&2/Actual:&3) |
| 063 | Node &1 must contain at lease one occurrence |
| 064 | Object reference &1 for node &2 is not supported |
| 065 | Operation &1 chosen for node &2 |
| 066 | Constant value for a node &1 was not derived |
| 067 | Constant &1 from file is being parsed for node &2 (&3) |
| 068 | Too many values are available for node &1 (&2) |
| 069 | Expected constant &1 not found in the file |
| 070 | Node &1 has no assigned currency field |
| 071 | Missing record tag for node &1/&2 |
| 072 | Parsing record &1 (&2) |
| 073 | Engine run failed. |
| 074 | Parsing content based on record code &1 |
| 075 | &1 is not a valid ISO currency (check contents of table TCURC). |
| 076 | Parsed &1 from node &2 (&3). |
| 078 | Group &2 (&1) requires one subnode |
| 079 | Mandatory node &2 (&1) is missing |
| 080 | Inconsistent tree; Missing record node |
| 081 | Inconsistent tree; Missing record group node |
| 082 | Node of type record expected. |
| 083 | Inconsistent tree; Variant &1 |
| 084 | Parsing record group &1 (&2) |
| 085 | An unexpected situation occurred. This is a developer error. Reason: &1 |
| 086 | Parsing field group &1 (&2) |
| 087 | Not supported node &1 (&2) for length operation |
| 088 | Endless iteration of processing &1 (&2) content: &3 |
| 089 | There is some content which would be skipped (&2,&1) |
| 090 | Node &1 (&2) has incorrect length, content: &3 |
| 091 | Node &1 (&2) has no type assigned |
| 092 | Unable to interpret &1 as date |
| 093 | Group &2 (&1) contains too many subnodes. Expected only one subnode |
| 094 | Unable to interpret &1 as time |
| 095 | Unable to interpret &1 as a number |
| 096 | Unable to interpret &1 as a currency |
| 097 | Unknown data type &1 |
| 098 | Fixed length field expected &1 (&2) |
| 099 | Fixed length field not expected &1 (&2) |
| 100 | Object reference is missing for a field &1 (&2) |
| 101 | Field or Record expected. &1 (&2) |
| 102 | Parent node is missing &1 (&2) |
| 103 | Node &1(&2) has insufficient length (amount: &3 decimals: &4) |
| 104 | Mandatory node &1 (&2) has no content |
| 105 | Unable to parse delimiter &1 (&2) |
| 107 | Delimited block has no content &1 (&2) |
| 108 | Alternative failed, remaining content exists: &1 |
| 109 | Node has incorrect value &1 (&2) with content:&3 |
| 110 | Too many delimited values for record &1 (&2) content:&3 |
| 111 | &1 (&2) is a candidate for mapping result of &3. |
| 112 | Could not parse node &1 (&2) |
| 113 | Missing delimiter after record tag &1 |
| 114 | Enumeration value &1 parsed for node &2 (&3) |
| 115 | Record is expected &1 (&2) |
| 116 | Mandatory node has not met condition for node &1 (&2) |
| 117 | Variable node &1 (&2) has no content |
| 118 | An attempt was made to map &1 into &2, which does not exist on &3. |
| 119 | Following mandatory node is missing |
| 120 | &2-&3 = &1. |
| 121 | Beginning new line of &1. |
| 122 | [Append &1] |
| 123 | Cannot locate structure & |
| 124 | Cannot locate structure &1 field &2 |
| 125 | Delimiter not defined |
| 126 | Separator not defined |
| 127 | Parsing date with format &1. |
| 128 | Delimiter has not been derived for node & (&) |
| 129 | --[Action]--Append previously parsed values of &1-- |
| 130 | Missing column in source data |
| 131 | New line not defined |
| 132 | Initial content for node &1 (&2) |
| 133 | Preparing data structures for mapping |
| 134 | Created subtree for &1, iteration &2&3. |
| 135 | Starting next iteration of &1: &2. |
| 136 | &1&2&3&4 |
| 137 | Assigning to target structure: |
| 138 | Missing content for fixed delimited processing &1 (&2) |
| 139 | Invalid composition of a sub-tree &1 (&2) for CSV processing |
| 140 | Expecting group node &1 (&2) for CSV processing |
| 141 | Different record tag is expected &1 (&2) Tag: &3 Content: '&4' |
| 142 | Mandatory node is missing &2 (&1). Input &3 |
| 143 | Mapping plan: |
| 145 | CSV Parsing error; Expected value [&1] actual value [&2] |
| 146 | Inconsistent CSV file |
| 147 | &1 = &2 |
| 148 | Mapping process complete. |
| 149 | Begin iteration &1 of &2. |
| 150 | Expected CSV block &1 (&2) |
| 151 | Performing assignments |
| 152 | Currency value &1 is invalid or not defined in tcurx |
| 153 | No errors were detected during the run, but no data was mapped. |
| 154 | Record &1 (&2) is missing |
| 155 | No data received from parser. Skipping mapping phase. |
| 156 | Input data is empty. |
| 157 | Based on file contents, the line terminator is &1. |
| 158 | Based on format, fields should be separated by &1. |
| 159 | Filter does not exist |
| 160 | Record &1 (&2) is not relevant for upcomming tag [&3]/[&4] |
| 161 | Missing content for the mandatory node &1 (&2) |
| 162 | The input data is empty. CSV cannot be processed further. |
| 163 | Continuing with record &1 &2 |
| 164 | Variable &1 changed from &2 to &3 |
| 165 | Variable &1 unchanged (&2) |
| 166 | Value (&1) is incompatible with type of the structure field &2-&3 (&4) |
| 167 | Alternative skips nodes &1&2&3&4 |
| 168 | Parsing based on offset &1, length &2 |
| 169 | Value was truncated to output field length &1 |
| 170 | Error occurred when mapping to field &1 |