Está en la página 1de 18

An Oracle White Paper

December 2014

Fusion Sourcing and Fusion Procurement Contracts


Integration Options

Release 9
Fusion Sourcing and Fusion Procurement Contracts Co-existence and Integration Options

Disclaimer
The following is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code,
or functionality, and should not be relied upon in making purchasing decisions. The development, release,
and timing of any features or functionality described for Oracles products remains at the sole discretion
of Oracle.
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Executive Overview ............................................................................. 1


Introduction ......................................................................................... 1
Getting started with Integration ........................................................... 2
Other System Considerations ......................................................... 2
Oracle Enterprise Repository (OER) ............................................... 2
Integration Methods ........................................................................ 3
Integrating Fusion Sourcing ................................................................ 4
Inbound Negotiation Creation ......................................................... 5
Outbound Negotiation Award .......................................................... 7
Integrating Fusion Procurement Contracts ......................................... 8
Inbound Award to Fusion Procurement Contracts .......................... 9
Outbound Contract to Purchasing Execution .................................. 9
Fusion Sourcing and Procurement Contracts ................................. 9
Fusion Procurement Contracts using Enterprise Contract Management
Integration ..................................................................................... 10
Identifying Reference Data ................................................................ 10
Suppliers ....................................................................................... 10
Items ............................................................................................. 13
Additional Reference Data ............................................................ 14
Conclusion ........................................................................................ 14
Additional Resources ........................................................................ 14
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Executive Overview

Practice smart sourcing, broaden the end user experience, and protect business interests by
taking advantage of next generation Fusion Procurement applications with Fusion Sourcing
and Fusion Procurement Contracts. These applications can operate as stand-alone solutions
and provide value to you out of the box, even before you consider how they might best fit into
the rest of your application environment. In some cases, a stand-alone deployment might be
the best approach, in others, some reference data and transactional integration with
Purchasing and other execution systems might make sense. With the right integration strategy,
you can successfully deploy Fusion Sourcing and Fusion Procurement Contracts to
complement your existing solutions while gaining the benefits of Fusion technology with
minimal investment and reduced risk.

Introduction

As part of your of Fusion Sourcing and Fusion Procurement Contracts implementation, you
should evaluate how these solutions will work with your existing systems and the different
integration options available to you. The approach you take will depend on your business
needs and processes as well as your existing systems and configurations. Fusion provides
flexible options for inbound and outbound integration that you can leverage during your
implementation.

This paper provides an overview of integration options for Fusion Sourcing and Fusion
Procurement Contracts. It will provide considerations for different integration approaches,
discuss the available integration technologies, and refer you to additional sources of
information. With a successful co-existence strategy, you can gain the benefits of Fusion
Sourcing and Procurement Contracts and start taking advantage of a superior user experience
today.

1
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Getting started with Integration


Before embarking on any integration project, you should analyze your current business processes and
assess the options that make the most sense for your organization. The first step is to assess the
technical costs and realities of deploying direct system-to-system integration verses running Fusion
stand-alone (without automatic integration) and using a process-based approach to achieve your
objectives. You should evaluate both the frequency and volume of information needed for each
potential integration. In addition, you should take into consideration your future process state, the
impacts it will have to the integration approach, and whether certain integrations could become
obsolete or need to be re-worked.
Keep in mind that you can still take advantage of all the features in Fusion Sourcing and Fusion
Procurement Contracts, without having to build integrations with your existing systems. Some
complexities are unavoidable when implementing systematic integration. For example, you must
consider exception cases and error-handling, error recovery, and adaptability to changing or extended
data models. The right strategy can mitigate unnecessary investments in building integration and
simplify your overall strategy.

Other System Considerations


For any integration project you will need to assess the inbound/outbound integration capabilities of
your current systems. The integration approach you use will be dependent both on the integration
technology of Fusion Applications as well as your existing systems.
Over time, additional Fusion integration technologies and web services will become available. The
integration approach with Fusion Sourcing and Procurement Contracts is to support generic input and
output methods that other systems can utilize according to the technologies available in those source
applications. For example, most existing procurement systems have a way of creating purchase orders
from an external source. In most cases it should be possible to map the information generated from
Fusion into an appropriate input format.

Oracle Enterprise Repository (OER)


The Oracle Enterprise Repository (OER) for Oracle Fusion Applications is an online resource for
discovering Oracle Fusion Applications metadata. You can use OER to find information on the
integration assets that are available for particular objects and processes across Fusion, including those
relating to Oracle Fusion Sourcing and Oracle Fusion Procurement Contracts. OER will always
contain the most recent information on what is available. As time passes, you should consult OER for
the most currently available assets (and any new updates) prior to beginning an integration project.
Oracle expects that new assets will become available over time.
Examples of the types of assets that you can discover within OER include:
Web Services
File-Based Data Integrations

2
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

View Objects
Interface Table Definitions
Sample Templates
Data Model Diagrams
For more information on these assets and OER in general, please refer to Making the Most of the
Oracle Enterprise Repository for Oracle Fusion Applications white paper.

Integration Methods
Fusion applications are built with Oracles Application Development Framework (ADF) and provide
many methods of integration with other applications including: ADF Services (commonly referred to
as Web Services), Spreadsheet Integration, File Based Data Import, and Reporting Tools.

Figure 1. Integration Methods for Oracle Fusion Applications

Web Services

A web service provides a standardized way of integrating two web-based applications. A web service is
a program that can be accessed remotely using different XML-based languages. ADF Services simplify
integration by enabling XML data exchange between different applications and different platforms.
On premise implementations can access the Enterprise Manager and tailor the available web services
for inbound/outbound integration. But for areas where there are no web services currently available,
generating OTBI or BI Publisher reports that can be used for integration may suffice depending on
what is being integrated.

Spreadsheet Integration

3
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Spreadsheet integration through ADFi or other methods enables the use of familiar spreadsheet tools
such as Excel. ADF Desktop Integration (ADFdi) is part of the ADF framework and enables desktop
integration with MS Excel spreadsheets to manage large volume data uploads into Fusion Applications.
The integration provided with ADFdi includes interactivity that enables web picker to search for valid
values, perform validation during data entry, display error messages, and immediately submit
transactions directly from Microsoft Excel.

File Based Data Import

File Based Data Import (FBDI) is another option for getting information into your Fusion
applications. For applications deployed in the public cloud, in the absence of a delivered web service,
the currently available option is file based integration to transfer files to a location that the source
system can consume. The process of using FBDI is quite simple: download an excel template that
identifies all of the fields, populate the spreadsheet with data from the external system, save the file as a
.csv file type, upload the file, and run processes to transfer the data to the interface tables and import
into the various applications. All of the data is validated during import to insure its integrity. External
data can be extracted and formatted into a source file for transfer into interface tables and import into
Oracle Fusion applications. The FBDI process can be automated using the Financial Utility web
service as described in detail within the External Data Integration white paper.

Reporting Tools

Reporting tools can be used to extract data from Fusion applications for further analysis and import
data into external systems via XML, Excel or other file types. Oracle Transactional Business
Intelligence (OTBI) Reporting, can be used to extract data for import into your external systems.
Oracle Transactional Business Intelligence provides the ability to build custom queries on transactional
data, and the output can be downloaded to Excel. You can configure an Oracle Business Transaction
Intelligence (OTBI) report or BI Publisher report and generate it based on your organizations specific
requirements.

Integrating Fusion Sourcing


In order to facilitate effective negotiation, buyers and suppliers should be able to quickly find the
information they need, easily figure out what actions to take and provide the necessary information in
minimal time. Oracle Fusion Sourcing delivers the structure, tools and information you need to
maximize your negotiating success which saves you time and money while delivering quality and value.
In a typical Sourcing process, you conduct research on potential Sourcing opportunities, identify
suppliers, and define a strategy for your negotiation. Once you have determined and created the
content of the sourcing event, you conduct your negotiation with suppliers, analyze the results and
determine the best award. After your award has been determined, you can generate your purchase
orders or agreements for execution.
Several areas of potential integration exist. When creating a negotiation, you can bring in information
from other sources to create the content of the negotiation. After an award decision has been
finalized, you can pass award information to your Purchasing system for execution. For reference data,

4
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

you can decide how to import and maintain information such as your suppliers and items based on
your business process. When integrating Fusion Sourcing, choose the integrated option that best fits
the volume and frequency of events that your organization conducts.

TABLE 1. FUSION SOURCING INTEGRATION OPTIONS

INTEGRATION AREA INTEGRATION OPTION INTEGRATION METHOD NOTES

Negotiation Import Requirements Spreadsheet Use delivered spreadsheet template to import


Creation and Lines requirements (questions to suppliers) and negotiation
lines to create negotiations. Copy/Paste from your
current document(s) into rich text boxes in Fusion
Sourcing negotiations.

Negotiation Import Requisitions Requisition Import Use Requisition Import program to bring requisitions
Creation from Existing into Fusion Purchasing. Requisition Import can
System(S) process excel, xml and flat file formats. Use
Document Builder to create Negotiation.

Award Generate Award Spreadsheet Use delivered Award Analysis spreadsheet for import
Analysis Spreadsheet into existing Purchasing system.

Award Create Award Report Reporting Tools Create Award report with the fields you need for your
source purchasing system. You can use Fusion
reporting tools such as OTBI or BI Publisher.

Award Generate Purchase Reporting Tools Create purchase orders or blanket purchase
Orders and Blanket agreements in Fusion Purchasing automatically from
Agreements in Fusion Fusion Sourcing. Use reporting tools to push the data
Purchasing to your existing purchasing system

Inbound Negotiation Creation


Fusion Sourcing provides tools to make the negotiation creation process easier. The first option to
bring in negotiation information from another source system is to utilize the web service for
negotiation creation in Fusion Sourcing. In the Oracle Enterprise Repository (OER), you can find all
the information for the negation creation ADF service called Supplier Negotiation.

Existing Fusion
Purchasing Web Service Sourcing
System (s) Negotiations

5
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Figure 2. Integration using the Create Negotiation Web Service

Another option is to create negotiations in Fusion Sourcing and copy/paste information into rich text
boxes and used the delivered Excel uploads throughout the negotiation creation process. For a large
number of requirements (questions asked to suppliers), Fusion Sourcing provides a spreadsheet upload
capability. For example, a Request for Proposal (RFP) could be quite large with hundreds of questions
being asked to the supplier. You can take questions from your existing documents, copy them into the
formatted spreadsheet template, and easily import them into the negotiation. Similarly, if a negotiation
has a large number of negotiation lines, you can enter negotiation line information such as item
description, pricing, etc in the formatted spreadsheet and upload the spreadsheet into the negotiation.
The spreadsheet upload capabilities make the process of creating negotiations simple and efficient in
Fusion Sourcing

Negotiation
Lines Excel Upload Fusion
Sourcing
Excel Upload
Requirements Negotiation

Figure 3. Excel Integration for Requirements and Negotiation Lines in Fusion Sourcing

Another source of negotiation lines can be requisition lines from your source purchasing system. If
you have a large number of requisition lines that you want to consolidate and bring into a negotiation,
you can use the Supplier Negotiation web service or you may want to consider leveraging the
requisition import capabilities available with Fusion Purchasing. Requisition lines targeted for
negotiation from your source purchasing system may be imported into Fusion Purchasing using the
Requisition Import program. Requisition Import can process excel, xml and flat file formats. You
can select to consolidate requisition lines according to your business needs in the Process Requisitions
workbench. Once you have identified and selected the requisition lines for negotiation, you can easily
create the negotiation lines in Fusion Sourcing. It is important to consider that this process is useful if
there is a high volume of requisition lines that need to be consolidated and then undergo negotiation
events. However, this process requires more master data synchronization into Fusion to recreate the
requisitions. Depending on the volume of information being brought into the negotiation, you may
consider consolidating demand from your source system and creating negotiations directly in Fusion
Sourcing as described above.

Fusion
Existing Fusion
Purchasing
Purchasing Req Import Document Builder Sourcing
Process
System (s) Negotiation
Requisitions

Figure 4. Importing Requisitions to Create Negotiation

6
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Outbound Negotiation Award


Once you have conducted a negotiation with your suppliers, analyzed supplier responses and
determined how to award your business, you can finalize your award decision. At this point, the award
decision may need to be created in your existing purchasing system for execution. The simplest
approach is to manually create the purchase order or blanket purchase agreement in each instance of
your purchasing execution system based on your Fusion Sourcing award decision. You can use the
Award Analysis spreadsheet in Fusion Sourcing as a summary of your award decision or build a report
with award information with OTBI or BI Publisher. For an integrated approach, you can create a file
with award information in a format that can be processed by your existing purchasing system.

Award Report
OTBI
Existing
or BI Publisher Purchasing
Fusion System
Sourcing
Award System Generated Award
Analysis
Spreadsheet

Figure 5. Fusion Sourcing Award to Existing Purchasing System

Another option is to create your purchase orders or blanket purchase agreements in Fusion Purchasing
automatically from Fusion Sourcing. Once the purchasing documents are created in Fusion
Purchasing, you can use reporting tools to push the data to your existing purchasing system. With this
method, you would use the standard award process to create the PO or BPA from Fusion Sourcing
into Fusion Purchasing and then use reporting tools to generate data that can be consumed by your
existing execution systems.

Fusion
Purchasing
Purchase
Outbound XML Existing
Order
System Generated Purchasing
Fusion System
Sourcing Fusion Outbound XML
Award System Generated Purchasing
Blanket
Purchase
Agreement

Figure 6. Fusion Sourcing Award through Fusion Purchasing

Overall, you should assess the volume and frequency of events to determine the best way to execute
your award decision.

7
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Integrating Fusion Procurement Contracts


Oracle Fusion Procurement Contracts can help you take control of the contracting process, reduce
risk, and ensure you achieve the benefits you negotiate during your sourcing process. As part of the
Oracle Fusion Procurement suite, you can create agreements with Oracle Fusion Procurement
Contracts that follow your policies and deliver better visibility and compliance.
The following table illustrates the high-level options for integrating Fusion Procurement Contracts
with respect to the inbound award information that serves as the basis for the contract, and the
outbound contract information used by your purchasing system to execute the contract. The
integrated options are explained in more detail in the sections that follow.

TABLE 2. FUSION PROCUREMENT CONTRACTS POTENTIAL INTEGRATION APPROACHES

INTEGRATION AREA INTEGRATION OPTION INTEGRATION METHOD NOTES

Inbound award From 3rd party Sourcing solution Contract author manually Use an underlying agreement or PO
information to Fusion enters minimal award transaction as the mechanism for holding
Procurement Contracts information (such as the structured data required for authoring.
contract amount & Many award details are not required on
pricing) to facilitate this contract.
authoring.

Inbound award From Fusion Sourcing Award Automatic creation of Create purchase orders or blanket
information to Fusion POs and Agreements purchase agreements in Fusion
Procurement Contracts Purchasing automatically from Fusion
Sourcing. Draft Terms and Conditions
from Sourcing can automatically carry
forward as the draft contract language on
Agreement or PO.

Inbound award Direct creation of agreement Spreadsheet Create spreadsheet with the required
information to Fusion information for Fusion agreements or
Procurement Contracts Purchase Orders. Add Terms and
Conditions for authoring.

Outbound contract Purchase Orders and Manual transfer of Structured purchasing information can be
execution information from Agreements financial details entered manually into execution system.
Fusion Procurement Related authored contract can be
Contracts to target referenced or attached.
purchasing system(s)

Outbound contract Purchase Orders and Reporting Tools Create Fusion purchase orders or blanket
execution information from Agreements purchase agreements as part of contract
Fusion Procurement authoring process. Use reporting tools to
Contracts to target push the data to your existing purchasing
purchasing system(s) system.

8
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Inbound Award to Fusion Procurement Contracts


When creating a contract, you may wish to load information into Fusion Procurement Contracts from
your existing sourcing or purchasing systems. Typically you would create a contract purchase
agreement or blanket purchase agreement in Fusion and then associate the appropriate terms and
conditions using Procurement Contracts. The agreements or POs could come from a spreadsheet that
you create from a source system (such as a third-party sourcing application) or via the Fusion Sourcing
award process. Fusion allows the creation of a blanket agreement or contract purchase agreement as
described in table 2 above.

Outbound Contract to Purchasing Execution


To interface contract information into your existing systems you may choose to utilize the purchase
order or agreement transactions within Fusion. After you create these transactions and author the
terms and conditions, the structured purchasing data would then be available. One advantage of
having the structured data available on the Fusion Purchase Order or Agreement transaction is that
you can leverage rules that use that data to drive compliance to your policies when authoring the
contract language. You can then integrate to your existing execution systems from the Fusion
transactions using an XML-based integration. This is summarized in Table 2 above. The approach is
the same for both Purchase Orders and Blanket Purchase Agreements as shown in Figure 7 below.
Fusion
Purchasing
Purchase
Orders

Outbound XML
Fusion
Procurement Existing
Contracts Purchasing
Terms / System
Conditions
Outbound XML

Fusion
Purchasing
Blanket
Purchase
Agreements

Figure 7. Fusion Procurement Contracts Outbound Flow leveraging Purchasing to Purchasing integration

Fusion Sourcing and Procurement Contracts


If you wish to deploy both Fusion Sourcing and Fusion Procurement Contracts with a non-Fusion
Procure-to-Pay execution system, you can extend the contracts integration and sourcing integration
mentioned in the above sections to work as a combined flow (see Figure 8 below.) In this model, a
Fusion Sourcing award integrates directly into a Fusion purchase order or agreement, passing over

9
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

draft terms and conditions from the RFx. You can then use Fusion Procurement Contracts to author
the final terms and conditions. Finally, you can choose to integrate the purchase order and agreement
transactions from Fusion to your execution systems.
Fusion
Purchasing
Purchase
Orders
System Generated Outbound XML
Fusion
Fusion Procurement Existing
Sourcing Contracts Purchasing
Award Terms / System
Conditions
System Generated Outbound XML

Fusion
Purchasing
Blanket
Purchase
Agreements

Figure 8. Fusion Sourcing and Procurement Contracts Integration Flow

Fusion Procurement Contracts using Enterprise Contract Management Integration


For cases when Fusion Procurement Contracts is the only Fusion Procurement module being
deployed, you can leverage the Enterprise Contract Management (ECM) outbound integration to non-
Fusion purchasing systems. This integration consists of defining line level purchasing information on
the ECM buy-intent contract such that it can be pushed out to one or more purchasing systems for
execution. This integration assumes that the receiving purchasing system is able to accept an
agreement or purchase order transaction that is generated from a third-party web service. A separate
white paper, Customizing Fusion Enterprise Contracts for Purchasing Integration, discusses the set up
and required configuration. Consult that document for details on setting up this scenario

Identifying Reference Data


Reference data (such as item and supplier details) is the supporting information necessary for Fusion
Sourcing and Fusion Procurement Contracts to be able to function according to your organizations
business process. Reference data is typically maintained on a periodic basis and should be kept in sync
with the source system of record. The integration methods you use for reference data really depend on
the type of organization, business needs, and deployment method (i.e., public cloud, private cloud or
on premise). For some organizations, reference data with a large volume and frequency of changes
may require building direct system to system integration to keep information synchronized.

Suppliers

10
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Integration of supplier information is subject to the same considerations detailed in the opening
paragraphs of this document. You must have a good knowledge of the volume and frequency of
change for reference data like suppliers. Depending on the volume and frequency of change, you may
find that it is preferable to maintain your data rather than build and manage integration. In defining
your supplier data integration strategy for a Fusion Sourcing or Fusion Procurement Contracts co-
existence deployment, the first consideration will be to determine which system will maintain the
supplier source of truth; Fusion or an existing transaction system. The answer to this question will
impact your integration strategy. The table below summarizes the high level integration options.
If you choose to maintain supplier information in your existing transactional system, you will need to
load and update supplier information in Fusion. When loading supplier information in Oracle Public
Cloud, inbound integration is supported through file based upload using FBDI. You can find the
spreadsheet template for loading supplier information in Oracle Enterprise Repository. Fusion
supports the supplier import processes outlined in the table below.

TABLE 3. SUPPLIER IMPORT

INTEGRATION AREA INTEGRATION OPTION INTEGRATION NOTES

METHOD

Suppliers Import and update supplier information including FBDI Interface tables available for on
profile and organization details. Interface Tables premise and private cloud

Supplier Addresses Import and update supplier address information FBDI Interface tables available for on
including location and communication details. Interface Tables premise and private cloud

Supplier Sites Import supplier site information including generic FBDI Interface tables available for on
site information such as site name, site Interface Tables premise and private cloud
purposes, alternate site name as well as site-
specific purchasing, receiving and invoicing
terms and conditions.

Supplier Site Import site assignments representing client FBDI Interface tables available for on
Assignments business units that are the recipient of Interface Tables premise and private cloud
procurement services from the supplier site.
Details imported can include tax and accounting
information.

Supplier Contacts Import and update contacts of the supplier FBDI Interface tables available for on
responsible for coordinating procurement Interface Tables premise and private cloud
activities with the buying organization.

Supplier Business Import and update business classification details FBDI Interface tables available for on
Classifications including certification and agency information Interface Tables premise and private cloud
that establish diversity qualifications of the
supplier.

11
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Supplier Products Import and update products and services FBDI Interface tables available for on
and Services category information representing what the Interface Tables premise and private cloud
Categories buying organization can expect to procure from
the supplier.

As of release 9, in addition to the traditional use of importing new supplier data, Fusion Procurement
Cloud Service supports updates to existing suppliers through the supplier import process. Mass
updates can be made to supplier data using this feature. Any changes to one or many suppliers can be
easily handled through our import process rather than having to update these details manually through
the application.
As of release 9, the system supports update on the following entities:
Suppliers
Supplier Addresses
Supplier Contacts
Supplier Business Classifications
Supplier Products and Services Categories
Delete is supported on the following entities:
Business Classifications
Contact Addresses
Supplier Products and Services Categories
The import template now supports an action, Update, that should be used to perform both changes
and deletes to the supplier profile data.

File based upload of supplier data is not reserved for Public Cloud only. On premise and private cloud
deployments may also use FBDI for file based supplier data upload. Additionally, on premise and
private cloud customers have direct access to interface tables. Using SQL, supplier data can be directly
inserted into the supplier interface tables to be imported into the supplier master.
Another choice is to use Fusion as the system of record for supplier data. A customer might choose
this approach if the Fusion supplier master better meets their requirements for managing supplier
information to assist in developing the increasingly strategic value of supplier relationships. The
requirement is to get supplier data from Fusion into your existing systems.

TABLE 4. SUPPLIER EXPORT

INTEGRATION AREA INTEGRATION OPTION INTEGRATION METHOD NOTES

Suppliers Export all Supplier Information including: Supplier Sync Service Some supplier attributes not
Supplier, Address, Supplier Site, Site Reporting Tools supported for export in
Assignments, Contacts, Business reporting tools.
Classifications, Products and Services Supplier Sync Service is
currently available for on
premise and private cloud.

12
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Outbound integration for publishing supplier data from Fusion Procurement to your existing systems
is supported by a web service; Supplier Sync Service. The Supplier Sync Service can publish supplier
information updates to your existing systems. This enables your existing systems to use Fusion as the
supplier source of truth that maintains all supplier profile information. Near real-time synchronization
of supplier information allows your existing systems to leverage Fusion supplier information to drive
other procurement transaction flows. The Supplier Sync Service can provide data for creation or
update of supplier information and is dependent on the integration capabilities of your existing
systems. This approach is currently available for private cloud and on premise deployments.
Another option to export supplier data from Fusion is reporting tools. Fusion reporting tools can be
used to create an output file containing structured supplier information (based on the attributes that
are currently available for suppler data). This output file can then be used to import supplier data into
your existing transaction systems.

Items
Similar to other types of reference data, you should consider the volume, use, and frequency of change
for your purchasing items and categories to determine the appropriate integration approach. You can
load purchasing item categories into catalogs using ADFDi for your cloud or on premise deployment.
For item integration, you have several options and it depends on the level of automation that your
organization requires and how you have deployed your Fusion application. For public cloud or on
premise, you can load data into the interface tables via UCM (Universal Content Manager). If you are
deploying on premise, you can load the interface tables directly with SQL or import items through
Item web services. The different integration options for items are outlined in the table below.

TABLE 5. FUSION SOURCING INTEGRATION OPTIONS

INTEGRATION AREA INTEGRATION OPTION INTEGRATION METHOD NOTES

Items Direct Population of Interface SQL Available for an on premise deployment


Tables without Item Batch Support only.

Items Direct Population of Interface SQL Available for an on premise deployment


Tables with Item Batch Support and with Product Hub.

Items Microsoft Excel (ADFdi) through Spreadsheet Available in Product Hub and on premise,
Item Batch private or public cloud deployment.

Items CSV file (pre-defined format) File Available in public cloud only.
upload via secure FBDI

Items CSV/XML file (any format) upload File Available on premise, private or public
through Item Batch cloud.

13
Fusion Sourcing and Procurement Contracts Co-existence and Integration Options

Items Product Hub Portal: suppliers load Web Services Available with Product Hub
items through supplier portal,

Additional Reference Data


Additional reference data needs to be set up in Fusion to use Fusion Sourcing and Fusion Procurement
Contracts according to your business process. The additional reference data includes: HR Users, GL
Accounts, Business Units, Terms (Freight, Payment, etc.), Unit of Measure, Locations, etc. You need
to assess the volume and frequency of changes and updates to reference data in order to determine the
best integration method. As a general rule, reference data can be maintained within Fusion
Applications and will typically have low volume/change that can be manually maintained.

Conclusion
You can start taking advantage of the next generation Fusion Procurement applications with Fusion
Sourcing and Fusion Procurement Contracts to practice smart sourcing, broaden the end user
experience, and protect business interests. Consider the various integration options that exist, as there
are always costs and complexity trade-offs when making decisions about the right level of automation.
You should carefully evaluate the entire business process to find the most workable option for your
particular business needs.
This paper provides recommendations based on technologies and web services available at the time of
publication. Please consult the Oracle Enterprise Repository for the latest available web services,
import/export processes, and other integration assets.

Additional Resources
Oracle provides many resources to help with integration options. Please reference the resources below for
additional information.

TABLE 6. ADDITIONAL RESOURCES

SUBJECT AREA TYPE RESOURCE DESCRIPTION

OER White Paper Making the most of Oracle Enterprise Repository for Fusion
Applications

Fusion Sourcing White Paper Standalone Fusion Sourcing Implementation

Fusion Procurement Contracts White Paper Standalone Fusion Procurement Contracts Implementation

Fusion Procurement Contracts White Paper Customizing Fusion Enterprise Contracts for Purchasing
Integration

External Data Integration White Paper Import and extract data from Oracle ERP Cloud

14
Fusion Sourcing and Fusion Procurement Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Contracts Integatoin Options
December 2014 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 warranties or conditions, whether expressed orally or implied in
Author: Cynthia Pavana
law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
Contributing Authors: Mike OConnor
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This
Oracle Corporation document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our
World Headquarters prior written permission.
500 Oracle Parkway
Redwood Shores, CA 94065 Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
U.S.A.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
Worldwide Inquiries: are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
Phone: +1.650.506.7000 trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0113
Fax: +1.650.506.7200

oracle.com