• Home
  • About Me
  • Contact Me
  • Downloads
  • White Papers
  • Web Sites
  • Post List
  • Articles
  • FAQ

Olof Simren - Microsoft Dynamics NAV & 365 Business Central Blog

  • Home
  • About Me
  • Contact Me
  • Downloads
  • White Papers
  • Web Sites
  • Post List
  • Articles
  • FAQ

Dimensions on Production Orders

April 4, 2014 Posted by Olof Simren Finance, Manufacturing 9 Comments

The dimensions involved in posting production orders are a bit interesting. It is interesting since there is a slight difference between on how they behave compared to other parts of Microsoft Dynamics NAV (like the sales and purchase orders). It can be argued what is right and wrong, but knowing how it works in standard Dynamics NAV is requirement for setting a system that is easy to work with and provides correct reportable and understandable data. As an example; if you have default dimensions on the items and set them up with the ‘Value Posting’ equal to ‘Same Code’ and you mix items with different default dimension values on a production order you will not be able to post it (this is a very common mistake).

An example of how it is working:

We have a dimension called ‘ITEMGROUP’ for the items, we default the ‘ITEMGROUP’ dimension value on the Bicycle we are producing to be ‘SPORT’ (e.g. sport products).

BicycleDimension

We then default the ‘ITEMGROUP’ dimension value for the components that goes into making the Bicycle as ‘COMP’ (e.g. components).

FrontWheelDimension

Work Centers also have dimensions, in our example we default the ‘DEPARTMENT’ to ‘PROD’ (e.g. production) for the work center where the production is done (e.g. the assembly department). Note that machine centers do not have dimensions but will inherit the dimensions from the related work center during postings.

WorkCenterDimension

We now create a production order for the bicycle and have a look at where we can see the dimensions. The production order header has the dimensions according to the output item (as expected).

ProductionOrderDimension

So does the production order line (also as expected).

ProductionOrderLineDimension

And even the production order components get the dimensions according to the output item (less expected).

ProductionOrderComponents

This is what can be argued if it is right or wrong since the consumption posting of the components will then get the dimensions according to the default dimensions on the item being produced and not according to the default dimensions on the individual components. Defining the default dimensions on the components with the ‘Value Posting’ equal to ‘Same Code’ will for this reason not work, neither will it work to create reports like inventory value per ‘ITEMGROUP’ since the components inventory in this case will be debited with ‘COMP’ and credited with ‘SPORT’. As long as users are aware of this there will probably not be any issues. If there is, changing the code to use the default dimensions from the component items on the production order components is not too hard (look out for a future blog about this).

Looking at the routing of a production order you will see that there are no dimensions at all.

ProductionOrderRouting

This is how it is, although it would have been nice to see and being able to adjust the dimensions on each individual operation in the production order routing.

Opening the production journal you will see that the components have the dimensions according to the item being produced (just like on the production order components, so no surprises here).

ProductionJournalComponentDim

While the operations have the dimensions as the combination of the dimensions on the production order line and the default dimensions defined on the related work centers (and here it can be changed).

ProductionJournalRoutingDim

The components are then posted through the production journal (without altering the dimensions in the journal) and all the consumption item ledger entries (and the related value and g/l entries) get the ‘SPORT’ dimension value for the ‘ITEMGROUP’ dimension.

ConsumtionDimensions

Then the outputs for all operations are posted through the production journal (without altering the dimensions in the journal) and the output item ledger entry (and the related value and g/l entries) gets the ‘SPORT’ dimension value for the ‘ITEMGROUP’ dimension and the ‘PROD’ dimension value for the ‘DEPARTMENT’ dimension (inherited from the work center).

OutputDimensions

Same dimensions go on the capacity ledger entries (and the related value and g/l entries).

CapacityLedgerDimensions

The production order is then changed to finished, being on a standard costing method this calculates and posts the variance into a variance account in the P&L. The variance is posted with the dimensions according to the output (in this case with both the ‘ITEMGROUP’ and ‘DEPARTMENT’ dimensions).

VarianceDimensions

Conclusion

The consumption is posted with dimensions according to the item being produced but without any of the dimensions defined in the work centers. In the general ledger this should only be balance sheet transactions, so not having the department dimension in our case should not be an issue since it is probably more applicable to the P&L transactions.

The output, capacities and variance are all posted with both the dimensions from the item being produced and from the work center (assuming that if you have multiple work centers with different dimension values, then it is the work center on the last operation that controls the dimensions on the output and variance).

On as side note; when creating a production order from a sales order you also get the dimensions from the sales order line on the production order, this is quite nice. 🙂

Share this:

  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on X (Opens in new window) X

Related


Discover more from Olof Simren - Microsoft Dynamics NAV & 365 Business Central Blog

Subscribe to get the latest posts sent to your email.

Tags: DimensionsFinanceProduction
9 Comments
Share
4

About Olof Simren

I am a Microsoft Dynamics NAV and 365 Business Central Expert, I started implementing Microsoft Dynamics NAV in 2002, back then it was called Navision Attain. Throughout the years there has been many exciting implementations in different parts of the world, all of them with different challenges but with one common theme; manufacturing. As a consultant, I bring over 20 years of experience in implementing Microsoft Dynamics NAV and 365 Business Central within manufacturing and distribution companies. The services I offer includes project management, consultation, development and training. Feel free to contact me if you need help with anything related to Microsoft Dynamics NAV or 365 Business Central. I work through my company Naviona where I team up with other skilled Microsoft Dynamics NAV and 365 Business Central Experts.

You also might be interested in

Production Lot Sizes

Apr 24, 2014

In the manufacturing part of Microsoft Dynamics NAV there are[...]

Mandatory Dimensions by Account Type

Feb 20, 2014

Dimensions are great in Dynamics NAV and one of the[...]

Default Dimension Priorities for Production Order Components

May 4, 2014

In one of my earlier blog posts, Dimensions on Production[...]

9 Comments

Leave your reply.
  • Henrik Ohm
    · Reply

    July 31, 2014 at 3:50 AM

    Hi Olof

    Thank you for a very nice blog with good articles. I can see that you have been messing around with some of the same issues I have 🙂 Keep up the great work!

    Regarding the dimensions: I have wondered about the Same Value issue as well. I have come to the conclusion that while it’s a bit weird to tell a customer that they shouldn’t add Same Value on components (makes sense for pos/neg adjust to have it) then it’s easier to have dimension analysis on output cost vs. consumption cost for a single ITEMGROUP output item if the dimensions are equal. If component and output items are different (normal logic) then comparing costs for output/comsumption is a bit more difficult. The capacity ledg. also gets the order line dimensions and therefore a complete analysis can be made: Output Cost vs. material cost vs. work cost.
    I know that different reports exists to see this information per production order, but you know Finance – they don’t care for that kind of details – only that the costs should match the G/L 🙂

    Again thanks
    Henrik

    • Olof Simren
      · Reply

      Author
      August 1, 2014 at 11:07 AM

      Hi Henrik,
      Thanks for your comments. Yes, it is a very recurring topic during implementations.
      You can also do this mod and then the issue will go away:
      http://www.olofsimren.com/default-dimension-priorities-for-production-order-components/

      /Olof

      • Henrik Ohm
        · Reply

        August 4, 2014 at 9:35 AM

        Hi Olof

        Yes I’m aware, but thanks 🙂 Sometimes as a consultant one needs an explanation why NAV acts the way it does.
        I’m a programmer myself and have made nummerous hacks on standard NAV to make it work as we expect it to. It’s just that there is a deeper meaning (sometimes) to why NAV is weird and programming is not always the answer.

        In a production scenario the above solution would have to choose either T5406 or T27 dimensions for output and consumption entries. If priority is on 5406 then it’s standard NAV, but if priority is on 5407 then there is a mismatch that cannot be solved. The ITEMGROUP is still only one or the another, not both.

        That’s why another (non-programming required) solution is to:
        1. Component item ITEMCOMP = COMP, ITEMFINISH = ”, because it’s not used as fisnished
        2. Fisnished item ITEMCOMP = ”, ITEMFINISH = SPORT.
        3. Semi-fab. as finished and component ITEMCOMP = COMP, ITEMFINISH = SPORT.
        This will make it possible for you to BOTH analyse same item as consumption AND as finished item using dimensions.
        The finished item ITEMFINISH = SPORT will override the COMP, but ITEMCOMP = COMP will still stand.

        When people are using ITEMGROUP for the same item for two different purposes then it doesn’t work. That’s the same as saying DEPARTMENT = SALES and DEPARTMENT = LOGISTICS on the same item. It doesn’t make sense, because it’s two different contexts and uses for the same item 🙂

        Still I do understand why you have posted the solution, because many companies ask on this topic.

        Br,
        Henrik

        • Henrik Ohm
          · Reply

          August 4, 2014 at 9:37 AM

          “but if priority is on 5407 then there is a mismatch” => “but if priority is on 27 then there is a mismatch”

          sorry..
          Henrik

  • Karl
    · Reply

    August 9, 2014 at 2:15 AM

    Great post and blog! 🙂

    Ended up setting all our product dimensions to Code Mandatory, it works ok and users are aware of that consumption transactions are posted with a different dimension than the one setup on the item.

    We tried the other suggestion with setting up different dimensions for different types of products but it didn’t work for us. Sometimes we have finished products as components and also subassemblies that go into subassemblies, and then it became wrong. Also, setup mandatory dimension for items was not possible since some items have some dimensions and some items have some other dimensions.

    Cheers!!

    • Henrik Ohm
      · Reply

      August 9, 2014 at 3:31 AM

      I get your point Carl. I can in clear hindsight see why my suggestion on double dimensions per item will not work in multi hierarchy structures. Here the ITEMCOMP dim on the finished item will override the component and it will get us nowhere.

      Henrik

  • Amanda
    · Reply

    November 6, 2015 at 10:28 AM

    Hello Olof

    This is a brilliant post, nicely laid out and explained. Looking forward to future posts!

    Amanda

  • Stewart
    · Reply

    September 14, 2016 at 9:30 AM

    dimensions do not work in Nav MRP manufacture from a sales order line using the MRP worksheet.

    effectively this means it cannot do contract costing across multi level order networks, or single.

  • Slavic
    · Reply

    July 25, 2019 at 6:21 PM

    Hi Olof,

    Love your blogs, – they really highlight a lot of interesting topics and quirks of NAV. Thank you for spreading the knowledge throughout the NAV community.

    On the topic of dimensions for components, we were able to achieve assignment of the appropriate department dimension by setting it in CU99000773 for components that actually credit consumables to a P&L department.

Leave a Reply

Your email is safe with us.
Cancel Reply

My Dynamics NAV Partner

Naviona, LLC

Developers Wanted

Naviona is looking for NAV/BC developers. Let me know if you want to work with the best (instead of the rest :-)).

Categories

  • Assembly (3)
  • Development (31)
  • Finance (14)
  • General (26)
  • Inventory (22)
  • Manufacturing (34)
  • Miscellaneous (25)
  • Purchase (9)
  • Sales (11)
  • Warehouse (7)

Tags

.net Add-in Assembly Assembly BOM CAL Capacity Components Consumption Contact Costs Customer Development Dimensions Excel Finance Flushing General Ledger Inventory Item Items Lot Size Low-Level Code MRP NAV 2015 NAV 2016 Output PDF Planning Production Production BOM Production Orders Purchase Orders Receipts Reporting Reports Role Center Routing Sales Sales Order Sales Orders Stockkeeping Unit Subcontracting Task List Warehouse Warehouse Shipment

Recent Posts

  • XML Buffer and CSV Buffer Tables
  • Functionality Improvements in NAV 2017
  • Reversing Production Output and Consumption
  • Return Merchandise Authorization (RMA)
  • Sales Quote without Customer
  • Parallel Routings
  • Add Fields to the Item Tracking Lines
  • Field Level Security using Events in Dynamics NAV 2016
  • Schedule MRP
  • Activate WMS Functionality for Existing Location

Categories

  • Assembly
  • Development
  • Finance
  • General
  • Inventory
  • Manufacturing
  • Miscellaneous
  • Purchase
  • Sales
  • Warehouse

Contact Us

We're currently offline. Send us an email and we'll get back to you, asap.

Send Message

Categories

  • Assembly (3)
  • Development (31)
  • Finance (14)
  • General (26)
  • Inventory (22)
  • Manufacturing (34)
  • Miscellaneous (25)
  • Purchase (9)
  • Sales (11)
  • Warehouse (7)

Tags

.net Add-in Assembly Assembly BOM CAL Capacity Components Consumption Contact Costs Customer Development Dimensions Excel Finance Flushing General Ledger Inventory Item Items Lot Size Low-Level Code MRP NAV 2015 NAV 2016 Output PDF Planning Production Production BOM Production Orders Purchase Orders Receipts Reporting Reports Role Center Routing Sales Sales Order Sales Orders Stockkeeping Unit Subcontracting Task List Warehouse Warehouse Shipment

Recent Posts

  • XML Buffer and CSV Buffer Tables
  • Functionality Improvements in NAV 2017
  • Reversing Production Output and Consumption
  • Return Merchandise Authorization (RMA)
  • Sales Quote without Customer
  • Parallel Routings
  • Add Fields to the Item Tracking Lines
  • Field Level Security using Events in Dynamics NAV 2016
  • Schedule MRP
  • Activate WMS Functionality for Existing Location

Recent Comments

  • Isabel de los Santos on Production Lot Sizes
  • Abdelatif EL HANI on Reversing Production Output and Consumption
  • Roshan on Processing of Receipts
  • kuldeep Nama on Subcontracting Part 1: The Basics
  • Janine on Flushing Methods
  • Nathalie on Activate WMS Functionality for Existing Location
  • Georges W on Bill-to vs. Sell-to Customer
  • Richard L on Subcontracting Part 4: Warehouse Receipts

© 2025 · Olof Simren

  • Home
  • About Me
  • Contact Me
  • Downloads
  • White Papers
  • Web Sites
  • Post List
  • Articles
  • FAQ
Prev Next