How to require complete issuing of "manual" issue material lines

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

​@Anna_B Is it required to set the Reserve/Issue Method to Manual? Say you set it to Backflush instead, you will still avoid having that material included when reserving the shop order, and you can still choose to manually issue the material, and the system would check that all material has been issued.

At this point in our manufacturing process it is, it is required to issue on the line. 

Example of why: Line A builds 20 of a part number that is serialized that is fed to line B, and then when it gets to Line B, we want the team to manually scan the serial numbers they are issuing to their assembly to ensure they are consuming the proper serial numbers. This example never goes back to the warehouse which is where our stock is picked via our materials team.  It’s all on the assembly floor at this point.   We also would prefer not to use bakflush as it would grab serials potentially out of sequence.

A serialized part system would never allow to backflush even if you set it to Reserve and Backflush. Hence, system would force you to manually issue it, and issue the full quantity.

Ah ok, so I understand what you're saying now, but what happens if at the last operation they miss manually issuing them and check the “backflush” button on closing the SO?  Will IFS just backflush serial numbers and close the SO out?

This looks really promising!  I did some testing in our UAT environment and we’re going to test it on an assembly line this week before swapping over our settings, but I think this is EXACTLY what we needed.  Thank you, Björn!