Skip to main content

I am using Cloud 22-R2: I want the Proposed Location on a shop order to automatically pull from the Inventory Part’s Default Location rather than the standard default outbound location defined for the Work Center.

i.e. multiple products are produced on a particular work center - 99% of which are required to output to the standard post production, pre-shipping location which is defined as the default outbound location on the work center.  However, there is one product produced on the same work center that I want to output to a different location - a location that has an availability control assigned to it.  i.e. I want to assign a particular Availability Control to a certain part every time it is receipted from a shop order - I thought I would use a unique location for this purpose.  I want to use standard functionality ideally, without the need for a CRIM.

I know I can manually change the Proposed Location on the shop order or I can manually change the output location when receiving/approving the shop order but I want the shop order when first created, to automatically use a different location.

Or is there a better way for me to ensure that any specific product output from a shop order, will always be put on hold or attract a certain Availability Control?

Without a custom event action, one option could be to

  1. create a zero cost dummy Work Center
  2. assign the inventory location with the default availability control as the outbound for this WC
  3. add one operation to this part’s routing using this WC as the final operation.
  4. backflush the operation reporting in this WC at receipt

Thanks Matt! 👍 Certainly a good idea for my particular issue at hand.  I don’t think my colleagues in Structure/Routing maintenance would mind my requesting a slight routing change to just one part!

And only a small piece of education to our production operatives regarding a new ‘dummy’ operation appearing on the Workbench.

Terms & ConditionsCookie settingsAccessibility statement