0% found this document useful (0 votes)
22 views11 pages

Understanding Contracts Import White Paper

This document outlines the process for importing contracts into Oracle Fusion Enterprise Contracts, including the necessary preparations, data structure, and import steps. It details the types of contracts that can be imported, the required CSV templates, and how to handle attachments. Additionally, it provides guidance on reviewing the import process and troubleshooting any errors that may occur.

Uploaded by

yuda.prawira
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views11 pages

Understanding Contracts Import White Paper

This document outlines the process for importing contracts into Oracle Fusion Enterprise Contracts, including the necessary preparations, data structure, and import steps. It details the types of contracts that can be imported, the required CSV templates, and how to handle attachments. Additionally, it provides guidance on reviewing the import process and troubleshooting any errors that may occur.

Uploaded by

yuda.prawira
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

Understanding Fusion Enterprise Contracts

Import
ORACLE WHITE PAPER | JUNE 2016
Table of Contents

Introduction 1

Understand the Overall Structure and Types of Contracts 1

Prepare Your Existing Contract Data 2

Download the Contract Import csv Template File 2

Populate Your Data into the Import csv Template File 4

Importing Attachments 5

Upload the Completed Import csv File 5

Review Mapping of the Source File Attributes With the Target Import Object Attributes 6

Schedule the Import Process 7

Review the Import Log Files 7

Resources 8

UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


Introduction
This document provides the information you need to import contracts into Oracle Fusion Enterprise
Contracts. It complements information available in the Oracle Help Center, which you can reference at
the end of this document.

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.

To import contracts, you need to do the following:


1. Understand the overall structure and types of contracts you can manage in Enterprise Contracts.
2. Prepare your existing contract data.
3. Download the contract import csv template file(s).
4. Populate your data into the import csv template file(s).
5. Upload the completed import csv file(s).
6. Review the mapping of the source file attributes with the target import object attributes.
7. Schedule the import process.
8. Review the import log files

Understand the Overall Structure and Types of Contracts


Enterprise Contracts provides a repository for different types of contracts. Contracts base functionality provides the
foundation for other contracts options such as Fusion Procurement Contracts and Fusion Project Contract Billing.

1 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


Figure 1: Enterprise Contract options and contract types.

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.

Prepare Your Existing Contract Data


This would be different in each implementation but some general questions can help you assess your needs:
» Are your contracts with suppliers (buy contracts) or are they with customers (sell contracts)?
» Do you need to import only contract header information, for example, contract amount, dates, parties, or do you
also need to import contract lines?
» If you need to import lines, what type of lines are these, e.g. project lines, buy agreement lines?
» Do you have document attachments to import?

Download the Contract Import csv Template File


Refer to the topic Using Predefined Templates to Import Data Through File-Based Data Import.

To download an import template:

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:

2 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


Figure 2: File Import Mapping page showing the seeded import mappings you can use to import your contracts.

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.

3 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


i. Contract with no lines (Non-Hierarchical)_Template.csv
 NOTE: This mapping is deprecated and replaced by ‘Contract with no lines’
8. The Edit Import Mapping page is displayed.
9. On the Edit Import Mapping page, click Download Template.
10. A zip file opens with the list of csv files included in the import mapping template.
11. Save the csv files to a location on your desktop.

Figure 3: Edit Import Mapping page where you can download the csv files associated with the seeded import mapping you have
selected.

Populate Your Data into the Import csv Template File


You must understand the columns in the import templates to populate the templates with the correct data. Use the
header reference file to help you understand the attributes that can be imported into the Contract.csv file. You can
access the reference file from the Contract Import topic on the Help Center.

The reference file includes:

» The names and descriptions of attributes that can be imported.


» Whether the attribute is required, conditionally required, or optional.
» The required data type and maximum length.
» Defaulting logic and validation.
» The interface column name that the attribute uses.
» The destination table and table column where the attribute will be stored, and whether it is required in that
destination table.
You can also use the Contracts Service Version 2 section in the SOAP Web Services for Sales Cloud document to
obtain descriptions of attributes not included in the reference file.

You can enter names in the import file in place of IDs to identify data, for example, Party Name instead of ID.

4 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


When importing child entities such as contract lines, or parties to the contract, you must associate them to the
parent contract record. For example in the Contract_Line.csv file, use the attributes Header Ext Source and Header
Ext Key to point to the parent of the contract line. The contract header csv file (Contract.csv) has the equivalent
columns ExtSource and ExtKey which need to be populated with a unique combination when importing. The same
values must be referenced in each file to associate a line to its header.

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.

Upload the Completed Import csv File


Once you have completed entering your contracts data into the csv file(s), you can upload it. The help topic
Importing Data from a File: Procedure explains the steps needed to complete the Manage File Import Activities task.

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.”

5 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


Figure 5: Browsing for your completed import files

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:

6 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


Figure 6: Review the mapping from source to target.

You do not need to update anything at this step if you are using the seeded mapping.

Schedule the Import Process


If you are satisfied, click Next and then click Activate to start the import process.

Figure 7: Schedule your import process.

Review the Import Log Files


Once your import process completes, you can review the import log files.

7 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


1. Navigate to the Setup and Maintenance work area and search for the Manage File Import Activities task.
2. Query for your import process.
3. If your process completed with errors, you can click on the status to view more details.

Figure 8: Checking the status of your import process

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.

Figure 9: Opening the error file.

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

8 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT


» Importing Data from a File: Procedure

Oracle Corporation, World Headquarters Worldwide Inquiries


500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

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

White Paper Title


January 2016
Author: [OPTIONAL]
Contributing Authors: [OPTIONAL]

9 | UNDERSTANDING FUSION ENTERPRISE CONTRACTS IMPORT

You might also like