Item Inactivation does not validate existing “On Hold” Work Orders.
We noticed that when an item has a Work Order in On Hold status, the system still allows Item Inactivation without any validation error.
Is this the expected Oracle behavior? Should On Hold Work Orders be treated as active/open transactions during item status validation, similar to Released or Unreleased WOs?
We tested multiple items and the issue is consistent. Let us know if this is seeded behavior
Tagged:
0