Instructions for Restarting Concurrent Programs with a Manual Restart Mode in Oracle iProcurement

Instructions for Restarting Concurrent Programs with a Manual Restart Mode in Oracle iProcurement

For Oracle E-Business concurrent programs, the Restart Mode attribute indicates how a program can be restarted in case of system failure.

The Restart Mode can be one of four values:

Important: The Restart Mode for Oracle-provided programs should not be modified. If it were to be modified, the value may be overwritten without warning by future Oracle EBS software updates.

For more information about the Restart Mode, see the Oracle E-Business Suite Setup Guide

For the Oracle iProcurement concurrent programs with a Restart Mode of Manual, an administrator must perform the steps specified prior to restarting the program following a system failure.

Requisition Import Concurrent Program

The manual restart steps for Requisition Import are as follows:

  1. Identify the failed request

    • Navigate to the Find Requests window using Procurement Responsibility: click Requests, then click Find Requests in the Requests window.

    • Search for the failed Requisition Import request.

    • Note the Request ID and any error messages.

  2. Review, purge, and reinsert the unprocessed data

    • Identify unprocessed records using the following SQL:

      SELECT * FROM PO_REQUISITIONS_INTERFACE_ALL WHERE NVL (PROCESS_FLAG,'NEW') IN ('COPIED', 'IN PROCESS','ERROR') AND REQUEST_ID=&request_id;

    • Review the PROCESS_FLAG status column:

      • If the PROCESS_FLAG displays ERROR status, then these are error records. You remove or correct these records by updating, deleting, or fixing these records as required.

      • If the PROCESS_FLAG displays IN PROCESS status, then these are partially processed records. You must ensure that duplicate requisitions are not created and then purge these records.

      • If the PROCESS_FLAG displays COPIED status, then these are successfully processed records. You must ensure that requisitions are created and then purge these records so that they do not result in duplicates in the next run.

    • Reinsert the corrected data.

  3. Resubmit the Requisition Import Program

    • Navigate to the Requests window.

    • Submit the Requisition Import program again.

    • Monitor its progress until completion.