Identical Retail transaction gets lost during posting of statements when store is in a different time zone than the HQ.

Symptoms

When MPOS is in a time zone which is different from AX, and  two identical transactions are made
with same customer in MPOS, it considers one as the duplicate of the other during retail statement creation and posting.

Resolution

 During RetailStatements posting of sales transactions done in MPOS, we should not have check for duplicate sales order. This is because, for RetailTransactionType = Sales, salesorder is loaded in AX
only via Statements (Not RTS). There is no reason for timeout and duplicates as there is no RTS call, so everything in the RetailtransactionTable should be imported to AX. However, duplicate check should still be executed during RTS call for customer order creation, as in this case, there is a chance of timeout and retry, creating duplicates.

More information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Eigenschaften

Artikelnummer: 4014196 – Letzte Überarbeitung: 27.02.2017 – Revision: 1

Feedback