1. Implementing Enterprise Contracts
  2. Import Contracts

Import Contracts

You can import contracts from a source file into the application. To set up Import Management for importing contract data, use Import Management.

Import Management supports the import of data from an external text or XML file to interface tables, and from interface tables to target application tables.

This topic describes:

  • What you can import

  • The interface table

  • The import process

What You Can Import

All contracts can be imported except for those in Expired status. The import file can use names as well as IDs to identify data, for example, Party ID or Party Name. You can import only one version for each contract, with this data:

  • Contract header

  • Primary party (supplier, customer, or partner)

  • One contract owner: depending on the owner role, this is either an employee or salesperson of the contract's business

  • One primary contract party: a supplier or partner or customer

  • Primary contract document as an attachment

  • Additional attachments: the import file lists the attachments which are imported using the file import user interface (UI), either individually or as a ZIP file.

You can import new contracts as well as update or delete a contract using import. The same restrictions apply to update and delete as are applied when you perform those same actions in the application UI.

Interface Table

The table describes that the application uses these database tables for importing contracts:

Table

Description

OKC_IMP_CONTRACT_HEADERS

The interface table used to load contract data from external systems. This table maps to logical contract data: contract header, contract party, contract party contact, contract terms, and contract attachments.

OKC_IMP_CONTRACT_ADDRS

Interface table for importing contract addresses.

OKC_IMP_CONTRACT_CNTACTS

Interface table for importing contract contacts.

OKC_IMP_CONTRACT_LINES

Interface table for importing contract lines.

OKC_IMP_CONTRACT_PARTIES

Interface table for importing contract parties.

OKC_IMP_CONTRACT_RELNS

Interface table for importing contract relationships.

OKC_K_SALES_CREDITS_INT

Interface table for sales credits.

PJB_BILL_PLANS_INT

Interface table for importing project billing plans.

PJB_BILLING_CONTROLS_INT

Interface table for importing project billing controls.

PJB_CNTRCT_PROJ_LINKS_INT

Interface table for importing project procurement links.

Details about the fields and valid values for import are available from Contracts section of the Oracle CX Tables and Views for CX Sales and Fusion Service guide. See Related Topics.

Importing Contracts from a Source File

To import contracts, use the Import Management and upload contract data into the interface table. To access this feature, select the Manage File Import Activities task. This task in the Setup and Maintenance work area is part of the Enterprise Contracts offering in the Enterprise Profile functional area.

Note: The Edit Import Activity: Map Fields page contains an import mapping that details the mapping between source file columns and contract attributes, but you may define additional import mappings.

For more information, see the Understanding Import and Export Management for CX Sales and Fusion Service guide.

Related Topics