Improve error identification for a routine batch

When a routine encounters an error in a batch, it commits the rows successfully processed prior to the error. It displays the details of the error for the row that caused the issue and then attempts to process the remaining rows. This process will be repeated for the batch. However, after several tries, any rows remaining won't be processed due to the high number of errors in the batch. The unprocessed rows will have an error indicating they couldn't be processed and the batch must be corrected before running the routine again. 

Improved error handling helps administrators easily identify the rows that need to be corrected while balancing performance by continuing to use batched records.  

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

If a batch continues to error after 8 attempts, then the remaining rows won't get processed. You'll need to review and correct the rows that errored, and ensure the remaining rows don't have the same issue before running the routine again

Key Resources

For information about Routines, see https://docs.oracle.com/en/cloud/saas/sales/fadsi/overview-of-routines.html

Access Requirements

To use Routines, you must have the Manage Routines privilege (ZCA_MANAGE_ROUTINES). This privilege is available to the following roles by default:

• Application Implementation Consultant
• Sales Administrator
• Customer Relationship Management Application Administrator

Note: If you're working with custom objects, you will also require the ORA_CRM_EXTN_ROLE role.