Hotfix 2734019 is available to update the India DSA register for export sales order transactions in Microsoft Dynamics AX 2009 Service Pack 1 with the India localization layer installed

This article applies to Microsoft Dynamics AX for the India (in) region.

INTRODUCTION

This article describes a hotfix that is available to update the India Daily Stock Accounting (DSA) register for export sales order transactions in Microsoft Dynamics AX 2009 Service Pack 1 (SP1) with the India localization layer installed.

More Information

The DSA register must be updated with the produced quantity of finished goods (also known as BOMs) when the finished goods are sold. This hotfix provides a feature to make sure that export sales orders are included so that you can obtain correct details of stock movement on the DSA. This is a legal requirement for Indian government.
Summary description
This hotfix treats export sales order in the following ways:
  • Make sure that all taxes are calculated and posted at the time of an Export Sales Order/Invoice level. Before you install this hotfix, only taxes for customs are calculated.
  • Custom duty is recalculated and posted at the shipping bill level. (No change from current release.)
  • Based on the Excise selection, Microsoft Dynamics AX updates the DSA register accordingly:
    • If an export sales order is tagged as exempt, a zero amount against the applicable quantity will appear on the DSA register, just as it does for a regular sales order.
    • If a regular sales order or an export sales order is tagged by using a Zero% tax value for exempted goods, the DSA register is updated with a correct quantity and zero tax amount.
  • If there are regular exports in which excise duty is payable, such as non-submission of ARE.1, the excise duty will be calculated at the time of removal of goods from the factory.

    Note Excise goods cannot be removed without the excise invoice. Therefore, the excise duty will be calculated at the invoice time.

    The procedure is as follows:
    1. Inspectors of central excise verify the identity of goods mentioned in the application and the details of the duty paid or payable.
    2. If they find that the declaration in ARE.1 and the invoices are correct from the point of view of identity of goods and its assessment to duty, and that the exporter has recorded the duty payable in the DSA register, they shall seal each package or the container to make sure that the goods cannot be tampered after the examination.
    3. Then, the exporter will submit the shipping bill.
Background information
Currently, exporters cannot easily manage their Daily Stock QTY obligations to the Indian government. This hotfix makes sure that the DSA register provides accurate details and meet these obligations.
Corresponding information
When manufactured excisable goods are sold, transferred or exported out of country by a manufacturer, the DSA register (prescribed for finished goods register) must be updated. According to Rule 10 of Central Excise Rules, 2002, the DSA should contain the following:
  • Description of the goods produced or manufactured
  • Opening balance
  • Quantity produced
  • Inventory of goods
  • Quantity removed (sold/exported/transferred)
  • Closing Balance
  • Assessable value
  • Duty amount payable/amount of duty actually paid

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.

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:
  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.


For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have Microsoft Dynamics AX 2009 Service Pack 1 with the India localization layer installed to apply this hotfix.

Restart requirement

You must restart the Application Object Server (AOS) service after you apply this hotfix.

File information

The Hindi version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Axupdate.exeNot applicable61,67225-Sep-201216:28x86
Kb2734019glp.xpoNot applicable53,053,52125-Sep-201216:09Not applicable
Metadata.xmlNot applicable7225-Sep-201216:09Not applicable
Kb2734019.xpoNot applicable68,252,24825-Sep-201216:10Not applicable
Metadata.xmlNot applicable7225-Sep-201216:10Not applicable
Axsetupsp.exe5.0.1100.451,636,59225-Sep-201216:28x86
Cabextractor.dllNot applicable19,18425-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.dll5.0.1100.9150,44017-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40538,88025-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4517,33617-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82417-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82417-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40538,88025-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82417-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40538,88025-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1500.121216,32017-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82417-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40542,97625-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4517,84817-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82417-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40534,78425-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40547,07225-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4518,87217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40559,36025-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4520,40817-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40530,68825-Sep-201216:27x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31217-Feb-201200:02x86
Axsetupsp.resources.dll5.0.1100.40526,59225-Sep-201216:28x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4515,80017-Feb-201200:02x86
Cabextractor.dllNot applicable22,76825-Sep-201216:28x64

Validation of the application hotfix installation

To validate the installation of the application hotfix, open the SysHotfixManifest class in the Application Object Tree (AOT). Then, verify that there is a method whose name includes the Knowledge Base (KB) article number of the installed hotfix. Additionally, you can cross-check the affected objects by comparing the KBXXXXXX.txt file against the objects in the AOT. By doing this, you can make sure that the objects are changed correctly in the SYP layer or in the GLP layer.

Note The XXXXXX placeholder represents the KB article number of the installed hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

974255 Impact Analysis feature for Dynamics AX 2009

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein 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.
Svojstva

ID članka: 2734019 - Poslednji pregled: 17.02.2017. - Verzija: 2

Microsoft Dynamics AX 2009 Service Pack 1, Microsoft Dynamics AX Application Object Server

Povratne informacije