【问题标题】:Acumatica and Avalara and Failed to Get TaxesAcumatica 和 Avalara 未能征税
【发布时间】:2019-02-28 22:53:13
【问题描述】:

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

屏幕错误 - 无法从 Avalara 获取税款。检查跟踪以获取详细信息 (https://www.dropbox.com/s/b7sxdo5nsblu54w/Screenshot%202019-02-28%2017.39.03.png?dl=0)

这是 Acumatica 版本 Acumatica 2017 R2 构建 17.210.0034

当我们测试 avalara 连接时 - 我们看到了这一点。与 Avalara 的连接成功。服务版本为19.2.0.39。

这是下面的痕迹 错误:TX 错误:无法从 Avalara 获取税款。检查跟踪以获取详细信息发送 提出时间:2019 年 2 月 28 日晚上 10:38:50 屏幕:SO.30.20.00
细节: 2/28/2019 晚上 10:38:50 错误: TX 错误:无法从 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() 

【问题讨论】:

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

标签: acumatica avalara


【解决方案1】:

真正的错误包含在痕迹中:

DocStatus is invalid for this operation.: Expected Saved|Posted 

错误来自 Avalara API,但我不确定应该在哪里修复。 我会先尝试一下 Avalara 文档。他们建议在他们的管理命令面板中进行更改。

来自阿瓦拉的来源: https://help.avalara.com/Frequently_Asked_Questions/Miscellaneous/How_do_I_resolve_the_Doc_Status_error_DocStatus_Is_Invalid_for_This_Operation_Expected_Saved%2F%2FPosted%3F

从上面的链接复制文本:

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

编辑: Joshua Van Hoesen 评论是最可能的解释:

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

【讨论】:

    猜你喜欢
    • 2019-03-02
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2022-01-13
    • 1970-01-01
    • 1970-01-01
    • 2013-04-08
    • 1970-01-01
    相关资源
    最近更新 更多