Supply Chain Management in Dynamics AX

Import Vendor Catalogs – Part 3 (Troubleshooting)

Vanya Lebedev — Thu, 07 Mar 2013 13:35:58 GMT

It’s seems like it’s time for a new post in the series about importing vendor catalogs in Dynamics AX 2012. The previous couple of blog posts covered setup and importing a sample catalog. It’s all well and nice but what if something went wrong somewhere along the way of setting up the feature. Below you will find a list of problems that can arise during vendor catalog import setup. And of course the solutions to the problems will be described in detail.

Questions and Answers

I try to import a Vendor catalog with Dynamics AX. I generate the XSD File but it is really not clear how to populate it.

The XSD file that you can generate from the vendor catalog form provides you with the schema of the CMR file that can be imported. XSD (XML Schema Definition) is one of several XML schema languages. The blog post about importing a sample catalog contains a detailed list of steps that you need to take to generated a sample CMR file.

I’d like to see an example of a CMR file with data to import?

It is important to note that the XSD schema for CMR files depends on the procurement hierarchy that you set up in Dynamics AX so the chances of successfully importing sample CMR files are really-really low because the XSD schema produced from your system will most probably differ from the one that was used to generate the sample file. However it’s always nice to see a sample file just to have an idea of what kind of beast the CMR file is. Below is the XML that a sample file might contain:

     <?xml version="1.0" encoding="utf-8"?>

    <VendorCatalog VendorName="CatImpVend" LoadDate="1900-01-01T01:01:01+01:00" ProductClassification="Procurement Category" xmlns="http://dax.com/vendorcatalog">

      <Product xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="root" Delete="No" ProductCode="ProductCode1" ProductSearchName="ProductSearchName1">

        <PriceInformation>

          <Price Currency="USD" UnitOfMeasure="%" Value="100">

          </Price>

        </PriceInformation>

        <ProductNameAndDescription>

          <NameAndDescription>

            <Description>Description1</Description>

            <Name>Name1</Name>

            <Language>af</Language>

          </NameAndDescription>

        </ProductNameAndDescription>

        <ProductAttributes>

          <Color Language="af">Blue</Color>

        </ProductAttributes>

      </Product>

    </VendorCatalog>

I’m getting the error “Imported schema for namespace ‘http://www.w3.org/XML/1998/namespace’ was not resolved” when trying to generate in Visual Studio a sample CMR file based on the XSD schema.

This is a known issue. The workaround is to remove the line below from the XSD file:

    <xs:import schemaLocation="http://www.w3.org/2001/xml.xsd" namespace="http://www.w3.org/XML/1998/namespace" />

When I run the AIF job for processing no error is given but the status of the import in the Catalog file history does not change

The error was most probably logged in the AIF exception log: System administration\Periodic\Application integrationServices and Application Integration Framework\Exceptions.

In the AIF exception log there is an error: Could not find schema information for the element 'http://dax.com/vendorcatalog:VendorCatalog'.

Make sure that you set up the inbound port in AIF as in Walkthrough: Configuring an inbound integration port for catalog import [AX 2012]. Pay special attention to the paragraph about setting up the pipeline component:

The catalog import service requires a special component that processes CMR documents. To enable this component, follow these steps.

In the Inbound ports form, on the Processing options tab, select the Preprocess service operation requests check box, and then click Inbound pipelines.
In the Inbound pipelines form, click Add. Then, in the Class name list, select CatVendorXmlTransform.
In the Purpose field, enter an optional description, such as “Transform vendor XML files,” and then close the Inbound pipelines form.
Click Activate to deploy the integration port.

Conclusion

I hope this information was useful. I would like to make this article into a live blog post. So if you have any problems with setting up vendor catalog import please write to me or post a comment and I will do my best to resolve your problem and post the resolution in this article.

What's New in Microsoft Dynamics AX 2012 R2 for Product Information Management

Mai-Britt Winther — Tue, 18 Dec 2012 11:03:00 GMT

This blog post describes some of the enhancements to the Product Information Management (PIM)
area that have been implemented in the R2 release after the launch of Microsoft Dynamics AX 2012 (RTM).

Discovering the small secrets of the Authorized by
company fact box

Yes, it almost qualifies as an Easter egg! If you resize the Authorized by company fact box in R2, you will find a new column by the end of the grid, and in this column you’ll find the item number that identifies the product within its legal entity.

This field saves you the hassle of first having to select the company and then the More link to be able to right-click on the Item number field in order to jump to the details of the product in the specific legal entity. Since these fields are part of a grid, you can of course drag the Item number field closer to the company field and thereby have a smaller FactBox with the direct link.

This allows you to jump directly to the record and continue the setup process for the product, with the option to use templates.

And speaking of templates…

“Catching” the process fields in templates

With the addition of the Process Industry (PI) solution, a lot of new functionality and product characteristics have been enabled. A small subset of the fields that were added with the solution brought about some minor issues and especially the question of whether a field was a catch weight item or not has caused some confusion.
These issues have now been resolved in order to unblock the procedure.

Enhancing the product services

If you rely on some of your products to be created via AIF services, you will find a couple of updates to the services.

Firstly, the PI characteristics have been added to the released product services, allowing you to read and write product definitions.

Secondly, a much requested field such as the default order type has been added to the released product service. This allows you to indicate whether the product should be purchased or produced or if it should use Kanban.

And thirdly, the product and product master dimension value services have been updated to offer full CRUD support.

Monitor and analyse current and future warehouse space utilization with Dynamics AX 2012 R2

Mirza Abdic' — Tue, 11 Dec 2012 23:37:01 GMT

It’s the warehouse managers’ responsibility to make sure that sufficient space is available for all goods that are to be stored in the warehouses that they control. This can be a challenging task. Warehouse space is expensive, and warehouse managers must avoid an excess of free space and on the other hand they must make sure that space is available at the time when goods arrive at the warehouse locations.

In some industries, a shortage of space at the time when goods arrive at a warehouse location can result in huge financial losses for a company. If, for example, there is not space in a warehouse when a truck load of frozen fish arrives, the warehouse manager cannot just unload the fish on the parking lot outside the buildings. Possible solutions to the problem would be to redirect goods to another warehouse owned by the company, to buy inventory space at the warehouse hotels, or, if there are no other options, to send the goods back.

All of the solutions mentioned above to the problem of not being able to store goods due to a lack of available warehouse space, will result in added expenses for the warehouse and they might even result in goods not being available for customers or the production.

What is important for the warehouse manager is to be able to quickly get an overview of the current space utilization in terms of, for example, pallets, volume or weight and to be able to project the future space utilization based on transactions generated by master planning.

In Dynamics AX 2012 R2, a new report provides a possibility of short and long term operation planning for current and future space utilization of a warehouse.

How the space utilization feature can help the warehouse manager

As already mentioned, warehouse managers manage the space that is available in the warehouse and they must make sure that the inbound products can be stored in the warehouse. Information about current and forecasted space utilization can enable the warehouse manager to make decisions about where items should be stored. The new report can help the warehouse manager to identify problems with missing space for items that will arrive today or in the future and it can provide insights in transaction details that are related to an excess of unused space.

To avoid space related issues, the warehouse manager can analyze the amount of capacity that the warehouse or warehouses are currently using and the amount they will use in the future. The warehouse manager can get a detailed overview of the transactions that cause space management issues, and maybe these issues can be avoided by using projections that allow more lead time.

The space utilization feature in Microsoft Dynamics AX 2012 R2 can display the current capacity of a warehouse and the projected capacity of the future. Capacity can be displayed in pallets (if advanced WMS is used), weight, or volume. Forecasted capacity is based on a master plan and other space utilization settings as defined by the warehouse manager. This will be covered in the sections below.

The warehouse manager can:

· Choose a master plan based on the need of a space utilization analysis.

· Select how many days of future space need to be calculated

· Specify if either planned or confirmed transactions or both should be included in the report.

Space utilization is calculated from transactions that are generated by a master plan for the warehouse. The calculation model uses the space utilization situation in the warehouse from before the last MRP run. All of the transactions that are to happen on that warehouse space are calculated no matter if they are planned or confirmed. The result as it would look by the end of the day is shown in percentage vs. maximal space available. The result can be viewed in pallets, volume, or weight provided that this information is set up correctly for all of the products.

· Check the setting of the products on the Manage inventory fast tab in the Released product details form under Product information management.

Reports provide warning functionality for master data configurations. For example, say that the warehouse space utilization report is viewed in a unit volume and there is a purchase order line with an item that does not have any setup for physical dimensions. In this case a warning will be shown for this instance and for all similar cases. A detailed report will be generated for all of the missing inventory item setups. If items do not have fallback warehouses, this will be included in the report as well. A warning icon on the report indicates to the warehouse manager that calculations might not be precise and that a fallback warehouse or some inventory item setups are missing.

How to use the space utilization feature

To use the Space utilization feature in Microsoft Dynamics AX 2012 R2, you must complete the following three steps. Also, data from at least one master plan must be created before the report can be generated.

Master planning > Periodic> Master scheduling

Figure 1

Configure and run the report:

1. Configure one or more space utilization setup templates.

2. Run the Schedule load utilization periodic job.

3. Analyze the space utilization information. This can be accomplished in one of two ways:

1. Run the Warehouse load utilization report from Inventory and warehouse management in Dynamics AX 2012 R2.

2. View the report in the Space utilization web part in the Warehouse manager role center.

1. Configure one or more space utilization setup templates.

Click Inventory and warehouse management > Setup > Warehouse reports > Space utilization.

Figure 2

From the Schedule load utilization form, you can create any number of space utilization setups and switch between the setups.

Space utilization: Enter the space utilization ID.

Name: Enter the space utilization name.

Storage load mode: In the Storage load field, you can select Warehouse, Zone or warehouse and Zone. This field is used to determine the output of the report. For example, if you select Warehouse, one line is printed for each warehouse. If you select Zone, one line is printed for each store zone. If you select Warehouse and zone, one line is printed for each warehouse and store zone combination.

Exclude blocked locations: When this check box is selected, the report will not include capacity for a location that is locked by the inventory blocking feature.

Location type: Select location types to be used as available allowed space. The information on the Location type FastTab is used when you run the Schedule load utilization periodic job in step 2 below. When the current and forecasted capacity is calculated, only location types that are selected are analyzed.

Note: The setup only needs to be created once.

2. Run the Schedule load utilization periodic job.

Open Inventory and warehouse management > Periodic > Schedule load utilization.

Figure 3

Master plan: Select the master plan that you want to use for space utilization calculations.

Note: the warehouse manager can shift to another master plan at any time. This is useful in order to determine how the space utilization will look if the planning team decides to change to another plan.

Number of days: Enter the number of days that you want to project and analyze warehouse space utilization for in the future. The current report shows space utilization for 10 days in the future.

Space utilization: Select the space utilization configuration to be used in combination with the number of days and the master plan that is selected in step 1.

Click OK to generate data for the report.

Use the options on the Batch tab to schedule the generation of data for report as a batch process. Normally the batch process is set to run automatically once a day after the master planning has been completed.

3. Analyze the space utilization information (generated in step 2).

As mentioned previously, the report can be viewed from the warehouse manager’s role center (out-of-the-box), or from the Dynamics AX client. This description is based on Dynamics AX 2012 R2 client.

Note: To be able to view the report from the warehouse manager’s role center page, the configuration and generation of data in step 1 and 2 must be completed.

Complete the following setup to run the report:

Open Inventory and warehouse management > Reports > Analysis > Warehouse load utilization.

Figure 4

Show by: Use this field to determine how the rows of the report are displayed. If you select Site, one row is printed for each site. If you select Load unit, the Storage load field on the Space utilization setup template is used to determine how the rows are printed (Warehouse, Zone or Warehouse and Zone). If you select Site, a report will be generated on the site level where each site can contain load units of the types Warehouse, Zones, and Warehouse and zone.

Site: Select one or more sites.

Load unit: When one or more sites and a space utilization setup are selected, load units are displayed for all the sites that are selected under Site. The Load unit field only applies if the Show by field is set to Load unit and the Space utilization setup field is selected. The options in the Load unit field varies based on the option selected in the Storage load field for the current space utilization setup. For example, if storage load is set to Zone, a list of store zones is displayed in the Load unit field.

Load type: Indicate if the report percentages should be calculated and viewed using pallet, volume or weight.

Space utilization setup: Select the space utilization setup that should be used for the report.

Click OK to run the report.

Example of a generated report

Figure 5

In the example above, the report shows what site we are looking at, what load units have been selected, and what load type we are using.

The report is generate by a load unit combination of warehouse and zones as specified in the selected warehouse space utilization configuration. The combination of warehouse and zones basically means that the warehouse capacity is divided by a unique combination of warehouse and zone. In this example, the warehouse manager can monitor space utilization for each zone and, at the same time, identify the warehouse of the zone.

If there is an intersection between zones and they share the same location in one warehouse, they will automatically be grouped in one single load unit and capacities for the intersections are not counted twice. In the example, the load unit on warehouse WH1 combines two zones, Z1 and Z2, due to an intersection.

When looking at the table columns, the column to the far left is the space utilization situation by the end of the current day. The other columns represent the future with increments of one day each. If a load unit exceeds the maximum space available, the color of the cells turns red. This will happen if, when all transactions are conducted on a particular day, the total available space on the load unit is less than what is needed to store the goods by the end of the day.

Every single table cell can be clicked regardless of the color. The color indicates when and where there is or will be a problem with space utilization.

When one cell is selected, a new report is shown with a list of all of the transactions that are to be conducted on that day, grouped by regular issues, receipts, and backlog transactions, if any.

Backlog transactions are transactions that should have been conducted before the current day. Backlog transactions are not displayed for each cell in the report, but if any backlog transactions exist it will be indicated by an icon for the particular load unit. If you then select the icon, a report with list of backlog transactions will be generated.

Transactions that occupy the largest part of the space are shown on top in the detailed view of the report. This helps the warehouse manager identify transactions that must be accommodated or moved to another date in order to avoid space utilization problems.

Example of a detailed report view

Open this view by clicking a cell in the report:

Figure 6

A warning icon is displayed for items that are part of the transactions but which cannot be calculated correctly due to insufficient setup information as presented on Figure 5.

If you select the warning icon, reports will be generated with information about the setup that must be completed in order to calculate transactions correctly.

There can be may be many reasons why space utilization calculations cannot be completed correctly for all transactions.

The yellow warning icons indicate if the numbers of the report can be trusted or not. By selecting a warning icon you can then identify the missing setup, correct the problem, and rerun the report again.

Warning icons will be shown in the following situations:

· Warehouse item setup is not correct.

· Pallet conversion has not been set.

· The Weight of an item has not been specified.

· The volume of an item has not been specified.

· A fallback warehouse has not been specified.

Example of a missing setup report

When you select a warning sign, the report representing the Deficiency types in data setup t might look like this:

Figure 7

From this report it appears that on Warehouse WH3 we have two items missing pallet conversion and two Items missing warehouse item setup.

These missing setups need to be corrected and after warehouse space utilization report can be selected and warning icon wil not be there anymore, wich means that we can trust calculations and numbers presented in a report.

Demo of the Warehouse space utilization

Warehouse Space utilization report in Dynamics AX 2012 R2

Warehouse space utilization report on Youtube

Understanding the product validation process in Dynamics AX 2012

Ievgenii Korovin — Thu, 06 Dec 2012 19:09:00 GMT

Introduction

Dynamics AX 2012 provides a new feature that allows you to validate the released product setup and ensure data integrity and overall process readiness. This feature is useful for managing master data and we expect it to be widely used by our partners and customers in order to support the product data life cycle processes, engineering change, approval workflows etc.

Retrospective look at the previous versions of Dynamics AX

Traditionally, the system stores item definition data in one main table (Invent Table). Every time a user creates a new item, a set of mandatory fields must be addressed in order to successfully save the new item definition. This approach looks simple and logical; however, the item definition requires a good overview of all the mandatory settings. Insights into these settings are usually divided between users in multiple departments in an enterprise organization and it usually requires quite a lot of work to coordinate this information. A common approach in order to ensure consistency is to create shared and approved item templates which are strictly controlled and can be re-used across enterprises for the initial item data creation.

Another inconvenience of requiring users to address all mandatory fields relates to in-flexibility since it makes users working with the system less agile and process driven. Say, for example, that an engineering department wants to create a new product definition in the ERP system. There is an urgent need to send product descriptions to the external vendor for the localization and for the creation of marketing materials for the upcoming sales campaign. However, users cannot simply create items with the settings to control the external vendor relation processes. In this case, ALL settings must be defined which includes setup of financial accounts, inventory tracking, reservation rules etc.

Item master data setup enables the core business processes within ERP, so it’s not a surprise that we see a number of partner customizations in this space. If, for example, a company wants to retire an item, the company must ensure that the item cannot be produced or sold any longer within the organization. At the same time, it should be still possible to handle customer returns based on the existing customer agreements. When the item master data setup changes, one would expect some validation mechanism to ensure that the new item master data state is consistent with the user’s expectation. Unfortunately, there is no single centralized place to support such item validation process, so our partners and customers have to introduce such capabilities by themselves.

Why are there no any mandatory product master data fields in Dynamics AX 2012?

With the introduction of the Product Information Management (PIM) module in Dynamics AX 2012 we get an opportunity to remove some of the above described boundaries and to build a more flexible and process-oriented solution. There are a couple of key differences for users who deal with products compared to the previous versions of Dynamics AX:

No mandatory fields

When you create a new shared product definition, the only property that you must provide is a product number (product ID). Once a new shared product is created, you can continue with the master data setup.

Figure 1 Create new product

When you release a product to the given legal entity you need not set any company-specific properties.
When you create a new released product from a legal entity, the only property you have to provide is the product number and the item number. Usually those IDs are bound to the automatic number sequence, so you can create a new released product definition with just one click with the mouse.

Figure 2 Create new released product

Once you have a basic product or released product definition in place, the system allows you to continue with the various master data setup processes such as to define translation, attach documents and images, sync product data to an external solution via existing product-item services etc.

When can my product be used for procurement, sales, and production?

This is a valid question at this point because if there are no mandatory fields anymore, how do I know when my product can used for procurement, sales, production, quotation …?

In order to answer this question let’s focus on process readiness and how the system behaves in Dynamics AX 2012.

There are hundreds if not a thousand different business processes which can be controlled by product master data. The total number of those processes varies from industry to industry and the processes vary a lot based on the end customer business requirements. It’s hard, if not impossible, to predict or know in advance which product master data is required in order to enable each unique business process.

Therefore, in Dynamics AX 2012, every single business process has to, metaphorically speaking, verify all required product master data. In other words, if some master data is not set for a given business process, the system will throw an error and the end user must set the master data before the system can continue.

Example

A user creates an inventory movement journal. The system tries to retrieve all inventory dimensions that should be tracked for the product. If the setup is not complete, the process will fail since the basic pre-requirements are not fulfilled.

Figure 3 Create journal line for product with missing setup

Understanding a product validation feature

The new product validation process has been introduced in order to help assess the overall product data readiness for the main business processes.

As mentioned before, it’s impossible to predict what master data will be required for what process in the system. However, we can definitely focus on the setup that is most essential in order to cover key processes in Dynamics AX 2012.

The product master data validation logic can be triggered from released product list pages and released product details forms. The functionality will verify that the following essential fields are specified for the released product:

Product storage dimension group
Product tracking dimension group
Model group
Item group

In addition to the previous fields list, the following essential fields have been added to the validation logic to cover the Process Industry for Dynamics AX 2012 Feature Pack:

Catch weight unit setup for the catch weight enabled products

All these settings can be set on the released product list page which prevents the need to navigate across different places and modules in the system. Users can then leverage one single form to complete all the setup that is required.

When, why and how to run a product validation

We strongly recommend to always validate the product data setup to ensure overall process readiness. This process helps to prevent last minute issues for end users.

Example

A product manager releases all product data to a legal entity.
The product manager uses product templates to address the main field values and to execute the validation logic.

You can run validation logic for one or for multiple products and you can apply a product template for multiple products at the same time.

Figure 4 Run a product validation function for multiple products

Tip: Read more about how to use product templates: previous blog post

How to customize the product validation process

The EcoResProductValidationService class holds all the product validation logic. The class gets the number of released product references as an input, runs the validation logic, and reports all validation errors in a standard infolog message.

static void runValidationForReleasedProducts(Args _args)

{

    container                           packedProductsPerCompanyInfo;

    InventTable                         inventTable;    

    EcoResProductValidatonDataContract  dataContract = new EcoResProductValidatonDataContract();

    EcoResProductValidatonService       service = new EcoResProductValidatonService();

    

    // Find all released product with the itemId pattern like 'production*'

    while select itemId from inventTable

            where inventTable.ItemId like 'production*'

    {

        packedProductsPerCompanyInfo += [[inventTable.ItemId]];

    }

        

    if (conLen(packedProductsPerCompanyInfo) > 0)

    {

        // Create service operation data contract class and pass all released product references

        dataContract = new EcoResProductValidatonDataContract();

        dataContract.packedProductsPerCompanyData(SysOperationHelper::base64Encode(packedProductsPerCompanyInfo));

  

        // Run validation logic

        service.validateProducts(dataContract);

    }

}

Assume that we need to make sure that all items are produced with a production order for the current manufacturing company. The existing EcoResProductValidator can easily be extended to accommodate such a validation check:

Figure 5 Customization example

Summary

Managing product master data can be a complex and challenging task. We hope that the product information management features in Dynamics AX 2012 can help your organization to deal with some of these challenges. The product validation process is there for you, so please learn how to use it and enhance it if you need to.

Thanks for reading.

Relocation transports – a new pallet transport type in Microsoft Dynamics AX 2012 R2

Lennart Conrad — Tue, 04 Dec 2012 10:23:54 GMT

By Bibi Christensen, Per Lykke Lynnerup & Lennart Conrad

Introduction the Relocation Transport

A new type of pallet transports called Relocation transport has been introduced in Microsoft Dynamics AX 2012 R2.

The new pallet transport type can be used to move items on a pallet from one warehouse location to another warehouse location even when you have transactions that are physically reserved against the quantity on the pallet. With this added functionality the common warehouse activity of moving pallets between locations is supported more efficiently.

When the transport is created, two sets of inventory transactions are created:

- Issue transactions with the issue status Reserved physical that will reserve items on the pallet at the from-location.

- Receipt transactions with the receipt status Ordered on the to-location.

When the transport is created, existing transactions that are Reserved physical on the pallet at the from-location will be updated to Reserved ordered on the to-location. If there are any transactions that are Reserved physical and fixed against the from-warehouse or from-location, and any of these are changed, the transport cannot be created.

If there are any transactions with the pallet id that have status Arrived the transport is not created. This is typically the case if a transport already exists for the pallet.

Transactions with the pallet id that have an issue status of Quotation Issue, On order, Reserved ordered or a receipt status of Ordered are not updated. In this case the from-location and pallet remains the same on these transactions.

Once the transport is completed Reserved ordered transactions on the to-location will be updated to Reserved physical.

How to set up and use the new transport type

The new transport type is set up the same way as the existing transports.

In the Inventory and warehouse management parameters form you can set up the priorities for pallet transports.

· Click Inventory and warehouse management > Setup to open the Inventory and warehouse management form.

In the Forklift form you can specify the forklifts that should handle the relocation transports.

· Click Inventory and warehouse management > Setup > Inventory equipment > Forklift to open the Forklift form.

When you move a pallet, you can create the relocation transport.

A check box is added to the Move pallet form and when the checkbox is selected, a relocation pallet transport will be created.

· Click Inventory and warehouse management > Setup > Inventory equipment > Pallets > Functions > Move pallet to open the Move pallet form.

New code APIs and thebackporting of feature to the previous releases

The API to create a relocation transport from code is quite simple; You basically just call one line of code:

WMSTransport::createRelocationTransport(wmsPalletToMove,newWMSLocation);

It has also been decided to port this new functionality to Microsoft Dynamics AX 2012 and it will be available as part of AX 2012 RU5 and with KB2770782.

What’s New for Microsoft Dynamics AX 2012 R2 for WMS

Per Lykke Lynnerup — Fri, 30 Nov 2012 12:16:00 GMT

This blog post describes some of the enhancements to the Warehouse management (WMS) functionality that have been implemented in the R2 release after the launch of Microsoft Dynamics AX 2012 (RTM).

Shipment list report printed in a batch job at shipment update

By using outbound rules for a shipment and by setting up automatic printing of the shipment list you can have the shipment list report sent to a batch job.

Make sure you assign a printer setting that uses a paper printer for the batch job printing.

You can define the printer setup from Inventory and warehouse management > Shipments > Printer setup > Shipment list:

New uses of the location type Picking location

The location type Picking location can now be used as part of the item arrival process and for pallet movements.

· Item arrival: Locations of the type Picking location are now available in the registration process and you can apply a picking location on a journal line in an item arrival journal even if the inventory item’s warehouse item setting does not use a picking location.

· Pallet movements: When you use the Move pallet functionality, you can now select a location type of Picking location even though the location is not an item picking location.

Relocation pallet transport

In AX 2012 R2 you can create a relocation pallet transport and then assign the actual pallet transport processing to a warehouse worker.

You can access the new functionality from the Move pallet menu item via Inventory and warehouse management > Setup > Inventory equipment > Pallets > Functions:

You can then process the pallet transport from Inventory and warehouse management > Common > Pallet transports:

Detailed blog post on the relocation transport

A detailed blog post about the implementation of the relocation pallet transport will follow.

Shipment template enhancements for joint shipping

An option called Grouping inventory reference has been added to the Joint shipping field in the Shipment templates form.

You can access the Shipment templates form from Inventory and warehouse management > Setup > Distribution > Shipment templates

When the Grouping inventory reference option is selected, output orders for withdrawal of kanbans are grouped based on the ID of the parent manufacturing kanban. If you use this option with output orders that do not reference kanbans, the grouping reference is the same as the reference for the output order.

Troubleshooting the product release process

Ievgenii Korovin — Fri, 05 Oct 2012 11:58:00 GMT

The product release process is part of the product setup in Dynamics AX 2012. Every single product must be released to a legal entity before the system allows you to procure, sell, or produce it.

For more details, about how to release products, product masters and product variants, see: Release products.

In some cases, the product release process can fail to release products due to inconsistencies or missing setup. In this post, we will take a look at system capabilities that allow you to troubleshoot the product release process and take action to resolve any issues.

Quick overview of the product release process

The product release process allows you to release multiple products and product variants or, in other words, make multiple products available in various legal entities. This action can be executed from various list pages and detail forms.

If you work with a small number of products, it’s a very quick process to release them to a single legal entity. But in the case of, for example, a new site deployment, it can be a time consuming task to release all products to the new legal entity.

For this scenario, we recommend using a server batch job to execute the product release process in order to avoid extra load on the system during work hours. If issues arise during a batch job execution, the release session concept in Dynamics AX 2012 will help provide you with information about any issues or conflicts. Based on the system reports you can then resolve the issues or conflicts that occurred during the batch job execution.

The release session concept and the release process

The release session is a database persisted object which groups all products that should be released to legal entities. The release session object is automatically created behind the scene when you request to release one or more products.

If all products have been successfully released without any issues, the release session is automatically deleted and no further actions are required for the release product request. However, if issues occurred during the release process, then the release session will remain open with all the individual products that failed during the process. This allows you to troubleshoot the release process, fix the issues and repeat the action without having to select all products and legal entities one more time.

Example

Assume that a product manager must release a new collection of products to a new legal entity. When he executes the release process, various errors are reported by the system. The product manager can now navigate to the most recent release session, troubleshoot the issues and repeat the entire release action from there.

Open product releases list page

All open release sessions can be found under Product Information Management -> Periodic -> Open product releases list page. This list page contains all release sessions where something went wrong. You can filter all sessions by the user ID and release session time stamp to see all the products and product variants that the system could not release to the legal entity.

You can click the View Infolog button to view details about the issues with the specific product or product variant. This is a great way to figure out what went wrong and why.

Let’s take a look at some issues that commonly occur during the product release process:

· The product already exists in a legal entity.

o This can happen if you release a product for the first time by mistake and then release the product again after having made changes to it. This action will create a conflict and one way to solve the conflict would be to delete the released product from the legal entity, go back to your product definition, make the required changes, and then release the product again.

· A different product already exists with the specified item ID.

o This might happen due to an issue with the number sequence for the item number or because the item number has been defaulted from the product number and by coincidence, another released product exists with the same item number. To solve this issue, you must use another number sequence or rename a product with a different product number value. For more information about the product and item numbers, read this blog post: Product Number and Item Number in Dynamics AX 2012

· The product variant could not be released

o This usually happens when the inventory dimensions (InventDim) number sequence setup is missing in the legal entity. Make sure that the number sequence is properly set up. For more information, see Set up number sequences.

When you have investigated and resolved all issues, you can repeat the release action by clicking the Release product button. For more information about the Open Product Releases List Page, see: Open product releases (form).

Working with the release session from the code

If you have access to the code, you can also release a series of products without using the user interface. The following code example demonstrates how the release session can be created and how it should be used for release purposes:

static void releaseProductToCurrentLegalEntity(Args _args)

{

    EcoResProductReleaseSessionManager  productReleaseSessionManager;

    EcoResProduct                       product;

    CompanyInfo                         companyInfo;

    

    companyInfo = CompanyInfo::findDataArea(curext());

    

    product = EcoResProduct::findByDisplayProductNumber('myProduct');

    

    ttsBegin;

    

    // Create a new release session

    productReleaseSessionManager = EcoResProductReleaseSessionManager::newReleaseSession();

   

    // Add a product to the release session

    productReleaseSessionManager.addProduct(product.RecId);

    

    // Add a legal entity where tne product should be released to 

    productReleaseSessionManager.addLegalEntityForAllProducts(companyInfo.RecId);

    

    // Release all products within the current session to the specified legal entity

    productReleaseSessionManager.execute();

    

    ttsCommit;

}

Another approach would be to use the existing Product-Item data management services. For more information, read this blog post: Product-item data management services.

Summary

The product release process is an important concept in Dynamics AX 2012. We hope that the tools and functionality of the system sufficiently and effectively support your business process. Please leave any feedback or suggestions here or provide the information via our AX SCM requirements group: AX SCM requirements.

Thank you for reading this!

Evgenij Korovin

Inventory blocking

Volodymyr Giginiak — Fri, 28 Sep 2012 07:49:53 GMT

Overview

The possibility to prevent items currently in your warehouse from being used in standard processes has often been requested. In previous versions of Dynamics AX this was primarily possible with the quarantine order functionality. However quarantine orders require items to be (logically) moved to a separate quarantine warehouse.

So the new blocking functionality is designed to allow items to be blocked at their current location.

The first requirement is to be able to block some of the current on-hand. During the analysis for the new functionality it was discovered that in addition there is also a need to block some incoming goods until quality inspection is complete.

The second requirement is that the current on-hand is always correct – both from a quantity point of view and from a value point of view.

The ideas behind it all

For most types of issue transactions – like sales orders – it is possible to point out specific on hand and use the physical reservation to reserve/block current on-hand for the specified transaction. To ensure that items on-hand are blocked we create a set of issue transactions and use the same physical reservation mechanism. This set is identified by a unique InventTransId value.

To ensure that the expected on-hand is always correct we create a set of expected receipt transactions. The date when the items are expected to be released back to inventory can be modified by the user. This ensures that master planning can correctly considers items currently blocked.
The set of expected receipt transactions is identified by another unique InventTransId value.

We have defined a new reference type for the inventory transactions related to blocking called “Inventory blocking”.

This screen shot shows the transactions for a blocking entity where a single piece is being blocked

The corresponding on-hand form in a scenario where 1000 pieces are on hand is shown below

The inventory blocking functionality intentionally doesn’t have any scrap functionality – or other means of deducting some of the blocked on-hand. If you want to allow for such functionality you need to combine the blocking functionality with other processes for issuing items.

As the inventory blocking functionality never consumes or moves any on-hand there is no need to ever pick, pack or invoice any of the issue transactions (which would also require updating of the receipt transactions). When the items are no longer to be blocked the quantity is simply reduced or the entire blocking entity is deleted along with all the transactions associated.

Manual inventory blocking

Manual inventory blocking – as opposed to quality order blocking – is the process where a user directly creates a new inventory blocking entity and specifies quantity and inventory dimensions.
The form for maintaining inventory blockings can be found in the “Periodic” section under “Inventory and warehouse management”.

When saving the new inventory blocking entity inventory transactions are automatically created which makes the physical reservation and represent the release back to inventory.

Quality order blocking

A quality order can be created either manually or automatically as part of the receipts process. For both cases an inventory blocking entity is automatically created – just as for a manual inventory blocking entity. However as the received items may be part of a linked chain (marked) of transactions the blocking transactions are inserted into this chain upon creation and the original chain is recreated again upon release from blocking.

Author: Kim Moerup

Using product templates in Dynamics AX 2012

Ievgenii Korovin — Sat, 22 Sep 2012 20:21:00 GMT

Introduction

Dynamics AX 2012 provides a new feature that allows you to create and apply product templates to speed up the product creation process. We believe that this is one out of hundreds of small hidden features that will delight our partners and make our end customers more efficient.

Item record templates in the previous version of Dynamics AX

Traditionally, the Record Templates functionality plays an important role in the user experience during a creation process of key master data entities such as items, customers, and vendors. The system allows you to create a copy of any record in the grid and use it to create a new entity of the same type. This approach helps to ensure data consistency and to establish enterprise process control.

If, for example, you want to create a new engineering component, you can apply a predefined and approved item template that contains data which has been carefully gathered across different departments such as account setup, reservation rules, and dimensions tracking.

Understanding the product templates in Dynamics AX 2012

In Dynamics AX 2012, there is a rich and normalized data model behind key entities such as products and released products. This means that when you create a product, multiple tables get updated behind the scene. Using a template will help you create uniform product master data in a more intelligent manner.

The product template feature in Dynamics AX 2012 takes into account the new data model by extending an old limitation where the template was only associated with one record in one table. Now, the template can build records from multiple tables and records.

Create product templates in Dynamics AX 2012

To create a new product template, navigate to the Released Product Details Form -> Action Pane -> Template menu. Here you can create a snapshot of the current product entity and save it as a shared product template or as a personal product template.

Work with the shared product templates

You find the shared product templates under Home -> Area Page -> Setup -> Record Templates.

You can edit a shared product template at any time. This means that if, for example, you want to use a different counting group for a given predefined product template, then you do not need to create a new product template. You can just update the existing template.

Also, the system allows you to modify the shared product template from the Product details form. This makes it easy to identify all the fields that you want to change.

Apply product templates

Product creation form

You can select a product template when you create a new released product. Key fields in the product structure are populated by the template.

Once you have selected a product template, you can click Show more fields in order to view the important field content that has been provided by the template. You can overwrite template values which are displayed on the form.

Please note, that you can view only the most essential fields in this dialog. Rest fields from the template will be automatically applied during the product creation.

Released Product Details form

You can apply and try to re-apply a template from the Released product details form. Every time you apply a template, the system tries to update the various fields of the released product entity.

If you have applied a wrong template by mistake during product creation you can easily re-apply the proper template to the same product, rather than delete and create a new product. However, the system runs regular validation logic for all updated fields so if a released product is already in use, any attempt to re-apply the template will fail if the product contains data that don’t match the template.

Assume that you have a stocked product with transactions. You try to apply a new version of the template to the product. However, on the template, the Stocked Product policy is not selected which means that products based on the template are non-stocked. In this case, the system will fail during the apply template action. This is because a stocked product with existing inventory transactions cannot be converted to a non-stocked product.

Apply a product template to multiple products in one go

When you release a bulk of products in a legal entity, you can apply a template all the products in one go rather than one by one. From the main Release product list page, you select the products where you want to add the template and click Apply template.

Product templates in Dynamics AX 2012 Feature Pack

As you probably know, the recent feature pack contains new, exiting capabilities within retail and process manufacturing industries. And as you might expect, the product template functionality has been extended to accommodate key product data for those industries as well. You can, for example, create and re-use a template that stores retail-specific released product data.

Summary and some thoughts for the next releases

The product master data creation process is an essential part of any ERP product. Going forward we will do our best to make sure that the system offers more intelligent ways to simplify and streamline the product data creation and maintenance processes.

Please let us know if you have any specific suggestions on how we can improve the product in this area. We encourage you to join the AX SCM requirements LinkedIn group to either let us know what requirements you see in the field or to answer polls that we setup to gather feedback or by setting up your polls/discussions.This is a great way for you to influence the product direction.

Thanks for reading!

Evgenij Korovin

Avoid index length issues with InventDim

Kim Moerup — Tue, 11 Sep 2012 12:51:00 GMT

In Microsoft Dynamics AX we use indexes to ensure uniqueness.
An example of this is the DimIdx index in InventDim, where all dimension fields are included to ensure that only a single record exists for a given set of dimensions.

However, the SQL Server has a limitation of 16 fields in an index.
With the first versions of InventDim (which was introduced in Axapta 2.0) this was rarely a problem since only a few dimensions where shipped out-of-the-box.
So partners and customers could still add more dimensions. Over time, numerous dimensions have been added in the standard version and in country specific solutions.
As a result, we are now very close to the 16 field limit. With the Dynamics AX2012 Feature Pack and Russian functionality installed we have 14 fields in the index and more to come in future releases.

We have received an increasing amount of questions about how to get around this issue so we have implemented a solution which allows you to add custom inventory dimensions and still have the uniqueness validated and enforced.

In our investigation of possible solutions we have tried to find a balance between simplicity, maintainability, and performance.
What we found to be the best solution can be described as follows:

- Introduce a new field based on the Sha1HashCode data type.
- Remove some of the least used dimensions from the DimIdx index and add the new field instead. The removed fields must be hashed in the new field during the insertion.
- Calculate the hash and use it in the findDim method when looking for an existing dimension.
- Create a new InventDimIdAllDimensions field in the InventSumDeltaDim table (I guess the name says what it contains) and replace all the dimension fields in the TTSItemCheckDimIdx index with this new field.

This solution will be available in an upcoming release of Microsoft Dynamics AX so if you cannot wait for this release, feel free to be inspired by our findings – hopefully it will also make it easier for you to upgrade your data.

An AX environmental process map in detail

David M Probst — Tue, 11 Sep 2012 12:10:47 GMT

I recently reviewed the new training material for the AX2012 version of the Environmental dashboard (EMS). A little late in the process I realized that the details on the Environmental process map were a bit insufficient for this feature. I wanted to...(read more)

Import vendor catalogs: from setup to importing a sample catalog – Part 2 (Importing a sample catalog)

Vanya Lebedev — Sat, 08 Sep 2012 22:23:00 GMT

The previous blog post in this series gave an overview of setting up AX 2012 to enable the Import vendor catalogs functionality. Now it’s time to see how to produce a sample CMR (catalog maintenance request) file and import it into AX using both AX Windows client and the Vendor self-service portal in Enterprise portal.

Create a vendor catalog

First of all a vendor catalog needs to be created.

Go to Procurement and sourcing > Common > Catalogs > Vendor catalogs.
Create a new record.
Select the vendor in the vendor field.

You can enable/disable the catalog for auto approval by clicking the corresponding button in the action pane. This flag can be used to setup workflow automatic actions.

Create a sample catalog maintenance request (CMR) file

CMR file is an XML file which contains the information about the products which are available for purchase from the vendor. You can use the CMR file to create a new catalog, replace an existing catalog, or modify an existing catalog. In order to create a sample CMR file you need to generate a catalog import file template first.

Generate a catalog import file template

The catalog import file template is an industry-standard XSD file that you use to create a CMR file for vendor’s products. In order to create the XSD file you need to:

Click Procurement and sourcing > Common > Catalogs > Vendor catalogs.
On the Vendor catalogs list page, double-click the catalog that you want to work with.
To download a current catalog import template (XSD file), in the Update catalog form, on the Action Pane, on the Catalogs tab, in the Related information group, click Generate catalog template. Select one of the following options:

Procurement category – Generate a catalog template that includes the procurement categories in which the vendor is authorized to provide products.
Commodity code – Generate a catalog template that includes industry-standard commodity codes.

In the Save as dialog box, select the location where you want to store the catalog file template and save the file.

Generate a sample CMR file

One thing to note about the catalog import template XSD file is that for each procurement category where the vendor is approved there will be a separate product definition with a separate set of attributes so it is important to use the current version of the XSD file for producing the sample CMR file. In order to create a sample CMR file you can:

Open the XSD file in Visual Studio.
Go to the Schema explorer view.
Right click the Products node.
Click the Generate sample XML item.
Modify the auto-generated contents with the valid data: vendor name, product name, price and other attributes. Some of the attributes like product name can be filled with any string value. Other attributes (like currency) will only accept a fixed set of values which can be found by navigating the XSD file.

A sample CMR file will typically look like the one below:

<?xml version="1.0" encoding="utf-8"?>

<VendorCatalog VendorName="CatImp2" LoadDate="2012-01-01T01:01:01+01:00" ProductClassification="Procurement Category" xmlns="http://dax.com/vendorcatalog">

  <Product xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:type='Accessories' Delete='No' ProductCode='ImpCatVend2_1' ProductSearchName='ImpCatVends2_1'>

    <PriceInformation>

      <Price Currency='USD' UnitOfMeasure='Pcs' Value='5000'></Price>

    </PriceInformation>

    <ProductNameAndDescription>

      <NameAndDescription>

        <Description>ImpCatVends2_1</Description>

        <Name>ImpCatVends2_1</Name>

        <Language>en</Language>

      </NameAndDescription>

    </ProductNameAndDescription>

    <ProductAttributes></ProductAttributes>

  </Product>

</VendorCatalog>

Upload the CMR file using AX Windows client

Having generated the sample CMR file you can proceed with the import.

Click Procurement and sourcing > Common > Catalogs > Vendor catalogs.
On the Vendor catalogs list page, double-click the catalog that you want to work with.
In the Update catalog form, on the Catalog file history tab, click Upload file.
In the Upload file dialog box, browse to the location of the CMR file that you created.
Enter an effective date and an expiration date. These dates define the date range in which the pricing for the products in the CMR file is valid.
Select one of the following update types for the CMR file:

Add updates to the existing vendor catalog
Replace the existing vendor catalog with a new catalog

Click OK to start the upload process for the CMR file.
To view the details about the processing status of the CMR file, on the Catalog file history tab, click Event log.
In the Event log form, the status of the CMR file is updated as the file is processed.
The status of the catalog import will be ”New” (unless an error occurred).
A new XML file will be placed in the catalog import pickup folder. This file is a WSDL message for the CatImpService.create service for which a file adapter-based inbound integration port has been set up previously (see the previous blog post for details). This message contains all the information from the CMR file that we just uploaded plus the WSDL ”envelope”. Find the sample WSDL catalog import message below:

<?xml version="1.0" encoding="utf-8"?>

<Batch>

    <Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">

        <Header>

            <Action>http://schemas.microsoft.com/dynamics/2008/01/services/CatImpService/create</Action>

        </Header>

        <Body>

            <MessageParts>

                <VendorCatalog>

                ...

                </VendorCatalog>

            </MessageParts>

        </Body>

    </Envelope>

</Batch>

Process the CMR file

After the WSDL message has been placed in the catalog import pickup folder the catalog import service needs to be called. The service will copy the data from the CMR file to the vendor catalog staging tables.

Run the AIF vendor catalog import processing job which has been setup previously (see the previous blog post for details).
After you do that the status of the catalog import will change to ”In progress”.

Approve the catalog import

In this example we will assume that the workflow has been set up for manual approval, i.e. there are no automated actions setup in the Catalog import product approval workflow.

After the status of the catalog has changed to ”In progress” the workflow bar will appear in the top of the Vendor Catalog form.
Click the submit button.
Run the workflow processing job (see the previous blog post for details).
Refresh the Vendor Catalog form.
The status of the catalog import has changed to ”Pending approval”.
Click the Details button on the Catalog file history fast tab.
Select all products and click the Actions > Approve button in the workflow bar.
Run the workflow processing job.
The status of the products has changed to ”Approved”.
Go back to the Vendor Catalog form.
The status of the import has changed to ”Succeeded”.
After the imported product candidates have been approved they are added to the product master.
After the product candidates have been approved they can be released to legal entities by clicking the Release approved products button on the Vendor Catalog form.

Vendor self-service portal (VSS)

Some of the actions described above can also be performed using the Enterprise Portal (EP). In order to run this scenario it is required to associate the user with a vendor.

Create an AX user for the vendor party

First of all you need to associate an AX user with the vendor account. Large companies will probably take advantage of more complicated workflows available in AX to perform this operation (see the Vendor Management and Collaboration in Microsoft Dynamics AX 2012 training materials for more details). Smaller companies can utilize the simplified process described below.

Go to System administration > Common > Users > Users.
Grant the user that you want to associate with the vendor the Vendor (external) role.
Click the Relations button in the action pane.
Set the Relation type = Vendor and select the vendor which you want to enable for uploading catalogs using the Vendor portal.

Upload the CMR file using the VSS portal

After setting up the user-vendor association you can proceed with opening the Vendor portal and uploading the CMR file.

Go to System administration > Common > Users > Users.
Select the user that you have configured to represent the vendor party.
Click the profiles button.
Click the view role centers button.
In the enterprise portal make sure that the correct user is active (if not click the login as a different user button and login as the user which has been configured to represent the vendor party).
If you logged on as an admin or have multiple vendors associated with your account then make sure that the correct vendor association is active. The current vendor association can be changed by clicking the vendor dropdown box in the top right corner of the screen.

Now you can navigate to Vendor portal > Catalogs and upload the CMR file. I will not go into more details since the vendor catalogs form in the enterprise portal is similar to the vendor catalogs form in AX Windows client.

AX2012 Purchasing with: Advanced warehouse management and quarantine management.

Karina N Jakobsen — Tue, 04 Sep 2012 09:13:00 GMT

AX2012 Purchasing with: Advanced warehouse management and quarantine management.

If it’s ever been an issue for you that no items in Contoso CEU are set up with both advanced warehouse management and quarantine management this information might be useful to you.

Here you get a cheat sheet that you can use to set up Contoso CEU in order to handle an advanced warehouse procedure like the following in AX2012.

Go to Inventory and warehouse management/Setup/Inventory breakdown/Warehouses

· Select warehouse 28.
· Click Inquiries/Inventory aisles.
· Select Aisle 01, and click Inventory location.
· Click New.
·
· Save to create the location.

The above setup indicates that we do not control each location within the quarantine area separately; we just see the entire quarantine area as one location.

Close the form and go to Product information management/Released products and select item 1601

Navigate to the action pane tab Manage Inventory and click Warehouse items

· Click New and add warehouse items for warehouse 28:
·

Save and close

From the detailed item form open the item model group FRP_Pick.

·
· Select the Quarantine management check box and close the form.

This way you enable quarantine management for the item arrival journal lines. You can also set this parameter for individual item arrival journal lines

Now item 1601 is set up with advanced warehouse management and quarantine order, so try the procedure:

Go to Procurement and sourcing/Purchase orders/All purchase orders

· Create a new purchase order for vendor 1001. Accept the default values.
· Create a purchase order line for item 1601.
· Change the quantity to 24 and click No in the dialog box.
·
· Confirm the purchase order

Close all forms.

Go to Inventory and warehouse management/Periodic/Arrival overview

· Find the purchase order and click Start arrival
· Open the item arrival journal and add a pallet ID.
- o You can use the function “Pallet ID”
· The check box “Pallet transport “= selected
· The check box “Check pick location” = cleared
· The check box “Check bulk location” = selected
· The check box “Quarantine management” = selected

Post the journal and close all forms.

The pallet and the item are now recorded in the inbound location and a pallet transport to the quarantine warehouse is ordered.

Go to Inventory and warehouse management/Common/Pallet transport

· Start the pallet transport
· Complete the pallet transport

The pallet and the item are now recorded in the quarantine warehouse and the quarantine order is created.

Close all forms.

Go to Inventory and warehouse management/Periodic/Quarantine order

· Find the quarantine order
· Click Report as finished.
·
· Click OK

The quarantine order is reported as finished and an item arrival journal is created.

Open the item arrival journal that was created.

Click Post

A pallet transport to the warehouse is ordered.

Close all forms.

Go to Inventory and warehouse management/Common/Pallet transport

· Start the pallet transport
· Complete the pallet transport

Close all forms.

Now the flow is completed.

Import vendor catalogs: from setup to importing a sample catalog – Part 1 (Setup)

Vanya Lebedev — Wed, 29 Aug 2012 13:16:00 GMT

We’ve been working on the import vendor catalogs functionality recently and realized that the ramp up time in this area is quite high. There is a lot of information on MSDN and on InformationSource about the topic but there aren’t any documents which would guide you from the initial setup to creating and importing a sample catalog.

Creating and maintaining procurement catalogs that company employees can use when they order items or services for internal use is one of the major tasks in Procurement and Sourcing. This can be done in several ways. Vendor catalog data can be added to the product master manually; the catalog can be hosted externally or it can be imported from a Catalog Maintenance Request (CMR) file. In this blog post I will focus on the last option: importing vendor catalogs. Before reading this blog post I recommend watching the “How to define procurement categories and catalogs – part 3” video on InformationSource.

Vendor catalog import parameters

The first step will be to setup the Vendor catalog import parameters.

Create a root folder where the CMR files will be stored (e.g. c:\temp\CMR).
Click Procurement and sourcing > Setup > Vendors > Vendor catalog import parameters.
In the Vendor catalog import parameters form, in the Root folder path field, enter the location of the root folder that you created for storing CMR files.
The CatalogImportPickup folder is created automatically inside the folder you specified.

Setup AIF

After you set up the vendor catalog import parameters you will need to configure an inbound AIF integration port for catalog import. I will not go into details since the process is very well described in this article.

There are a couple of additional steps which are not mentioned in the article:

1. When setting up the file adapter click the Configure button, mark both checkboxes and specify the administrator user in the lookup. Not doing this will lead to an error during the import.

2. If you can’t see the CatImpService.create in the service selection dialog you can go to the AOT, find the CatImpService under the Services node and click Addins\Register service. The alternative is to go to System administration > Setup > Checklists > Initialization checklist and click Set up Application Integration Framework in the Initialize system group.

You will also need some way of running the catalog import service. Normally this is done by setting up recurring batch jobs responsible for executing business logic through integration ports. To learn more about it read the Configure and start the AIF batch services section of this MSDN article.

This standard approach is intended for production. However it’s not very convenient for testing/learning purposes since the catalog import processing will be done asynchronously and the minimum recurrence interval is 1 minute. So I recommend using the x++ job below which performs the import catalog processing instantly:

static void runAIFReceive(Args _args)

{

    new AifGatewayReceiveService().run();

    new AifInboundProcessingService().run(); 

  

    info('AIF processing done');

}

Setup workflow

The import vendor catalog functionality is leveraging another powerful feature of AX: workflow processing. You are allowed to setup rules for automated approval of vendor catalogs and specify one or more reviewers if manual approval is required. To enable the vendor catalog import functionality it is required to set up two types of workflows: Catalog import product approval (line-level), Catalog import approval (catalog-level).

Catalog import product approval

This type of workflow processes all the products that are included in the CMR file. Completion of all of the individual line-level workflow completes the overall catalog import workflow. In order to create a product approval workflow:

Click Procurement and sourcing > Setup > Procurement and sourcing workflows.
On the Action Pane, click New.
Select Catalog import product approval and then click Create workflow.

General setup

The common catalog import product approval workflow should look like this:

Set up approvers

1. Double click the Catalog import product approval element.

2. Click the Step 1 element.

3. Click Assignment in the action pane.

4. The simplest assignment would be User->Admin.

Set up automatic actions

Automatic actions allow the workflow framework to automatically approve or reject the products in the imported vendor catalog which meet certain conditions. In order to set up an automatic action you need to:

1. Select the Catalog import product approval element.

2. Click Automatic actions in the action pane.

3. Click the Enable automatic actions check box

4. Setup the conditions for auto approval/rejection

There is one type of condition which I would like to focus on. You can specify Product candidate.Price delta as a parameter of the automatic action. The price delta is calculated as a ratio: (new price – old price) / old price. So if you want to make sure that the price delta is within 20% you need to set the condition to Product candidate.Price delta <= 0.2

5. Select the type of automatic action (approve/reject)

Catalog import approval

This type of workflow is used for setting up the rules for approving the whole catalog. When you configure this workflow, you can reference the Catalog import product approval workflow that you configured earlier. The common setup would be to automatically approve the whole catalog import after all the products have been approved:

In the properties of the Vendor catalog lines (products) element you need to reference the catalog import product approval that you created earlier.

Enable a vendor for catalog import

In order to be able to import catalogs for a particular vendor it has to be enabled for catalog import. There are two ways to achieve that

- Click Procurement\Set up\Configure vendor for catalog import

- If you don’t do this you will be prompted if you want to enable the vendor for catalog import when creating a new catalog for the vendor

After you do this a subfolder in the catalog import root folder is created. The name of the folder is the RecId of the vendor.

Inside the folder you will find an archive folder with all the CMR files that have been imported for this vendor. You will also find a folder that is used for importing images of the vendor’s products.

Setup procurement hierarchy

You won’t be able to import products from categories where the vendor is not approved for procurement. To approve the vendor:

1. Go to Procurement and sourcing/Setup/Categories/Procurement categories.

2. Select the category.

Add the vendor to the list of approved vendors in the Vendors fast tab.

Importing a vendor catalog

Now that all the setup is done we are ready for creating a sample CMR file and importing it. We will write about it the next blog post.

Electronic signature in Dynamics AX

David M Probst — Tue, 21 Aug 2012 14:46:00 GMT

Most presentations I have made during the last few years have involved one or more personas. Shannon the machine operator, Lisa the Customer Service representative, Charlie the CEO, Lars the Shop supervisor etc. etc. At a presentation a few years back...(read more)

Improved integration to warehouse management in process manufacturing AX2012

AksheyGupta — Thu, 16 Aug 2012 15:43:34 GMT

Process manufacturing adds multiple capabilities to ensure that the inventory that is reserved is the inventory that meets the customer criteria. This capability is useful for any enterprise irrespective of nature of manufacturing environment.

For instance customer could ask for an inventory batch of chocolate bars with cocoa content between 80 and 100. In addition of course, AX should not ship expired batches or batches that are currently unavailable for picking, shipping etc. In previous versions it was possible to apply these criteria of inventory reservation on sales orders and transfer orders but was not possible to apply these criteria if warehouse management was used to pick, ship, stage & load goods. However AX2012 will take all these requirements into consideration when doing warehouse reservations.

In this post, a brief scenario is used to show how warehouse management reservation now works to ensure that customer criteria are met just like as in case of inventory reservation system.

Consider this on-hand information for different batches of chocolate bars

On-hand info for item WMS:

Create a sales order. Add a line for chocolate bars to the sales order with quantity of 1700. On-hand inventory is automatically reserved. You can see here that reservation is only done on batches that are available, is done in FEFO order and the batch outside attribute range (batch B2, requirement: cocoa content must be between 80 and 100) is not reserved.

Release the sales order line and create an inventory order (output order) which is the basis for shipment.

Create a shipment, inventory order created above will automatically be added to the shipment.

Shipment status is registered at this point. If you look at the shipment lines, you will see 1500 reserved on B1 and 200 on B3. As you can see this is not correct according to the WMS reservation policy because we should first create output transports from bulk locations (location 001-01-3) and then pick the rest from the picking location (002-02-1)

Click Functions-> reserve now, shipment will have reserved status now. If you look at the shipment lines now, you will notice that the shipment is reserving according to the WMS reservation principles (First output transport from bulk locations and the pick the rest on picking locations). So 1500 reserved on B3 and then 200 on B1.

Activate the shipment, complete the pallet transport and picking route.
Key thing to note here is that just like inventory reservation, WMS reservation also picks batch B3 and not batch B2 as it did in previous versions.

Contributors: Johan Hoffman, Akshey Gupta

Installing a stand-alone Dynamics AX 2012 on Windows 8

David M Probst — Mon, 13 Aug 2012 15:20:00 GMT

It took a little while but finally I managed to get my AX up and running on Windows 8. For those of you who want to do the same, here are a couple of pointers: SharePoint 2010 is as tricky as it was on Windows 7. This KB article will help out: http...(read more)

Product Number and Item Number in Dynamics AX 2012

Ievgenii Korovin — Mon, 13 Feb 2012 09:14:00 GMT

What is the purpose of the product number?

This is a common question since the product number is a new concept in Dynamics AX 2012. The main purpose is to have a single, unified identification of a product throughout the entire organization.

In addition to the product number you have a legal entity-specific item number. The item number supports the need to be able to identify products based on numbers that make sense to users within a legal entity.

In this post we will describe the purpose and the use of product numbers and item numbers.

Product number

The new Product information management module in Dynamics AX 2012 allows users to create and manage shared product definition data in a centralized and consistent way. For companies that run a business across multiple legal entities, the concept of shared products can be a help to manage product master data and establish company-wide data governance processes.

For example, consider a company that wants to ensure that the same product data is consistent across different manufacturing plants or retail stores.

The product number is the main product identification (ID) in the system. It helps users to identify or to search for the same product instance across the entire organizational structure. The product number serves as a common reference for company-wide operational and reporting purposes.

In Dynamics AX 2012, a product has to be released to a legal entity before it can be included on a transaction, line or before orders can be created against the product. The release process allows users to control which products become released products in which legal entities.

Item Number

The item number (or item ID) is the legal entity-specific identification of the released product. When a product is released to a legal entity, the item number is aligned with the product number, unless a number sequence exists for the item number in the legal entity.

The system does not validate whether the values are identical or not. So in cases where a specific item number is required in order to identify products within an organization, the item number can be renamed.

For example, some manufacturing companies include the unit of measure in the legal entity-specific item number. In cases where items are consolidated between a legal entity and an acquired organization, it would also be necessary to rename the item number in the legal entity.

Intercompany supply chains and consolidated reporting

For intercompany chains and for consolidated reporting purposes the system always uses a product reference. The system does not take any dependency on the legal entity-specific item numbers. Instead, a shared product reference is used to map intercompany demand and supply during master scheduling or to establish the relationship between the intercompany sales and purchase orders.

Please note that in previous versions of Dynamics AX, the system uses the concept of a company item to allow for intercompany trade between two parties. All items in one company have to be mapped manually to every item in the other company before the intercompany order can be created. With Dynamics AX 2012 there is no longer a need for manual mapping. As long as a product is released to both companies, all intercompany chains can operate smoothly.

Recommendation regarding intercompany trade

As a general guideline, we recommend that you avoid using the item number for any purposes that are related to intercompany trade. Instead, aim to use the product number for any data consolidation across multiple legal entities.

Please note that in previous versions of Dynamics AX, the system uses the item number as the main reference for entry of orders such as sales orders and production orders. The system also uses the item number to identify inventory transactions. This is unchanged in Dynamics AX 2012.

Ievgenii Korovin and Dynamics AX SCM Team

Dynamics AX 2009 Cost Accounting White papers

Ievgenii Korovin — Fri, 02 Dec 2011 13:09:00 GMT

If you are looking for information about inventory close and reconciliation, please check out Tracy Taylor’s post on the AX Support blog.

Enjoy!

Use of One Pallet for Shipping and for Receipt

Ievgenii Korovin — Fri, 02 Sep 2011 10:19:00 GMT

By using the Item arrival journal in the Inventory and warehouse management module in AX2012 you can ship and receive a transfer order using the same pallet.

In addition to the normal criteria that are used to validate pallet moves, the use of one pallet requires that the pallet is empty. If the pallet is used for receipt, it is automatically moved to the receipt location when the journal is posted.

The validation of the pallet move is implemented in the class WMSPalletMoveValidator.

By Lennart Conrad, Per Lykke Lynnerup and Bibi Christensen

Visualizing Security in Microsoft Dynamics AX 2012

Ievgenii Korovin — Fri, 26 Aug 2011 09:43:00 GMT

Introduction

Microsoft Dynamics AX 2012 introduces role-based security, which makes security easier to manage. Relations between security roles, duties and privileges are complex. However, you can apply a tool to represent these relations in a grid.

This document describes another way to represent security objects and the relations between these objects.

DGML is an XML based file format for directed graphs. For example, this is the graph:

…and this is the DGML file behind it:

<?xml version="1.0" encoding="utf-8"?>

<DirectedGraph GraphDirection="LeftToRight" Layout="Sugiyama" xmlns="http://schemas.microsoft.com/vs/2009/dgml">

<Nodes>

    <Node Id="Duty D" Area="X" Type="SecDuty" />

    <Node Id="Duty E" Area="Y" Type="SecDuty" />

    <Node Id="Privilege F" Area="X" Type="SecPrivilege" />

    <Node Id="Privilege G" Area="Y" Type="SecPrivilege" />

    <Node Id="Privilege H" Area="Z" Type="SecPrivilege" />

    <Node Id="Role A" Area="X" Type="SecRole" />

    <Node Id="Role B" Area="X" Type="SecRole" />

    <Node Id="Role C" Area="Y" Type="SecRole" />

</Nodes>

<Links>

    <Link Source="Duty D" Target="Privilege F" />

    <Link Source="Duty D" Target="Privilege G" />

    <Link Source="Duty D" Target="Privilege H" />

    <Link Source="Duty E" Target="Privilege F" />

    <Link Source="Duty E" Target="Privilege G" />

    <Link Source="Role A" Target="Role B" />

    <Link Source="Role B" Target="Duty D" />

    <Link Source="Role B" Target="Duty E" />

    <Link Source="Role C" Target="Duty D" />

    <Link Source="Role C" Target="Duty E" />

</Links>

<Properties>

    <Property Id="Area" DataType="System.String" />

    <Property Id="GraphDirection" DataType="Microsoft.VisualStudio.Progression.Layout.GraphDirection" />

    <Property Id="Layout" DataType="System.String" />

    <Property Id="Type" DataType="System.String" />

</Properties>

<Styles>

    <Style TargetType="Node" GroupLabel="Type" ValueLabel="SecPrivilege">

        <Condition Expression="Type = 'SecPrivilege'" />

        <Setter Property="Icon" Value="pack://application:,,,/Microsoft.VisualStudio.Progression.GraphControl;component/Icons/Key.png" />

    </Style>

    <Style TargetType="Node" GroupLabel="Type" ValueLabel="SecRole">

        <Condition Expression="Type = 'SecRole'" />

        <Setter Property="Icon" Value="pack://application:,,,/Microsoft.VisualStudio.Progression.GraphControl;component/Icons/Users.png" />

    </Style>

    <Style TargetType="Node" GroupLabel="Type" ValueLabel="SecDuty">

        <Condition Expression="Type = 'SecDuty'" />

        <Setter Property="Icon" Value="pack://application:,,,/Microsoft.VisualStudio.Progression.GraphControl;component/Icons/kpi_green_sym2_large.png" />

    </Style>

    <Style TargetType="Node" GroupLabel="Type" ValueLabel="SecProcessCycle">

        <Condition Expression="Type = 'SecProcessCycle'" />

        <Setter Property="Icon" Value="pack://application:,,,/Microsoft.VisualStudio.Progression.GraphControl;component/Icons/Gears.png" />

    </Style>

</Styles>

</DirectedGraph>

The DGML format is supported in Visual Studio 2010 Ultimate and Premium and in some other third party tools as well. In this document, Visual Studio is used:

In Visual Studio 2010, there is Directed Graph toolbar and a Legend window that allow you to change the appearance of the graph. For example, this is one graph, rendered in different ways:

There is a context menu, which provides even more options, such as Advanced selection. For example, you can also:

select all nodes with a specific property value
group nodes
hide the nodes in order to simplify the graph
select all incoming and/or outgoing connections for the currently selected nodes

Before reading any further, we recommend that you watch this 10 minute video for a brief introduction. We also recommend this video which is dedicated to large graphs.

Generating graphs

First of all, import the attached XPO file to Microsoft Dynamics AX 2012.

There are 4 classes in the SecurityToDGML private project. SysDgmlFromSecurity is the main class, which should be run in order to generate the DGML file. The SysDgmlGraph, SysDgmlNode and SysDgmlLink classes encapsulate graph construction logic.

Note: Eventually, you may want to customize the solution by adding more attributes to the nodes and links. For example, objects with a particular prefix may require an additional attribute to make it easier to select them when manipulating the graph.

When you have imported the XPO to AX, run the SysDgmlFromSecurity class. In the dialog, verify the output file name, and then click OK. After several minutes, the file is generated and it opens in Visual Studio (or in the tool that you have assigned to open DGML-files).

Important: The graph is comprehensive so every little change, such as adding a property to the Legend or switching the rendering mode from Left to right to Quick clusters, will take 10 to 20 seconds or more to complete. So avoid any unnecessary clicks on the workspace. The idea is to hide as many nodes as possible and still be able to explore the nodes and relations that you want to focus on. The fewer nodes on the visible graph, the faster it is rendered.

Working with graphs

Scenario 1: Find out what external* roles have access to duties and privileges in your area (in this example, Inventory)

*External roles: In this example, roles from areas other than Inventory, such as Manufacturing. There is some logic in the SysDgmlGraph class that tries to determine the owner team of the object and add an Area attribute to the corresponding graph node. The owner team is determined based on a prefix and/or a suffix of the object name. This is where you may need customization. You can find a sample Excel sheet attached to the this post.

1. Open the DGML-file.

At first, the graph looks like a vertical stripe in the middle of the workspace:

This is because there are too many nodes (while this is being written, about 6000 nodes and 10000 relations).

2. Right-click to select a little area on the stripe.

When you release the button, this part of the graph is zoomed in.

3. Repeat zooming until you see something like the following:

You can see 3 columns of nodes, left to right: roles, duties, and then privileges. There are too many visible relations, so some have to be hidden.

4. Right-click anywhere on the workspace and select Show Advanced Selection in the menu.

A new window will appear on the right side of the workspace:

Area, Type and AOT name are properties of the nodes.

5. Select the nodes that belong to Inventory.

You will notice that some relations and nodes are selected now:

6. Click the I button three times to select incoming connections.
With three clicks you can select a chain of Inventory privileges: For example, a non-Inventory role can have a non-Inventory sub-role which can have a non-Inventory duty which can provide access to the Inventory privileges. By clicking once on the I button you select the duty, with two clicks you also select the sub-role, and with three clicks the whole chain is selected.

At this point, you see all Inventory nodes and all the external nodes that relate to these nodes.

7. Right-click on any of the selected nodes, and click Selection > Hide unselected in order to hide nodes.

The graph becomes much smaller and all remaining nodes remain selected:

8. Click anywhere on the workspace to clear the selection of the nodes. The Selection window looks as follows:

Note the 600 nodes compared to the 6000 nodes on the original graph.

9. Select all areas in the Selection window except for Inventory to view only the Inventory nodes that are used by external roles and duties.

10. Click the O button three times like you did with the I button in order to select all outgoing connections for the selected (=non-Inventory) nodes.

11. Right-click any of the selected nodes and select Selection > Hide unselected.

12. Click anywhere in the workspace to clear the selection of the nodes. This way you reduce the number of nodes in the graph to about 300.

13. Select Zoom to fit in the toolbar to see the following:

The final graph is not very large. The only thing missing is the set of highlighted external duties and roles.

14. In the Legend window, click the Add button and then select Node Property > Area.

15. Click on the new Area stripe and then select Background.

16. In the Color Set Picker window, click the button at the top and then select one of the predefined color sets.

17. Change the color for Inventory to White to leave only nodes from other areas highlighted.

18. Click OK.
This is the final graph:

19. Select one of the external nodes, such as Maintain BOM master, in order to zoom in and check the external nodes for eligibility to use Inventory privileges.

20. Turn on the Butterfly mode.

The graph now looks as follows:

The product designer has access to 4 Inventory privileges. If something is wrong here, we have an issue.

21. Turn off the Butterfly mode and proceed to the next non-Inventory node. Repeat until you are finished.

Scenario 2: Do the opposite of the first scenario to figure out what external privileges and duties are used by roles in your area

This scenario is similar to the first scenario except for the fact that you should use the I and the O buttons in the reverse order.

Note: If objects are marked with wrong areas, you must update the prefixes in the ownership Excel sheet and generate the DGML file again.

Further information about Security can be found on MSDN

By Sasha Nazarov, SCM, Microsoft Dynamics AX

Microsoft Dynamics AX 2012: Where is the Shop floor control module?

Ievgenii Korovin — Fri, 29 Jul 2011 21:36:00 GMT

Introduction

Those of you who know the Shop floor control module in Dynamics AX 2009 will notice that it is not a separate module in Dynamics AX 2012. This post gives you a quick overview of how to access the Shop floor control functionality in Dynamics AX 2012.

Time attendance and Manufacturing execution

The Shop floor control module has been divided into two feature sets:

Time and attendance contains functionality to register work time and attendance such as clock-in and clock-out, indirect activities, absences, breaks, overtime, and flextime. It also includes features to generate payroll information that can be used in a payroll system.
Manufacturing execution allows you to register time and item consumption for a specific production job or project, provide job feedback, do job scheduling and prioritization, etc.

The division of the time and attendance and the job registration functionality provides more flexibility. The licenses for the two feature areas are separate and more users and more industries can now benefit from the functionality that is relevant for their work areas.

The Time and attendance features are moved to the Human resources module and the features can be accessed through the Human resources area page. The related menu items are located in Time and attendance groups under Common, Reports, Inquiries, Periodic and Setup. There is also a Time registration workers list page menu item under the Workers group in the Common area.

The features to clock-in and clock-out and to register time with an electronic timecard are available on the Home area page in the Time and attendance group under Common. These tasks can be performed by any employee and this is the reason why the features are not located in the Human resources or Production control areas.

The menu items for Manufacturing execution are located on the Production control area page in the Manufacturing execution groups under Common, Periodic and Setup and in the Registration group under Inquiries

We hope this short post was useful for you. Further information about Manufacturing execution can be found on MSDN

By Slava Chernenko, SCM, Microsoft Dynamics AX

Disclaimer

All the information about AX 2012 posted here is a pre-release. Any feature is a subject to be changed before the release without notice.
This disclaimer is applicable to all posts about AX 2012 in this blog.

Product-item data management services

Ievgenii Korovin — Wed, 06 Jul 2011 09:05:00 GMT

Introduction

In this blog entry we will provide guidelines for the use of new and modified product-item data management services.

Product-item data management services

The following services have been created or modified in order to enable manipulation of product-item data. These services are AIF document services so they follow all the conventions applicable to the AIF document services:

Service	Purpose
EcoResProductService	Create products (all three types). The service can also be used to retrieve data that has already been created.
EcoResProductMasterDimValueService	Specify values of product dimensions for a product master. These values become available for the creation of product variants. The service can also be used to retrieve data that has already been created.
ItemService	Release distinct products and product masters. The service can also be used to retrieve data that has already been created.
InventDimCombinationService	Release product variants. The service can also be used to retrieve data that has already been created.

Setup of product services

Product-item services must be enabled on an AIF inbound port before they can be used. All services can be enabled on one port or several ports can be used.

An inbound port can be created in the Inbound ports form (System administration > Setup > Services and Application Integration Framework > Inbound ports). This article illustrates the creation of two ports:

A port that uses a NetTcp adapter
A port that uses a File system adapter.

A port that uses a NetTcp adapter can be used to access services programmatically; for example, from a C# application. A port that uses a File system adapter can be used when input data is in the format of an XML document. The following guidelines are based on the use of a default configuration of ports. Advanced configuration of ports is beyond the scope of this article.

Create a port that uses a NetTcp adapter

1. For a new port, specify name and adapter:

2. Click the Service operations button to specify the service operations that are going to be available on the port:

3. In the Select service operations form, select all the product-item service operations:

4. Click the Activate button in the action pane strip to activate the port.

When the port has been activated, a control appears which displays the URI of a WSDL document for the service. This value can then be used for adding a service reference in Visual Studio.

Create a port that uses File system adapter

1. Specify a port name, and from the list of adapters, select File system adapter:

2. In the URI field, specify a path to a folder for incoming XML documents that are to be picked up by the service:

3. Follow the guidelines in the previous procedure to specify the service operations that are going to be available on the port.

4. Click the Activate button in the action pane strip to activate the port.

Now you have two ports with product-item service operations available. Use the following guidelines to create and retrieve data.

Set up Visual Studio

In this article a C# console application project in Visual Studio is used. The only thing that is required here is to create a project and add a service reference for the services:

Create products

All types of products are created by using the EcoResProductService service. However, the methods to create a distinct product, a product master, and a product variant are different so each method is described separately.

Create a distinct product

To create a distinct product, use the EcoResProductService.create operation. First, create a product using C# code, and then create an XML document with data to create a product.

The following code creates a distinct product in Dynamics AX:

static void createDistinctProduct()
{
    AxdEntity_Product_EcoResDistinctProduct distinctProduct = new AxdEntity_Product_EcoResDistinctProduct()
    {
        DisplayProductNumber = "Bulb60W",
        ProductType = AxdEnum_EcoResProductType.Item,
        SearchName = "Bulb60W"
    };
    distinctProduct.Translation = new AxdEntity_Translation[1];
    distinctProduct.Translation[0] = new AxdEntity_Translation()
    {
        LanguageId = "en-us", Name = "Transparent Bulb 60W"
    };
    distinctProduct.Identifier = new AxdEntity_Identifier[1];
    distinctProduct.Identifier[0] = new AxdEntity_Identifier()
    {
        ProductNumber = "Bulb60W"
    };
    distinctProduct.StorageDimGroup = new AxdEntity_StorageDimGroup[1];
    distinctProduct.StorageDimGroup[0] = new AxdEntity_StorageDimGroup()
    {
        Product = "Bulb60W", StorageDimensionGroup = "Std-Dim"
    };
    distinctProduct.TrackingDimGroup = new AxdEntity_TrackingDimGroup[1];
    distinctProduct.TrackingDimGroup[0] = new AxdEntity_TrackingDimGroup()
    {
        Product = "Bulb60W", TrackingDimensionGroup = "Std-Dim"
    };

    AxdEcoResProduct axdProduct = new AxdEcoResProduct()
    {
        Product = new AxdEntity_Product_EcoResProduct[1] { distinctProduct }
    };

    CallContext ctx = new CallContext();
    EcoResProductServiceClient service = new EcoResProductServiceClient();
    try
    {
        service.create(ctx, axdProduct);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

As it appears, the create operation accepts an array of products so it is possible to create multiple products in one call to the service.

The following XML code creates a distinct product. Note that storage and tracking dimension groups are specified. The storage and tracking dimension groups are not mandatory information to create a product so the C# code for the creation of a distinct product does not create these groups.

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
  <Header>
    <Company>DMO</Company>
    <Action>http://schemas.microsoft.com/dynamics/2008/01/services/EcoResProductService/create</Action>
  </Header>
  <Body>
    <MessageParts xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
      <EcoResProduct xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/EcoResProduct">
        <Product xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" class="entity" xsi:type="AxdEntity_Product_EcoResDistinctProduct">
          <DisplayProductNumber>Bulb40W</DisplayProductNumber>
          <SearchName>Bulb40W</SearchName>
          <ProductType>Item</ProductType>
          <Translation class="entity">
            <LanguageId>en-us</LanguageId>
            <Name>Transparent Bulb 40W</Name>
          </Translation>
          <StorageDimGroup class="entity">
            <Product>Bulb40W</Product>
            <StorageDimensionGroup>Std-Dim</StorageDimensionGroup>
          </StorageDimGroup>
          <TrackingDimGroup class="entity">
            <Product>Bulb40W</Product>
            <TrackingDimensionGroup>Std-Dim</TrackingDimensionGroup>
          </TrackingDimGroup>
          <Identifier class="entity">
            <ProductNumber>Bulb40W</ProductNumber>
          </Identifier>
        </Product>
      </EcoResProduct>
    </MessageParts>
  </Body>
</Envelope>

The EcoResProduct element can contain multiple Product elements in order to create multiple products in one service call.

Create a product master and a related product variant

To create a product master, use the EcoResProductService.create operation. Then use the EcoResProductMasterDimValue.create operation to associate product dimension values with the product master. Finally, use the EcoResProductService.create operation again, this time to create a product variant.

The code to create a product master is basically similar to the code that creates a distinct product. One difference is the code that associates the product master with a product dimension group (in the following example: Size-Dim):

static void createMaster()
{
    //master definition
    AxdEntity_Product_EcoResProductMaster productMaster = new AxdEntity_Product_EcoResProductMaster()
    {
        DisplayProductNumber = "RunningShoe",
        ProductType = AxdEnum_EcoResProductType.Item,
        SearchName = "RunningShoe",
    };
    productMaster.Translation = new AxdEntity_Translation[1];
    productMaster.Translation[0] = new AxdEntity_Translation()
    {
        LanguageId = "en-us", Name = "Comfortable running shoe"
    };
    productMaster.Identifier = new AxdEntity_Identifier[1];
    productMaster.Identifier[0] = new AxdEntity_Identifier()
    {
        ProductNumber = "RunningShoe"
    };

    productMaster.ProductDimGroup = new AxdEntity_ProductDimGroup[1];
    productMaster.ProductDimGroup[0] = new AxdEntity_ProductDimGroup()
    {
        Product = "RunningShoe", ProductDimensionGroup = "Size-Dim"
    };
    productMaster.VariantConfigurationTechnology = AxdEnum_EcoResVariantConfigurationTechnologyType.PredefinedVariants;

    AxdEcoResProduct axdProduct = new AxdEcoResProduct()
    {
        Product = new AxdEntity_Product_EcoResProduct[1] { productMaster }
    };

    CallContext ctx = new CallContext();
    EcoResProductServiceClient productService = new EcoResProductServiceClient();
    try
    {
        productService.create(ctx, axdProduct);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

When the product master is created, associate two size dimension values with the product master (size L and M):

static void createMasterDimensions()
{
    //master dimensions definition (two sizes, L and M)
    AxdEntity_MasterDim_EcoResProductMasterSize sizeDimensionL = new AxdEntity_MasterDim_EcoResProductMasterSize()
    {
        SizeProductMaster = "RunningShoe",
        Size = "L",
        EcoResSize = new AxdEntity_EcoResSize[1] 
        { 
            new AxdEntity_EcoResSize() { Name = "L" }
        }
    };
    AxdEntity_MasterDim_EcoResProductMasterSize sizeDimensionM = new AxdEntity_MasterDim_EcoResProductMasterSize()
    {
        SizeProductMaster = "RunningShoe",
        Size = "M",
        EcoResSize = new AxdEntity_EcoResSize[1] 
        { 
            new AxdEntity_EcoResSize() { Name = "M" }
        }
    };

    AxdEcoResProductMasterDimValue axdDimValue = new AxdEcoResProductMasterDimValue()
    {
        MasterDim = new AxdEntity_MasterDim_EcoResProductMasterDimensionValue[2] { sizeDimensionL, sizeDimensionM }
    };

    CallContext ctx = new CallContext();
    EcoResProductMasterDimValueServiceClient masterDimensionService = new EcoResProductMasterDimValueServiceClient();
    try
    {
        masterDimensionService.create(ctx, axdDimValue);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

Create a product variant with the size L for the product master. One thing that may not be obvious is the value required for the ProductDimensionAttribute field of the AxdEntity_VariantDimValue_EcoResProductVariantConfiguration, the AxdEntity_VariantDimValue_EcoResProductVariantSize, and the AxdEntity_VariantDimValue_EcoResProductVariant entities. The value must correspond to the IDs of the EcoResConfiguration, the EcoResSize, and the EcoResColor tables, respectively.

static void createVariant()
{
    //product variant definition
    AxdEntity_Product_EcoResDistinctProductVariant productVariant = new AxdEntity_Product_EcoResDistinctProductVariant()
    {
        DisplayProductNumber = "RunningShoeL",
        ProductType = AxdEnum_EcoResProductType.Item,
        SearchName = "RunningShoeL",
        ProductMaster = "RunningShoe"
    };
    productVariant.Translation = new AxdEntity_Translation[1];
    productVariant.Translation[0] = new AxdEntity_Translation()
    {    
        LanguageId = "en-us", Name = "Comfortable running shoe L size"
    };
    productVariant.VariantDimValue = new AxdEntity_VariantDimValue_EcoResProductVariantDimensionValue[1];
    productVariant.VariantDimValue[0] = new AxdEntity_VariantDimValue_EcoResProductVariantSize()
    {
        DistinctProductVariant = "RunningShoeL",
        ProductDimensionAttribute = 3173,//The ID of the EcoResSize table
        Size = "L",
        EcoResSize = new AxdEntity_EcoResSize1[1]
        {
            new AxdEntity_EcoResSize1() { Name = "L" }
        }
    };

    AxdEcoResProduct axdProduct = new AxdEcoResProduct()
    {
        Product = new AxdEntity_Product_EcoResProduct[1] { productVariant }
    };

    CallContext ctx = new CallContext();
    EcoResProductServiceClient productService = new EcoResProductServiceClient();
    try
    {
        productService.create(ctx, axdProduct);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

The following XML code does almost the same thing. The only difference is that it creates a product master that is associated with a product dimension group where the Color dimension is active. At first, create a product master:

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
  <Header>
    <Action>http://schemas.microsoft.com/dynamics/2008/01/services/EcoResProductService/create</Action>
  </Header>
  <Body>
    <MessageParts xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
      <EcoResProduct xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/EcoResProduct">
        <Product xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" class="entity" xsi:type="AxdEntity_Product_EcoResProductMaster">
          <DisplayProductNumber>BoardMarker</DisplayProductNumber>
          <SearchName>BoardMarker</SearchName>
          <ProductType>Item</ProductType>
          <Translation class="entity">
            <LanguageId>en-us</LanguageId>
            <Name>Whiteboard marker</Name>
          </Translation>
          <ProductDimGroup class="entity">
            <Product>BoardMarker</Product>
            <ProductDimensionGroup>Col-Dim</ProductDimensionGroup>
          </ProductDimGroup>
          <Identifier class="entity">
            <ProductNumber>BoardMarker</ProductNumber>
          </Identifier>
          <VariantConfigurationTechnology>PredefinedVariants</VariantConfigurationTechnology>
        </Product>        
      </EcoResProduct>
    </MessageParts>
  </Body>
</Envelope>

Associate values of the Color dimension with the product master:

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
  <Header>
    <Action>http://schemas.microsoft.com/dynamics/2008/01/services/EcoResProductMasterDimValueService/create</Action>
  </Header>
  <Body>
    <MessageParts xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
      <EcoResProductMasterDimValue xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/EcoResProductMasterDimValue">
        <MasterDim class="entity" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AxdEntity_MasterDim_EcoResProductMasterColor">
          <ColorProductMaster>BoardMarker</ColorProductMaster>
          <Color>Red</Color>
          <EcoResColor class="entity">
            <Name>Red</Name>
          </EcoResColor>
        </MasterDim>
        <MasterDim class="entity" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AxdEntity_MasterDim_EcoResProductMasterColor">
          <ColorProductMaster>BoardMarker</ColorProductMaster>
          <Color>Blue</Color>
          <EcoResColor class="entity">
            <Name>Blue</Name>
          </EcoResColor>
        </MasterDim>
      </EcoResProductMasterDimValue>
    </MessageParts>
  </Body>
</Envelope>

Create a product variant:

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
  <Header>
    <Action>http://schemas.microsoft.com/dynamics/2008/01/services/EcoResProductService/create</Action>
  </Header>
  <Body>
    <MessageParts xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
      <EcoResProduct xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/EcoResProduct">
        <Product xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" class="entity" xsi:type="AxdEntity_Product_EcoResDistinctProductVariant">
          <DisplayProductNumber>BoardMarkerRed</DisplayProductNumber>
          <SearchName>BoardMarkerRed</SearchName>
          <ProductType>Item</ProductType>
          <Translation class="entity">
            <LanguageId>en-us</LanguageId>
            <Name>Whiteboard marker red</Name>
          </Translation>
          <Identifier class="entity">
            <ProductNumber>BoardMarkerRed</ProductNumber>
          </Identifier>
          <ProductMaster>BoardMarker</ProductMaster>
          <VariantDimValue class="entity" xsi:type="AxdEntity_VariantDimValue_EcoResProductVariantColor">
            <DistinctProductVariant>BoardMarkerRed</DistinctProductVariant>
            <ProductDimensionAttribute>3169</ProductDimensionAttribute>
            <Color>Red</Color>
            <EcoResColor class="entity">
              <Name>Red</Name>
            </EcoResColor>
          </VariantDimValue>
        </Product>        
      </EcoResProduct>
    </MessageParts>
  </Body>
</Envelope>

Release products

A product must be released to a company before it can be used in that company. The ItemService and InventDimCombinationService serve this purpose. The former can be used to release distinct products and product masters. The latter can be used to release product variants. A product master must be released before any of its product variants can be released.

Release a distinct product or a product master

The only information required to release a product to a company is the ID of the product and the ID by which it will be represented in the company (ItemId). It is possible to add information to the ItemService service. In the following example, information about units used for storage, purchasing, and selling is provided:

private static void releaseProduct()
{
    AxdEntity_InventTable inventTable = new AxdEntity_InventTable()
    {
        ItemId = "Bulb60W",
        Product = "Bulb60W",
        Invent = new AxdEntity_Invent[1]
        {
            new AxdEntity_Invent()
            {
                ItemId = "Bulb60W", UnitId = "Box"
            }
        },
        Purch = new AxdEntity_Purch[1]
        {
            new AxdEntity_Purch()
            {
                ItemId = "Bulb60W", UnitId = "Box"
            }
        },
        Sales = new AxdEntity_Sales[1]
        {
            new AxdEntity_Sales()
            {
                ItemId = "Bulb60W", UnitId = "Pcs"
            }
        }
    };

    AxdItem item = new AxdItem()
    {
        InventTable = new AxdEntity_InventTable[1] { inventTable }
    };

    CallContext ctx = new CallContext() { Company = "DMO" };
    ItemServiceClient itemService = new ItemServiceClient();
    try
    {
        itemService.create(ctx, item);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

The following XML code releases a product master with the minimum amount of information required:

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
  <Header>
    <Company>DMO</Company>
    <Action>http://schemas.microsoft.com/dynamics/2008/01/services/ItemService/create</Action>
  </Header>
  <Body>
    <MessageParts xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
      <Item xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/Item">
        <InventTable class="entity">
          <ItemId>BoardMarker</ItemId>
          <Product>BoardMarker</Product>
        </InventTable>
      </Item>
    </MessageParts>
  </Body>
</Envelope>

Release a product variant

A product variant can be released once a related product master has been released. When you release a product variant to a company, the product variant can be identified in two different ways.

Use the product number of the product variant.
Use the ID of the associated product master in the company (ItemId) and the InventDim structure with the relevant fields set to the dimension values for the variant (the ItemId/InventDim approach).

For details, see the following examples.

Use the product number of the product variant (DistinctProductVariant):

private static void releaseProductVariants()
{
    AxdEntity_InventDimCombination releasedVariant = new AxdEntity_InventDimCombination()
    {
        DistinctProductVariant = "RunningShoeL",
        ItemId = ""
    };

    AxdInventDimCombination inventDimCombination = new AxdInventDimCombination()
    {
        InventDimCombination = new AxdEntity_InventDimCombination[1] { releasedVariantL }
    };

    CallContext ctx = new CallContext() { Company = "DMO" };
    InventDimCombinationServiceClient inventDimCombinationService = new InventDimCombinationServiceClient();
    try
    {
        inventDimCombinationService.create(ctx, inventDimCombination);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

Use the ItemId/InventDim approach:

private static void releaseProductVariants()
{
    AxdEntity_InventDimCombination releasedVariant = new AxdEntity_InventDimCombination()
    {
        DistinctProductVariant = "",
        ItemId = "RunningShoe",
        InventDim = new AxdEntity_InventDim[1] 
        {
            new AxdEntity_InventDim()
            {
                InventSizeId = "M"
            }
        }
    };

    AxdInventDimCombination inventDimCombination = new AxdInventDimCombination()
    {
        InventDimCombination = new AxdEntity_InventDimCombination[2] { releasedVariantM }
    };

    CallContext ctx = new CallContext() { Company = "DMO" };
    InventDimCombinationServiceClient inventDimCombinationService = new InventDimCombinationServiceClient();
    try
    {
        inventDimCombinationService.create(ctx, inventDimCombination);
    }
    catch (Exception e)
    {
        System.Console.WriteLine(e.Message);
        System.Console.ReadKey();
    }
}

The following XML code releases two variants in one call and uses both approaches to identify a product variant:

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
  <Header>
    <Company>DMO</Company>
    <Action>http://schemas.microsoft.com/dynamics/2008/01/services/InventDimCombinationService/create</Action>
  </Header>
  <Body>
    <MessageParts xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
      <InventDimCombination xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/InventDimCombination">
        <InventDimCombination class="entity">
          <DistinctProductVariant>BoardMarkerRed</DistinctProductVariant>
          <ItemId></ItemId>
        </InventDimCombination>
        <InventDimCombination class="entity">
          <DistinctProductVariant></DistinctProductVariant>
          <ItemId>BoardMarker</ItemId>
          <InventDim class="entity">
            <InventColorId>Blue</InventColorId>
          </InventDim>
        </InventDimCombination>      
      </InventDimCombination>
    </MessageParts>
  </Body>
</Envelope>

Summary

We hope that this blog post will help developers to better understand and use the services for the new product-item data model.

More detailed information regarding the creation and release of products can be found in the Application user Help in the “Product information management” section.

Further developer information about AIF and services can be found on MSDN.

By Wojciech Bardzinski

Disclaimer

All the information about AX 2012 posted here is a pre-release. Any feature is a subject to be changed before the release without notice.
This disclaimer is applicable to all posts about AX 2012 in this blog.

Back ported features from Dynamics AX 2012 to Dynamics AX 2009 (Close non-financial transfers, Inventory Reconciliation and Reporting)

Ievgenii Korovin — Sun, 05 Jun 2011 13:19:00 GMT

Some of the new functionality that is created in the Dynamics AX development cycle brings about so much feedback from customers and partners that we decide to back port the features to previous versions of Dynamics AX products. The back ported features become available as part of hot fixes or service packs to previous versions of Dynamics AX.

Today, we would like to bring your attention to the great SCM features that were developed as part of the Dynamics AX 2012 release cycle and which are already included in Dynamics AX 2009 Service Pack 1 (Hotfix rollup 5 for Microsoft Dynamics AX 2009 Service Pack 1)

Close non-financial transfers

This feature significantly improves performance for the inventory closing and inventory recalculation processes. The essence of the feature is the fact that inventory transactions which represent the physical transfers are disregarded during cost calculation. For example, inventory transactions might indicate a physical item movement between different warehouses or warehouse locations. However, from a costing perspective, the movement does not contribute to the final item cost.

With the new approach, the cost calculation process becomes significantly faster and more accurate. Please refer to the following white paper to learn more about the feature. Microsoft Dynamics AX 2009 White Paper: Close Non-Financial Transfers

Inventory Reconciliation and Reporting

The Inventory value report framework allows you to report and reconcile Inventory and WIP values on one report. The new report framework replace six individual reports and manual adjustments, which were required in previous versions of Dynamcs AX to achieve the same result.

Also, the Potential conflicts report can be used to report transactions that violate rules as defined by parameter settings in various modules. This report significantly reduces the time spent on identifying the causes of discrepancies between Inventory and General ledger values. Please refer to the following white paper to learn more about the feature. Microsoft Dynamics AX 2009 White Paper: Inventory Reconciliation and Reporting

Disclaimer

Service products in Microsoft Dynamics AX 2012

Ievgenii Korovin — Wed, 01 Jun 2011 12:34:00 GMT

With Microsoft Dynamics AX 2012 new capabilities of selling and procuring products, decoupled from inventory control, have been introduced. The purpose of this post is to describe the difference between stocked and non-stocked products of type service and to provide general recommendation about this subject.

Item definitions in Microsoft Dynamics AX 2009 and earlier

Microsoft Dynamics AX 2009 offered the options to define different types of items. The table below illustrates these options:

Item type	Purpose	System behavior
Item	Represent finished items and raw materials.	- Inventory balances are stored, which means these items can be reserved and picked - Inventory on-hand overview exists - Can be defined as warehouse items - Production orders cannot be created - Planned purchase orders and transfer orders can be created when running master planning - Coverage plan settings can be defined as purchase - Inventory transactions are created for source documents, allowing the user to receive/issue inventory for service items
Service	Represent services like sub-contracting	- No inventory balances are stored, which means these items cannot be reserved nor picked - No inventory on-hand overview - Cannot be defined as warehouse items - Production order cannot be created - Master planning cannot produce or transfer service - Coverage plan settings can only be defined as purchase - Cannot configure items using the Product Configurator - Inventory transactions are created for source documents, allowing the user to receive/issue inventory for service items
BOM	Represents the bills of materials. BOMs can be semi-finished items or finished items	- Inventory balances are stored, which means these items can be reserved and picked - Inventory on-hand overview exists - Can be defined as warehouse items - Production order can be created - BOMs can be produced and transferred when running master planning - Coverage plan settings can be defined as purchase, transfer or production - Inventory transactions are created for source documents, allowing the user to receive/issue inventory for service items

Service items

Whereas the item types Item and BOM share to a very high degree the same characteristics, the item type service is different.

Services are by definition consumed at the moment they are produced and can therefore not be stocked nor “owned” unlike items.

An example of a service is

The Contoso Company (consumer) has a fleet of company cars. Once a year, the company car must undergo service inspection at a local car shop (producer). The employee will take the company car and “purchase” (consumes) the service at the car shop.

The example illustrates the normal practice for service items. A business has certain services (items of type service) in their inventory, which they would like to, in the above scenario, purchase. The financial value of the service would be posted directly to expense accounts rather than inventory accounts.

In order to support the scenario in Microsoft Dynamics AX 2009 the reference data for such a service item would have to be defined specially for these items.

In the inventory model group, negative physical and financial inventory must be allowed for service items. Furthermore, all ledger integration options, particularly the Post financial inventory must be left blank. This will ensure that, in the example of purchasing the car service, an expense account will be used for receipt transactions.

From an inventory costing perspective, the system does expect service item transactions to be adjusted. Therefore the service items transactions will be excluded during the inventory recalculation process. During the inventory closing run, the service items will be settled according to the special “service item settlement” principle, which will close service item transactions without making any adjustments, therefore will be no additional posting created.

If for some reason whatsoever a service item was to be promoted to become a standard item to be purchased, the system offered the option to change the item type from service to item. This change would have a series of ripple effects, since the core definition of what functions was allowed performed with the previous service item has been changed.

Order management and inventory control management

In Microsoft Dynamics AX 2009 order management and inventory control management were tightly coupled. This resulted in alternate solutions when trying to decouple them.

In the case of procurement, Microsoft Dynamics AX 2009 introduced the purchase requisition function with its concept of non-catalog. The non-catalog concept required a dummy item of type service. This catalog item would be the only item that could be expensed directly without effecting inventory or cost accounting.

To be able to support non-stocked trade for the sales side, you would instead of defining dummy service items, use the free text invoice function next to the sales order function.

Product definitions in Microsoft Dynamics AX 2012

Microsoft Dynamics AX 2012 introduces the concept of shared products. Core product definitions containing key product attributes are defined and controlled without an organizational context. A new product process allows you to release the core product definitions to all or parts of an organization, and finalization of the product data setup is done at the individual organizational level.

The item type in Microsoft Dynamics AX 2009 has been promoted into the product type in Microsoft Dynamics AX 2012. With the new concept the core product types have been revised and so some extend altered. See the table below for reference.

Product type	Purpose	System behavior
Item	Represent finished items and raw materials.	The behavior is similar to Dynamics AX 2009 - Any item can be associated with a BOM, and thereby be produced or purchased
Service	Represent services	- Products of type service, should be associated with an item model group, where the policy not stocked is selected - No support for service BOMs - Coverage plan setting can only be purchase
BOM	DISCONTINUED	N/A

Service products

Defining products of type service in Microsoft Dynamics AX 2012 is fairly simple. Apart from selecting the correct product type, one essential component to remember is to associate the released product in a legal entity with an item model group, where the policy Stocked product is left blank.

This policy is new, and it ensures that products of type service will be expensed and not stocked in inventory.

The following recommendations apply:

Standard service product

Service product as part of BOM

(subcontracting)

Stocked product = false

- Recommended – will ensure that product costs are expensed directly

- No inventory operations required

- Not recommended

Stocked product = true

- Not recommended

- Recommended – will ensure that product costs can be captured in a BOM structure

As the above matrix illustrates, if a product of type service is to be used both as a standard product offering and included in a BOM cost calculation (for a subcontracting scenario for example), it will require two unique product IDs.

From a master planning and subcontracting perspective, the below constraints dictate that non-stocked service products cannot participate in subcontracting scenarios:

· From Master planning perspective, the non-stocked service product cannot be part of a bill of material. Demand from a higher level bill of material item cannot create drive demand towards a non-stocked product

· From product costing perspective, the non-stocked service product cannot be part of a bill of material and cannot contribute to the direct cost of a finished goods

For a service item to support subcontracting and be included in master planning, the service item has to be setup as stocked.

Regardless of the policy setting in the associated item model group for a product of type service, the inventory storage dimension group will still have to be specified on the product setup. However, only storage dimension site is mandatory for a source document line for a non-stocked service.

Notice: during upgrade from Microsoft Dynamics AX 2009 or earlier to Microsoft Dynamics AX 2012, all items defined with item type = service, will be upgraded to products of product type = service. The associated item model group for the released product of type service will have its Stocked product value, by default, set to true.

Order management and inventory control management

Looking at the service item example from in the beginning of this document, the most noticeable change in Microsoft Dynamics AX 2012 is the ability to decouple order management and inventory control management.

Although products of type service can either be not stocked or stocked (in subcontracting scenarios), the purchase requisition in Microsoft Dynamics AX 2012 no longer requires dummy service items to include in catalogs, because of the new stocked product policy.

The policy now supports to be able to both procure and sell all kinds of products in a consolidated manner, which means on a single order.

Please note that system supports the conversion between stocked and non-stocked services.

Summary

With Microsoft Dynamics AX 2012 new capabilities of selling and procuring, decoupled from inventory control, have been introduced. This non-stocked trade is being supported by a new policy called stocked product on the item model group.

By applying the policy, products of type service can be expensed directly without any use of inventory control processes.

By Mai-Britt Winther and Ievgenii Korovin