Acumatica和Avalara未能获得税收

Acumatica和Avalara未能获得税收,acumatica,avalara,Acumatica,Avalara,我们在Acumatica内部看到一个问题(见下面的版本),当我们试图从发货转向“准备发票”时。我们在安装salesdemo base acumatica时看到了这一点,因此我们知道它与我们的任何定制无关。有人有方向吗?我在谷歌上搜索过,但我并没有真正得到任何导致进展的线索 屏幕错误-无法从Avalara获取税款。检查跟踪以了解详细信息() 这是针灸的构造 Acumatica 2017 R2 构建17.210.0034 当我们测试avalara连接时,我们看到了这一点。与阿瓦拉拉的连接是成功的。该

我们在Acumatica内部看到一个问题(见下面的版本),当我们试图从发货转向“准备发票”时。我们在安装salesdemo base acumatica时看到了这一点,因此我们知道它与我们的任何定制无关。有人有方向吗?我在谷歌上搜索过,但我并没有真正得到任何导致进展的线索

屏幕错误-无法从Avalara获取税款。检查跟踪以了解详细信息()

这是针灸的构造 Acumatica 2017 R2 构建17.210.0034

当我们测试avalara连接时,我们看到了这一点。与阿瓦拉拉的连接是成功的。该服务的版本为19.2.0.39

这是下面的痕迹 错误:发送错误:无法从Avalara获取税款。检查跟踪以了解发送的详细信息 提高时间:2019年2月28日10:38:50下午屏幕:SO.30.20.00
细节: 2019年2月28日10:38:50下午错误: 发送错误:无法从Avalara获取税款。检查跟踪以了解详细信息

   at PX.Objects.AR.ARInvoiceEntry.CalculateAvalaraTax(ARInvoice invoice) 
   at PX.Objects.AR.ARInvoiceEntry.Persist() 
   at PX.Objects.SO.SOInvoiceEntry.Persist() 
   at PX.Data.PXSave`1.d__2.MoveNext() 
   at PX.Data.PXAction`1.d__31.MoveNext() 
   at PX.Data.PXAction`1.d__31.MoveNext() 
   at PX.Data.PXAction`1.PressImpl(Boolean internalCall, Boolean externalCall) 
   at PX.Data.PXAction`1.Press() 
   at PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(DateTime invoiceDate, PXResult`6 order, PXResultset`2 details, Customer customer, DocumentList`2 list) 
   at PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(DateTime invoiceDate, PXResult`6 order, Customer customer, DocumentList`2 list) 
   at PX.Objects.SO.SOShipmentEntry.InvoiceShipment(SOInvoiceEntry docgraph, SOShipment shiporder, DateTime invoiceDate, DocumentList`2 list) 
   at PX.Objects.SO.SOShipmentEntry.<>c__DisplayClass41_1.b__1() 
   at PX.Data.PXLongOperation.<>c__DisplayClass17_0.b__0() 
Error:  DocStatus is invalid for this operation.: Expected Saved|Posted    Send
Raised At: 2/28/2019 10:38:50 PM    Screen: SO.30.20.00     
   Details: 
2/28/2019 10:38:50 PM Error: 
DocStatus is invalid for this operation.: Expected Saved|Posted 

   at PX.Objects.AR.ARInvoiceEntry.LogMessages(BaseResult result) 
   at PX.Objects.AR.ARInvoiceEntry.CalculateAvalaraTax(ARInvoice invoice) 
   at PX.Objects.AR.ARInvoiceEntry.Persist() 
   at PX.Objects.SO.SOInvoiceEntry.Persist() 
   at PX.Data.PXSave`1.d__2.MoveNext() 
   at PX.Data.PXAction`1.d__31.MoveNext() 
   at PX.Data.PXAction`1.PressImpl(Boolean internalCall, Boolean externalCall) 
   at PX.Data.PXAction`1.Press() 
   at PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(DateTime invoiceDate, PXResult`6 order, PXResultset`2 details, Customer customer, DocumentList`2 list) 
   at PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(DateTime invoiceDate, PXResult`6 order, Customer customer, DocumentList`2 list) 
   at PX.Objects.SO.SOShipmentEntry.InvoiceShipment(SOInvoiceEntry docgraph, SOShipment shiporder, DateTime invoiceDate, DocumentList`2 list) 
   at PX.Objects.SO.SOShipmentEntry.<>c__DisplayClass41_1.b__1() 
   at PX.Data.PXLongOperation.<>c__DisplayClass17_0.b__0() 
   at PX.Data.PXLongOperation.d(Object A_0) 
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) 
   at PX.Data.PXThreadPool.a() 
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) 
   at System.Threading.ThreadHelper.ThreadStart() 
PX.Objects.AR.ARInvoiceEntry.CalculateAvalaraTax(ARInvoice发票)处的

在PX.Objects.AR.ARInvoiceEntry.Persist()处
在PX.Objects.SO.SOInvoiceEntry.Persist()处
在PX.Data.PXSave`1.d_uuu2.MoveNext()中
在PX.Data.PXAction`1.d_uu31.MoveNext()中
在PX.Data.PXAction`1.d_uu31.MoveNext()中
在PX.Data.PXAction`1.PressImpl(布尔内部调用,布尔外部调用)
在PX.Data.PXAction`1.Press()处
在PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(日期时间invoiceDate,PXResult`6订单,PXResultset`2详细信息,客户,文档列表`2列表)
在PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(日期时间invoiceDate,PXResult`6订单,客户,文档列表`2列表)
在PX.Objects.SO.SOShipmentEntry.InvoiceShipping(SOInvoiceEntry docgraph、SoShipping shiporder、DateTime invoiceDate、DocumentList`2列表)
在PX.Objects.SO.SOShipmentEntry.c__显示类41_1.b__1()
在PX.Data.PXLongOperation.c_uuu显示class17_0.b_uu0()
错误:DocStatus对此操作无效。:预期已保存|已发送
提高时间:2019年2月28日10:38:50下午屏幕:SO.30.20.00
细节:
2019年2月28日10:38:50下午错误:
DocStatus对此操作无效。:预期已保存|已发布
在PX.Objects.AR.ARInvoiceEntry.LogMessages处(BaseResult)
在PX.Objects.AR.ARInvoiceEntry.CalculateAvalaraTax(ARInvoice发票)
在PX.Objects.AR.ARInvoiceEntry.Persist()处
在PX.Objects.SO.SOInvoiceEntry.Persist()处
在PX.Data.PXSave`1.d_uuu2.MoveNext()中
在PX.Data.PXAction`1.d_uu31.MoveNext()中
在PX.Data.PXAction`1.PressImpl(布尔内部调用,布尔外部调用)
在PX.Data.PXAction`1.Press()处
在PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(日期时间invoiceDate,PXResult`6订单,PXResultset`2详细信息,客户,文档列表`2列表)
在PX.Objects.SO.SOInvoiceEntry.InvoiceOrder(日期时间invoiceDate,PXResult`6订单,客户,文档列表`2列表)
在PX.Objects.SO.SOShipmentEntry.InvoiceShipping(SOInvoiceEntry docgraph、SoShipping shiporder、DateTime invoiceDate、DocumentList`2列表)
在PX.Objects.SO.SOShipmentEntry.c__显示类41_1.b__1()
在PX.Data.PXLongOperation.c_uuu显示class17_0.b_uu0()
在PX.Data.PXLongOperation.d处(对象A_0)
位于System.Threading.ExecutionContext.RunInternal(ExecutionContext ExecutionContext、ContextCallback回调、对象状态、布尔值preserveSyncCtx)
在System.Threading.ExecutionContext.Run(ExecutionContext ExecutionContext,ContextCallback回调,对象状态,布尔保存SyncCTX)
在System.Threading.ExecutionContext.Run(ExecutionContext ExecutionContext,ContextCallback回调,对象状态)
在PX.Data.pxreadpool.a()处
位于System.Threading.ExecutionContext.RunInternal(ExecutionContext ExecutionContext、ContextCallback回调、对象状态、布尔值preserveSyncCtx)
在System.Threading.ExecutionContext.Run(ExecutionContext ExecutionContext,ContextCallback回调,对象状态,布尔保存SyncCTX)
在System.Threading.ExecutionContext.Run(ExecutionContext ExecutionContext,ContextCallback回调,对象状态)
位于System.Threading.ThreadHelper.ThreadStart()处

实际错误包含在跟踪中:

DocStatus is invalid for this operation.: Expected Saved|Posted 
错误来自Avalara API,但我不确定应该在哪里修复。 我会试着先给阿瓦拉一个机会。他们建议在管理命令面板中更改某些内容

资料来源:阿瓦拉拉:

从上面的链接复制文本:

Overview
You want to know how to resolve the error: "DocStatus Is Invalid for This Operation. Expected Saved/Posted."

Environment
AvaTax

Resolution
This error message indicates that the DocCode used to calculate on or import transactions already exists within your Admin Console 
Each document requires a unique identifier for the DocCode
Confirm the duplicate DocCode: Go to the Transactions tab in the Admin Console and search for the particular DocCode 
Try adjusting the beginning date range to a date a few months or years in the past, then search for the specific DocCode
Once you find the transaction with the matching DocCode, determine if this is an exact copy of the transaction you are trying to import or calculate 
If the two transactions are duplicates, you can: 
Not add the transaction again
Change the DocCode by adding a number or letter and add the transaction in a different period
For imports: Use a ProcessCode of 2 or 4 and adjust the current transaction upon import
Change the original transaction to Uncommitted and recalculate the current transaction 
Open the transaction in the Admin Console > click Edit > choose Adjustment Reason > click Save as Uncommitted in orange 
Void will not avoid the error, it must be Uncommitted.
If the two transactions aren't duplicates, change the new transaction's DocCode/invoice number
编辑:约书亚·范·霍森的评论是最有可能的解释:


如果您使用的销售演示数据带有有效的Avalara税 集成—您很可能尝试过将文档与 相同的[refNbr | doctype]组合,您必须删除 Avalara仪表板之外的那些文档-或-更改编号 使文档的顺序高于已有的值 用过。如果您使用演示数据集进行测试,并且 然后使用相同的数据集刷新/重新安装实例


如果您将销售演示数据与有效的Avalara税务集成一起使用,则您很可能尝试使用具有相同[refNbr | doctype]组合的文档,您必须将这些文档从Avalara仪表板中删除,或者更改文档的编号顺序,使其高于您已使用的值。如果您使用演示数据集进行测试,然后使用相同的数据集刷新/重新安装实例,则可能会发生这种情况。@Joshua我在回答中添加了您的评论,因为这也是我怀疑的,也是最可能的解释。