Skip to main content

In IFS Cloud, we have serialized subcomponents set to Manual Issue so that the manufacturing team can issue the components as they are installed on the assembly. The challenge is that sometimes the team under-issues the required quantity, since Manual Issue allows the shop order to progress without fully issuing the required qty.

Is there a standard setting or configuration in IFS Cloud that would prevent under-issuing, so that the team must issue the full required quantity before closing (or finishing) the shop order — while still keeping Manual Issue as the issue method?

Hi ​@Anna_B,

There is no standard setup available to enforce complete material issuance before starting the Shop Order operation, though, I have handled same requirement through a custom event for a client. 

 

Regards 

Abdul Rehman 


Yes, IFS Cloud does allow some control over how serialized components are issued in shop orders, even when using Manual Issue. However, by default, Manual Issue does not enforce full issuance before allowing the shop order to progress or finish, which is exactly the challenge you're facing.

1. IFS Cloud provides four issue methods for shop order material lines:

  • Manual
  • Reserve
  • Backflush
  • Reserve and Backflush

Manual Issue allows flexibility but does not enforce full issuance. It’s designed for cases where components are issued manually as needed, which means under-issuing is technically allowed.

2. There is a site-level setting that can trigger an error when serialized components are not issued according to the quantity per assembly. This is visible in the Shop Order Tracked Structure page, where you can monitor and edit component assignments.
This setting may help flag under-issuance, but it doesn’t block shop order completion by default. You may need to configure validations or use custom events or workflows to enforce stricter control.

 

If you want to keep Manual Issue but enforce full issuance:

  1. Use Shop Order Tracked Structure to monitor serialized component assignments.
  2. Enable site-level validation that checks for missing components per assembly.
  3. Consider a custom event or workflow that prevents shop order completion unless all required serialized components are issued