Date that is sent to the Fiscal Book Integration for "Cupom fiscal" is incorrect when you create a fiscal file that uses the "Cupom fiscal" data and the Z report data in Microsoft Dynamics AX for Retail 2009 R2 Refresh with the Brazil localization layer

This article applies to Microsoft Dynamics AX for Retail for all regions.

Symptoms

Assume that you perform the Z report operation in POS in Microsoft Dynamics AX for Retail 2009 R2 Refresh with the Brazil localization layer installed. When you create a fiscal file that uses the "Cupom fiscal" data and the Z report data, the Fiscal Book Integration tables that are used for Sintegra registers are filled with the issue date information from the "Cupons fiscais" and Z reports. However, the Fiscal Book Integration tables should be filled with the accounting date information from the "Cupons fiscais" and Z reports.

Cause

This problem occurs because the SoftTeam tables adopt DATEMI (date of emission) instead of DATMOVTO (date of movement) for the Z Report date. Although DATMVTO exists in the POS, it is the DATEMI field that is copied back to Microsoft Dynamics AX and reported.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website: You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

PartnersCustomersIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.


ERROR: PhantomJS timeout occurred