Prepare a legal entity for use in the consolidation process [AX 2012]

In a consolidation, you gather transactions from several sets of legal entity accounts into a single set of legal entity accounts.

Note : We recommend that you use Management Reporter for Microsoft Dynamics ERP to combine the financial results for multiple legal entities in a consolidated format. Management Reporter lets you create consolidated financial reports across legal entities, use Microsoft Excel to import consolidation data from other sources, and translate amounts into any number of reporting currencies without having to run the consolidation process in Microsoft Dynamics AX.

 

For more information about how to consolidate transactions by using Management Reporter, see Financial consolidations and currency translation.

You can print reports, such as financial statements, from the consolidated legal entity. However, you cannot use the consolidated legal entity for daily transactions.

You can consolidate data from legal entities that use different databases than the database for the consolidated legal entity. This consolidation process is referred to as an import consolidation. Alternatively, the legal entities can use the same database as the consolidated legal entity. This consolidation process is referred to as an online consolidation.

The consolidated legal entity collects the results and balances of the subsidiaries. To prepare a consolidated legal entity for a consolidation, you must follow these steps:

1. Click General ledger > Setup > Organization > Legal entities.

2. Click New to create a new legal entity that will be the consolidated legal entity.

3. Select the Use for financial consolidation process check box, and then enter information about the consolidated legal entity. Enter this information exactly as you want it to appear on financial statements for the consolidated legal entity.

4. Close the form.

5. In the lower-right corner of the Microsoft Dynamics AX workspace, click the Current company field to open the Select company form. Select the consolidated legal entity, and then click OK.

6. Click General ledger > Setup > Ledger.

7. Select the chart of accounts, the fiscal calendar, the accounting currency, an optional reporting currency, and the default exchange rate type for the consolidated legal entity. For more information, see Ledger (form).

8. Click General ledger > Setup > Currency > Currency exchange rates.

9. Set up currency exchange rates in relevant periods for the currencies of the subsidiary legal entities. For more information, see Currency exchange rates (form).

10. Close the form.

11. If the consolidated legal entity has subsidiaries that use foreign currencies, open the Accounts for automatic transactions form. (Click General ledger > Setup > Posting > Accounts for automatic transactions.) In the Posting type field, select an appropriate account:

    • If the legal entity has foreign subsidiaries that are financially or operationally interdependent with the parent legal entity, select an appropriate account for the Profit and loss account for consolidation differences posting type.

    • If you are consolidating a subsidiary that is financially and operationally independent from the parent legal entity, or a legal entity that contains the results of several subsidiaries that are financially and operationally independent from the parent legal entity, and if you are using translation methods to consolidate the data, select an appropriate account for the Balance account for consolidation differences posting type.

12. In the Main account field, select the main accounts that will be used for foreign currency revaluation adjustments.

13. Close the form.

If you create the consolidated legal entity early in a period, you can revalue the foreign currency amounts as exchange rates change during the consolidation period.

The consolidated legal entity is now set up for the Consolidate periodic job. You can specify whether to perform either an online consolidation or an import consolidation:

Click General ledger > Periodic > Consolidate > Consolidate [Import from].

–or–

Click General ledger > Periodic > Consolidate > Consolidate [Online].

Note : Before you can process the consolidation, prepare the subsidiary legal entities for consolidation. For more information, see Set up a subsidiary legal entity for consolidation.

Reporting Architecture – AX 2012

The following diagram illustrates the architecture of the reporting functionality in Microsoft Dynamics AX.

1. A user requests a report.
Assume that a user clicks a menu item in the Microsoft Dynamics AX client. The menu item is bound to a SQL  Server Reporting Services report.
After the user clicks the menu item, a parameters form is displayed to the user. The user enters parameters to filter the data that will be displayed on the report.
The Microsoft Dynamics AX client then requests the report from Reporting Services. (The request includes the parameters entered by the user.)

2. Reporting Services receives the request and asks the Microsoft Dynamics AX server for the report data.
Reporting Services receives the request and examines the report on the server. The report is stored as an .rdl file. The .rdl file indicates the report’s data source. (The data source could be a Microsoft Dynamics AX query, a report data provider class, or an external data source via report data methods.)
In cases where a Microsoft Dynamics AX data source is used for the report, Reporting Services will use the Microsoft Dynamics AX data extension to retrieve the data.
At this point, Reporting Services asks Microsoft Dynamics AX for metadata about the data source. Reporting Services then requests the data for the report.

3. The Microsoft Dynamics AX server receives the request and sends the report data back to Reporting Services.
The Microsoft Dynamics AX services examine the query in the AOT to return the requested metadata. The services also execute the query to generate the data for the report.

Microsoft Dynamics AX returns the metadata and data to Reporting Services.

NOTE: Microsoft Dynamics AX enforces security on all data returned. If the user who is running the report is not allowed to see a specific field, the data for that field is not returned.

4. Reporting Services renders the report and sends it to the Microsoft Dynamics AX client.
The Microsoft Dynamics AX customization extension formats the report.
The customization extension uses metadata to provide automatic formatting of data and can affect the positioning and layout of elements in the report.
Reporting Services then renders the report into a visual representation and sends that to the Microsoft Dynamics AX client.

5. The report is displayed to the user.
The Microsoft Dynamics AX client displays the report to the user in the report viewer control.

Drain users from an AOS – AX 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic describes how to close client sessions that are connected to an instance of Application Object Server (AOS) for Microsoft Dynamics AX. When you close client sessions without force, you are said to drain users. Administrators drain users from an AOS instance before they perform maintenance on the server or take it offline.

 

Important

The following procedure requires that you click the Reject new clients button in Microsoft Dynamics AX. After you click this button, you must not close your client. If you close your client before you click the Accept new clients button, you cannot open a new client session unless you restart the AOS instance by using the Windows Services Management console, or unless you reset Status of the SysServerSessions table in Microsoft SQL Server  to a value of 1.

 

1. Click System administration > Common > Users > Online users.

2. On the Server instances tab, select the AOS instance that you want to perform maintenance on.

3. Click Reject new clients.

4. When you are prompted, click OK to stop the AOS instance from accepting new client connections.

   After 5 minutes, all users receive a message informing them that they must save their work, because the administrator is shutting down the AOS instance. No new client connections are accepted during this time. The server forces client sessions to close after they have been idle for 2 minutes. Client sessions for administrators are never closed. When the number of clients that are connected to the AOS instance is displayed as 0 (zero), you can perform maintenance on the server.

5. After you have finished performing maintenance on the server, click Accept new clients or restart the AOS instance.

How to: Call an AIF Web Service from C# to Create a Sales Order - Sample Code

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using ConsumeSalesOrderService.SalesOrder;

// Add a using statement for the service reference.

using System.Collections;

namespace ConsumeSalesOrderService

{

    class Program

    {

        static void Main(string[] args)

        {

            // Instantiate an instance of the service client class.

            SalesOrderService proxy = new SalesOrderService();

            // Create an instance of the document class.

            AxdSalesOrder salesOrder = new AxdSalesOrder();

            // Create instances of the entities that are used in the service and

            // set the needed fields on those entities.

            AxdEntity_SalesTable salesTable = new AxdEntity_SalesTable();

            salesTable.CurrencyCode = "USD";

            salesTable.CustAccount = "1101";

            salesTable.DeliveryDate = Convert.ToDateTime("2/14/2010");

            salesTable.Payment = "N060";

            salesTable.PurchOrderFormNum = "PO";

            AxdEntity_SalesLine salesLine = new AxdEntity_SalesLine();

            salesLine.ItemId = "1001";

            salesLine.SalesQty = 88;

            salesLine.SalesUnit = "ea";

            AxdEntity_InventDim inventDim = new AxdEntity_InventDim();

            inventDim.configId = "HD";

            inventDim.InventColorId = "01";

            inventDim.InventSizeId = "42";

            // Add the sub-entity instances to their parent entities as an array

            // of the sub-entity type.

            salesLine.InventDim = new AxdEntity_InventDim[1] { inventDim };

            salesTable.SalesLine = new AxdEntity_SalesLine[1] { salesLine };

            salesOrder.SalesTable = new AxdEntity_SalesTable[1] { salesTable };

            try

            {

                // Call the create method on the service passing in the document.

                EntityKey[] returnedSalesOrderEntityKey = proxy.create(salesOrder);

                // The create method returns an EntityKey which contains the ID of the sales order.

                EntityKey returnedSalesOrder = (EntityKey)returnedSalesOrderEntityKey.GetValue(0);

                Console.WriteLine("The sales order created has a Sales ID of " + returnedSalesOrder.KeyData[0].Value);

                Console.ReadLine();

            }

            catch (Exception e)

            {

                Console.WriteLine(e.ToString());

                Console.ReadLine();

            }

        }

    }

}

Microsoft Dynamics AX 2012 Data Import/Export Framework standalone version for AX 2012 R2 without installing full CU7

We have recently released the new version for Microsoft Dynamics AX 2012 Data Import/Export Framework as part of Microsoft Dynamics AX 2012 R2 CU7. We received lot of requests to get the new version for AX 2012 R2 (Base R2 and/or CU1, CU6, hotfixes) without taking full CU7. To make this happen, we have released an application hotfix for DIXF which can be installed on AX 2012 R2 (Base R2 and/or CU1, CU6, hotfixes).  The hotfix does not contain the binary files for the Data Import/Export Framework. You must install the binary files for the Data Import/Export Framework by using the CU7 update installer.

Application Components

The application hotfix contains the application files for the version of the Data Import/Export Framework that was released with cumulative update 7.

Important: This hotfix does not contain the binary files for the Data Import/Export Framework. You must install the binary files for the Data Import/Export Framework by using the CU7 update installer.

Download:

Application files for the Data Import/Export Framework, cumulative update 7 version

Instructions:

To install the Data Import/Export Framework:

1. Install this hotfix using the installer that it ships with.
2. Complete the software update checklist.

Binary Components

You must install the binary files for the Data Import/Export Framework by using the CU7 update installer.

Download:

Microsoft Dynamics AX 2012 R2 Cumulative Update 7 (KB2885603 )

Instructions:

Install Data import export framework Client, AOS and Service components.

http://technet.microsoft.com/EN-US/library/hh538446.aspx%23InstallCU7

CU 7: Install the Data Import/Export Framework (binary)

---

As of cumulative update 7, you can install the Data Import/Export Framework from the update installer. For an overview of the Data Import/Export Framework, see Data import/export framework user guide ( (DIXF, DMF).

Caution

If you have previously installed the Data Import/Export Framework from InformationSource, you must fully uninstall it before installing again with cumulative update 7 for Microsoft Dynamics AX 2012 R2. This includes removing all binary files by using Add/Remove Programs, and the uninstalling Data Import/Export Framework model. For more information see How to: Remove (Uninstall) a Model.

1. Browse to the location where you extracted the files for the update, and then double-click AxUpdate.exe.
2. On the Welcome to Microsoft Dynamics AX Update Setup page, click Next.
3. On the Software license terms page, review the license terms, and then click Accept and continue.
4. On the Select packages to update page, select the components of the Data Import/Export Framework that can be installed on the local computer, and then click Next.
5. The prerequisite validation check runs. Address any issues that the prerequisite check finds outside the installer, and then restart the validation check. When all prerequisites have been found, click Next.
6. If you are installing on the computer that runs Microsoft SQL Server Integration Services, specify a service account and the version of SQL Server that is running. We recommend that you use the AOS service account.

–or–

If you are installing on the AOS computer, specify the name of the server that is running SQL Server Integration Services.

1. On the Review updates to be installed page, click Next.
2. On the Ready to install page, review the summary, select the Automatically restart the AOS instances after installation check box, and then click Install.
3. After the installation is completed, verify that the updates were installed successfully, and then exit the wizard.

 

Imparted from here