NAV 2013 Timesheet Integration–Jobs

In earlier versions of MS Dynamics NAV, journals were used to collect resource time registrations. In Dynamics NAV 2013, this has been enhanced by the provision of Time Sheet functionality, which is a much more functionally rich and user friendly way of capturing basic resource information.

Users and Approvers can be created and linked so that Timesheets can be viewed and approved by the relevant responsible person.

Timesheets can then be used to track the time that is used on a job, service order or assembly order and are created for weekly time periods.

Provided Jobs have the correct Resource/Responsibility assigned then it is possible to create Time Sheets by populating the Time Sheet Lines using the Job Planning Lines as the source data.

Or alternatively create Timesheets based on individual Resources

Time Sheets can also be configured to be viewed, edited and managed through the NAV Sharepoint portal.

Resource configured for using Time Sheets


Job Card with Planned Resource


Timesheets created by using Job Planning Lines


Example Time Sheet to be completed


The Time Sheet Approver or Manager can view a list of those Employee Timesheets that require actioning….


Clicking on the [Edit Time Sheet] button then allows the Manager to Approve, Reject or Re-Open previously Approved Timesheets or review the Activity Details of specific tasks that have been linked to the Timesheet.


Time Sheets lines can also be used to populate Job Journals..


Use the [Suggest Lines from Time Sheets…] button to populate the Journal Lines.


NAV 2013 Item Availability Views

Three new item availability views have been included in MS Dynamics NAV 2013

· Item Availability by Event

· Item Availability by Time-Line

· Item Availability by BOM Level


Item Availability by Event.

This new view shows how projected inventory figures change over time by the inclusion or otherwise of supply and demand events. The window shows information only about the dates when figures change because of an event. Where no change occurs then that time period is not shown.

Filters allow the inclusion of forecasted figures and planning suggestions, such as blanket orders and uncommitted purchases.

Time periods can be defined and expanded or collapsed as required.

Expanding a line in the view shows the document or event that gives rise to the change in inventory.

Using the [Show Documents] action then displays the actual document related to the line.



Item Availability by Timeline

This view provides a graphical representation of the items projected inventory based on future supply and demand events. Similar to the view by Event, filters are provided to include or exclude planning suggestions.

Each change in projected inventory is shown with an ‘X’. Moving the cursor over the ‘X’ shows the underlying documents that give rise to the change.

It is possible to click and drag the ‘X’ point to different time periods to show the difference that would be made to projected inventory levels if the document were re-planned. This is function is only available when the ‘Planning Suggestion’ view is selected. It is not possible to change the timeline of actual Sales or Purchase Orders, for example,

The view can be opened from an Item Card (example shown), planning or requisition worksheet line.

If the graph is changed a [Reload] Action is available to re-populate the view with the original data.


This view shows the projected inventory levels and the supply and demand occurrences that affect that inventory.

Click on the ‘Planning Suggestion’ tick box will show the current suggested requirements that have been calculated.


On this view it is possible to ‘drag and drop’ the highlighted nodes to model the different inventory levels that would be achieved by amending the suggested requisition.

Item Availability by BOM Level

This view is extremely useful for seeing the availability of BOM items in terms of how many parent Items can be made for its underlying ‘child’ items and when each will be needed to satisfy demand.

Each BOM item is shown as a collapsible line that can be expanded to show its constituent parts and through multiple BOM levels.

The view shows how many of each Item is available and also how many of the top level and each subsequent ‘parent’ item the projected inventory can supply.

The ‘Bottleneck’ field indicates which item is restricting the quantity of the top level item that can be made. For example a Sales order expected receipt date is too late to make additional items as shown by the ‘Needed Date’ field.


Using NAV 2013 Query Objects

Microsoft Dynamics NAV 2013 has introduced a new object type!

‘Query’ is a new object that allows you to specify a dataset from a NAV table or multiple tables. It will allow you to specify how to join multiple tables, filter the results set and specify totalling methods on fields such as Sums or Averages.

Queries run on the NAV 2013 Server as optimised efficient SQL statements, (i.e. not the User’s client), and can be used for:

· Creating generic Charts using Query Objects rather than basing them on Tables.

· Saving a result dataset as an .xml or .csv file that can then be integrated with external applications.

· Exposing data as an OData Web service for access via Excel PowerPivot or SQL Reporting Services.

To create a Query in Object Designer, you create Data Items and Columns and then link the data items specified.

A data item specifies the table to retrieve records from. A column specifies a field of the table to include in the resulting dataset of a query.

A data item link determines which records to include in the dataset based on a common field between two data items. E.g. Customer No. from the Customer table and the Sell-To-Customer No. from the Sales Line table.

The data items can be linked so that the resulting dataset includes all the records from the first table, even if no matching record can be found in the second table. If matching records do not exist in the second table, then the default value for that data type is output. E.g. if a field is an integer data type then ‘0’ will be returned. This is defined in the query by selecting the value ‘Use Default Values If No Match’ in the DataItemLinks property.

If the resulting dataset should only contain matching records across all linked tables, then select the value ‘Exclude Row If No Match’.

More sophisticated joins can be specified by choosing the ‘SQL Advanced Options’. In this instance the ‘SQLJoinType’ property will be displayed allowing you to specify the join using an SQL statement.

Example of NAV Query


This query links the Sales Header to the Salesperson/Purchaser table in order to retrieve the E-mail address of the Salesperson and links the Sales Line to the Item table in order to retrieve the Category and Posting Group information.

Example of DataItem Link between Sales Line and Item


Here the value in the ‘Field’ column refers to the ‘No.’ field of the Item and is referenced to the ‘Sales Line’ table, joined by using a match on the Reference Field, ‘No.’, the Item from the Sales Line table.

Running this query gives the following dataset…