Understanding Contracts Import White Paper
Understanding Contracts Import White Paper
Import
ORACLE WHITE PAPER | JUNE 2016
Table of Contents
Introduction 1
Importing Attachments 5
Review Mapping of the Source File Attributes With the Target Import Object Attributes 6
Resources 8
Contracts can be imported into Oracle Enterprise Contracts using the import process. Imported contracts can be in
Draft, Active, Closed, Canceled or Hold status. You can also update or delete existing contracts using import. In this
case, the same restrictions would apply as if you were taking the same action in the application interface, for
example:
» Contracts in a status that cannot be deleted in the application interface cannot be deleted through the import
process (see Contract Actions and Status Changes: Explained).
» Only a limited set of attributes can be updated in an active contract, i.e. those that can be changed without
initiating a contract amendment.
You can import only one version for each contract. Contract header information such as name, dates, and amount
can be imported, along with parties to the contract, limited types of contract lines, and contract attachments.
Structured terms and conditions (aligned with sections and clauses defined in your Terms Library) cannot be
imported.
See Managing Contract Types for more information on the contract types you can set up.
The data you can import will depend on the type of contract you are importing. Step 3 below “Download the
contract import csv template file” will help you understand which csv files you need to complete for your type of
contract.
1. Navigate to the Setup and Maintenance work area and search for the Manage File Import Mappings task.
2. Click the Go to Task icon.
3. In the Manage File Import Mappings page, select Contract from the Object drop down.
4. Select the Seeded check box.
5. Click Search.
6. The seeded Contract Import Mappings are displayed in the search results:
7. Click on the import mapping template that you want to download. This depends on the contract type that
you have decided to create.
a. Contract with sell intent lines: Used to import project contracts.
i. Contract.csv
ii. Contract_Party.csv
iii. Contract_Party_Contact.csv
iv. Contract_Line.csv
v. Associated_Projects.csv
vi. BillPlans.csv
vii. BillingControls.csv
viii. Contract_Sales_Credit.csv
b. Contract with no lines: Repository contract with the option of having more than one party or party
contacts.
i. Contract.csv
ii. Contract_Party.csv
iii. Contract_Party_Contact.csv
c. Contract with buy intent lines: Purchase agreements.
i. Contract.csv
ii. Contract_Party.csv
iii. Contract_Party_Contact.csv
iv. Contract_Line.csv
d. Contract with no lines (Non-Hierarchical): Simple repository contract with only one party, one
contact, and no lines.
Figure 3: Edit Import Mapping page where you can download the csv files associated with the seeded import mapping you have
selected.
You can enter names in the import file in place of IDs to identify data, for example, Party Name instead of ID.
Figure 4: Attributes required to relate contract lines with their parent (contract header).
Importing Attachments
If you wish to upload contract attachments, you will need to add the following columns to the Contract.csv file or the
file Contract with no lines (Non-Hierarchical) Template.csv:
» ATTACHMENT_FILE_NAME
» Can be an individual file or a zip file.
» Your zip file should contain less than 1000 attachments.
» ATTACHMENT_FILE_DESC
» ATTACHMENT_FILE_TITLE
» ATTACHMENT_CATEGORY_NAME
» Can be one of the following:
• OKC_DOCUMENTS_CONTRACT
• OKC_DOCUMENTS_CONTRACT_IMAGE
• OKC_DOCUMENTS_PCD
• OKC_DOCUMENTS_SUPPORTING_DOC
• OKC_DOCUMENTS_APP_ABSTRACT
NOTE: If you wish to import additional attributes not included in the seeded mapping, refer to Using Predefined
Templates to Import Data Through File-Based Data Import.
Note that in the Manage File Import Objects page, when uploading your file you need to select a File Type. The
options are Text file, XML file, or ZIP file. If you are importing contracts with child entities such as parties, lines,
associated projects, etc., then you will need to upload a zip file with all the csv files collected within it. If you are
using a seeded mapping with your zip file, you will need to first uncheck the Enable Automatic Mapping check box
before selecting the Seeded checkbox.
Select the mapping you are using to map the attributes you are uploading in your csv with those in the application.
The example below shows project contracts being imported using the seeded import mapping “Contract with sell
intent lines.”
Review Mapping of the Source File Attributes With the Target Import Object
Attributes
Select the import source file and then select ‘Next’ to see the mapping. This shows the mapping of the source csv
columns to the corresponding target contract attributes:
You do not need to update anything at this step if you are using the seeded mapping.
4. The View Import Status page provides a link to open the error file.
5. The error file contains one error csv for each entity you are uploading.
Resources
» Oracle Enterprise Repository (OER) Information formerly available in OER is now available via the Oracle Help
Center, for example see File-Based Data Import for Sales Cloud under the Development category.
» Contract Import
» Using Predefined Templates to Import Data Through File-Based Data Import
CONNECT WITH US
blogs.oracle.com/oracle
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116