Are you ready for 1099 reporting?

1099 REPORTING IS JUST AROUND THE CORNER!

Tridea recommends that you start testing your 1099 reports to allow plenty of time for report refinements.

We recommend that you:

  • Start reviewing your vendors for potential 1099 recipients
  • Begin identifying amounts to be reported as 1099
  • Print test reports to verify form alignment

Tridea is here for you!  Please contact us for training or questions at info@trideapartners.com .

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 Year-End Close Webinar

Join Tridea for our annual Dynamics AX year-end close webinar! We will share best practices related to year-end processes for your Microsoft Dynamics AX system. We will go through the general steps of the year end close process and discuss key items that will be required to setup the next fiscal year.register here

Event Details: Wednesday: December 14, 2016 at 9:30 AM – 10:30 AM (PST)
Presenters: Matthew Caffrey & Robin Ellsworth  – Tridea Partners

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.