Instructions for Restarting Concurrent Programs with a Manual Restart Mode

Instructions for Restarting Concurrent Programs with a Manual Restart Mode in Oracle Contract Lifecycle Management

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:

Resumable: This program can be automatically restarted and can resume its processing at the point where it left off before the system failure.
Restartable: This program can be automatically restarted but will go back to the beginning of its processing.
Manual: An administrator must perform manual steps to restart this program. Product-specific documentation lists the steps required to restart any shipped programs with a Manual restart mode.
Unknown: It is unknown whether this program can be restarted automatically or not. This value is the initial default setting.

Caution: 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 following Oracle CLM concurrent programs with a Restart Mode of Manual, an administrator must perform the steps specified prior to restarting the program following a system failure.

The following table provides details about the help topics for restart steps in Oracle HRMS Applications.

How to Restart the Import CLM IDVs Concurrent Program After System Failure

Find the failed request.
1. Navigate to the Requests window: CLM Purchasing responsibility > Requests > Find Requests > Find.
2. Search for the failed Import CLM Awards request.
3. Note the Request ID and any error messages.
Review, purge, and reinsert the unprocessed data.
1. Identify unprocessed records in the following interface tables:
  - PO_HEADERS_INTERFACE
  - PO_LINES_INTERFACE
  - PO_LINE_LOCATIONS_INTERFACE
  - PO_DISTRIBUTIONS_INTERFACE
  - PO_UDA_INTERFACE
2. Review the PROCESS_CODE status column in the PO_HEADERS_INTERFACE table for the REQUEST_ID (noted in the previous step) using a SELECT SQL statement. All the records for this REQUEST_ID with PROCESS_CODE other than ACCEPTED are unprocessed records.
3. Complete the following steps for the unprocessed records:
  - Purge the data from the interface tables.
  - Reinsert the corrected data as applicable.
Resubmit the Import program.
1. Navigate to the Submit Request window.
2. Run the Import CLM Awards program.
3. Monitor the program until completion.

How to Restart the Import CLM IDVs Concurrent Program After System Failure

Find the failed request.
1. Navigate to the Requests window: CLM Purchasing responsibility > Requests > Find Requests > Find.
2. Search for the failed Import CLM IDVs request.
3. Note the Request ID and any error messages.
Review, purge and reinsert the unprocessed data.
1. Identify unprocessed records in the following interface tables:
  - PO_HEADERS_INTERFACE
  - PO_LINES_INTERFACE
  - PO_UDA_INTERFACE
2. Review the PROCESS_CODE status column in the PO_HEADERS_INTERFACE table for the REQUEST_ID (noted in the previous step) using a SELECT SQL statement. All the records for this REQUEST_ID with PROCESS_CODE other than ACCEPTED are unprocessed records.
3. Complete the following steps for the unprocessed records:
  - Purge the data from the interface tables.
  - Reinsert the corrected data as applicable.
Resubmit the Import Program.
1. Navigate to the Submit Request window.
2. Run the Import CLM IDVs program.
3. Monitor the program until completion.

How to Restart the PO CLM PDS Inbound Concurrent Program After System Failure

Find the failed request.
1. Navigate to the Requests window: CLM Purchasing responsibility > Requests > Find Requests > Find.
2. Search for the failed PO CLM PDS Inbound request. Search using BATCH_ID (if the concurrent program was launched directly) or URL provided as output when the PDS Rest Service runs in asynchronous mode (i.e., when "aSyncMode" is set to "Y").
3. Note the Request ID and any error messages.
Review, purge and reinsert the unprocessed data.
1. Examine the interface table PO_PDS_INBOUND_INTERFACE for any unprocessed records.
2. Review the PROCESS_STATUS column to find records not marked as COMPLETE.
3. Complete the following steps for the unprocessed records:
  - Purge the data from the interface tables.
  - Correct and reinsert the data or resubmit the PDS Rest Service in asynchronous mode.
Resubmit the Import Program.
1. Navigate to the Submit Request window.
2. Run the PO CLM PDS Inbound program.
3. Monitor the program until completion.

How to Restart the Mass Closeout Concurrent Program After System Failure

Find the failed request.
1. Navigate to the Requests window: CLM Purchasing responsibility > Requests > Find Requests > Find.
2. Search for the failed Mass Closeout Submit request using the Request ID shown when you submitted the Mass Closeout page.
3. Note the Request ID, p_req_id (input parameter), and any error messages.
Check for unprocessed data.
1. Examine the following staging tables for any unprocessed records:
  - PO_CLOSEOUT_DETAILS
  - PO_MULTI_MOD_DOCS
  - PO_MULTI_MOD_REQUESTS
2. Query the PO_MULTI_MOD_REQUESTS table using the p_req_id. If a record is present, this indicates that the Mass Closeout Submit process has failed. Note the description column value for reference.
Resubmit the Mass Closeout program from Contract Administration.
1. Navigate to the Document Sets page: CLM Purchasing responsibility > Buyer Work Center > Contract Administration > Document Sets.
2. Search for the Document Set using the description you noted in the previous step. Click the link.
3. Resubmit.

How to Restart the Create Multiple Modifications Concurrent Program After System Failure

Find the failed request.
1. Navigate to the Requests window: CLM Purchasing responsibility > Requests > Find Requests > Find.
2. Search for the failed Create Multiple Modifications request using the Request ID shown when you submitted the Multiple Modifications page.
3. Note the Request ID, p_req_id (input parameter) and any error messages.
Check for unprocessed data.
1. Examine the following staging tables for any unprocessed records:
  - PO_MULTI_MOD_DOCS
  - PO_MULTI_MOD_REQUESTS
2. Determine if the concurrent program has failed in either of these scenarios:
  1. The concurrent program did not complete successfully.
  2. The output from the concurrent program lists any documents in the "List of Error Documents" section.
3. If a failure is identified in either case above, query the PO_MULTI_MOD_REQUESTS table using the p_req_id.
4. Record the value found in the description column.
Resubmit the Multiple Modifications program from Contract Administration.
1. Navigate to the Document Sets page: CLM Purchasing responsibility > Buyer Work Center > Contract Administration > Document Sets.
2. Search for the Document Set using the description you noted in the previous step. Click the link.
3. Resubmit.