Import Contract Agreements
Use the Import Contract Agreements scheduled process to import purchase contract agreements.
When to Use
Use this process when you must perform these tasks:
- Perform an initial load of contract purchase agreements from your legacy application to Oracle Fusion Cloud Applications.
- Import contract purchase agreements from an external application to Oracle Fusion Applications.
- Update selected fields to existing contract purchase agreements.
Before you run the Import process, you must first load the relevant information into the appropriate interface using file-based data import (FBDI).
Privileges Required
-
Import Contract Purchase Agreement (PO_IMPORT_CONTRACT_PURCHASE_AGREEMENT_PRIV)
Specifications
Specification | Description |
---|---|
Job Type | Scheduled. |
Frequency | You're encouraged to schedule the process to run at least once per day. The process can be run more than once per day, but you should avoid scheduling processes more frequently than necessary for your business purposes. Avoid scheduling the process on a frequency that might overlap. Allow for a lag between the end of each scheduled process and the start of the next scheduled process. |
Time of Day | Choose the time of day that doesn't interfere with your daily business activity, such as at the end of the workday, after the end of shifts, after peak transaction activity, or during a lull in transaction activity. |
Duration | The runtime of this process varies based on the number of contract purchase agreements being imported. |
Compatibility | There should be only one instance of the job running at any point of time. This is automatically handled by the application. If you must run more than one instance of this process, then consider spacing them out over a period of time. |
Parameters
Parameter | Optional or Required | Description | Parameter Values | Special Combinations Required | Notes |
---|---|---|---|---|---|
Procurement BU | Required | Specify the name of the procurement business unit that these documents should be imported into. | N/A | None | N/A |
Default Buyer | Required | Specify the name of the buyer to be used when one isn't included in the import data. | N/A | None | N/A |
Approval Action | Optional |
Select one of the following actions:
|
N/A | None | N/A |
Import Source | Optional | Used to match against the records in the interface tables to retrieve the correct set of records for processing. For example: Import Source = External Contracts. Use it with Batch ID to identify the documents to be loaded to the application tables. | N/A | None | N/A |
Batch ID | Optional |
Used to match against the records in the interface tables to retrieve the correct set of records for processing. For example: Batch ID = 123. Use it with Import Source to identify the documents to be loaded to the application tables. |
N/A | None | N/A |
Communicate Agreements | Optional |
Select Yes to have imported purchasing documents communicated to the supplier. Select No to not have imported purchasing documents communicated to the supplier. |
N/A | None | N/A |
Troubleshooting Information
- You can view the status of the Import Contract Agreements process in the Scheduled Processes work area.
- The validation errors and warning messages that prevented the import contract agreements are displayed in the error log.
- After you've corrected the validation errors, you can resubmit the process.