Skip to content
+1-888-319-3663

COMMUNITY FORUM

I am trying to Insert a Batch but I keep getting a error with and existing ACTNUMST it says it does not exist

Adrian asked 6 years ago
 
Log Name:      eConnect
Source:        Microsoft.Dynamics.GP.eConnect14
Date:          4/13/2016 10:26:14 AM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Action:
Service Create
 
Current User Name:
 
 
Input parameters:
 
Exception type:
Microsoft.Dynamics.GP.eConnect.eConnectException
 
Exception message:
Sql procedure error codes returned: 
 
Error Number = 679  Stored Procedure= taGLTransactionLineInsert  Error Description = The Account Number (ACTNUMST) does not exist in the Account Index Master Table
Node Identifier Parameters: taGLTransactionLineInsert
BACHNUMB = CON20160413102614
JRNENTRY = 126981
CRDTAMNT = 0
DEBITAMT = 223.7
Related Error Code Parameters for Node : taGLTransactionLineInsert
ACTNUMST = 90-01-900-828015
 
 
<taGLTransactionLineInsert>
  <UpdateIfExists>1</UpdateIfExists>
  <ACTNUMST>90-01-900-828015</ACTNUMST>
  <CRDTAMNT>0</CRDTAMNT>
  <DEBITAMT>223.7</DEBITAMT>
  <DSCRIPTN>JBeckn-5291-CDW DIRECT LLC</DSCRIPTN>
  <JRNENTRY>126981</JRNENTRY>
  <BACHNUMB>CON20160413102614</BACHNUMB>
</taGLTransactionLineInsert>
 
 
Stack Trace:
   at Microsoft.Dynamics.GP.eConnect.EntityMessageProcessor.ExecuteSqlCommands(XElement transactionNode, EntityMessage message)
   at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessMessageImport(EntityMessage message)
   at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction)
   at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateEntity(String connectionString, String sXML)
   at Microsoft.Dynamics.GP.eConnect.Service.CreateEntity(String ConnectionString, String sXML)
Exception type:
Microsoft.Dynamics.GP.eConnect.eConnectException
 
Exception message:
Error Number = 679 Stored Procedure taGLTransactionLineInsert  Error Description = The Account Number (ACTNUMST) does not exist in the Account Index Master Table  
 
 
 
Stack Trace:
 
 
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft.Dynamics.GP.eConnect14″ />
    <EventID Qualifiers=”0″>0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2016-04-13T14:26:14.000000000Z” />
    <EventRecordID>6190</EventRecordID>
    <Channel>eConnect</Channel>
    <Computer>clw-gp-ts1.jtwalker.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Action:
Service Create
 
Current User Name:
 
 
Input parameters:
 
Exception type:
Microsoft.Dynamics.GP.eConnect.eConnectException
 
Exception message:
Sql procedure error codes returned: 
 
Error Number = 679  Stored Procedure= taGLTransactionLineInsert  Error Description = The Account Number (ACTNUMST) does not exist in the Account Index Master Table
Node Identifier Parameters: taGLTransactionLineInsert
BACHNUMB = CON20160413102614
JRNENTRY = 126981
CRDTAMNT = 0
DEBITAMT = 223.7
Related Error Code Parameters for Node : taGLTransactionLineInsert
ACTNUMST = 90-01-900-828015
 
 
&lt;taGLTransactionLineInsert&gt;
  &lt;UpdateIfExists&gt;1&lt;/UpdateIfExists&gt;
  &lt;ACTNUMST&gt;90-01-900-828015&lt;/ACTNUMST&gt;
  &lt;CRDTAMNT&gt;0&lt;/CRDTAMNT&gt;
  &lt;DEBITAMT&gt;223.7&lt;/DEBITAMT&gt;
  &lt;DSCRIPTN&gt;JBeckn-5291-CDW DIRECT LLC&lt;/DSCRIPTN&gt;
  &lt;JRNENTRY&gt;126981&lt;/JRNENTRY&gt;
  &lt;BACHNUMB&gt;CON20160413102614&lt;/BACHNUMB&gt;
&lt;/taGLTransactionLineInsert&gt;
 
 
Stack Trace:
   at Microsoft.Dynamics.GP.eConnect.EntityMessageProcessor.ExecuteSqlCommands(XElement transactionNode, EntityMessage message)
   at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessMessageImport(EntityMessage message)
   at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction)
   at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateEntity(String connectionString, String sXML)
   at Microsoft.Dynamics.GP.eConnect.Service.CreateEntity(String ConnectionString, String sXML)
Exception type:
Microsoft.Dynamics.GP.eConnect.eConnectException
 
Exception message:
Error Number = 679 Stored Procedure taGLTransactionLineInsert  Error Description = The Account Number (ACTNUMST) does not exist in the Account Index Master Table  
 
 
 
Stack Trace:
 
</Data>
  </EventData>
</Event>
 
I run the queries below
 
Select * from dbo.GL00105
where actnumbr_4=828015
returns 
 
 
 
ACTINDX ACTNUMBR_1 ACTNUMBR_2 ACTNUMBR_3 ACTNUMBR_4 ACTNUMBR_5 ACTNUMBR_6 ACTNUMBR_7 ACTNUMBR_8 ACTNUMBR_9 ACTNUMBR_10 ACTNUMST DEX_ROW_ID
288 90 01 900 828015 90-01-900-828015 290
 
 
 
Select * from dbo.GL00100
where actnumbr_4=828015
returns 
 
ACTINDX ACTNUMBR_1 ACTNUMBR_2 ACTNUMBR_3 ACTNUMBR_4 ACTNUMBR_5 ACTNUMBR_6 ACTNUMBR_7 ACTNUMBR_8 ACTNUMBR_9 ACTNUMBR_10 ACTALIAS MNACSGMT ACCTTYPE ACTDESCR PSTNGTYP ACCATNUM ACTIVE TPCLBLNC DECPLACS FXDORVAR BALFRCLC DSPLKUPS CNVRMTHD HSTRCLRT NOTEINDX CREATDDT MODIFDT USERDEF1 USERDEF2 PostSlsIn PostIvIn PostPurchIn PostPRIn ADJINFL INFLAREV INFLAEQU ACCTENTR USRDEFS1 USRDEFS2 Clear_Balance DEX_ROW_TS DEX_ROW_ID
288 90 01 900 828015 828015 1 JTW-CORP-ADMIN-COMPUTER MAINTENANCE 1 76 1 0 0 0 0 0xFFFFFFFF 1 0 14749 2012-03-01 2012-03-01 1 1 1 1 0 0 0 1 0001-9001900-828015-0000 0 2015-10-29 148
 
Answers
Patrick Roth Staff answered 6 years ago
Well, looking at the error it is clear that eConnect (not smartconnect) does not believe that account
90-01-900-828015
does not exist in the GL00105 table.
I do notice that you chose an interesting way to look in the GL00105 for the record however – querying for the segment4.  Possibly just quicker to do?
 
select * from GL00105 where ACTNUMST = ’90-01-900-828015′
But I’m going to assume that is going to show as well.
Assuming so, then the only explanation that I can see is that your destination company or destination server is incorrect.
Or more common, you have multiple destination companies chosen and so the one going to the correct company works fine but the second company is the one that fails because it doesn’t have that account.
 
Adrian answered 6 years ago
Thanks Patrick

If you would like to submit an answer or comment, please sign in to the eOne portal.