eConnect payables transaction fails with invalid currency error

(0) Share

Report

Posted on by Brad Forgey

I am trying to write an app that imports payables entries into GP using eConnect. I keep getting the following error:

Sql procedure error codes returned:
Error Number = 761 Stored Procedure= taPMTransactionInsert Error Description = Invalid Currency, a Functional currency must be set up
Node Identifier Parameters: taPMTransactionInsert
BACHNUMB = 03052020-01P
VCHNUMWK = 00000000000070587
VENDORID = 190
DOCNUMBR = 109931014
DOCTYPE = 1
DOCDATE = 2/18/2020
Related Error Code Parameters for Node : taPMTransactionInsert
CURNCYID = USA

I've tried not sending the currency ID, passing Z-US$, passing blank, and padding the curency with spaces but get the same error.

He said the problem is probably something to do with the zeros for the functional indices. This is a production GP 2018 database and has been upgraded several times for over 20 years. Is there any way to fix this?

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (5)

Answers (2)

Suggested answer

Derek Albaugh on at

Like (1)

Report

Looking specifically at error number 761 for the taPMTransactionInsert procedure for eConnect, it appears that this error fires when the CURRNIDX is 0 (zero) or CURNCYID is blank:

if ((@CURRNIDX = 0) or (@I_vCURNCYID = ''))

begin

select @O_iErrorState = 761

I see you specifying CURNCYID as USA but don't see what you have the CURRNIDX value specified as. By default, in this procedure, the @CURRNIDX value is set to 0 (zero), so if you're not making a change to it in the eConnect code being passed through, then this error could definitely occur.

I would verify those two values and make sure CURRNIDX is not 0 (zero) and the CURNCYID value is not blank.

The only other thing I'd mention is, since CURNCYID is a character data type, make sure it also has the single quotes around it.

@I_vCURNCYID char(15) = '',

@CURRNIDX = 0,

Thanks

Was this reply helpful? Yes No
Brad Forgey 5 on at

Like (1)

Report

In MC40000 for all three databases (we have three companies) the functional currency is USA with a function index of 0. There is also a TWO database with Z-US$ and 1007. In DYNAMICS..MC40200 all currencies have a number except USA which is 0 (otherwise all the other values match Z-US$). Can we just change the USA entry in MC40000 and MC40200 to some number other than zero as long as it is unique in the table? Can we then just run the update in community.dynamics.com/.../update-currency-index-field-across-all-database to change the zeros to the new number?

Was this reply helpful? Yes No
Nicole Hellerud 1,712 on at

Like (1)

Report

Hey Brad-

Thank you for your post and update!

If the USA company is supposed to have a functional currency of Z-US$, then I'd consider changing the values to that vs. creating a new one that is unique as noted in the following line:

Can we just change the USA entry in MC40000 and MC40200 to some number other than zero as long as it is unique in the table?

I would not attempt this in production though without verifying it's data integrity in test first.

Hope this helps.

Let us know if you continue to have issues.

Wishing you the best day ahead!

Nicole Fiskum

Was this reply helpful? Yes No
Verified answer

Brad Forgey 5 on at

Like (1)

Report

Thanks for the help. We were able to use the above information to resolve the issue. We were using USA as a default currency which had an index of zero. We ran the script based on the article at community.dynamics.com/.../update-currency-index-field-across-all-database . I changed all CURNCYID fields from ‘USA’ to ‘Z-US$’ and also ran a similar script changing CURRNIDX fields from 0 to 1007. We also had to change the values for the functional and reporting currencies in MC40000.

Was this reply helpful? Yes No
Verified answer

Kevin Day 610 on at

Like (1)

Report

I was googling an issue I had and this one came up. Then I remembered the solution I had before. Might not be exactly the issue, but this one is bizzare so I figured I'd get it online.

I have an eConnect Journal Entry Integration.

All of my companies use Z-USD$ and that's it.

We have 75 companies.

In one company, the Journal Entry was integrating successfully, but was missing the Currency ID on the Transaction. Odd because number one, it is a required field on the Transaction and number two, I am literally hard coding it in eConnect

glH.CURNCYID = "Z-US$"

But nonetheless, it was coming in as blank when successful. Users go to post and it goes to batch recovery because it is missing a currency.

Now, we are on GP 18.2 and upgraded from GP 10.0 about 2 years ago. This was an issue in GP 10, figured they would have fixed this by now.

The Solution?

Add a Checkbook to the company. Any checkbook. No idea why, but I've now seen this several times and I can't quite remember if it applies to Subledger transactions (it might), but this just solved my issue. We have a company that is just a GL company, so no Customers or Vendors. So never needed a Checkbook. Except now we have one.

Was this reply helpful? Yes No

Join the conversation

Community site session details

eConnect payables transaction fails with invalid currency error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

eConnect payables transaction fails with invalid currency error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates