The Recover Errors ESS job is a scheduled process to fix errors during order fulfillment. For example, an order fulfillment line can only reserve inventory if more inventory is available to fulfill the item. This job can not only help you with order fulfillment problems but also help you fix system errors on order fulfillment lines. You can find below the navigation path to schedule this job:
Tools > Scheduled Processes > Schedule New Process > Select the process with the name “Recover Errors.”
Required Privileges
The privilege required is: Launch Orchestration Order Error Recovery Bulk Update DOO_LAUNCH_ORCHESTRATION_ORDER_ERROR_RECOVERY_BULK_UPDATE_PRIV as specified in
Fusion Cloud SCM > Order Management Scheduled Processes > Recover Errors
System Errors vs. Order Fulfillment Errors
It is crucial to fix the problem that causes the error. If you don’t fix the problem, the same problem will continue. Subsequent runs of error recovery will continue to get stuck in this error and will not proceed further.
Order Fulfillment Errors happen only with sales order data in your downstream applications during a fulfillment task.
System Errors are caused by order lines stuck because of a system problem. For example, when the database times out, the server times out, there’s an unstable server connection, a resource isn’t available because there’s a stuck thread, insufficient memory, etc.
Scope parameters for Recover Errors jobs
The applicable parameters for a system errors scope are:
- Number of Days to Look for System Errors
- Date to Start Looking, Counting Backward
The applicable parameters for a fulfillment errors scope are:
- Orchestration Order Number
- Source Order Number
- From Ordered Date
- To Ordered Date
- Source System
- Process Name
- Customer Name
- Inventory Item
- Task Type
- Task Name
- Order Orchestration Function
The administrator may find a further explanation about these parameters at:
Fusion Cloud SCM > Maintain and Troubleshoot > Details > Downstream > Fix Errors in All Sales Orders
The scope for the Recover Errors job can be set to one of the following three values:
- Order Fulfillment Errors: This will ignore the “Number of Days to Look for System Errors” and “Date to Start Looking Counting Backward” parameters.
- System Errors: If they were set, this would only use the “Number of Days to Look for System Errors” and “Date to Start Looking Counting Backward” parameters.
- Order Fulfillment and System Errors: This will apply the “Number of Days to Look for System Errors” and “Date to Start Looking Counting Backward” parameters to the System Errors and all other parameters to the Order Fulfillment Errors.
Order Management Recover Errors Best Practices
(1) Schedule a ONE TIME Recover Errors job with a “Number of Days to Look for System Errors” parameter set to 180 to clean up all old errors.
This job should take care of system errors from the past six months. Do not schedule any other Recover Errors job while this is running.
(2) Schedule Recover Errors jobs to run once a week and set the Number of Days to Look for System Errors to 7.
(3) If you do not set the Number of Days to Look for System Errors parameter, it will look back for all system errors in the instance.
(4) Fulfillment task errors are best recovered by task type or name.
Fix the sales order data associated with this task type or name before running the job.
(5) Fulfillment process errors are best recovered by process name.
Fix the sales order data associated with this process name before running the job.
(6) If the system is running fine and you’re still getting system errors, you may need to provide a scope that doesn’t include the last time the Recover Errors job has run. Whenever a system error happens, the date for the system error for a given order will be reset.
For example, if a system error took place back in January of last year for order XYZ and the Recover Errors job runs on the 1st of every month,
if the system error continues to happen repeatedly, it will reset its time of occurrence to the latest run date.
If the order was reprocessed and this order XYZ is no longer needed, this reoccurring system error will not go away.
The following Recover Errors job needs to run with a scope window that doesn’t include the date of the last time the job ran to make this error go out of scope. Our example of monthly job runs means using a scope that goes back 2 or 3 weeks.
The system error will not disappear from the instance but will no longer be processed as it would be out of scope.