最新消息:ww12345678 的部落格重装上线,希望大家继续支持。

Dynamics 365 Retail Statement Statement Posting Issues Caused by a Previous Statement Posting Failure in Batch

网络文摘 William 37浏览 0评论
When posting Retail Statements in batch and there has been an error, Customers have been receiving errors manually posting the Retail Statements after the original failure. One example of a Retail Statement error: “One or more sales orders in statement XXXX have not been invoiced; abort payment journal posting” A majority of the time, the Sales order and invoice are not populated, but the RetailTransactionTable EntryStatus contains a value of 7 (PendingInvoice) or 8 (CreatingOrder). Once the statement is in this state, it cannot be posted manually or in batch without updating the table. Prior to the below hotfixes, this issue requires a ticket with support to update the RetailTransactionTable to update the EntryStatus from 7 or 8 back to 0 (None). The changes in the hotfixes below make sure the transactions that are in the Status “CreatingOrder” or “PendingInvoice” can now be posted as expected.   KB4051955 can be downloaded from LifeCycle Services for App7.1 at the following link or by searching for 4051955 https://fix.lcs.dynamics.com/Issue/Resolved?kb=4051955&bugId=3867956&qc=0f5574b25d65cc19bef518cf99ec1af6f700c479d018755f37cabd916874100b   KB 4053789 can be downloaded from LifeCycle Services for App7.2 at the following link or by searching for 4053789 https://fix.lcs.dynamics.com/Issue/Resolved?kb=4053789&bugId=3889253&qc=5797df003e90a0bd6aa07d5253295fcb2812b20cf74928889ce9eab557c538bc    
发表我的评论
取消评论

表情

Hi,您需要填写昵称和邮箱!

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址