Bypass Count Tasks Workflow

You follow a simple and flexible process where you perform self-attestation on the recall tasks generated in the application after physically completing the containment actions.

You can mark the bypass tasks as completed by selecting a containment action code which is configured through user-defined lookups, without performing the recall counts or disposition transactions.

On locating recalled parts:

1. Trace Details Generation
   • When recalled parts are located, trace records are generated showing where the parts may reside. These include:
     • Inventory organization
     • Location or department
     • Subinventory
     • Stock locator
   • These records help warehouse staff and par counters locate and move these parts to quarantine.
2. Bypass Task Generation
   • Instead of sequential task flows in the Recall Count workflow, this bypass workflow generates bypass tasks based on task grouping in the Recall Parameters:
     • Inventory Organization: One bypass task per inventory org
     • Location: One bypass task per location + inventory org
     • Subinventory: One per subinventory + location + inventory org
     • Expense Locations: One task per cost center + inventory org for parts delivered to expense locations
   • Each bypass task includes a material status indicating whether the part is already received or inbound.
3. Manual Bypass Task Creation
   • You can manually create bypass tasks for any inventory org, location, subinventory, or cost center—not identified by the Locate process—to alert additional stakeholders beyond those auto-generated.
4. Adding Containment Instructions
   • Each bypass task can include specific instructions for containment actions.
5. Notifications & Task Completion
   • FYI notifications are sent to assigned stakeholders per business rules—configured to align with your task grouping.
   • When a stakeholder receives a notification, they can navigate to the Notice Details page to view recall details and perform the required action.
   • After executing the physical containment/disposition action, the stakeholder marks the task Completed, selecting a containment action code.
6. Recall Closure
   • The recall notice closes automatically once all tasks :mandatory and optional. They are marked as Completed.
   • Manual tasks can be flagged optional or mandatory; recalling can close the notice even if optional tasks remain incomplete.