Quantcast
Channel: Microsoft Dynamics AX Forum - Recent Threads
Viewing all articles
Browse latest Browse all 175888

RE: System generated inventory markings

$
0
0

There are certain types of updates that will cause the system to automatically mark transactions together. For example, when you create a direct delivery purchase order from a sales order, or when you create a production order directly from a sales order.  There are also options to updating marking when orders are generated from master planning.

Let me not just repeat what others have already done see Evert Bos's 2 part article Note the AR reservation parameter.http://www.sikichtech.com/insights/marking-microsoft-dynamics-ax-part-1-understand-basics/

Intercompany purchase and sales orders used to be marked to each other. This is no longer true in AX 2012.  Special links in the action bar are available just for intercompany references. These references can no longer be removed as was possible in 2009 and older versions.

To find out whether marking exists, check the inventory pull-down menu on any line of any transaction. Or also check the "Product" tab of a sales line, a purchase line.

In Production orders the references show in a different way.  If the marking was created by firming a planned order, then the references are not always populated, even though marking exists.  When firming planned orders, choose whether to: use marking, or standard marking, or extended marking.  This parameter setting is not enforced. It provides the default value for the user default.

In the inventory section of the Action bar of the Production order grid is the "Update markings" option. The interesting feature is the "Related information" in the View tab, which gives the Reference list. This screen shows all production orders that are marked to each other. A multi-level hierarchy of marked orders is shown, together with the BOM level of the related sub-bom production orders.

For the production order status change, there is a checkbox "References” which is about those "referenced orders", orders that are marked and can be processed together as a group.

For the Scheduling. Status   There are two checkboxes:  "Schedule References" and "Synchronize references". When you schedule a production order, and include all the referenced orders, i.e. the marked orders, so that you can synchronize all of their dates. This works from any production order in the reference group whether the parent Production order or the sub bom orders.

This linking means that you can also update the status of all the group orders to Start.

Pegged Supply line type in the BOM creates marking relationships between production orders, with the same result as  firming planned production orders with marking set to ‘standard' or ‘extended'.  MRP will do the BOM explosion from those that are "Pegged Supply and will create planned production orders " that are "directly derived" and which display as "Dynamic”.

You can reserve the inventory for any dimension that is tracked physically. When using standard costing, system generated marking works the same way, but the user cannot manually mark anything.

 

 

 

What is marking?

Marking is a database link between a supply and a demand transaction for the same item. It is the same type of relationship as pegging in the Master Planning module. The difference is that pegging can change any time, after each MRP-run, while marking is a semi-permanent link that can only be removed manually or by running the sales order line explosion with the checkbox 'remove marking'. It is a solid link between two transactions.

There is a second difference with pegging. Marking has a financial aspect and I believe the original reason of existence for this functionality is the effect it has in costing. At month end closing, any marking links between demand and supply orders override the cost method of the item. This has no effect when the item is on standard cost, but for FIFO or LIFO, marking will override whatever the system would have done following FIFO or LIFO. Marking increases the precision of FIFO costing, making it truly actual cost. With marking we know exactly which supply order was used for which issue transaction.

Marking creates links in the logistic/supply chain, which is our main focus for this article. It creates references between orders. This supports key functionality in many functional areas. A marking link always creates an ordered reserved transaction. This is not true the other way around.

Microsoft Dynamics AX marking

Above a typical example of marking between a direct delivery Purchase order and a Sales order line. The green checkbox is a sign that the marking exists. In this case the marking is for the full quantity of the purchase line.

Microsoft Dynamics AX marking

The bottom half of the marking screen. This will show details of the demand transaction, the sales order. It is very interesting to look at the date fields. 1/31/2016 is the requested ship date. The other dates fill in when we actually ship and invoice.

Marking means item references

To find out whether marking exists, we can always check the inventory pull-down menu on any line of any transaction.

Microsoft Dynamics AX marking

We can also check the "Product" tab of a sales line, a purchase line. In Production orders the references show in a different way. See the paragraph about Production orders and marking further below. (Warning: if the marking was created by firming a planned order, the references are not always populated, even though marking exists. See paragraph about Master Planning)

In the product tab we would see an item reference. Microsoft Dynamics AX marking

System generated marking

There are many business scenarios in AX that require marking to function. Marking is used there for logistic and costing reasons:

  • Subcontracted purchase orders or subcontracted production orders are marked to the Prod- BOM line of the finished item Prod order.
  • Direct delivery purchase orders are marked to the sales order line
  • When using line type "pegged supply" in the BOM,  production orders for lower level components that are created during Estimation are marked to the parent production order BOM lines
  • RMA lines created from copying from the original sales line are marked to that original sales line
  • Return purchase order lines created from the original PO line are marked to that original PO line
  • NOTE: Intercompany purchase order lines and Intercompany sales lines are no longer using marking since AX 2012.The product tab does not contain item references either. Special links in the action bar are available just for intercompany references. These references can no longer be removed as was possible in 2009 and older versions.

The user could manually remove these system-generated markings but it would break the functionality.  Is removing a marking link ever necessary? Yes, there are error situations where removing the marking is required to solve the problem. But those are rare occurrences. Normally the user will not touch these system-generated markings.

Marking and Master planning

When firming planned orders, we can choose whether to use marking, use standard marking or extended marking. 

Microsoft Dynamics AX marking

WARNING. This parameter setting is not enforced. It only provides the default value for the user default. The user defaults are determining the marking parameter value. Once a user firms with marking = no, the screen will always come back with default ‘no' for this user.

NOTE: some customers have modified the system so the parameter in the Master Planning parameters does enforce its value for all users.

A better customization might be to link the marking parameter to coverage groups, assuming item numbers involved in MTO and ETO scenarios could be identified.

For now, the user has to be aware of his/her default setting in the Firming window itself.

The help text for this parameter follows below.

Microsoft Dynamics AX marking

The standard/extended difference is only relevant when my supply order quantity is larger than the demand. That part is mentioned in the help text. What is not mentioned so clearly is that the difference between standard/extended has nothing to do with the marking link itself. In both cases we will see the link with the familiar green checkbox in the marking screen. But with "standard" we would not see the item references filled in in case of an over-supply.  In a Make-to-Order scenario this would be very unwise, we want to see that Sales order reference on a production order even if the quantity of the order is larger than the sales line quantity.  Normally the quantities would match. We recommend to use "extended" just to make sure we have maximum visibility.

Marking in Production

In Dynamics AX I can always get to the marking screen through the pull down menu "inventory". In the production module this is also true, but there are special access points for marking there, reflecting the fact that the marking functionality for production is quite important.

Microsoft Dynamics AX marking

In the inventory section of the Action bar of the Production order grid we find the "Update markings".

Microsoft Dynamics AX marking

It accesses the same marking screen we find everywhere else. In this case there are two sales order lines that are being marked "to" one production order.

Microsoft Dynamics AX marking

In the  section "Related information" in the VIEW tab, we have the Reference list.

This is the more interesting choice!

Microsoft Dynamics AX marking

This is a reference list with one parent order and two child orders. The Name field has been added through personalization. If you look close, you will see that the scheduled order dates are synchronized.

This screen shows all production orders that are marked to each other. A hierarchy of orders is shown. This family of orders can have as many levels as necessary.

This is great for MTO and ETO companies! The BOM level is also indicated.

The marking links show as references also. For the finished item in the production order, there is a fast tab ‘references', see below.

Microsoft Dynamics AX marking

The Summary reference is the production order I am on right now.

Microsoft Dynamics AX marking

In the Prod-BOM we have a Reference tab. This is where we always see the Subcontract Purchase orders. We will see any reference orders there.  In this example we see the two child Production orders of the Production order I am currently on.

Using the "references" checkbox in Production order status change

For the production order status change, we will often see a checkbox "references". We should realize that this is about "referenced orders", orders that are marked.  This means I can process them as a group.

Microsoft Dynamics AX marking

  • Estimation. When I estimate, there is a ‘references' checkbox, when checked, I will estimate the entire family of orders.

Microsoft Dynamics AX marking

  • Scheduling. This is an interesting transaction for marking. There are two checkboxes:  "Schedule References" and "Synchronize references".  When we schedule a production order, and we include all the referenced orders, the marked orders, it makes sense to synchronize their dates. This works from any production order in the reference group. I can schedule the parent Production order or the children, the result is the same.

Microsoft Dynamics AX marking

Release:  I can release the entire family of orders

Microsoft Dynamics AX marking

  • Start. I can start the entire family of orders.
  • Report as finished has no option for references. This makes sense. Orders get completed one by one from the bottom up. A massive Report as Finish would only make sense for contract manufacturing scenarios where I receive my end product from the contractor and I have to Report as finish all prod orders in a batch, starting on the lowest BOM level.
  • End. There is no reference checkbox here. Some companies do run a batch program that ends a bunch of production orders.

Viewing all articles
Browse latest Browse all 175888

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>