Why Attend BCUG/NAVUG Summit 2019 in Orlando

14/09/201914/09/2019 atotovic Business Central, Conference, Dynamics 365, Microsoft Dynamics NAV BCUG Summit, Business Central, D365BC, Dynamics, Dynamics 365, dynamics 365 Business Central, Microsoft Dynamics NAV, NAV, NAVUG, NAVUG Summit, Orlando, Posting Group, Summit

In a month, BCUG/NAVUG Summit in Orlando will start. There will be dozens of amazing lectures and if you are NAV or Business Central user, this event is probably something you must attend, especially if you want to continue with improving your knowledge.

I like to come back to this event every year as this is probably only one opportunity where you can get directly feedback from thousands of Dynamics users.

This time, I would try to explain why you should attend this amazing event using video message and I hope you will like it 🙂

Posting Groups in Project Madeira

26/04/201626/07/2016 atotovic Microsoft Dynamics NAV, SaaS configuration, Dynamics, Fixed Asset, Madeira, Microsoft, Microsoft Dynamics NAV, NAV, NAV2016, NAVUG, Posting, Posting Group, Project, Project Madeira, SaaS, Setup

When you create a new company in Project Madeira, you will get the new Chart of Account by default. This Chart of Account is created in this case by US legislation (this version is only for US); I hope it will contain for all countries as we will have localisations.

The same thing is with all posting groups. We have these posting groups already created from the beginning, and we need to use them in data migration process. Of course, if you need more posting groups, you need to add new and setup them as well. By default, we have limited set of posting groups:

Customer/Vendor Posting Groups: DOMESTIC
Gen. Business Posting Groups: DOMESTIC
Get. Product Posting Groups: NO TAX, RETAIL and SERVICES
Bank Account Posting Groups: CASH, CHECKING and SAVINGS
Inventory Posting Groups: RESALE

And when you open Inventory Posting Setup for your existed group, you will see that we can add GL accounts, but is has not Locations.

That means we have not locations in the Project “Madeira”. This is not connected only with setup; that also means we cannot use locations in inventory process. You also cannot find fixed assets in Project “Madeira”.

It also means setup is not so hard, but it still requires some specific knowledge about the main thing of system and we cannot expect from client to configure it by himself.

Costing in NAV – Inventory Posting

08/03/2016 atotovic Microsoft Dynamics NAV costing, inventory, Item Ledger Entry, Microsoft Dynamics NAV, NAV, NAV 2015, NAV2016, NAVUG, Posting, Posting Group, Value Entry

Costing methods usually differ in the way that they value inventory decreases. But, regardless of what costing type you use, all of them have minimum one common thing. When the quantity on inventory is zero, the inventory value must also be zero. The next common thing is way of the posting all incoming and outgoing entries. This posting results entries as quantity and as value. Quantity posting describes the change in quantity on inventory and this transaction is stored in Item Ledger Entries. Value posting describes the change in inventory value and this transaction is stored in Value Entries. Each entry in Value Entries table is linked with entry in the Item Ledger Entries table. More entries in the Value Entries table can be applied with the same entry in the Item Ledger Entry.

Each Item ledger entry is applied against each other. All these applications between incoming and outgoing quantities in the Item Ledger Entries are stored in the Item Application Entry table as links between inventory increase and inventory decrease in an Item Ledger Entry. NAV records the entry number of the Item Ledger Entry corresponding to the inventory increase in the Inbound Item Entry No. field and the entry number of the Item Ledger Entry corresponding to the inventory decrease in the Outbound Item Entry No. field. The program also reduces the Remaining Quantity fields in the corresponding item ledger entries by the applied quantity.

Based on the Inventory Posting Setup, system will post all these entries to the General Ledger Entries.

Posting Groups in Assembly Order in NAV

18/02/201619/02/2016 atotovic Microsoft Dynamics NAV Assembly, assembly order, Dynamics, entries, flowchart, Microsoft, Microsoft Dynamics, Microsoft Dynamics NAV, NAV, NAV 2015, NAV2013, NAV2013R2, NAV2016, NAVUG, order, Posting, Posting Group

In my previous articles about using of posting groups in Dynamics NAV, I didn’t describe using of posting groups in Assembly Orders. Assembly Orders are here in the few last versions of NAV and I want to show them as well.

Using of Assembly Orders is not so complex and we can use only Items on header and Items and Resources in lines. Because of that, we can use only Inventory Setup and General Posting Setup. You can see the flow chart with description of usage these posting groups:

When we post one Assembly Order, we will get the following G/L Entries:

Posting Groups in Service Management in NAV

15/02/2016 atotovic Microsoft Dynamics NAV Dynamics, entries, flowchart, Microsoft, Microsoft Dynamics, Microsoft Dynamics NAV, NAV, NAV 2015, NAV2016, NAVUG, Posting, Posting Group, service, Service Management, Service Order

I’ve already wrote 27 articles about using of Posting Groups in NAV. Now, I’ll continue this series with the new topic – Service. When we use Service Order, all posting will be based on the following flow-chart:

You can notice, this is very similar with postings in Sales, but we have some specifics about using of additional fees. But if you look at the part based on Service Lines, everything is the same. I want to accent that this part is drawn for items ()because of usage Inventory Posting Group and Location); if you use G/L Account or Resource, there will not be inventory postings.

Now, let look at the posting results. First, if we decide to post “Ship and Consume” from Service Line, that means these lines have been used for servicing but cannot be included in the invoice to the customer and we will have only inventory postings if we used items (in other cases, we will not have anything for posting):

But if we decide to post “Ship and Invoice” from Service Line, the result will be different. In this case, we have some additional entries except inventory posting:

And on the end, we need to finish posting from Service Order. If we have not some additional fees for invoicing, it will not be anything for posting, but if we have additional fees, it looks the same (for “Ship and Consume” and “Ship and Invoice” examples):

Posting Groups #27 – Deferrals in Sales

03/02/201603/02/2016 atotovic Microsoft Dynamics NAV Deferrals, Dynamics, entries, Microsoft, Microsoft Dynamics, Microsoft Dynamics NAV, NAV, NAV2016, NAVUG, Posting, Posting Group, Sales

Few days ago I’ve published how you can use Posting Groups in Microsoft Dynamics NAV 2016 when you have purchase where you use Deferrals. Now, I want to show you how it looks like when you use Deferrals in sales process. In my old post, you can find everything about using Posting Groups in standard sales process. Now, I’ll show difference. One of the main difference is that system doesn’t use inventory posting groups when posts sales invoice (the same as in purchase scenario).

In the following chart, you can understand how system uses Posting Groups when we have deferrals on Sales document:

When we post document and get Posted Sales Invoice, we will get the following G/L Entries. You can find completely description of them in the next table:

When you use Items and Resources, system will use Sales Account from General Posting Setup, but if you use G/L Account in the sales line, system will use this G/L Account you typed.

You can notice that we have more line amounts. Number of lines is based on number of period defined in Deferral Template. For each period, we have two lines (positive and negative). We have always first period lines, but other period lines are behind all entries, because they have not the same posting date. Their posting date is based on setup in Deferral Template.

And I’ve forgot one things in the last post. If you want to see all lines using Navigate, you have to delete Posting Date in Navigate page or if you didn’t it, you have to delete Posting Date from filters in General Ledger Entry.

Posting Groups #26 – Deferrals in Purchase

01/02/201601/02/2016 atotovic Microsoft Dynamics NAV chart, Deferrals, Dynamics, entries, GL, Item, Microsoft, Microsoft Dynamics, Microsoft Dynamics NAV, NAV, NAV2016, NAVUG, Posting, Posting Group

Last year I had a series of articles about using Posting Groups in Microsoft Dynamics NAV. Now, I want to continue with some small updates.

I already wrote about using Posting Groups in purchasing process, but now I want to add a model when we use Deferrals (a very nice new feature in NAV 2016). In this case, we have some differences compared with a standard posting. System will use some different rules about Posting Groups (you can check standard purchase posting model here). In the following chart, you can understand how system uses Posting Groups when we have deferrals on Purchase document:

When we post document and get purchase posted invoice, we will get the following G/L Entries. You can find completely description of them in the next table:

What is Posting Preview in NAV 2016?

05/10/2015 atotovic Microsoft Dynamics NAV Directions, Directions EMEA, entries, Microsoft, Microsoft Dynamics NAV, NAV, NAV2016, NAVUG, objects, Posting, Posting Group, Preview

I’m sure that your clients many times asked to make some feature to see results of posting before they post document, at least G/L entries as report. My clients asked for this a hundred times.

This was on first sight very simple requirement, but in practice… Now with NAV 2016, we finally got it. And not only we did get it… we have got the awesome feature. It looks like so simply and because of that it is awesome.

You just need to click on Preview Posting command in your ribbon and you will get completely navigated page with all entries (G/L entries, Customer/Vendor entries, VAT entries, Value entries…). Everything is the same as you already post this document, but this is not posted. All links are here… perfect.

Of course, you will not see Document No. for example; this is because we still have not this data.

You can find this feature on almost all documents and journals. It miss maybe only on few of them. This solution is based on temporary tables. When you look at these objects, everything will be clearer.

Try it and you will see how good it is.

Posting Groups #25 – Job WIP Posting (3 – Cost Value)

18/06/201518/06/2015 atotovic Microsoft Dynamics NAV Contract, course, GL, Job Task, Jobs, learn, Microsoft, Microsoft Dynamics NAV, NAV, NAV 2015, NAV2013, NAV2013R2, NAVUG, Posting Group, Schedule, Tips & Tricks, usage, WIP

In one of my previous posts, I have already described how you can post Job WIP entries if you use Cost Value as recognized cost in WIP posting method. But, it was only part of posting when you calculate Job WIP for the first time. But if you have already posted Job WIP entries and want to post WIP, again after new usage posting (as Contract).

In this situation, system first need to post correction of previous Job WIP entries and that post new entries. You can see how there G/L entries look like on following table:

When we speak about “Remaining Cost in Comparison with Schedule”, we already think about relation between Contract usage posting and values as Schedule.

Posting Groups #24 – Job WIP Posting (2)

12/06/2015 atotovic Microsoft Dynamics NAV course, GL, Job Task, Jobs, learn, Microsoft, Microsoft Dynamics NAV, NAV, NAV 2015, NAV2013, NAV2013R2, NAVUG, Posting Group, Tips & Tricks, usage, WIP

If you have the same example as in previous post, but with using different methods of WIP posting (e.g. Completed Contract, Cost of Sales or Contract-Invoiced Cost), you will get the some different results. To repeat, my example was only posted usage of resources and items, without invoicing. System calculates WIP for all Resource and Item usage, based on Unit Cost and consumed Quantity. Result of this posting is following: