Understand why Data is Rejected
Rejected data corresponds to a row that doesn't match any of the mapping rules.
For rejected data, the log indicates the mapping, and the filters in this mapping, that rejected the data. As soon as one mapping can't map the data, the process stops. Other mappings are not processed.
A specific type of rejected data is also displayed in the traceability log: some rows are mapped correctly but the data isn't uploaded, because the format of the generated data is not compliant. In this case, the Message column provides further information about the issue.
The example below illustrates how rejected data can be traced from source data to the mapping that rejected this data.
Source Data
|
I_FSItem |
I_SubItem |
I_SubItemCategory |
I_Version |
I_PartnerConsolidationUnit |
I_Amount |
I_AmountInLocalCurrency |
|---|---|---|---|---|---|---|
|
121910 |
900 |
Y1 |
Y10 |
S004 |
400 |
EUR |
|
121920 |
900 |
Y1 |
Y10 |
S004 |
500 |
EUR |
|
141200 |
999 |
Y1 |
Y10 |
S004 |
600 |
EUR |
|
314000 |
955 |
Y1 |
Y10 |
S005 |
200 |
EUR |
Mapping Definition
|
I |
||
|---|---|---|
|
Level |
I_FSItem |
FinancialStatementItem |
|
0 |
121910 |
"121900" |
|
0 |
121920 |
"121900" |
|
0 |
141200 |
"141200" |
|
0 |
314000 |
"314000" |
|
I |
I |
|||
|---|---|---|---|---|
|
Level |
I_SubItem |
I_SubItemCategory |
Subitem |
SubitemCategory |
|
0 |
900 |
Y1 |
"900" |
"1" |
|
0 |
950 |
Y1 |
"950" |
"1" |
|
0 |
955 |
Y1 |
"955" |
"1" |
|
I |
I |
I |
I |
||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Level |
I_Amount |
I_Version |
I_PartnerConsolidationUnit |
I_AmountInLocalCurrency |
AmountInLocalCurrency |
PartnerConsolidationUnit |
LocalCurrency |
FiscalYear |
FiscalPeriod |
ConsolidationVersion |
ConsolidationUnit |
|
0 |
Y10 |
S004 |
EUR |
[I_Amount] |
"S004" |
"EUR" |
"2021" |
"012" |
"Y10" |
"S000" |
|
|
0 |
Y10 |
S005 |
EUR |
[I_Amount] |
"S005" |
"EURO" |
"2021" |
"012" |
"Y10" |
"S000" |
Traceability Log
|
Input Row ID |
i_fsitem |
i_subitem |
i_subitemcategory |
i_version |
i_partnerconsolidationunit |
i_amount |
i_amountinlocalcurrency |
Rule Path |
Mapping Message |
Amount in Local Currency (Detail) |
Item Type |
Row Number |
Consolidation Unit |
Financial Statement Item |
Subitem |
Partner Unit |
Subitem Category |
Uploaded Amount in Local Currency (Total) |
Import Message |
||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
FSItems |
SubItems |
Amounts |
|||||||||||||||||||
|
4 |
314000 |
955 |
Y1 |
Y10 |
S005 |
200 |
EUR |
R6 |
R5 |
R4 |
Column localcurrency accepts values with 3 characters. |
200.00 |
S000 |
3140000 |
955 |
S005 |
1 |
200.000 |
|||
|
5 |
141200 |
999 |
Y1 |
Y10 |
S004 |
600 |
EUR |
i_subitem |
|||||||||||||
-
As indicated in the Mapping Message column of the traceability log, the local currency has been defined in the mapping file in a four digit format ("EURO"), whereas the ACDOCU table requires a three digit format ("EUR").
-
As indicated in the Rule Path columns of the traceability log, the mapping process stops at the subItems mapping I_subitem column, because subitem "999" exists in the source file, but subitem "950" which is specified in the SubItems tab of the mapping file does not.