Import Negotiation Lines
Use the Import Negotiation Lines process to import negotiation lines from external systems into a large negotiation created in Oracle Sourcing.
When to Use
Use this process to add new lines, update or delete existing lines to existing draft large negotiations. The process also supports addition, update and deletion of line level external cost factors, quantity-based price tiers and price breaks. This process can only be used for large negotiations. A large negotiation must be enabled in the negotiation style. Before you run the import process, you must load the relevant information into the appropriate interface tables.
Privileges Required
- Edit Supplier Negotiation (PON_EDIT_SUPPLIER_NEGOTIATION_PRIV)
Specifications
Review these before setting up this scheduled process:
| Specification | Description |
|---|---|
| Job Type | Ad hoc job. |
| Frequency | Based on your business needs. |
| Time of Day | Based on your business needs. |
| Duration | Depends on the total number of lines and the line level details (external cost factors, quantity-based price tiers, price breaks) being imported. |
| Compatibility | There should be only one instance of the job running at any one time for a given negotiation. For different negotiations, you can run multiple jobs in parallel (one per negotiation). Application will throw an error if you try to run multiple jobs at the same time for a single negotiation. |
Parameters
| Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required | Notes |
|---|---|---|---|---|---|
| Procurement BU | Required | Specify the name of the Procurement business unit of the negotiation to which the lines should be imported into. | For example: Vision Operations | None | N/A |
| Negotiation | Required | Number or ID of the negotiation to which the lines should be imported into. | For example: Negotiation = 567893 | None | N/A |
| Batch ID | Optional | To import a specific group of lines or line level child entities from the interface table, enter the value of batch ID parameter as available for these records in the interface table. | For example: Batch ID = 123 | None | N/A |
| ORA_PON_LARGE_ERROR_THRESHOLD | Required | This administrator profile option sets the error threshold for line level validations while importing. | For example: ORA_PON_LARGE_ERROR_THRESHOLD = 50 | None | N/A |
| ORA_PON_IMPORT_NEGOTIATION_LINES_PARALLEL_REQUESTS | Required | This administrator profile option controls number of parallel requests that can run at a time for import negotiation lines process. | For example: ORA_PON_IMPORT_NEGOTIATION_LINES_PARALLEL_REQUESTS = 10 | None | N/A |
Troubleshooting Information
- The validation error messages that prevented the importing of lines are displayed in the job’s output report.
- If the line level errors are above the threshold (configurable profile option ORA_PON_LARGE_ERROR_THRESHOLD), then you need to identify the values that caused errors, update the original FBDI template, reload the entire records into interface table and re-run the job.
- If the line level errors are below the threshold (configurable profile option ORA_PON_LARGE_ERROR_THRESHOLD) then lines and child entities without any validation issues are successfully imported to the application. In the job’s output report, a BAD ROW XLS file is generated with only the lines and child entities that are having validation issues and the error is displayed inline. You just need to fix the issues in the BAD ROW XLS file itself, load only the fixed records in the interface table and re-run the job.
- Specifying #NULL for a given field during UPDATE operation will empty out already existing value in the application table. Read the descriptions in the FBDI import template for more details.
- You can speed up the import process by increasing the value set to profile option ORA_PON_IMPORT_NEGOTIATION_LINES_PARALLEL_REQUESTS. It is generally recommended not to set this value more than 10.