Documente Academic
Documente Profesional
Documente Cultură
INTRODUCTION.................................................................................................................................................. 4
INTRODUCTION.............................................................................................................................................................12
DISCOVERING AUTOMATION SERVICE DETAILS....................................................................................................................12
CONSTRUCTING END POINT URL.....................................................................................................................................13
WEB SERVICE OPERATIONS.............................................................................................................................................13
WEB SERVICE OPERATIONS WITH PARAMETER DETAILS.........................................................................................................13
Operation: uploadFileToUcm...............................................................................................................................14
Operation: submitESSJobRequest........................................................................................................................15
Operation: getEssJobStatus.................................................................................................................................16
Operation: downloadESSJobExecutionDetails.....................................................................................................16
TROUBLESHOOTING.......................................................................................................................................... 17
PRE-REQUISITES:...........................................................................................................................................................17
FLOW STEPS:................................................................................................................................................................18
PRE-REQUISITES:...........................................................................................................................................................21
FLOW STEPS:................................................................................................................................................................21
APPENDIX 1 SECURITY PRE-REQUISITES NEEDED FOR DOWNLOADING ESS JOB EXECUTION DETAILS................23
APPENDIX 2 SAMPLE CODE FOR PREPARING DATA FILE FOR THE INBOUND FLOW............................................25
Templates for structuring, formatting and generating the data file according to the requirements of
the target application tables.
A File based load process for loading data from the data file into the interface tables.
Application-specific data import processes for transferring data from interface tables to the
application tables in your Oracle Fusion Applications.
The below process flow diagram briefly explains the steps in the flow.
Download
Download the
the
File
File Import
Import template
template
Prepare
Prepare data
data file
file using
using
downloaded
downloaded template
template
Upload
Upload File
File to
to content
content
server
server (UCM)
(UCM)
Import
Import data
data to
to application
application
table
table using
using import
import job
job
Data
Data successfully
successfully uploaded
uploaded to
to
product
product tables
tables
You access these files from the Details tab of the Import process that corresponds to the interface tables
that store the data. To find the process, you can search the interface table or you can search the specific
process. E.g. Journal Import process
Field Value
Search String FBDI
Type File Based Data Import
Product family <product family>
3. Click Search.
4. Select your respective import process from the results pane. E.g. Journal Import.
Downloading Templates
1. Use the Search area to locate the import process and then select it from the search results.
2. Click on the Details tab on the lower pane. Here you can see the following links:
Control files, which describe the logical flow of the data load process.
XLSM templates, which include worksheets and macros that assist you in structuring, formatting, and
generating your data file.
Alternatively you can use XML templates, which you import into Oracle Data Integrator. Please refer to
3. Download the template using the link provided. E.g. JournalImportTemplate.xlsm used for Journal
Imports process.
Important
If you omit or fail to complete the instructions, data load errors and data import failures are likely.
Templates
Important
Deleting or reordering columns will cause the load process to fail and result in an unsuccessful data load.
The external data must conform to the data type that the control file and process for the associated
database column accepts.
Date column values must appear in the YYYY/MM/DD format.
Amount column values must appear with no separators other than a period (.) as the decimal separator.
Negative values must be preceded by the minus (-) sign.
Column values that require whole numbers include data validation to allow whole numbers only.
Columns are formatted, where applicable, to match the target field data type to eliminate data entry
errors.
For columns that require internal ID values, refer to the bubble text for additional guidance about finding
these values.
After you finish preparing the data in the sheet, click the Generate CSV File button to generate a ZIP file
containing one or more CSV files.
For using XML templates please refer to the Appendix 7- Using XML templates to generate Data Files.
File Import and Export page in Oracle Fusion Applications: Manual flow
Oracle Fusion Financials Utility web service: Automated flow
Oracle Fusion Financials Utility web service is explained in Flow Automation Web Service
section. The following section talks about the manual flow using File Import and Export page.
For information about what objects to upload and download, including templates for external data
integration, refer to the Oracle Enterprise Repository for Oracle Fusion Applications.
For general access to content management, including to all metadata and to manage accounts, use the
Oracle WebCenter Content Server's standard service user interface.
See: WebCenter Content System Administrator's Guide for Content Server: Accounts
For information about naming accounts involved with import and export,
See: sub-section Account Names under section Files for Import and Export: Explained
See: Oracle WebCenter Content System Administrator's Guide for Content Server: About Batch
Loading
For information about security, see the Security tab in Oracle Enterprise Repository for Oracle Fusion
Applications.
For information about roles such as the integration specialist roles for each product family,
You can import data into or export data out of Oracle Fusion Applications using repositories of content
and processes for import and export. Integration specialists stage data for import and export. Application
administrators run processes to import data in repositories of content to application transaction tables, or
retrieve data exported from applications.
Aspects of managing files for import and export involve the following:
The File Import and Export page lets you upload content to, or download content from the document
repository of Oracle WebCenter Content Management.
Search criteria on the page are limited to the minimum metadata of content management records needed
for file import and export.
Everyone who uses the File Import and Export page is assigned to one or more accounts in content
management. Accounts organize and secure access to content items.
Interaction between the File Import and Export page and Oracle WebCenter Content requires securing
content in an account. Oracle provides predefined accounts in Oracle WebCenter Content.
Areas of file import and export to consider involve the following:
Security
Searching records
Accessing content in a new account
Account names
Deleting files
Uploading for Import
Downloading for Export
File Size
8 2012 Oracle Corporation. All Rights Reserved.
Security
The duty role needed for accessing the File Import and Export page is File Import and Export
Management duty. This duty role is included in the predefined role hierarchy for integration specialist roles
and product family administrator roles.
Files in Oracle WebCenter Content are associated with an account so that only users who have
permission to a particular account can work with content items that belong to that account. You can only
upload and download files to and from content management that are associated with accounts that you
are entitled to access.
Oracle WebCenter Content does not support trailing slashes (/). Account names are appended with a $ to
ensure each account is unique. Account names are dynamic so that if they overlap (one name is
completely contained in another, longer name, such as US and US Sales), each account is treated as
discrete by access grants. Security such as virus scanning is handled by the underlying integrated
content management.
Searching Records
A record in Oracle WebCenter Content contains metadata used for accessing the file. When a scheduled
process has run to completion on a file, the record for the file includes a process ID.
When you create a new account in Oracle WebCenter Content and the content server is not restarted,
access to content in the new account from the File Import and Export page may be delayed until the
policy store is updated.
Account Names
If you create custom accounts for importing or exporting data, use the following conventions for naming
the account: Do not include a slash "/" at the beginning or end End with "$" to avoid partial string
matching Use "$/" as a separator in the hierarchical structure.
For example: fin$/journal$/import$ The File Import and Export page transforms account names by
removing the $s. For example fin$/journal$/import$ displays as fin/journal/import. The Remote Introdoc
Client (RIDC) HTTP command-line interface (CLI) transforms the account name you specify without $
symbols to one that includes them. For example, fin/journal/import becomes fin$/journal$/import$ in
WebCenter Content.
You must transfer files to these predefined account in content management that corresponds to the
interface table or assets.
See Appendix 3 - Predefined Target UCM Accounts for a list of the target accounts present for each
interface table.
You can create subaccounts to further organize your files. However, you must create the account
subordinate to the predefined account for the asset you are integrating.
Deleting Files
You can delete one file at a time when you use the File Import and Export page. To delete multiple files
simultaneously from the content repository, use the standard service page in Oracle WebCenter Content.
9 2012 Oracle Corporation. All Rights Reserved.
Uploading for Import
When you create a record, you must specify an account as well as the file. When you create a record, you
must specify an account as well as the file. The account you specify determines which import process
picks up that file to import it.
You can upload any file formats that can be parsed by the content repository being used, such as any
MIME or content types. However, the format uploaded should conform to the requirements of the import
process being used, such as a comma-separated values (CSV) file for the Load Interface File for Import
process.
Processes you run to export data result in files in content management. Records in the search results
table of the File Import and Export page provide links to the files for download.
File Size
Data compression
File chunking or splitting
The UPLOAD_MAX_DISK_SPACE parameter in the web.xml file determines the maximum allowable file
size in content management. The default maximum size is 10240000 (10MB).
Loads external setup or transaction data from the data file on the content management server to interface
tables.
You run this process from the Scheduled Processes page. You can run it on a recurring basis.
Parameters
Import Process
Data file
The final destination for your external data is the application data tables of your Oracle Fusion
Applications product.
Interface tables are intermediary tables that store your data temporarily while the system validates format
and structure. Run the Load Interface File for Import scheduled process to load data from the data file into
the interface table that corresponds to the template that you use to prepare the data.
To load your data into interface tables, submit the Load Interface File for Import scheduled process:
If no errors exist in the data file, the status will be SUCCEEDED. The process populates the
interface tables.
If there are upload errors, the status will be ERROR. The next section Troubleshooting explains how
to correct them.
Note
The data file remains in the content repository after the process ends.
If there are no errors then the status of the process will be SUCCEEDED. The data in the interface
tables will be validated and the successful records will be imported into the Fusion Application tables.
If there are errors during the import then the status will be ERROR. The next section Troubleshooting
explains the way to handle them.
Note
For more detailed information on the process used for data prepared using the spreadsheet template, see
the Instructions and CSV Generation tab of the spreadsheet template.
Introduction
A web service for Oracle Fusion Financials is an artifact that provides a standardized way of integrating
other web-based applications with Fusion Applications over the web. It allows organizations to
communicate with Fusion Applications without the need of intimate knowledge of the applications.
FinancialUtilService web service provides external web service operations like file upload operations to
Oracle Universal Content Management, and service operations to submit ESS jobs from external
applications.
Field Value
Search String Financial Utilities Service
Type ADF Service
Service.
The table maps the web services operations which can be used to automate the integration flow steps
Import data into the The step can be automated by invoking Web Service submitEssJobRequest
persistent tables from FinancialUtilService to submit ESS the relevant import job.
the interface table
Monitor the status of The step can be automated by invoking the Web service
the load interface FinancialUtilService and its operation to monitor the status of getEssJobStatus
process or import the web services invoked
process
View the errors during In order to view the errors the end user can invoke the downloadESSJobExecutionD
the import and load downloadESSJobExecutionDetails operation of the etails
process and fix them FinancialUtilService web service.
The details for the web services mentioned above have been explained in the following section.
Operation: uploadFileToUcm
Method Name: uploadFileToUcm
Description: The method uploads a file to the UCM server based on the document specified.
Parameters:
Document Attributes:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:uploadFileToUcm
xmlns:ns1="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/types/">
<ns1:document xmlns:ns2="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/">
<ns2:Content>UEsDBBQAAAAIAEhrrkQSDhHq5BLBQYAAAAAAQABAD0AAAATPQEAAAA=</ns2:Content>
<ns2:FileName>TestUploadFileName.zip</ns2:FileName>
<ns2:ContentType>zip</ns2:ContentType>
<ns2:DocumentTitle>Sample File1</ns2:DocumentTitle>
<ns2:DocumentAuthor>finuser1</ns2:DocumentAuthor>
<ns2:DocumentSecurityGroup>FAFusionImportExport</ns2:DocumentSecurityGroup>
<ns2:DocumentAccount>fin$/generalLedger$/import$</ns2:DocumentAccount>
</ns1:document>
</ns1:uploadFileToUcm>
</soap:Body>
</soap:Envelope>
Operation: submitESSJobRequest
Method Name: submitESSJobRequest
Description: Submits an ESS job request for the specified job definition.
Parameters:
jobDefinitionName The ESS job definition name for the IN Yes java.lang.String
ESS job that must be submitted.
Parameters:
return Returns the current status of the ESS job. OUT java.lang.String
The complete list of job statuses and description
is in the Appendix4 ESS Job Execution status
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:getESSJobStatus xmlns:ns1="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/types/">
<ns1:requestId>35961</ns1:requestId>
</ns1:getESSJobStatus>
</soap:Body>
</soap:Envelope>
Operation: downloadESSJobExecutionDetails
Method Name: downloadESSJobExecutionDetails
Description: Downloads the ESS job output and the logs as a zip file.
Security Access Needed: Application User Access and special access needed for Attachment read.
Refer to the appdendix-1 to provide the user with this access.
Parameters:
Load Interface File for Import process ends in error and the Load File to interface child process ends in
an error or warning. All the rows that were loaded by the process are deleted and the whole batch of
records is rejected.
To correct errors:
Please refer to the Appendix 6 Error Handling for import jobs, for a list of import processes and their
corresponding ADFdi correction spreadsheets.
Journal import flow is used as an example to illustrate the inbound data integration flow with Oracle
Fusion Applications:
Pre-requisites:
Importing certificate into your local keystore. Refer to Appendix-5 for more details
Configure the sample web service tester. Refer to Appendix-5 for more details.
Identify the user name & password to invoke Import Journals process.
Verify user access to AttachmentsRead role in the UCM. Refer to Appendix-1 for
more details
Flow Steps:
Step1: Download the Journal import template ( JournalImportTemplate.xlsm) from OER and populate the
xlsm sheet with the journals from the external /third party system. Click on the Generate CSV File to
create the zip file.
Step2: Prepare the payload to upload the file to UCM by invoking the web service.
The details for payload input parameters for the operation uploadFileToUcm is as follows:
Use the Service Tester to invoke the web service with the payload. You will get the response back and it
will contain the document id if the web service is successful. In case of error, you will get the error code
back as response.
Step3: Prepare the payload to load data to GL_INTERFACE table from the file on the UCM server using
ESS Process Load Interface File for Import
The details for payload input parameters for the operation submitESSJobRequest are as follows:
Step4: Prepare the payload to verify the status of the request submitted in step-3.
The details for payload input parameters for the operation getEssJobStatus are as follows:
Use the service tester to invoke the web service with the payload. You will get the response back with the
status of the ESS request. You need to wait for the ESS request to complete successfully. If the data is
uploaded successfully then the execution status is returned as SUCCEEDED. If there is any error during
the processing then the execution status will be returned as ERROR.
Step5: Prepare the payload to import the journals from the interface table to GL_JE_HEADERS &
GL_JE_LINES. You will invoke the Journal import ESS process for this. While preparing the payload for
the ESS job, in order to map the ESS parameters to the payload parameters perform the following steps
The details for payload input parameters for the operation submitESSJobRequest are as follows:
Step6: Prepare the payload to verify the status of the request submitted in step-3.
The details for payload input parameters for the operation getEssJobStatus are as follows:
Use the service tester to invoke the web service with the payload. You will get the response back with the
status of the ESS request. You need to wait for the ESS request to complete successfully.
Step7: Prepare the payload to retrieve the log/out file associated with the request submitted in step-5.
The details for payload input parameters for the operation downloadESSJobExecutionDetails are as
follows:
Use the service tester to invoke the web service with the payload. You will get the response payload back
for this ESS request.
Response Payload:
You need to run base64 decode sample program to convert the value of Content from the response
payload to 212913.zip file.
Extract Receivables Transactions flow is used as an example to illustrate the outbound data integration
flow with Oracle Fusion Applications:
A batch of transactions may be needed to be extracted from the system to be sent to the customers. The
transactions will be extracted as a part of the output file of the Print Receivables Transaction ESS
process.
Pre-requisites:
Importing certificate into your local keystore. Refer to Appendix-5 for more details.
Configure the sample web service tester. Refer to Appendix-5 for more details.
Identify the user name & password to invoke Print Receivables Transaction process.
Verify user access to AttachmentsRead role in the UCM. Refer to Appendix-1 for
more details
Verify the end point url for the web service. Refer to Automation web service for more
details. https://<domainname>/finFunShared/FinancialUtilService?WSDL
Flow Steps:
Step1: Prepare the payload to invoke the ESS Process Print Receivables Transactions
Please refer to the step5 in the inbound flow above in order to map the ESS parameters and the values
for preparing the payload.
The details for payload input parameters for the operation submitESSJobRequest are as follows:
Use the service tester to invoke the web service with the payload. You will get the response back and it
will contain the request id of the ESS process.
Step2: Prepare the payload to verify the status of the request submitted in step-1.
The details for payload input parameters for the operation getEssJobStatus is as follows:
Use the service tester to invoke the web service with the payload. You will get the response back with the
status of the ESS request. You need wait for the ESS request to complete successfully.
Step3: Prepare the payload to retrieve the log/out file associated with the request submitted in step-1.
The details for payload input parameters for the operation downloadESSJobExecutionDetails is as
follows:
Use the service tester to invoke the web service with the payload. You will get the response back with the
log/out file associated of the ESS request.
ESS Job and output files are placed in the Attachments Security group under the Universal Content
Management Server. The user needs to have the access to the security group Attachments in order to
download the log/out file using the web service operation downloadESSJobExecutionDetails.
The steps to grant access to AttachmentsRead role to a given User are as follows:
Step 1: Login to the Oracle Fusion Applications home page. Click on the Navigator Setup and
Maintenance. Query for the Task Name: Manage Duties and click on go to task to Invoke login to the
Entitlements Server.
Step2.4: Click on the Application Role Mapping tab and verify if under the Application Name
IDCCS, AttachmentsRead is associated with the user. Click on the Create Icon to Map
Application Role to Attachment User to grant AttachmentsRead access to User incase user
doesnt have access to it.
Step 3: Verify that the Attachments security group is listed in the UCM Search page .
import java.io.ByteArrayOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileReader;
import java.io.IOException;
import java.io.InputStream;
import org.apache.commons.codec.binary.Base64;
int offset = 0;
int numRead = 0;
while (offset < bytes.length &&
(numRead = is.read(bytes, offset, bytes.length - offset)) >=
0) {
offset += numRead;
}
is.close();
26 return bytes; 2012 Oracle Corporation. All Rights Reserved.
}
}
Sample FileName: utilDecodeBase.java
import java.io.ByteArrayOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.FileReader;
import java.io.IOException;
import java.io.InputStream;
import org.apache.commons.codec.binary.Base64;
Data files must be transferred to these predefined accounts in content management server (UCM Server)
corresponding to the interface table or assets
Field Value
Search String FBDI
Type File Based Data Import
Product family <product family>
Select your respective import process from the results pane. E.g. Journal Import.
Click on the Overview tab on the lower pane. The UCM account will be mentioned there.
The following table lists the main set of execution statuses of the ESS job and their descriptions. These
would be returned by the getEssJobStatus operation.
1. Export the certificate from the browser to the file using the following steps ( for IE )
a. Open the SSL URL for any web service.
b. Click on the lock icon besides the URL.
c. Go to the connections tab and click on the certificate information link.
d. Go to Details Copy to File Next.
e. Change the encoding to Base-64 and click Next.
f. Provide the filename and click finish.
2. Export the certificate from the browser to the file using the following steps if IE is not available on
your machine.
a. Open the SSL URL for any web service.
b. Copy the content from the xml element dsig:X509Certificate.
c. Create a <File name>.cer file with begin and end certificate tags and add the
certificate content from the previous step.
3. Then at the command prompt, type the below command,
keytool -import -trustcacerts -file <filename> -alias <aliasname> -keystore default-keystore.jks
- storepass welcome1
FinancialUtilServiceSoapHttpPortClient.java
public class FinancialUtilServiceSoapHttpPortClient
{
@WebServiceRef
private static FinancialUtilService_Service financialUtilService_Service;
private static final AddressingVersion WS_ADDR_VER = AddressingVersion.W3C;
{ System.out.println("inside main");
f.invokeServiceWithUsernameTokenMessageProtectionPolicy();
f.invokeEssJobStatus(submittedJobId);
f.invokeDownloadESSJobExecDetails(submittedJobId);
System.out.println("inside invokeservice");
Try {
}catch(MalformedURLException e){
e.printStackTrace();
System.setProperty("javax.net.ssl.trustStore", trustStore);
System.setProperty("javax.net.ssl.trustStorePassword", trustStorePassword);
financialUtilService_Service = new FinancialUtilService_Service(wsdlDoc, servicename);
financialUtilService = financialUtilService_Service.getFinancialUtilServiceSoapHttpPort(securityFeature);
WSBindingProvider wsbp = (WSBindingProvider)financialUtilService;
Map<String, Object> requestContext = wsbp.getRequestContext();
requestContext.put(BindingProvider.USERNAME_PROPERTY, username);
requestContext.put(BindingProvider.PASSWORD_PROPERTY, password);
requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointNonSSLURL);
requestContext.put(ClientConstants.WSSEC_KEYSTORE_TYPE, "JKS");
requestContext.put(ClientConstants.WSSEC_KEYSTORE_LOCATION, jksFPath);
requestContext.put(ClientConstants.WSSEC_KEYSTORE_PASSWORD, jksPassword);
System.out.println("Finished invokeservice");
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:uploadFileToUcm xmlns:ns1="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/types/">
<ns1:document xmlns:ns2="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/">
<ns2:Content>UEsDBBQAAAAIAEhrrkQSDhHq5BLBQYAAAAAAQABAD0AAAATPQEAAAA=</ns2:Content>
<ns2:FileName>TestUploadFileName.zip</ns2:FileName>
<ns2:ContentType>zip</ns2:ContentType>
<ns2:DocumentTitle>Sample File1</ns2:DocumentTitle>
<ns2:DocumentAuthor>finuser1</ns2:DocumentAuthor>
<ns2:DocumentSecurityGroup>FAFusionImportExport</ns2:DocumentSecurityGroup>
<ns2:DocumentAccount>fin$/generalLedger$/import$</ns2:DocumentAccount>
</ns1:document>
</ns1:uploadFileToUcm>
</soap:Body>
</soap:Envelope>
System.out.println("inside invokeupload");
ObjectFactory objectFactory = new ObjectFactory();
DocumentDetails documentDet = new DocumentDetails();
documentDet.setContent(objectFactory.createDocumentDetailsContent(getByteArray(fileNameWithPath)));
documentDet.setContentType(objectFactory.createDocumentDetailsContentType(contentType));
documentDet.setDocumentAccount(objectFactory.createDocumentDetailsDocumentAccount(ucmAccountInfo));
documentDet.setDocumentAuthor(objectFactory.createDocumentDetailsDocumentAuthor(username));
documentDet.setDocumentSecurityGroup(objectFactory.createDocumentDetailsDocumentSecurityGroup(ucmSecurityGroup));doc
umentDet.setDocumentTitle(objectFactory.createDocumentDetailsDocumentTitle(title));
documentDet.setFileName(objectFactory.createDocumentDetailsFileName(fileName));
try {
try {
is = new FileInputStream(file);
while ((nRead = is.read(data, 0, data.length)) != -1) {
buffer.write(data, 0, nRead);
}
buffer.flush();
} catch (IOException e) {
System.out.println("In getByteArray:IO Exception");
e.printStackTrace();
}
return buffer.toByteArray();
}
If there are errors generated during the import process then there are two ways to address them
depending upon whether the ADFdi correction spreadsheets are available for that interface
table. If the ADFdi correction spreadsheet is available then the data in the interface table can be
corrected using the spreadsheet for error records and the import process can be re-submitted. If
no correction spreadsheet is available then the purge process needs to be run to delete all the
records from the interface table. The data needs to be corrected in the data file and re-uploaded
to UCM account. The entire process needs to be repeated.
The following table lists the error handling process in case of errors during the import process
for each interface table.
To use the XML templates and generate the import files, you must:
Note
In Oracle Cloud implementations, you must upload the ZIP file to the content management repository in
Oracle Cloud. In non-Cloud implementations, you can streamline the data integration process by installing
the content management document transfer utility so ODI performs the ZIP file transfer.
Oracle Data Integrator provides a solution for integrating complex data from a variety of sources into your
Oracle Fusion applications. The Oracle Fusion Middleware Installation Guide for Oracle Data Integrator
and the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator provide complete details
pertaining to the installation and set up of this product.
Install Oracle Data Integrator to use Oracle Fusion Applications XML integration templates.
See: Oracle Fusion Middleware Installation Guide for Oracle Data Integrator: Installing Oracle Data
Integrator
Set up Oracle Data Integrator to use Oracle Fusion Applications XML integration templates.
.
See: Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator: Setting up the Topology
Create the ODI models for both the source and target datastores. You determine the source models
that
you use based on the system or technology of the external data that you to import into your Oracle
Fusion application. You create the target models by importing the XML files, which you download from
Oracle Enterprise Repository.
See: Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator: Creating and Reverse-
Engineering a Model
Create and configure an integration project, which entails selecting the knowledge modules, creating
the
See: Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator: Creating an Integration
Project
To prepare your data in Oracle Data Integrator (ODI), download and save the XML templates:
Use XML templates in Oracle Data Integrator to prepare your external data for loading and importing.
Oracle Enterprise Repository for Oracle Fusion Applications includes three types of XML templates that
you import as target models in your Oracle Data Integrator repository.
Family-level
Product-level
Product
A family-level XML file is common to a group of product-level model folders and product models.
Consider the following points when you use family-level XML files:
The family-level XML file supports all of the Oracle Enterprise Repository assets in the family, for
example Oracle Fusion Financials or Human Capital Management.
You import the family-level XML file into your Oracle Data Integrator repository prior to importing the
other XML files.
You import one family-level XML file as a model folder for each family of products.
You import each family-level XML file as a top-level model folder.
You import the family-level XML file one time; it supports all subsumed product-level model folders.
You select Synonym mode Insert Update as the import type.
The product-level XML file supports all of the Oracle Enterprise Repository assets in the product line, for
A product XML file represents a specific Oracle Enterprise Repository interface table asset.
Consider the following points when you use product XML files:
You import one product XML file as a model for each interface table or set of tables, for example Mass
Additions.
You import the product XML file as a model into your Oracle Data Integrator repository after you import
the product-level XML file.
You import each product XML file as a model within the appropriate product-level model folder.
You import each product XML file one time.
You select Synonym mode Insert Update as the import type.
The model is based on File technology.
After you import the product model, you connect the model to the correct logical schema.
Creating Integration Projects That Generate Data Files for Import: Points to Consider
When you use Oracle Data Integrator (ODI) to generate import data files from external data sources, you
must configure an integration project. Integration projects are collections of ODI components that provide
the procedural details of an integration from a source to a target. In this scenario, the source is your
external data and the target is the import data file that you load and import into your Oracle Fusion
Applications.
Knowledge modules
Integration interfaces
Knowledge Modules
Knowledge modules contain the information that Oracle Data Integrator requires to perform a specific set
of tasks against a specific technology or set of technologies. Examples include Check knowledge
modules, which ensure that constraints on the sources and targets are not violated and integration
knowledge modules, which load data to target tables.
The knowledge modules that you import into your integration project depend on the source and target
technologies, as well as other integration specific rules and processes.
40 2012 Oracle Corporation. All Rights Reserved.
Multiple types of knowledge modules exist in ODI.
Use the SQL File to Append module to create the import data file.
Integration Interfaces
Integration interfaces comprise sets of rules that define the loading of data from one or more sources to
the target.