Create Recall Notices through the REST API and Identify the Relevance of the Recall Data
You can now create recall notices using the Capture and Validate Recall Notices REST API. This feature allows external sources to provide recalled part details, which are then validated to determine their relevance to your enterprise.
The application validates the part details provided in this resource and derives the correct item identifier. It then checks whether these items were received during the designated recall tracking period. The recall notice is classified based on the following criteria:
- Relevant Recall Notice:
- If at least one line in the recall notice includes an item identifier that has been previously received during the tracking period, the recall notice is deemed relevant.
- This relevant recall notice is then assigned a status of Pending Acceptance to indicate that further action may be required.
- Irrelevant Recall Notice:
- If none of the lines in the recall notice contain a valid item identifier or if the identified items were not received during the tracking period, the notice is marked as irrelevant.
- The status for these notices is set to Pending Review, highlighting that no immediate action is necessary unless further review suggests otherwise.
You can focus on the relevant recalls by reviewing them in “Pending Acceptance” and then simply accept them so that they become eligible for tracing the material and managing the disposition of affected parts.
For irrelevant recalls that are in “Pending Review”, you can review the recall details as well.
Recall Managers may want to verify:
- if there is any misconfiguration in the product master, that is, product master does not have the required trading partner relationship or the item does not have the required extensible flex field attribute mapping. Therefore, a match is not being found.
- make the necessary changes and validate the item again or withdraw the recall if the recall manager believes that they are irrelevant.
Recalls that are deemed irrelevant, that are not withdrawn, continue to be re-evaluated by a scheduled process to determine if over time the recall becomes relevant.
You can create the following entities by doing a POST operation on this resource.
- Recall headers
- Contact details
- Recall attachments
- Recall lines
- Recalled lots
- Recalled serials
You can fetch the attributes pertaining to the following entities by doing a GET operation on this resource.
- Recall headers
- Contact details
- Association Entities that retrieve the impacted business units
- Recall attachments
- Recall lines
- Recalled lots
- Recalled serials
You can also continue to use the Recall Notices V2 REST API that already exists prior to this release to create the recall notices in draft or open status if you are confident that the recall data received from your source is already validated and relevant for you.
The capability of creating the recall notices using a REST API that also does validation to determine the relevance of a recall to your enterprise provides:
- Seamless integration with legacy applications using by different recall data aggregators
- Scalability by accommodating high volumes of recall notices with minimal manual intervention.
- Streamlined recall management by ensuring only pertinent notices receive attention, thereby, improve operational efficiency and compliance.
Steps to Enable
Perform the steps mentioned here which enables the application to validate the recalled parts upfront, does item match and identifies the recall notices that are relevant for you.
Key Resources
- Oracle Supply Chain Management Cloud: Using REST API for Oracle Supply Chain Management Cloud available on the Oracle Help Center.
Access Requirements
Users who are assigned with configured job role that contains the following privileges can access this feature:
- Manage Product Recall Notices (ENQ_MANAGE_PRODUCT_RECALL_NOTICES)
- View Product Recall Notices (ENQ_VIEW_PRODUCT_RECALL_NOTICES_PRIV)