Microsoft Dynamics AX Advanced Favorites

One of most widely used features in Microsoft Dynamics AX, is the ability to perform powerful searches on any of the AX grid pages. What many don’t realize is you can save these searches or filters as part of your favorites. This functionality is also available in Dynamics 365 for Operations as part of the workspaces. This article will show you how to add these filters as favorites in Dynamics AX 2009 or Dynamics AX 2012.

First, configure an advanced filter, in one of the grid screens. In this example, all sales order grid was used.

Dynamics AX Advanced Favorites

In this example, we’ll create a filter to show us all unconfirmed sales orders, created in the last 100 days.

Dynamics AX Advanced Favorites

Once you put in the filter criteria, click on the modify and “Save As” and save your query.

Dynamics AX Advanced Favorites

Now you can use this query as the default for a menu item you add to your favorites. To do this, right click on the “All Sales Orders” menu option on the left hand navigation, and click “Add to favorites..”

Dynamics AX Advanced Favorites

Give your favorite a name “Sales Orders Unconfirmed last 100 Days” and select the query you want to save with the favorite.

Dynamics AX Advanced Favorites

Now, when you click on the favorite, it will open already filtered based on your query.

Dynamics AX Advanced Favorites

This post was written by Jason Federspiel, AX Functional Consultant at Tridea Partners. Tridea is a leading Microsoft Dynamics provider.

Microsoft Dynamics AX 2012: Inventory Replenishment

In Microsoft Dynamics AX 2012, by setting up some item coverage settings and default order settings, you’ll easily be able to have Microsoft Dynamics AX recommend inventory replenishment when running master scheduling. Below are the steps to set this up.

Navigate to Product Information Management > Common > Released Products and select the item in edit mode.

  • On the Plan FastTab, select the appropriate coverage group for your company and item.

Inventory Replenishment

 

  • On the Plan tab of the action pane at the top, select item coverage and use the wizard to create the item coverage settings based on the coverage group selected (i.e. site, warehouse, minimum inventory, maximum inventory, lead times, etc), then click close. (See screen shot below)

 

  • On the Plan tab, select default order settings then set your purchase site, inventory site, minimum order quantity and purchase lead time, then click close. (See screen shot below)

 

  • On the Plan tab, add the site specific order settings such as site, purchase warehouse and inventory warehouse, then click close. (See screen shot below)

Inventory Replenishment

Next you’ll need to know which planning strategy to use with Master Scheduling. There are three types of plans to choose from to support your company’s operations. Dynamic plan is for short term planning and can be updated every time the master data changes. Forecast plan is for plans involving forecast and demand. Static plan is for long term planning, which remains unchanged until the next time you run master scheduling. These plans can be configured in the Master Plans form in the Master Planning module under setup then under plans. For example, if you have an item in which you want to maintain a minimum inventory level for the long term, then you would choose static plan.

 

On the Plan tab of the released product, click on Net Requirements. Select the plan type from the drop down menu at the top. Then in the middle section on the overview tab, select update > master scheduling and click ok. This runs the master scheduling to determine if inventory of this item needs to be replenished.

Inventory Replenishment

 

You can also run master scheduling from Master Planning > Periodic > Master scheduling. By running master scheduling from the Master Planning module, you can select multiple items to run at the same time.

 

Once the master scheduling job has completed, if AX determines that inventory should be replenished, it will automatically create a planned order for the item(s) that were included in the master scheduling run. The next step is to convert any planned orders (purchase, production, transfer) to actual orders.

Once you’ve converted your order, you can return to the released product form to view the status of your item under Net requirements. If you run master scheduling again from this screen while there are existing orders (planned or firmed), and/or on-hand inventory, and the quantities are at or above the minimum inventory quantity as set in the item coverage settings, then AX will not generate a planned order. If there are no planned orders, no open purchase orders and on-hand inventory is below the minimum, then AX will generate a planned order when you run master scheduling.

This article was written by Tracey Schebera, Dynamics AX Consultant for Tridea Partners. Tridea is a leading Microsoft Dynamics provider. www.trideapartners.com

 

Dynamics AX 2012 R3: Stopped Workflow Error

When working with different types of workflows in Microsoft Dynamics AX 2012, you may encounter a stopped workflow record with an error message detailing that AX ‘failed to create a session’.

AX 2012 R3 Stopped workflow error

The error message can be generated because the workflow is unable to assign the record to a user for review or approval.

To resolve this type of issue, the first step is to identify which user record is causing the issue. Because no user ID is mentioned in the error message, you can identify the user by first finding the step where the workflow stopped. In the Workflow history form, click the Tracking details tab (screenshot above) to identify the step in the Workflow activities pane which has the Workflow stopped error message.

Next, navigate to the workflow and open the workflow editor to determine if the workflow step is assigned to a user, user group, security role or hierarchy. If the step is assigned to a user, you can easily identify the user which is causing the issue. If the step is assigned to a user group, navigate to the ‘User group’ form [System administration>Common>Users>User groups] and click the Users tab for the user group to identify which users are assigned to the group. One or more of these users could be the cause of the issue. If the step is assigned to a security role, navigate to the ‘Assign users to roles’ form [System administration>Setup>Security>Assign users to roles] and select the role to identify which users are assigned to that security role. Again, it could be more than one user causing the issue. Lastly, if the assignment type is a hierarchy such as the managerial hierarchy, navigate to the Positions list page [Human resources>Common>Organization>Positions>Positions], filter on the worker who submitted the record to the workflow then pinpoint the position/worker the hierarchy would assign the record to based on the ‘Reports to’ field.

Once you have identified the user(s) the step is assigned to, verify that each user record is enabled, the user is assigned to the appropriate security roles and that the user record is associated with a worker record.

In the case I investigated recently, the approval step where the workflow stopped was assigned to a user group. One user in the group had been disabled in AX but the user was not removed from the user group. The workflow was attempting to assign the record to each user in the group. Because one user was not enabled, the workflow could not assign it to all users in the group which caused the workflow to stop at an approval step. Once the user was removed from the user group, the workflow was resumed and the record moved forward in the workflow as expected.

This post was written by Robin Ellsworth, AX Application Consultant at Tridea Partners. Tridea is a leading Microsoft Dynamics provider.

Dynamics AX: Verify W-9 Received from 1099 Vendors

Microsoft Dynamics AX 2012 R3 has many features that will make your life easier! If you work in the accounts payable department processing invoices, you may want to verify that a 1099 vendor has provided their W-9 form before any invoices are posted for that vendor. AX 2012 R3 has a helpful feature which will automatically generate an infolog to alert you that a W-9 has not yet been received from a 1099 reportable vendor when an invoice is being created.

To enable the ‘Check for W-9 form’ functionality in AX 2012 R3, follow these steps:

On the Accounts payable parameters form, enable the ‘Check for W-9 form’ checkbox on the Invoice tab.

By selecting this checkbox, any newly created vendor record will automatically have the ‘Check for W-9’ checkbox enabled by default. The AP clerk who maintains vendors then has the option to deselect the field for each vendor if the infolog warning is not necessary for a particular vendor.

1099 Vendors

On the vendor record, the ‘Check for W-9’ checkbox will default as selected on the Tax 1099 tab. If the vendor has provided a W-9 form, click the ‘W-9 received’ checkbox to record it. You can attach the W-9 document to the vendor record using the Document handling functionality by clicking the ‘Attachments’ button on the Action pane.

Vendor 1099

For our example, we have not yet received a W-9 from our 1099 vendor and want an infolog generated to warn the AP clerk. We will leave the ‘W-9 received’ checkbox cleared and the ‘Check for W-9’ checkbox enabled.

Vendor 1099

Now when the AP clerk creates an invoice for a purchase order or a non-purchase order invoice journal for our 1099 vendor, an infolog is generated which warning the user that a W-9 form has not yet been received for that vendor. The AP clerk can still post the invoice or place the invoice on hold until the W-9 is received from the vendor.

1099 Vendor

For more information – check out our Webinar on 1099 Report Processing

This post was written by Robin Ellsworth, AX Application Consultant at Tridea Partners. Tridea is a leading Microsoft Dynamics provider.

 

Custom Security Roles in Microsoft Dynamics AX 2012

Have you ever created a custom role in Microsoft Dynamics AX 2012 which seemed to have all of the privileges and duties required for the tasks the role needed to perform only to find out that when you are testing the role you run across an error similar to the one below?

custom role in Microsoft Dynamics AX 2012

The above error is related to a class that needs permission added to the role in order to complete the task. In AX 2012, Microsoft has given us a fairly easy way to perform this on a security role from the user interface.

To do so, navigate to the System Administration module and open the security role that you are receiving the error with.

custom role in Microsoft Dynamics AX 2012

On the top right section of the form, select the “Override permissions” button

custom role in Microsoft Dynamics AX 2012

This opens the Override permissions form. Click Add server methods

custom role in Microsoft Dynamics AX 2012

Type in the class name you want to add and the server method name. Click filter.

custom role in Microsoft Dynamics AX 2012

Select the available server method and click OK

custom role in Microsoft Dynamics AX 2012

The class will be added and you can locate it by expanding the server/method node

custom role in Microsoft Dynamics AX 2012

Now go back and test your security role to ensure the issue has been resolved.

This post was written by Laura Garcia, AX Application Consultant at Tridea Partners. Tridea is a leading Microsoft Dynamics provider.