Conrad Volkmann

When a customer has specific Batch Attribute requirements, pegging in Master planning must match these Requirements against available Onhand with batch dimension.

If you open Production Control > Operations > Current Operations (ProdRouteOprOverview) And then select an operation and open: Operation details > Materials You get to this very useful form: (ProdBOMOprNum) Unfortunately it has no capability to show product dimensions/variants – nor other typically related functions (like Onhand, Net requirements, explosion, Reservation, release to warehouse etc….) This form would work very well to manage the Subcontracted staged materials, if it would have a little more funcitionality.

In the current Operations resource model, it is not possible to plan for shifts, as a job cannot be split by shifts (Often the worker is the secondary resource on a machine resource, what makes it even more complex). The consequence is that you have to set up "Generic" worker resources, that have not worker assigned but just represent the worker required on a specific resource or resource group. In essence, this actually may work well for master planning, but the Shopfloor supervisor needs to have a dispatching / shift-planning instrument at his hands, where he can see the required times (how much is the generic resource loaded?) and dispatch the tasks of the generic resource to specific resources. Technically, this might be something to use the Scheduling board from professional services - but we need to make sure that we are not making Shopfloor resources more expensive (falling into different license terms). Warehouse and Quality supervisors have a similar problem, but the definition of the work ahead is different and not related to a resource model. Still would be good to have a generic solution, as for example waterspiders might be loaded with production AND warehouse work.

It must be possible to define Item allocation keys for catch weight items, that allows to enter the forecast quantity in catch weight unit. This could be managed by a simple flag on the Item allocation key that marks the allocation key as catch-weight. On such an item allocation key, only items with catch weight can be associated. For the forecast entry and the dependent data entities the catch weight quantity should be activated.

When selecting the resource by capability scheduling or by any other manual scheduling methods the Vendor that is used to create the subcontracting purchase order must be derived from the scheduled resource, not taken from the BOM line (or: the Vendor in the BOM line needs to be updated before firming the planned order). The simplest way to achieve this would be to update the BOM line for the operation service before or during the firming of the planned order: - Update the Vendor in the BOM line if the scheduled resource holds another vendor - Delete the BOM Line if the scheduled resource is NOT a vendor resource Obviously, the ideal solution would be to update the Vendor in the BOM line in the Resource Scheduling directly (but that might pull in additional complexity based on the question of what master data may be required for that, and what happens if no BOM line for a service is existing ....)

Currently, there is not line threshold to be set on Production order or Kanban Wave templates. Given the fact that Wave-processing results in critical long running transactions, if waves have more than 500 lines, there should be threshold definable, else there is a risk of servere performance problems while wave processing and work creation is running. You might argue, that you can create one wave per order - but if production orders or kanbans are produced for single piece flow, that would mean one wave to pick per piece - that model is not scalable either !! .

The released product variant listpage only has a few functions compared to the released product form. All functions that relate to further inquiries - like the Where Used analysis form - would be very helpful, as today, the user needs to go to he master, select a function, and then filter on the variant - what is very cumbersome.

A product cannot be effectively released and used, if the unit of measure conversions are not copied (actually BEFORE) the release to a legal entity is done, as this release might fail, if the purchase, sales or BOM unit do not have an existing conversion set up.