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