After Database restore, server is unavailable Error in Dynamics AX

Database restore Issue:

After Restoring Database Backup and tried to start Dynamics AX got following error

Error:

“The server is unavailable. Check your configuration and network connection and try again”

Reason:

When we restore the database where references are still from Old DB backup and service cannot be started with current network credentials.

Solution:

update configuration:

  1. To get SID using Open command window and write Whoami /user press enter SID Will be shown
  2. Start SQL Server Management Studio and execute following command by providing values:
update userinfo set SID='<SID>', Networkdomain = '<Network_domain_name>', networkalias = '<Network_alias>' where id = 'admin'

3. Restart AOS

Microsoft Dynamics AX 2012 SSRS REPORT ERROR: a connection attempt failed because the connected party did not properly respond after a period of time.

Error Detail:

After providing parameters and run the report after a while getting following error

“A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond”

Solution1:

  • The reason can be the the AX client config on the report server ,client configurations need to be refreshed (click the refresh button) for both the client config and the business connector config.
  • Run the command prompt as administrator
  • Flush the DNS by using ipconfig /flushdns command.

Solution2:

  • Stop all AOS’s
  • Stop Reporting Service
  • Start AOS
  • Start Reporting Service

Microsoft Dynamics AX 2012 R3 New Features – Sales and marketing

In previous article we have covered the several features that are added or changed in Microsoft Dynamics AX 2012 R3. In this article we will cover the detail of the features that are added or changed in module Sales and marketing.

Register serial numbers in inventory is no longer required, now serial numbers can be registered during the sales process when you prepare the packing slip or the invoice for a sales order.

Serial numbers can registered on the packing slip or invoice either by entering them manually or by using a scanner.

The following list of some scenarios that this feature is intended:

  • Registering serial numbers for items on sales orders on the packing slip or invoice.
  • Customer pickup of sales orders with serialized items.
  • Partial delivery and invoicing of sales orders with serialized items.
  • Correcting packing slips and invoices with serialized items.
  • Returning serialized items.
  • Tracing the history of orders that include serialized items.

Adding worker picture to the WorkerIDCard Microsoft Dynamics AX 2012

Requirement: There is a need to modify the jmgWorkerCard report by adding the worker’s image (HcmPersonImage)

Solution: Image is in the HcmPersonImage table, it only has 2 fields: person and image following code worked in the processReport part of the jmgWorkerCardDP class:

tmpWorkerCard.Image = hcmPersonImage::find(hcmWorker.RecId).Image;

Microsoft Dynamics AX 2012 R3 New Features – Master planning

In previous article we have covered the several features that are added or changed in Microsoft Dynamics AX 2012 R3. In this article we will cover the detail of the features that are added or changed in module Master planning.

Master planning is used to perform the following business processes:

  • Forecast scheduling to calculate gross requirements for forecasted demand.
  • Master scheduling to calculate net requirements for items to fulfill actual demand.
  • Process the action messages and futures messages that are generated during master scheduling. This information can be used to modify planned orders.
  • Process planned orders and kanbans (The kanban framework for lean manufacturing in Microsoft Dynamics AX is based on kanban rules. A kanban rule is a supply policy that defines when kanbans are generated and how they are replenished).

Following are the new features in Master planning:

Demand forecasting: Demand forecasting is a set of tools that enable you to estimate future demand and create demand forecasts based on historical transaction data.

The demand forecasting process includes the following tasks:

  • Complete the prerequisite setup tasks
    • Intercompany planning groups must be configured before you start
    • Select the items to include in the demand forecast: Demand forecasting uses the item allocation key to calculate forecast at the aggregated item level. Item allocation keys make it easier to manage multiple items, and manage the grouping of items that share the same forecast setup. To include an item in a demand forecast, you must assign it to an item allocation key.

Follow are the steps to assign item allocation key:

    • Click Inventory management > Setup > Forecast > Item allocation keys.
    • Create or select an item allocation key. For more information, see Item allocation keys (form).
    • Click Assign items.
    • In the Available items list, select the item that you want to assign, and then use the arrow buttons to move the item to Assigned items. An item can be assigned to only one item allocation key. When an item has been assigned, it is no longer available.
    • Repeat these steps for all items that you want to include in the demand forecast.
    • Assign items to the demand forecast of a specific company: Demand forecast is calculated for all companies that are part of an intercompany planning group. Demand forecast is calculated, by default, for all items that are assigned to all item allocation keys and for all companies. Therefore, to specify which item allocation keys to forecast per company, you must assign the item allocation keys to the company

To assign an item allocation key to a member of an intercompany planning group, follow these steps:

    • Click Master planning > Setup > Intercompany planning groups.
    • Select the intercompany planning group and the intercompany planning group member to which you want to assign item allocation keys.
    • Click Item allocation keys.
    • In the Unassigned item allocation keys list, select the key that you want assign, and then use the arrow buttons to move the key to Assigned item allocation keys.
    • Repeat these steps for all intercompany planning groups for which you want to assign item allocation keys.
    • Define the level of detail to use in the demand forecast: Use forecast dimensions to specify the level of detail for which a baseline forecast is generated. The forecast dimensions for item allocation key, company, and site are always used by default. In addition, you can assign forecast dimensions, such as warehouse or customer account, to create a greater level of detail in the demand forecast. Defining forecast dimensions is part of the initial setup for demand forecasting, you can modify the forecast dimensions at any time and then regenerate a baseline forecast to apply them

To assign forecast dimensions, follow these steps:

    • Click Master planning > Setup > Demand forecasting > Demand forecasting parameters.
    • Click Forecast dimensions.
    • In the Available forecast dimensions list, select the dimension that you want to assign, and then use the arrow buttons to move the dimension to Assigned forecast dimensions.
  • Set up the parameters to use in demand forecasting:Select the parameters to apply when baseline forecasts are generated. The parameter setup is global and applies for all companies that are members of the specified intercompany planning group.
    • Click Master planning > Setup > Demand forecasting > Demand forecasting parameters.
    • In the Demand forecast unit field, select the unit to use for forecast quantities. This field is required because demand forecasts are generated based on quantities of items. Also, make sure that there is a conversion rule defined for the forecast unit and the item unit.
    • In the Excel demand forecast file path field, enter the file path location that is used to save the Excel demand forecast file.
    • In the Include these historical transaction types to generate the statistical baseline forecast field group, select the types of historical transactions to include when the baseline forecast is calculated. For example, select the Production line check box to calculate the dependent demand for BOM line requirements. The items on lower BOM levels must be assigned to an item allocation key to be included in the forecast generation.

If you do not select any transaction types, there is no history with which to calculate the demand forecast.

  • On the Forecast algorithm parameters FastTab, in the Forecast generation strategy field, select one of the following options.
    1. This field is required.
    2. SSAS time series forecasting methods: Use the Microsoft SQL Server Analysis Services Time Series algorithm to calculate a statistical baseline forecast. For more information about Microsoft SQL Server Analysis Services
    3. Copy over historical demand: Use historical demand data to calculate a baseline forecast. This option does not use the Microsoft SQL Server Analysis Services Time Series algorithm.
  • If you select the SSAS time series forecasting methods option in the Forecast generation strategy field, you must select the Microsoft SQL Server Analysis Services cubes in the Demand forecast cube and Demand forecast accuracy cube fields. These cubes are used to analyze the historical demand transaction data and generate the statistical baseline forecast.
  • Select the Do not allow gaps in historical data check box to fill any gaps in the historical data with 0 (zero) before the data is passed to the SQL Server Analysis Services. Gaps are forecast buckets that do not contain historical data. For example, a month during which there are no sales for a specific product. For better system performance, clear this check box.
  • On the Item allocation keys tab, you can define demand forecasting parameters that are specific to a particular item allocation key. For example, for an item allocation key that is created for TVs, you can forecast only sales demand.

Forecast reduction for a customer or customer group: You can specify whether a customer forecast is included in the overall forecast. This setting determines how actual demand reduces the forecasted demand. You can use this setting to ensure that master planning covers the supply of items that are purchased by specific customers.

  • If a customer forecast is included in the overall forecast, actual customer demand reduces both the customer forecast and the overall forecast. Master planning generates planned orders to cover only the overall forecast quantity.
  • If a customer forecast is not included in the overall forecast, actual customer demand reduces only the customer forecast. Master planning generates planned orders to cover both the overall forecast quantity and the forecast for each customer quantity.
  • They Include customer forecast in the demand forecast check box is located in the Coverage groups form.

Start time for production scheduling: You can select the start time to schedule production orders.

  • The start time can be the start of the calendar work day or the current time. The current time option is used with the delivery date control and capable to promise (CTP) feature. The Scheduling start time field is located in the Master planning parameters form

Microsoft Dynamics AX 2012 R3 New Features – Inventory and warehouse management

In previous article we have covered the several features that are added or changed in Microsoft Dynamics AX 2012 R3. In this article we will cover the detail of the features that are added or changed in module Inventory and warehouse management.

Microsoft Dynamics AX 2012 R3 includes new Warehouse and Transportation management modules that are enabled by a single configuration key, along with the previously released Warehouse management II module.

Users should enable the configuration key for each of these modules, but not both, in a single-instance, single-partition deployment. Although technically feasible, enabling the configuration keys for both of these modules in a single-instance, single-partition deployment is not supported by Microsoft.

Following are the new features in Inventory and warehouse management module:

Compare item prices: The Compare item prices report enables you to compare the prices in a costing version to the pending prices in another costing version or to the active prices as per an effective.

For standard costs, the report compares the aggregate level and the cost rollup level:

At the aggregate level: Report compares the total aggregated cost per item, item variant, and site

At the cost rollup level: Report compares the cost rollup for each cost group per item, item variant, and site.

BOM journal posting: The posting routine in the BOM journal is redesigned and enhanced.

When you post a BOM journal, you post the journal to inventory profit and loss accounts instead of production WIP accounts. The imbalance expires and does not remain on the WIP account. For actual costs, a negative BOM journal leaves a balance on the WIP account.This imbalance is posted to general ledger as profit and loss.

Inventory aging report: displays the on-hand quantity, inventory value, and the related aging periods for a selected item or an item group. You can use the report parameters to filter the data that will be displayed in the report.

Microsoft Dynamics AX 2012 R3 New Features – General ledger

In pervious article we have covered the several features that are added or changed in Microsoft Dynamics AX 2012 R3. In this article we will cover the detail of the features that are added or changed in module general ledger.

Basic Definition: General ledger is used to define and manage the legal entity’s financial records. The general ledger is a register of debit and credit entries. These entries are classified using the accounts that are listed in a chart of accounts.

We can allocate, or distribute, monetary amounts to one or more accounts or account and dimension combinations based on allocation rules.

There are two types of allocations:

Fixed: Fixed allocation is used to distribute specified percentages of a transaction amount to distribution accounts and dimensions.

Variable: Variable allocation is used to distribute fluctuating percentages of a transaction amount to various accounts and dimensions.

You can also settle transactions between ledger accounts and revalue currency amounts. At the end of a fiscal year, you must generate closing transactions and prepare your accounts for the next fiscal year.

Following are the list of new features that are added or changed in General ledger module of Dynamics AX 2012 R3:

  • Opening balances for balance sheet accounts can be transferred to a new fiscal year in multiple companies at the same time.
  • The results of the accounting entries for stocked items on product receipts and vendor invoices are combined into one sub-ledger journal entry and voucher.