Semi-finished goods in an advanced warehouse

Semi-finished goods in an advanced warehouse

The management of semi-finished goods in the Production control module in Dynamics 365 SCM is notoriously messy in conjunction with the WHS (warehouse management), see my blog Missing flushing principle. The challenge is posed by the system if the material flows on the production shop floor do not require license plate handling, i.e. if people only need scanners to pick raw materials from the warehouse, but do not need them when passing semi-finished products from one working station to another. It becomes even harder if production orders overlap, i.e. if the downstream production order relies on a constant inflow of semi-finished orders and is started shortly after the upstream production order.

Preamble

We evaluated various scenarios:

  • a separate non-advanced warehouse in production is awkward, because every demand of raw materials results then in a transfer order which is a substantial overhead both in shipping and receiving. Moreover, transfer order put away directives do not ‘sense’ warehouse locations with material shortage, i.e. you cannot ‘aim’ multiple work station locations in one transfer order. Managing multiple transfer orders to different logical warehouses is even a greater overhead compared to a warehouse production picking wave, which flexibly consolidates all picking work for a production order or even for a set of production orders;
  • withdrawal Kanbans are awkward, because they require standalone rules for every material and every workstation. Managing BOMs is much easier than managing Kanban flows and withdrawal Kanban rules (where you don’t even have a data entity to import or update them in bulk!).
    Moreover, Kanbans do not ‘sense’ locations either, and rely on the MRP to trigger them. But the master planning usually does not consider the warehouse location level: if you do so, this renders the advanced warehouse management obsolete. We end up with logical warehouses per machine again. Finally, the MRP is not instant, the master planning may run for hours, but you need the material now!
  • phantom sub-assemblies do not invoke any movements at the warehouse and remain a viable and very safe alternative: the first inventory transaction will be at the very end of the last machine in the chain. This approach is not always possible (at least no at all stages in production) if the factory is required to count WIP items or builds up a safety stock of them.

The approach described below uses classic BOMs and production routes in combination with work policies or automatic work. Every route has a resource (machine, work station), and every resource is associated with one inbound and one outbound warehouse location. Materials in the BOM are marked for Resource consumption i.e. to be consumed from the inbound location of the respective machine. Provided that the locations are NOT license plate controlled, the warehouse management module may be configured to automatically pass the semi-finished materials from one location to another.

Converging or sequential material flows

Consider the following scenario: whatever the semi-finished products are, one machine supplies with them just one downstream machine. Or 2 or more machines feed together the next one, and the path never changes. In this case, the output location of the upstream machine can be defined the same as the input location of the downstream machine.

In the below example the outbound location of the machine 145 equals the inbound of 146: O145 = I146.
Converging material flowsThe inbound and outbound locations are set for a resource (Production control > Setup > Resources > Resource) in connection with a resource group. The group in turn specifies the [advanced] inbound and the outbound warehouses, which are normally the same (unless it’s subcontracting).
Resource locations

However, on an attempt to select a non-license plate controlled warehouse location (the one where in the Location profile the parameter Use license plate tracking = No) for the output, a warning message comes up: “A work policy does not exist for location %1. A work policy must exist for a non-license plate controlled output location”.
Indeed, a work policy must be created first to inhibit any put-away work on reporting products as finished into this location:
No put work policy
An unprocessed put away work is bad even if it points into the same location I146 -> I146, because it reserves the semi-finished product and makes it unavailable to the next machine. With the above policy no put-away work is going to be created out of the location I146, the material is reported as finished into this location and stays there, ready to be reserved and consumed by the downstream resource.

Diverging material flows

Forks in the material flow make it much harder to configure. For example, if one resource may feed different downstream resources depending on the context, then the above setup with a work policy is not going to work.
Diverging material flows
In short, one needs 3 ‘ingredients’:

  • a Work template with an automatic processing;
  • a specially prepared Location;
  • a set of “put” Location directives (“pick” directives are not necessary, because the picking location is always dictated by the resource).

The Work template (Warehouse management > Setup > Work > Work templates) for the Finished goods put away work order type should have a typical Pick-Put pair, the Automatically process flag (!) set and a distinct Query to react to pre-defined semi-finished products.
Work template for Automatic processing
Bear in mind that (1) the automatic work processing requires a Default work user ID in the Warehouse management parameters; (2) the automatic work processing fails if the product is serial number controlled; (3) a number sequence for the license plates must exist: the system is going to take a temporary target LP.

The Location should not be license plate controlled, because if it was, the production worker would have to manually select a distinct LP on the Report as finished or the Manufacturing execution Feedback screen.
However, such a location cannot be selected in a resource, as we know. On the one hand, you don’t wish to have license plates, on another hand you need an automatic put away work to a certain location, and a prohibitive put work policy is not an option anymore.
This is not intended by Microsoft to work, but one can trick the system into it. First, assign a LP-tracked profile to the output location, and select it in the resource. Second, change the profile of the location to a Non-LP-tracked one!

The Put Location directives (Warehouse management > Setup > Location directives) for the Finished goods put away work react to certain products or resources with the help of the directive header Query (one can join the production table with the production route in the query) and divert the automatic put operation from one location to another:
Putaway location directives
The target location is “hardcoded” in the Location directive action Query.

Let the worker report the production order as finished: the system creates and executes put away work despite the missing license plate. One product goes ‘left’ and another goes ‘right’ from the same station fully automatically:
Automatically executed work

Conclusion

It is possible to “hard-wire“ a certain material flow between machines into the Warehouse management. Overlapping production orders remains a nuisance, because BOM lines do not exhibit a location if the warehouse is an “advanced” one. The input location of the machine is derived dynamically and the WHS module works through the reservation: the raw material must be reserved in the inbound location prior to consumption. But how do you reserve a material if it did not exist as you started the downstream production order?! The orders may be chained by the “Pegged supply” or automatically “re-released to warehouse” every X minutes.

 

 

The case of a missing flushing principle

The case of a missing flushing principle

This article is about material consumption in a manufacturing scenario where Manufacturing execution terminals are used with a WHS – enabled (advanced) warehouse in Dynamics 365 for Finance and Operations, and how BOM flushing principles work on different devices.

BOM Flushing principles

Typically, materials are backflushed upon completion of a finished item, i.e. automatically consumed at a ratio defined in the Bill of materials. 4 flushing principles are applicable to a raw material:

In the BOM line the 5th flushing principle is available: <None>. It means the consumption should fall back to the either one of the 4 principles specified in the item master.

Here is how different actions in D365FO react to the flushing principles (ME stays for manufacturing execution i.e. shop floor control, and WHS for the mobile scanner device running the advanced Warehouse management front-end), all in a neat matrix:

 ManualAvailable
at location
StartFinish
Prod. order release (x)  
WHS picking (pick)    
WHS picking (put) x  
Prod. order Start  (x) 
WHS Start production order  (x) 
Route card + Auto BOM consumption(x)(x)(x)(x)
ME Job terminal – Start  (x) 
ME Job terminal – Feedback Operations   (X)
ME Job terminal – Manual consumption feedback(x)(x)(x)(x)
ME Job terminal – Feedback RaF   (X)
Prod. order Report as finished   (X)
WHS Report as finished (put)   X
WHS Report as finished (put away)    

The actions where the material consumption is optional and configurable are put in brackets: (X). For example, one may configure whether the classic production start is accompanied by forward-flushing and how: for all BOM lines or only those with the Flushing principle = Start.

Another example: a manufacturing execution Job card terminal may be configured to consume materials on the current operation (ME Job terminal – Feedback Operations), on the last operation only (ME Job terminal – Feedback RaF), or never. Activating both is clearly not an option, since every production order has a last operation on the route, and triggering both is going to result in double consumption.

I tend to say the intersection between:

  1. ME Job terminal – Feedback Operations
  2. ME Job terminal – Feedback Report as Finished and
  3. WHS Report as finished

is highly problematic, and here is why.

Job card terminals in conjunction with Mobile devices

Consider the following scenario: every machine along the production route is equipped with a Job terminal to report time and WIP quantity output, while packaging and labeling on a mobile device is only required at the last station:
Operations route
On a long-running operation it may be beneficial to consume materials at the run time, i.e. with the help of (1) the ME Job card terminal, “Feedback operations”. However, with the unconditional consumption at (3) the mobile scanner Report as finished, this may only happen at the scanner. Otherwise the consumption is going to be double.

Moreover, the mobile scanner only accepts the “good quantity”, while the ME Feedback offers both the “good quantity” and the “error quantity” i.e. scrap for entering. Since the mobile scanner always consumes raw material, the material consumption is going to be too low. The Production scrap WHS menu is not a good replacement, since it requires the extra consumption of every material SKU to be entered manually.

Now consider a sophisticated environment where packing is performed by a robot, and the operation 30 “Packing” is not managed by the Manufacturing execution module. The WHS “Report as finished” function is triggered as full boxes or pallets pass a simple photoelectric sensor or a bar code reader:
Operations route (no packing)
While the Op. 10 and Op. 20 materials are captured at the Job terminals, it might be tempting to backflush the packaging materials at the ‘non-operation’ Report as finished. This is not possible, because (A) the WHS “Report as finished” unconditionally consumes all materials with the Flushing principle = Finish, and (B) a material with no operation number is accredited to the first operation on the route.
A split of the Finish flushing principle into 2 could have addressed this scenario:

  • Operation finish
  • Production finish

where the mobile device only considered the latter.

Finally, imagine the 3 operations running in dedicated production orders, with tangible semi-finished goods (SFG) exchanged between the machines:
Production order route
This is a common scenario in process manufacturing where the SFG batches can hardly be quantized and bear no labels. The output and input resource locations in the middle (10-20, 20-30) are not license plate controlled and do not have to be equipped with mobile scanners, as there is nothing to scan.

Here we have a different dialectic between semi-finished goods reported as finished at Job devices, and finished goods reported from Mobile scanner devices. This configuration – whether to trigger Reporting as finished in Manufacturing execution or not – is available at the Site level only, not a single Resource level. Yet an Advanced warehouse process cannot span multiple warehouses, let alone sites. This would end up either in full blown transfer orders between machines, or in an inability to track actual time at the Job card device.

Conclusion

At first, there must be an option to turn off material consumption on the mobile scanner, and let the system only backflush materials at the Job card terminal. The Mobile menu items Report as finished and put away and Report as finished must be extended for non-compulsory material consumption.
Ultimately, the error-prone recording of the material consumption is an internal planning and controlling requirement, while labeling and shipping generates revenue. One does not want to see label printing failing just because one screw is missing in the ledger.
Please vote for this idea!

Secondly, advanced scenarios may require a distinction between an “Operation finish” and “Production finish” as opposed to a single flushing principle “Finish”. This is hard to achieve through an extension to D365FO, as the respective enumeration is not extendable.
Please vote for this idea!

Thirdly, the D365FO configuration is not granular enough to divide the Manufacturing execution RaF and the Warehouse management RaF (reporting as finished), and should better be enhanced.
Please vote for this idea!

Hope this helps.