Month: May 2015

Posting Groups #10 – Item Returns Posting (Sale & Purchase)

atotovic Microsoft Dynamics NAV , , , , , , , , , , , , , , ,

In my earl posts about posting groups, I have showed purchase and sales processes. But both of these processes have its opposite processes.

If our customer wants to return items to us, we can use the Sales Return Order for this. When we finish posting, we will get Return Receipt and Sales Credit Memo as result.

On other side, if we want to return items to our vendor, we can use the Purchase Return Order for this. As result of posting, we will get Return Shipment and Purchase Credit Memo.

I will not prepare flow chart about using posting groups, because we can use the same schemas as we already have in Item Sale Posting and Item Purchase Posting posts.

First, I will describe sales return process. When we post Return Receipt, we will get only these G/L Entries:

##1

But, when we finish posting and post Sales Credit Memo, we will get more G/L Entries:

##2

The similar situation is in purchase return process. When we post Return Shipment, we will get again only these G/L Entries:

##3

But, when we post Purchase Credit Memo for this item, we will get more G/L Entries:

##4

And, on the end when we run Adjust Cost – Item Entries batch job, we will get the following G/L Entries (variance between expected and actual cost):

##5

Posting Groups #9 –Item Sale Posting with Payment Method

atotovic Microsoft Dynamics NAV , , , , , , , , , , ,

I have already showed item sale process posting here in Posting Group #2 post. But, we can have some specific variants of this posting. One of them is when we use Payment Method.

If you choose Payment Method code on sales document header, and this Payment Method has configured Bal. Account Type and Bal. Account No., NAV will automatically create the balancing journal line. This functionality is great when we are being paid in full at the time of sale, but we can use this feature in some other specific process.

You can see how system works with Payment Method on following flow-chart:

SalesPMC

When we finish with this Sales Order posting, we can find following G/L entries navigated to Posted Sales Invoice. You can see standard G/L entries about invoice and the last two of them, connected with Payment:

SI_PyM_GLe

New Cumulative Update 7 for NAV 2015 has been released

atotovic Microsoft Dynamics NAV , , , , , , ,

Cumulative Update 7 for Microsoft Dynamics NAV 2015 has been released today, one hour ago. It includes the most of application area (Administration, Cash Flow, Client, Finance, Fixed Assets, Inventory, Jobs, Manufacturing, Purchase, Sales, Service and Warehouse) on almost 80 objects and very useful platform hotfixes and regulatory features that have been for Microsoft Dynamics NAV 2015. If you are upgrading to this cumulative update (CU7) from a cumulative update earlier than CU4 (build 39663), you first must convert the database.

It also has a lot application hotfixes for following localizations: Australia, Belgium, Switzerland, Czech Republic, Germany, Spanish, France, Italy, North America, Netherlands, Norway, Russia and Sweden.

You can download Cumulative Update 7 for Microsoft Dynamics NAV 2015 from here. This CU is named as Build 40938.

Posting Groups #8 – Revaluation Posting

atotovic Microsoft Dynamics NAV , , , , , , , , , , , , , , , ,

In my last post, I have touched Revaluation process, but only for Standard cost changing. We can use Revaluation for other cases, as well.

If we change cost only for items on stock, it will be the same situation as on previous example. But, if we want to change cost for already sold or consumed stock, it will be with some differences. First, when we change the cost, we will get the same entries, as I already show in previous post. But, when we run Adjust Cost – Item Entries batch job, we will get the new G/L entries.

I made three scenarios:

In the first scenario, I have raw material with FIFO cost type. I consume this raw material on production order to produce finish goods, configured as also FIFO cost type. In this case, result of posting in G/L entry will be as following:

RevPOfifo

In the second scenario, everything was the same, but only finish goods was configured as Standard cost type. In this case, result of posting in G/L entry will be a bit different, as following example:

RevPOstd

And, in the third scenario, I change the cost on already sold items. In this scenario, G/L entries will be as following:

RevSO

Posting Groups #7 – Change Standard Cost

atotovic Microsoft Dynamics NAV , , , , , , , , , , , , , ,

If you use Standard cost type for your Items and you want to change it, you need to use Standard Cost Worksheet. When you run Implement Standard Cost Changes command, all changes will be moved to Revaluation Journal.

When you post Revaluation Journal, you will get following G/L entries, if you have cost increasing:

std_rev_1

If you have cost decreasing, you will get the same Accounts, but the different values, as following:

std_rev_2

Posting Groups #6 – Manufacturing Posting (Std. Cost Type)

atotovic Microsoft Dynamics NAV , , , , , , , , , , , ,

In my previous post, I describe all G/L posting results when we do with production, but using FIFO costing method. It this new example, I will describe results of posting when we have finish goods with Costing Method configured as Standard.

In this case, we use the same flow chart for posting groups, as I have described in my previous post.

In this example, when we post consumption and output, we will get following entries in G/L Ledger. In this case, we will get entries from cost of Item consumption and cost of Work Centers using, and value for output Item based on Standard Cost:

C&OJPstd

When we change status of Production Order to Finished, we will get additional G/L Entries. These are correction of standard cost on output Item and variance from standard to actual cost. You can find these entries in next table:

POsFstd

Posting Groups #5 – Manufacturing Posting

atotovic Microsoft Dynamics NAV , , , , , , , , , , , ,

When we post manufacturing processes, we have Production Order as the base document. Then, we can use Production Journal (for posting in one step), or Consumption and Output Journals (for posting in two steps). Never mind, what you variant use, result in G/L Entries is the same.

In any case, we have some rules about using posting groups. Some posting groups are used from items, and other from work centers. In following chart, you can see how system uses posting groups in manufacturing posting.

Production Diagram

Difference in G/L Entries can be based on Costing Method you use for output items. It is not the same when you use Standard or some other costing methods. In this example, I will describe non-standard method (in this case I have used FIFO). I will describe using of standard method in next post.

In this example, when we post consumption and output, we will get following entries in G/L Ledger. These are only cost of Item consumption and cost of Work Centers using:

C&OJPfifo

When we change status of Production Order to Finished, we will get additional G/L Entries. These are cost of output Item, calculated from consumption Items and Work Centers usage. You can find these entries in next table:

POsFfifo

Posting Groups #4 – Adjust Cost – Item Entries Posting

atotovic Microsoft Dynamics NAV , , , , , , , ,

When we run Adjust Cost – Item Entries batch job, system forwards any cost changes from inbound entries, to the related outbound entries. In our small example, we will see what we will get after post Item Charges to already sold items. Currently, we will use very simple example; we have only purchased and sold item.

In this example, automatic cost adjustment is not configured. We can use example with additional costs using Item Charge or using higher cost on Invoice in comparison with Receipt.

When we run this batch job, we will get G/L Entries as result. You can find completely description of them in next table:

ACIE-1

System will post only the difference between the higher and lower costs. System will use Inventory Posting Setup from Inventory Posting Group and Location on source document. On the same way, system will use General Posting Setup from the same source document, but from General Business and Production Posting Groups from document header and line.

In some other examples, it can be more complex posting, but I will process this examples in another articles.

MS Network 5 Retrospection

atotovic Conference, General, Microsoft Dynamics NAV , , , , , , , ,

Last week, I was mainly in Neum (Bosnia and Herzegovina). Small town Neum on Adriatic see was a host of the MS Network 5, the biggest Microsoft Conference in Bosnia. I was on this conference for the second time, and I’m honored to be a part of this conference.

I have spent a 24 hours in my car on this trip, but I’m still happy about my participation on this conference. This is not Dynamics conference, but I was impressed how many people want to learn something about NAV. I had to stay an extra half-hour after the lecture to give an answers on all questions and I’m really happy about this. People want NAV and want to upgrade to the newest version.

Except my lecture, I attended on other sessions and learned a lot of news about other technology from my friends (outside NAV). I think I have to learn other technology every time I can. We have a small problems about internet in hotel, but this was a challenge how to prepare demo on Azure without internet :). But we solved all these problems, and everything was an awesome.

Big thank to Enis and other guys from Microsoft in Bosnia. I will gladly be a part of this conference the next year. We had adventures on trip (guys in my car know what I say) and big friendship on conference. In one word, awesome. See you.

WP_20150428_004

Posting Groups #3 – Item Charges Purchase Posting

atotovic Microsoft Dynamics NAV , , , , , , ,

When we post purchase of items, we have item charges very often. We can post item charges on the same order with items or on different one. In my example, I will use independent document for already receipted items.

In this case, we have the similar rules about using posting groups as we post item purchase. Some posting groups are used from document header, and other from document line, as I already described in older post. But, in this case some of posting groups are inherited from the already posted receipt. You can see all combination on following chart:

Dijagram Item Charge

When we post this document, we will get G/L Entries as result. You can find completely description of them in next table:

PPI-ic