map is creating additional entries
Madhu asked 6 years ago
Hi,
I have a Map which imports Excel data into CM20100 table with transaction header grouping on Date, Desc, ref columns and key column Date, Desc, Ref and amt.
When I run this map, its inserting additional entry with the Home account debit and credit lines.For Ex: below is my excel source
After execution the map, its creating 2 entries as
DATE
REF
TRANS #
Acct
DESC
AMOUNT
11/3/2016
Claims
2
22200.0000.HOME
Misc
100.42
11/3/2016
Claims
2
11100.0000.HOME
Misc
-100.42
1)
DATE
REF
Acct
DESC
AMOUNT
11/3/2016
Claims
22200.0000.HOME
Misc
100.42
11/3/2016
Claims
11100.0000.HOME
Misc
-100.42
2)
DATE
REF
Acct
DESC
AMOUNT
11/3/2016
Claims
11100.0000.HOME
Misc
100.42
11/3/2016
Claims
11100.0000.HOME
Misc
-100.42
Here second entry is not required, this additional second entry started appearing from this month onwards. I am not sure if someone changed the map settings.
I tried to import the file by removing the amount column from key fields but got a error message saying creditamount<>Debitamount.
here is the map settings, it uses Excel 2007 source.
Create Transaction header node mapping
there is no change in the source file structure, if I remove the debit lines then its not creating additional entry but our source contains debit and credit lines for each transaction. any help will be appreciated.
thanks,
I have a Map which imports Excel data into CM20100 table with transaction header grouping on Date, Desc, ref columns and key column Date, Desc, Ref and amt.
When I run this map, its inserting additional entry with the Home account debit and credit lines.For Ex: below is my excel source
After execution the map, its creating 2 entries as
DATE
REF
TRANS #
Acct
DESC
AMOUNT
11/3/2016
Claims
2
22200.0000.HOME
Misc
100.42
11/3/2016
Claims
2
11100.0000.HOME
Misc
-100.42
1)
DATE
REF
Acct
DESC
AMOUNT
11/3/2016
Claims
22200.0000.HOME
Misc
100.42
11/3/2016
Claims
11100.0000.HOME
Misc
-100.42
2)
DATE
REF
Acct
DESC
AMOUNT
11/3/2016
Claims
11100.0000.HOME
Misc
100.42
11/3/2016
Claims
11100.0000.HOME
Misc
-100.42
Here second entry is not required, this additional second entry started appearing from this month onwards. I am not sure if someone changed the map settings.
I tried to import the file by removing the amount column from key fields but got a error message saying creditamount<>Debitamount.
here is the map settings, it uses Excel 2007 source.
Create Transaction header node mapping
there is no change in the source file structure, if I remove the debit lines then its not creating additional entry but our source contains debit and credit lines for each transaction. any help will be appreciated.
thanks,
I’m a little fuzzy on what your source and destination are (since pictures don’t work in the forums). But the first thing I’d always do when using GP as your destination is to switch to output to Dynamics GP – File.
Examine the XML output. Do you see the number of lines in the output that you expect to see from your source?
If not, then you’d want to tackle it from that side.
However if the XML contains the lines you expect, then it is logic within the eConnect proc doing this. If so, then you’d want to talk to Microsoft to determine why this is happening.
Thanks for the response. My map source is excel and destination is Dynamics GP. As you suggested I changed the destination to Dynamics GP – Files and provided the destination path then executed the map. it created 2 xml files with 2 different transaction numbers, my source has one transaction with 2 lines (one debit line and one credit line) and I expected to see only one file with single transaction. I am not sure what went wrong here, it working fine till last Monday (10/31), seems someone changed the map settings. Is there a change history maintained for map setting changes? I tried with different grouping options but none seems to be working.
No, we don’t keep a change history although that was talked about as a feature with SC 2016 but I don’t see that it happened.
But if you expected one document with two lines and got two documents with one line each, that means that your Key Fields selected and the “Group on” fields that you selected in the header are different.
99% of the time, those should always be the same on “header” documents.
The other possibility is that your data changed and what was a good field to group on before maybe isn’t now.
thanks for your time and help. I think I should understand how the key fields, grouping and maps work. I have user manual which talks about the how to use the application but not about how key fields, grouping works. It will be of great help if you can share or let me know where to find documents about how these things work.