https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID=%7b36D52ACD-DF6D-4D7E-8136-6DF32DEDA27A%7d&NRORIGINALURL=%2fpartnersource%2fdownloads%2fmigrationtools%2fdatabasearchiveformicrosoftnavisionna%2ehtm&NRCACHEHINT=Guest

2. After the navigate screen show the related tables where the entries have been posted, go to fa ledger entry & click on show.

3. After this you will see all of the fa ledger entries like with posting type as Proceeds on Disposal, Gain/Loss, Acquisition Cost, Depreciation.

4. Select the Proceeds on Disposal posting type entry & under function menu click cancel entries, you will receive a message that the entries have been transferred to fa gl journal.

5. Go to fa gl journal there you will only see one entry, here enter the bal account type as gl account & the bal account no.
( i.e. any expense account for temp use) and remove value in the bal. gen. posting type ,bal. gen. prod. posting group, bal. gen. bus. posting group and post the entry.

6. After the entry has been posted you need to manually post a reverse entry to nullify the temp expense account(i.e. Dr the temp expense account & Cr the customer account that was selected at the time of posting the sales invoice for FA).

After this check your FA card & you will see that there is no check mark in disposed and more if you drill down in the book value the entries related to disposal have been moved to error ledger entries.

This error occurs when the total number of users accessing the Microsoft Dynamics NAV database at the same time has exceeded the total number of user sessions that a license gives access for. If you are licensed for 5 users and you are the 6th user trying to log into the Microsoft Dynamics NAV database, you will receive this error.

The error can occur even though the actual number of active users that are logged into the Microsoft Dynamics NAV database are less than the number of user sessions your license gives access for. The situations this may occur in are listed here:

1. If you are using N/ODBC or C/Front, each instance of these programs that you have running will use a user session.
2. There may be idle sessions still connected to the Microsoft Dynamics NAV database. This can happen if a user did not close Microsoft Dynamics NAV properly when exiting, or after power failures.
3. Microsoft Dynamics NAV Database Server only
   The maximum number of sessions that are allowed to log on to the Microsoft Dynamics NAV Database server simultaneously can be specified when you start the Microsoft Dynamics NAV Database service. If the maximum number of sessions was set when the Microsoft Dynamics NAV Database service was started, no more users than this maximum can log into the NAV Database server at the same time no matter how many sessions is on the license.

RESOLUTION

1. How to determine how may users are logged into the Microsoft Dynamics NAV database

You can see how many users are logged into the Microsoft Dynamics NAV database at any given time from the Database Sessions window. To access the Database Sessions window in Microsoft Dynamics NAV follow these steps:

1. Go to File, Database, Information, Sessions tab
2. Drill down into the Current Sessions field
   The Database Sessions window will show a list of all sessions connected to the Microsoft Dynamics NAV database, including users, N/ODBC sessions etc.

You can filter by the Microsoft Dynamics NAV database in the Database Name field to limit the records to only show sessions connected to this database.

2. Inactive/Idle Sessions

You can delete idle user sessions from the Database Sessions window by selecting the record for the session you want to delete, right-click and select Delete, or press the Delete key.

Note: Inactive/idle sessions will automatically expire after a certain amount of time, normally 2 hours.

3. Microsoft Dynamics NAV Database Server only

When the Microsoft Dynamics NAV Database Server is installed, the Sessions parameter is automatically set equal to the number of user sessions on the license that is installed on the server. However, this setting can be changed manually so that maximum sessions are set to less than the number of user sessions on the license installed on the server

You can check Maximum Sessions by going to a command prompt; go to the directory where the Microsoft Dynamics NAV Database server is installed and type SERVER, or go to the directory where the database server is installed from Windows Explorer and double click the Server.exe file.

If Maximum Sessions are set to less than the number of user sessions on your license, the Maximum Sessions parameter can be changed in the Microsoft Database Server Manager Snap-in for Microsoft Management Console or you can change the maximum sessions parameter from the command line when you start the server by entering sessions=XX, where XX is the number of sessions.

You can find this on Partner or Customer source also.

Below is the Horizontal Gridlayout setting,

The very first type should be a container.

2nd Type Group & Subtype as group ,without layout property set to row or column.

3rd Type Group & Subtype GridLayout ,with layout property set as row, and indented.

4th Type Group & Subtype as group,without layout property set to row or column and indented.

After wards select the field you want to show.

You can also search in the help file of NAV or see the Item card->Reorder-Point Parameters fast tab.

Below is a screen shot…

The Microsoft Dynamics NAV Server Administration tool shows settings for the currently selected Microsoft Dynamics NAV Server instance. Settings are grouped into the following tabs, according to service category.

General :- Settings apply to all kinds of services.

Client Services:- Settings apply to RoleTailored clients.

OData Web Services:- Settings apply to OData web services.

SOAP Web Services:- Settings apply to SOAP web services.

NAS Services:- Settings apply to NAV Application Server (NAS) services.

Management Services:- Settings apply to the Microsoft Dynamics NAV Server Administration tool.

Microsoft Dynamics NAV now uses the telephone client that is the default provider on the computer running the RoleTailored client. The call-to functionality is available from pages with phone number fields, such as on the Contacts page or the Customer page.

Filtering Enhancements

You can use filters on lines of any page. For example, in a Sales Order document, on a sales line, press Shift+F3, or choose Add Filter, select the field that you want to filter, and then type a value to filter in the Type to filter box.

Link Sharing

You can share a link to any page with another user who has Microsoft Dynamics NAV installed. That user can open the link in Microsoft Word, Outlook, or OneNote. For example, on the Actions menu of a card or list, choose Copy Link to Page. Open an email message in Microsoft Outlook, and then paste the link in the body of the message. Send the email message that contains the link to another user. When the user clicks the link, the page opens in Microsoft Dynamics NAV.

Financial Management: G/L Entry Table Locking Redesign

The G/L Entry table is not locked at the start of sales, purchase, and service posting. The table remains unlocked until a lock is needed. This can improve performance in multiuser environments.

Financial Management: Dimension Entry Storing and Posting Redesign

A new Dimension Set Entry table has been added. Instead of explicitly storing each dimension value in the database, a dimension set ID is assigned to the journal line, document header, or document line to specify the dimension set. Dimension sets are stored in the table as dimension set entries with the same dimension set ID. By storing dimension sets once in the database, database space is preserved, and overall performance is improved.

Inventory movement is a new warehouse activity document that is used to move items to and from internal departments, such as production and service departments, where posting of the items happens as consumption, shipment, or other.

Inventory movements resemble existing inventory picks and inventory put-aways, but they differ in the following ways:

• Each inventory movement includes both a pick and a put-away, which are represented by a take line and a place line.
• Inventory movements cannot be posted. They can only be registered as warehouse entries. However, the related source document is updated when an inventory movement is registered.
• Inventory movements can be made without a source document through an internal movement.

When you assemble an item to a sales order right before shipping it in basic warehouse installations, then an inventory movement is automatically created to move the components to the assembly area. This happens when the inventory pick for the assemble-to-order item is posted as sold, assembled, and shipped. For more information, see Inventory Pick. For information about the same process in advanced warehouse installations, see Warehouse Shipment.

Warehouse Management: Dedicated Bins

To manage the flow of items in and out of an internal operation area, you can set up locations or machine and work centers with a default bin structure that communicates to warehouse workers where to place components for a particular operation.

Although the items are placed in bins in internal operation areas, they are still part of availability until consumed. To secure bin content for the particular machine center where they have been placed, such as avoiding that they are consumed by another internal resource, you can set the bin to Dedicated, which makes it unavailable to other resources.

Making a bin dedicated provides similar functionality to using bin types, which is only available in advanced warehousing.

Warehouse Management: Integration to Service Orders

Service lines, like other outbound document lines, can function as source document lines for picking to shipment. After a service line is released to shipment, the warehouse handling involved in picking and then shipment posting the service order follows the same flow as for other source documents. For more information, see How to: Prepare Service Line Items for Warehouse Handling.

Inventory: Item Availability Views

To supplement the existing views of item availability, three new availability windows have been added.

• Item Availability by Event
• Item Availability by Timeline
• Item Availability by BOM Level

The Item Availability by Event window shows projected inventory figures by demand or supply event. The window only has information about the dates when figures change because of an event. You can filter the Item Availability by Event window to also include forecasted figures and planning suggestions. For more information, see Item Availability by Event.

The Item Availability by Timeline window provides a graphical view of an item’s projected inventory based on future supply and demand events, including planning suggestions. The result is a graphical representation of the inventory profile. For more information, see Item Availability by Timeline. You can change the quantity and due date of suggested supply orders by drag and drop in the graphical view and then save the changes to the planning worksheet. For more information, see How to: Modify Planning Suggestions in a Graphical View.

The Item Availability by BOM Level window provides availability figures for bills of material that tell you how many units of a parent you can make based on the availability of child items at lower levels. Any item that has a BOM structure, assembly BOM or production BOM, is shown in the window as a collapsible line, which you can expand to see the underlying components and any lower-level subassemblies with their own collapsed BOM structure. For more information, see Item Availability by BOM Level.

With the three new overview windows, you now have a total of six different ways to analyze an item’s availability. You can access all six from item cards and from document lines and worksheet lines for the item by clicking Item Availability By, and then selecting the option in question.

Supply Planning: Planning Parameters

To obtain a rational supply plan, a planner adjusts planning parameters to limit rescheduling suggestions, to accumulate demand (dynamic reorder quantity), and to avoid insignificant planning actions.

Five new reorder period fields have been added to the item card planning parameters to help optimize when and how much to reorder.

For more information, see the following field topics:

• Time Bucket
• Rescheduling Period
• Lot Accumulation Period
• Dampener Period
• Overflow Level

One new reorder quantity field has been added to the item card planning parameters to help optimize how much to reorder. For more information, see Dampener Quantity.

Two new global setup fields have been added to the Manufacturing Setup window to determine how to reorder when item cards do not have a specific planning parameter.

Supply Planning: Calculate and Carry Out

Items on planning lines with warnings typically do not respect the planning parameters. Now, you can define on the Calculate Plan request pages of the planning worksheet and the requisition worksheet that you want certain planning parameters to apply even though the planning line has an exception warning. For more information, see the new option descriptions in Calculate Plan - Plan. Wksh. and Calculate Plan - Req. Wksh., respectively.

When you carry out multiple transfer orders from the Planning Worksheet window that have the same transfer-from and transfer-to codes, then you can select the Combine Transfer Orders option to create only one transfer order. The result is the same as the default behavior when creating transfer orders planned in the Req. Worksheet window.

New Keyboard Shortcuts

With the introduction of the ribbon, some new keyboard shortcuts have been added.

Deprecated Features in Microsoft Dynamics NAV

The following table lists features that have been removed from Microsoft Dynamics NAV. In certain instances, a replacement technology is provided.

Error Message:-
“There are 65000 rows within the filter. Excel only allows up to 65000 rows”.

Now the error has been resolved from NAV 2013 onwards.

Now when you use the standard function of export to excel via analysis by dimension report, NAV now checks for the excel version is not less than Ver 12 and No. of Rows is greater than 65000.