Thanks for your reply. I tried but got an error connection failed. For SERVER, do I need to give path to the database?
Do I need to change Locale Identifier? if yes how would I get that?
The server is just the name of your SQL Server. The syntax was copied from a TK article, so I only edited the server, user ID, password and database fields.
I had problem with my userID, I used "sa" at this point just to check if I can connect and I did. I can see my columns. Thanks for the solution.
This integration is for expense invoices and I am giving Amount as Purchases and the Distribution account for debit. Do I need to give the credit amount and account also? I kept it at default but it did not take it from Vendor default.
Create 2 sources based on the one sp. The first will be the header, grouping in the invoice#,voucher# or whatever field that will determine a unique number. The second source will be all the fields.
In the Distribution section of the integration, link the account number and the debit to the amount. Leave the credit as "use default" and then click on the options tab and make sure record source is "default non-imported" and then the correct source.
This will then update the AP Control Account from the vendor card and you won't need to import it.
I had created two sources and did the way you told for credit account. It did work and took AP control account from Vendor Card. but it just applies first debit amount to credit as I have only debit transaction amount and not invoice total.
Let me give you some information about my source file.
My source has same invoice# for all the transactions for one Vendor. it groups and totals the transactions by GL account. We might have to change our stored procedure to give invoice total.
In integration I kept Voucher Number as default. When I run integration it assigns different voucher number for each transaction though my document number is same for all transctions. Do I need to give voucher number in integration?
I tried to use same source field as Document number, as we have done in one integration, used same source field for both but it failed with "already exists error" after first transaction.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.