ICA02 - ICA Matching Engine Message Class
The following messages are stored in message class ICA02: ICA Matching Engine Message Class.
It is part of development package FIN_ICA_MATCH in software component FIN-CS-ICR. This development package consists of objects that can be grouped under "Inter-Company Matching Engine".
It is part of development package FIN_ICA_MATCH in software component FIN-CS-ICR. This development package consists of objects that can be grouped under "Inter-Company Matching Engine".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | Method &1 does not exist. |
002 | Getting the next available document number failed (error code = &1). |
003 | Searching by the field & is not supported. |
004 | Method &1 already exists in the system. Importing will overwrite it. |
005 | The data source & does not exist. |
006 | Matching assignment number & does not exist. |
007 | Mandatory filter field "&1" is missing or inconsistent. |
008 | The unit or one of its partner units is locked in a background job for &. |
009 | Data source is missing in method &. |
010 | Field "&1" is not allowed in a filtering string. |
011 | CDS view &1 on data source &2 is inactive or nonexistent. Check in ADT. |
012 | An error occurred when saving the matching document header. |
013 | An error occurred when saving the assignment number. |
014 | An error occurred when posting the matching journal entries. |
015 | Data source "&1" is invalid. |
016 | The given data is inconsistent with the structure of data source "&1". |
017 | Timestamp &1 in one row is later than the data release time &2. |
018 | Fiscal year variant is missing. |
019 | Error in acquiring document numbers. |
020 | Error in acquiring assignment numbers. |
021 | Rule &1 does not exist in the method &2. |
022 | Field &1 does not exist in the CDS view &2. |
023 | Function &1 is not allowed for the field &2. |
024 | Comparator &1 is not allowed for the field &2. |
025 | Parameter &1 does not match the parameter pattern &2. |
026 | Parameter &1 must be a number. |
027 | Parameter &1 must be a character or a text string. |
028 | Assignment number & does not exist. |
029 | Matching document &1/&2 has been assigned to the assignment number &3. |
030 | Matching document &1/&2 cannot be found for method &3. |
031 | A second data source is required. No valid one available. |
032 | The second data source & is invalid. |
033 | Method &1 doesn't exist anymore and will be recorded as deleted. |
034 | The comment & does not exist. |
035 | A comment is required for reason code &. |
036 | Reason code & does not exist. |
037 | Processing status & is not allowed. |
038 | Automatic adjustment class is not maintained for the reason code &. |
039 | Output data is inconsistent with the defined structure &. |
040 | An error occurred during automatic adjustment posting. |
041 | An error occurred when updating the processing status. |
042 | Changing configurations (non-master data) only allowed in source system. |
043 | The assignment has not been unassigned. Re-matching is not necessary. |
044 | Cannot save your changes. Data has been changed by others, refresh first. |
045 | Matching expression incomplete. |
046 | Select either data slice as a basis for item grouping. |
047 | Item cannot be assigned manually. Run auto-match first to roll in data. |
048 | Processed by & in a batch. |
049 | The POST method is not defined in the automatic adjustment class &. |
050 | The selected assignment needs to have the processing status "Assigned". |
051 | The class & does not exist. |
052 | Cannot get current fiscal year/period. Check FYV setting in data source. |
053 | Cannot run matching in a future fiscal year period. |
054 | Specify a value for the mandatory field &1. |
055 | Value of mandatory field &1 inconsistent between header and line items. |
056 | The workflow is in process. |
057 | Triggering workflow failed. Try later. |
058 | The workflow scenario definition & does not exist. |
059 | Transporting the changes is forbidden by Solution Builder. |
060 | The reason codes predefined by SAP cannot be changed. |
061 | Use an ID not starting with S, Q, R, X, P, Y, 5, 6, 7, 8, 9, or 0. |
062 | Invalid attribute field in row &1 of filter &2. Check method data source. |
063 | Fill in attribute field for DIFFERENCE dimension in row &1 of filter &2. |
064 | Reconciliation case &1 doesn't exist. |
065 | CDS view & not found. |
066 | CDS view name is required. |
067 | When leading unit field is empty, no value allowed for other unit fields. |
068 | Partner unit field is required if the leading unit field is specified. |
069 | Superordinate fields must be consistent; either empty, or with values. |
070 | CDS view & contains no fields. |
071 | Field &1 of CDS view &2 not in database table ICADOCM. |
072 | Error in field &. Clear values and hit Enter key to get valid values. |
073 | Workflow scenario & does not exist. |
074 | Class & does not exist. |
075 | Enter an adjustment class that inherits from the superclass &. |
076 | Output structure invalid. |
077 | Transporting the changes is not allowed by Solution Builder. |
078 | Customization is not allowed in this client. |
079 | Method &1 is stored as master data and cannot be transported. |
080 | The hierarchy & is invalid. |
081 | Cannot assign reason &2 to method &1/rule &3. Check reason code settings. |
082 | Deletion not allowed. The object is not stored as master data. |
083 | File doesn't exist. |
084 | Enter a valid method. |
085 | Specify a file name for the template. |
086 | Specify a data source. |
087 | Select only the rows with same partner entity for the assignment. |
088 | No data is loaded. |
089 | Data source in the template doesn't match the one you selected. |
090 | Use the correct template and keep the first two rows unchanged. |
091 | The assigned partner entities are different from the selected ones. |
092 | Reconciliation case &1 is stored as master data and can't be transported. |
093 | No authorization for &1: &2 |
094 | Select a method with the same storage type (master/configuration data). |
095 | No data found for the selection criteria. |
096 | You are not authorized to execute the matching method &1. |
097 | You are not authorized to post data for the matching method &1. |
098 | You are not authorized to transport the matching method &1. |
099 | &1 cannot be reloaded. |
100 | You don't have permission to transport the reconciliation case &1. |
101 | Recon. case &1 doesn't exist anymore and will be recorded as deleted. |
102 | The data source name &1 predefined by SAP cannot be changed. |
103 | Value &1 of field &2 is not in data range of the matching method. |
104 | You are not authorized to post data for unit &1. |
105 | Data source &1 is incomplete or was deleted. |
106 | SQL syntax error in filter string. |
110 | The document templates predefined by SAP cannot be changed. |
111 | Same value (&2) not allowed in the filters for &1. |
112 | Field & doesn't exist in the data source of the matching method. |
113 | Method &1 in the &2 does not exist in the header file ICA_METHOD.xml. |
114 | The ZIP file must contain the correct files that were exported. |
115 | Method & is not master data. Changes only allowed in source system. |
116 | The method & already exists. |
117 | The rule already exists. |
118 | Document &1 &2 &3 posted. |
119 | The assignment only contains one-side data. Var. adjust. not applicable. |
120 | No variance. Adjustment posting is not needed. |
121 | No document template found. Check template assignment for leading unit. |
123 | No authorization for &. |
124 | Leading unit field cannot be same with its superordinate field. |
125 | Assign a reason code with no follow-ups required if match type is GM/EM. |
126 | No valid leading units found. Matching is canceled. |
127 | & has a match type GM or EM. Only reason code with no follow-ups allowed. |
128 | Import failed. &1 is not stored as master data. |
129 | Save failed. The current system doesn't allow configuration-type changes. |
130 | Items cannot be added to an assignment that has a different leading unit. |
131 | Delete failed. Matching documents for this matching method already exist. |
132 | Only alphanumeric characters and underscores are allowed for the ID. |
133 | Cannot post adjustment documents due to different transaction currencies. |
134 | Cannot process the assignment. It was unassigned by others. |
135 | Add an expression row with field &1 as it's used in CONVERT_CURRENCY. |
136 | Method ID does not exist. |
137 | Field name given is incorrect. |
138 | Success. The following documents are created: &1 to &2. |
139 | Generating matching items failed. Try again later. |
140 | Method &1 and data source &2 don't match. |
141 | Update failed. |
142 | Reversed with the reversal document &1 by &2 at &3. |
143 | Cleared with the clearing document &1 by &2 at &3. |
144 | Clearing was reset by &1 at &2. |
145 | Unit entity CDS view is required if a leading unit field is not empty. |
146 | Leading unit field and the unit authorization object must be consistent. |
147 | Unit CDS view must contain leading unit and its superordinate field. |
148 | &1 is already in the training process. Please don't execute again. |
149 | &1/&2 is already in the inference process. Please don't execute again. |
151 | Success. Batch UUID: &1; Execution ID: &2. |
152 | No data found. |
153 | Field &1 cannot be empty. |
154 | Batch UUID &1 does not exist. |
155 | Data processing terminated. |
156 | Only for inference jobs with status Sending/Sending Completed/Initiated. |
157 | Cannot get the pipeline status. Execution ID is empty. |
158 | Enter a data source. |
159 | Leading unit field is consistent. |
160 | Leading unit field is inconsistent between the two data sources. |
161 | Leading unit superordinate field is consistent. |
162 | Leading unit superordinate field inconsistent between two data sources. |
163 | Partner unit field is consistent. |
164 | Partner unit field is inconsistent between the two data sources. |
165 | Partner unit superordinate field is consistent. |
166 | Partner unit superordinate field inconsistent between two data sources. |
167 | Unit entity CDS view is consistent. |
168 | Unit entity CDS view is inconsistent between the two data sources. |
169 | Fields (&1) of data source &2 not found in data source &3. |
171 | Matching expression field &1 exists in data source &2. |
172 | Matching Expression field &1 doesn't exist in data source &2. |
173 | Method filter field &1 exists in data source &2. |
174 | Method filter field &1 doesn't exist in data source &2. |
175 | Reconciliation filter field &1 exists in data source &2. |
176 | Reconciliation filter field &1 doesn't exist in data source &2. |
177 | Reconciliation tolerance field &1 exists in data source &2. |
178 | Reconciliation tolerance field &1 doesn't exist in data source &2. |
179 | Your entry in the Change from Data Source field is invalid. |
180 | Your entry in the To field is invalid. |
181 | Consistency check failed. |
182 | Consistency check passed. |
183 | Data source is changed. |
184 | Data source change failed. |
185 | Machine learning initialization failed. |
186 | Only one matching method can be enabled for machine learning. |
187 | Machine learning only supports methods with the org. dimension company. |
188 | Method &1 is not enabled for machine learning. |
189 | Select a method. |
190 | Data sent successfully. |
191 | Failed sending data. |
192 | Target unit of measure is required for unit conversion. |
193 | Exchange rate type is required for currency conversion. |
194 | Reference date is required for currency conversion. |
195 | Target currency is required for currency conversion. |
196 | Unit entity CDS view must contain the field '&1'. |
198 | Cannot push inference data. Training model is not generated. |
199 | Use an ID not starting with "S". "S" is reserved for predefined objects. |
200 | Cannot edit or delete predefined objects with IDs starting with "S". |
202 | Select only the inference-type data rows with �ML Initiated� status. |
203 | Select a range of at least 3 periods. |
204 | Rule ID & already exists or is reserved. Specify a different rule ID. |
205 | The machine learning feature is not available in your current release. |
206 | Cannot delete. Matching method &1 has been assigned to recon. case &2. |
207 | Search help & is not an elementary search help. |
208 | Source field &1 for converted measure exists in data source &2. |
209 | Source field &1 for converted measure doesn't exist in data source &2. |
210 | Value &1 exceeds the maximum length for filter field &2. |
211 | Value of field &2 in row &1 is invalid. |
212 | Value of &2 in row &1 doesn't match data source settings. |
213 | Value &1 of field &2 in row &3 exceeds scope defined by entity CDS view. |
214 | Fill in at least one amount or quantity field in row &1. |
215 | Unit of measure is missing in field &1 for quantity field &2 in row &3. |
216 | Currency code is missing in field &1 for amount field &2 in row &3. |
217 | Value is missing for the mandatory filter field &1 in row &2. |
218 | Value is missing for leading unit field &1 in row &2. |
219 | Value is missing for partner unit field &1 in row &2. |
220 | Invalid value &1 for field &2 in row &3. |
221 | Invalid currency code &1 for field &2 in row &3. |
222 | Invalid unit of measure &1 for field &2 in row &3. |
223 | Invalid value &1 for FISCYEARPER in row &2. The format should be YYYYPPP. |
231 | Error in filter string: comment signs (--, /* and */) are not supported. |
232 | Error in filter string: keyword "SELECT" is not supported. |
233 | Connection successful. |