Microsoft Dynamics GP (Archived)

Problem with upload

(0) Share

Report

Posted on by rmalouin

Hi,

We have the following message with GP when we try to post JE via Smarconnect

7738 - taGLTransactionLineInsert - Input variable contains a duplicate Sequence Line Number (SQNCLINE) .

Does someone already see that?

Thanks

Richard

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Shyam Nath 505 on at

Like (0)

Report

SmartConnect ensures that all data created in GP is valid by applying all the business rules contained in GP with the use of eConnect.

As the error message rightly describe, the issues seems to be because of bad data. You might need to revisit the data and see the values passed to element "SQNCLINE" (Sequence line). If there are multiple lines for same Journal entry number, you need to pass different Sequence line number.

You can refer XML node for taGLTransactionLineInsert from msdn.microsoft.com/.../jj193354.aspx

It could also be because as it is not required field, if you havent passed any value, by default it might be going as zero and as I said if there are multiple lines for a single entry, the same error will popup.

Cheers,

Shyam.

Was this reply helpful? Yes No
rmalouin on at

Like (0)

Report

Thanks Shyam for you answer.

But do you know if we could have a limit with the number of lines that i can uploaded? Because the message we got also toll me that it looks like we have a duplicate with line 500. And i don't understand why especially line 500...

Regards,

Richard

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

There is a bug in the taGLTransactionLineInsert for eConnect. How sad after two years later I hit the exact same error. After decrypting the SQL stored procedure I discovered that Microsoft put logic in the sequence numbering that causes the sequence zero (your first line record) to automatically get reset to 500. This results in a duplicate sequence number when your integration exceeds 499 records.

Microsoft's logic:

if ( @I_vSQNCLINE = 0 )
begin
select @SQNCLINE = isnull(max(SQNCLINE),0) + 500 from GL10001 (nolock) where JRNENTRY = @I_vJRNENTRY
end
else
begin
select @SQNCLINE = @I_vSQNCLINE
end

Was this reply helpful? Yes No
Marc K 576 on at

Like (0)

Report

I don't think it is a bug. I think that 0 is a reserved value for SQNCLINE. You can supply 0 for all rows and eConnect will automatically allocate the sequence numbers for you. If you send in your own sequence numbers, then the minimum allowed value is 1.

Was this reply helpful? Yes No