Process flow

This sequence outlines the process flow:

  1. The product recall is manually initiated by an internal or external user in the Issue Management portlet in M3 Portals. The affected order lines are selected with the issue type set to Recall.
  2. The affected order lines are manually queried in M3 Graphical Lot Tracker (GLT) and a customer list reportCSV file is exported with the step ID for the affected item lot.

    See the M3 Graphical Lot Tracker User and Administration Library (Cloud) and select User > User Guide > Reports > Common report features.

  3. In the Product Recall widget for GLT, the user specifies key information about the recall issue. Additionally,the user uploads the customer list report CSV file into the widget.

    See Creating customer-specific recall issues using the Product Recall widget

  4. In RPA, key information about the recall issue is extracted from the Product Recall widget and the customer list report CSV file. Additionally, the customer list report CSV file is uploaded to IDM.
  5. RPA creates a recall issue header for each customer using the IMS100MI/Add API in M3 Portals.
  6. RPA adds the affected customer orders for each customer as recall issue lines under the appropriaterecall issue header using the IMS101MI/Add API in M3 Portals.
  7. RPA assigns a qualified external user as a watcher in M3 Portals for each new recall issue created.

    See the section on automatic watcher addition workflow.

  8. Actions are generated and watchers are notified using standard M3 Portals workflows.

Automatic watcher addition workflow

This sequence outlines the workflow used to add watchers to a recall issue:

  1. After a new recall issue header is created for a specific customer, a watcher addition workflow is started.
  2. RPA queries the M3 database to retrieve all potential contacts for the customer.
    Note: If the initial query does not return any customer contacts, RPA logs an exception. Additionally, RPA does not add any watchers to the recall issue header, and the process flags the issue for manual review.
  3. RPA validates the potential contacts for the customer by checking that each contact has an active statusand an external or limited M3 Portals license.
    Note: If no customer contacts meet the validation criteria, RPA does not add any watchers to the recall issue header.
  4. RPA adds the validated user to the new recall issue header using the IssueManagement_Watcher_ADDIMS110MI API in M3 Portals.