Documente Academic
Documente Profesional
Documente Cultură
Table of Contents
OVERVIEW .......................................................................................................................................................... 4
INTEGRATION TEMPLATES .................................................................................................................................. 5
FINDING TEMPLATES AND CONTROL FILES ........................................................................................................................... 5
DOWNLOADING TEMPLATES ............................................................................................................................................. 5
PREPARING DATA USING THE XLS TEMPLATE ....................................................................................................................... 5
TEMPLATE STRUCTURE .................................................................................................................................................... 6
TEMPLATE REQUIREMENTS .............................................................................................................................................. 6
DATA INTEGRATION USING MANUAL FLOW ........................................................................................................ 7
FILE FOR IMPORT AND EXPORT .......................................................................................................................................... 7
USING CONTENT MANAGEMENT ....................................................................................................................................... 7
MANAGING FILES FOR IMPORT AND EXPORT ........................................................................................................................ 7
USING THE FILE IMPORT AND EXPORT PAGE ........................................................................................................................ 8
INTERACTING WITH CONTENT MANAGEMENT ...................................................................................................................... 8
SECURITY ...................................................................................................................................................................... 8
SEARCHING RECORDS ...................................................................................................................................................... 9
ACCESSING CONTENT IN A NEW ACCOUNT .......................................................................................................................... 9
ACCOUNT NAMES .......................................................................................................................................................... 9
DELETING FILES.............................................................................................................................................................. 9
UPLOADING FOR IMPORT ................................................................................................................................................. 9
DOWNLOADING FOR EXPORT ............................................................................................................................................ 9
FILE SIZE ..................................................................................................................................................................... 10
LOAD INTERFACE FILE FOR IMPORT PROCESS ..................................................................................................................... 10
IMPORTING DATA INTO APPLICATION TABLES .................................................................................................................... 10
LOADING DATA INTO INTERFACE TABLES ........................................................................................................................... 10
FINDING AND SUBMITTING THE IMPORT PROCESS ............................................................................................................... 11
FLOW AUTOMATION USING WEB SERVICE ........................................................................................................ 12
ACCESSING AUTOMATION SERVICE DETAILS ...................................................................................................................... 12
CONSTRUCTING END POINT URL .................................................................................................................................... 12
WEB SERVICE OPERATIONS ............................................................................................................................................ 13
OPERATION: UPLOADFILETOUCM.................................................................................................................................... 13
OPERATION: SUBMITESSJOBREQUEST.............................................................................................................................. 14
OPERATION: GETESSJOBSTATUS ...................................................................................................................................... 15
OPERATION: DOWNLOADESSJOBEXECUTIONDETAILS .......................................................................................................... 15
TROUBLESHOOTING .......................................................................................................................................... 16
CORRECTING DATA UPLOAD ERRORS ............................................................................................................................... 16
CORRECTING IMPORT PROCESS ERRORS ............................................................................................................................ 16
INBOUND: AN END TO END AUTOMATION FLOW USE CASE ............................................................................... 17
PREREQUISITES ............................................................................................................................................................ 17
FLOW STEPS ................................................................................................................................................................ 17
Overview
You can use external data integration services to load data into Oracle Fusion Applications from external sources, such as legacy
systems and third-party applications.
The integration process includes the following components:
Templates to structure, format, and generate the data file according to the requirements of the target application tables.
File-based load process to load the data file into the interface tables.
Application-specific data import processes to transfer data from interface tables to the application tables in your Oracle
Fusion Applications.
The following flow diagram outlines the steps involved in the process:
Yes
Errors?
No
Yes
Errors?
No
Integration Templates
Oracle Enterprise Repository includes integration templates to help you prepare external data for loading and importing. Each
template includes table-specific instructions, guidelines, formatted spreadsheets, and best practices for preparing the data file for
upload. Use the templates to ensure that your data conforms to the structure and format of the target application tables.
Preparing external data using templates involve the following tasks:
Downloading templates
2.
Value
FBDI
File Based Data Import
<product family>
3.
Click Search.
4.
Select your respective import process from the results pane. For example, Journal Import.
Downloading Templates
To download the templates:
1.
Use the search criteria to locate and select the import process.
2.
Click the Details tab on the lower pane to view the list of files.
Control files describe the logical flow of the data load process.
XLSM templates include the worksheets and macros for structuring, formatting, and generating your data file.
Note
You can use XML templates to import data into Oracle Data Integrator. For more information on using XML
templates to generate data files, see Appendix 7.
3.
Click the template link to download the file. For example, click JournalImportTemplate.xlsm in the Journal Import
process.
Open the XLS template. The first worksheet in each template provides instructions for using the template.
Important
If you do not follow the instructions, you will get data load errors and data import failures.
2.
3.
The macro generates a comma-separated values (CSV) file and compresses the file into a ZIP file. You must transfer the ZIP file
to the content management server.
Template Structure
The integration templates include the following characteristics:
A worksheet column with a header in the first row represents each interface table field.
Each column header contains bubble text or comments that include details about the column, such as the expected
data type, length, and in some cases, other instruction text.
Columns are formatted, where applicable, to match the target field data type to eliminate data entry errors.
The worksheet columns are in the order that the control file processes the data file.
Template Requirements
To minimize the risks of an unsuccessful data load, ensure the following:
Important
Deleting or reordering columns causes the load process to fail and results in an unsuccessful data load.
External data must conform to the data type accepted by the control file and process for the associated database
column.
Amount column values cannot have separators other than a period (.) as the decimal separator.
Column values that require whole numbers include data validation to allow whole numbers only.
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 more information on using XML templates to generate data files, see Appendix 7.
File Import and Export page in Oracle Fusion Applications: Manual flow
For more information on the Oracle Fusion Financials Utility web service, see the Flow Automation Web Service section.
Resource
Oracle WebCenter Content User's Guide for Content Server
Oracle WebCenter Content System Administrator's Guide for
Content Server
Files for Import and Export section
Oracle WebCenter Content System Administrator's Guide for
Content Server
Oracle Enterprise Repository
Oracle Enterprise Repository
Oracle Fusion Applications Common Security Reference Manual
2.
Security
Searching records
Account names
Deleting files
File size
Security
Use the File Import and Export Management duty role to access the File Import and Export page. This duty role is included in the
predefined role hierarchy for integration specialist roles and product family administrator roles.
The files in Oracle WebCenter Content Management are associated with an account. The users who have the access privileges
to a specific account can work with content items that belong to that account.
Note
You can only upload and download files to and from the content management that are associated with the accounts that you
are entitled to access.
Oracle WebCenter Content Management server does not support trailing slashes (/). Account names are appended with a dollar
sign ($) 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 considered 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 Management contains metadata used to access the file. When you run a scheduled
process to completion on a file, the record for the file includes a process ID.
Account Names
If you create custom accounts for importing or exporting data, use the following naming conventions for the account:
Do not include a slash (/) at the beginning or use a dollar sign ($) at the end, to avoid partial string matching.
Use a dollar sign and slash ($/) as a separator in the hierarchical structure.
The File Import and Export page transforms account names by removing the dollar signs ($). 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 the
dollar signs ($) to one that includes them. For example, fin/journal/import becomes fin$/journal$/import$ in Oracle WebCenter
Content Management.
You must transfer files to these predefined accounts in content management that correspond to the interface table or assets. For
a list of the target accounts in each interface table, see Appendix 3.
You can create subaccounts to 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 in the File Import and Export page. To delete multiple files simultaneously from the content
repository, use the standard service page in Oracle WebCenter Content Management.
File Size
Upload and download does not apply for the following:
1.
Data compression
2.
The UPLOAD_MAX_DISK_SPACE parameter in the web.xml file determines the maximum allowable file size in the content
management. The default maximum size is 10240000 (10MB).
2.
Description
Select the target import process.
Choose the data file from the choice list.
2.
3.
4.
Search and select the Load Interface File for Import job.
5.
ii.
6.
If the process is successful, the status is SUCCEEDED and the process populates the interface tables. If the process is not
successful, the status is ERROR. For more information on correcting load errors, see the Troubleshooting section.
Note
The data file remains in the content repository after the process ends.
2.
3.
4.
Search and select the import process for the target application tables.
5.
On the Process Details page, select the process that corresponds to the data that you are importing. For example,
Journal Import.
6.
If you have prepared your data using the spreadsheet template, select the process shown in the Overview section of
the spreadsheet.
7.
If the process is successful, the status is SUCCEEDED. The data in the interface tables is validated and the successful records
are imported into the Oracle Fusion application tables. If the process in not successful, the status is ERROR. For more
information on correcting import errors, see the Troubleshooting section.
Note
For more information on the process used for data prepared using the spreadsheet template, see the Instructions and
CSV Generation tab of the spreadsheet template.
2.
3.
Value
Financial Utilities Service
ADF Service
Select Financial Utility Service from the results section. The bottom page tabs include the following:
2.
Then append the static context root that we extracted from OER,
"/finFunShared/FinancialUtilService".
https://<domainname>/finFunShared/FinancialUtilService is the WSDL URL for Financial
Utility Service.
uploadFileToUcm
submitEssJobRequest
getEssJobStatus
downloadESSJobExecutionDetails
The following table describes the web services operations used to automate the integration flow steps:
Step
Automation
Financial Service
Operation
uploadFileToUcm
submitEssJobRequest
getEssJobStatus
downloadESSJobExecution
Details
submitEssJobRequest
Operation: uploadFileToUcm
The uploadFileToUcm method uploads a file to the UCM server based on the document specified. This operation requires
application user access.
The following table lists the parameters for this operation:
Parameter
Name
Document
Return
Description
List of elements, each containing the details of the file to be
uploaded. The details include the file content, file name, content
type, file title, author, security group, and account.
Document Attributes:
Parameter
(In/Out)
IN
Mandatory
Type
Yes
java.lang.Strin
g
OUT
No
java.lang.Strin
g
Operation: submitESSJobRequest
The submitESSJobRequest method submits an ESS job request for the specified job definition. This operation requires
application user access.
Description
Mandatory
Type
Parameter
(In/Out)
IN
Yes
java.lang.String
jobDefinitionName
IN
Yes
java.lang.String
paramList
IN
No
java.util.List<jav
a.lang.String>
return
OUT
java.lang.Long
Operation: getEssJobStatus
The getEssJobStatus method obtains the execution status of the submitted ESS job. This operation requires application user
access.
The following table lists the parameters for this operation:
Parameter
Name
requestID
Description
return
Parameter
(In/Out)
IN
Mandatory
Type
Yes
java.lang.Long
OUT
java.lang.String
Operation: downloadESSJobExecutionDetails
The downloadESSJobExecutionDetails method downloads the ESS job output and the logs as a zip file. This operation requires
application user access and access to the AttachmentsRead role.
For more information on assigning a user with this access, see Appendix 1.
The following table lists the parameters for this operation:
Parameter
Name
requestID
fileType
return
Description
The request ID of the ESS job.
The file type used to determine the execution details to
download. Specify the file type as log/out to download the log
file and output file respectively.
A list of documents is returned.
Parameter
(In/Out)
IN
IN
OUT
Mandatory
Type
Yes
No
java.lang.String
java.lang.String
List<DocumentD
etailsVORowImp
l>
Troubleshooting
Correcting Data Upload Errors
If the load of the data file fails, the Load Interface File for Import process ends and shows an error. The Load File to Interface
child process ends as an error or warning. All rows that were loaded by the process are deleted and the entire batch of records is
rejected.
To correct errors::
1.
2.
3.
Generate the ZIP file containing the .csv files using the template.
4.
Upload the file to the UCM server and resubmit the Load Interface File for Import process.
5.
Repeat these steps until the process successfully loads all the data.
2.
For a list of import processes and their corresponding ADFdi correction spreadsheets, see Appendix 6.
Prerequisites
Import certificate into your local keystore. For more information, see Appendix 5.
Configure the sample web service tester. For more information, see Appendix 5.
Identify the user name and password to call the Import Journals process.
Verify the user access to the AttachmentsRead role in the UCM. For more information, see Appendix 1.
Verify the end point URL for the web service. For more information, see the Automation web service at
https://<domainname>/finFunShared/FinancialUtilService?WSDL.
Flow Steps
1.
Download the Journal Import template, JournalImportTemplate.xlsm, from OER and populate the XLSM sheet with the
journals from the external third-party system. Click the Generate CSV File button to create the ZIP file.
2.
Prepare the payload to upload the file to UCM by invoking the web service.
The payload input parameters for the uploadFileToUcm operation are as follows:
Payload Parameter Name
Content
Value
<Output from the sample
utilEncodeBase.java program>
ContentType
zip
DocumentTitle
DocumentAuthor
DocumentSecurityGroup
DocumentAccount
fin$/generalLedger$/import$
Comments
Run the base64 encoding sample
program to provide the Content value.
This sample program creates the zip file
as input and provides the content output.
Generate CSV File creates a ZIP file.
Other content types include .txt, and .csv.
Use the service tester to call the web service with the payload. Check the response for the document ID. If there is an
error, check the error code in the response.
3.
Prepare the payload to load data to the GL_INTERFACE table from the file on the UCM server, using ESS Process
Load Interface File for Import.
The payload input parameters for the submitESSJobRequest operation are as follows:
Payload Parameter Name
jobPackageName
jobDefinitionName
paramList
Value
oracle/apps/ess/financials/commonMod
ules
/shared/common/interfaceLoader
InterfaceLoaderController
15
paramList
<372750>
Comments
paramList
paramList
N
N
Use the service tester to call the web service with the payload. Check the response for the request ID of the ESS
process.
4.
Value
<372750>
Comments
The request identifier for the ESS process.
Use the service tester to call the web service with the payload. Check the response for the status of the ESS request. If
the data is uploaded successfully then the execution status is SUCCEEDED. If there is an error, the execution status is
ERROR.
5.
Prepare the payload to import the journals from the interface table to GL_JE_HEADERS and GL_JE_LINES, using the
Journal import ESS process.
To map the ESS parameters to the payload parameters:
i.
ii.
iii.
iv.
v.
vi.
In the Details region, expand the Parameters node. Review the ordered list of arguments and their values,
and find the arguments IDs that are passed internally.
The payload input parameters for the submitESSJobRequest operation are as follows:
Payload Parameter Name
jobPackageName
jobDefinitionName
paramList
paramList
paramList
paramList
paramList
Value
/oracle/apps/ess/financials/generalLedge
r/programs/common
JournalImportLauncher
1061
Expenses
1
ALL
N
paramList
paramList
N
N
Comments
Use the service tester to call the web service with the payload. You can see the response back and contains the
request ID of the ESS process.
6.
Value
<372750>
Comments
The request identifier for the ESS process.
Use the service tester to call the web service with the payload. Check the response for the status of the ESS request.
7.
Prepare the payload to retrieve the log/out file associated with the request.
The payload input parameters for the downloadESSJobExecutionDetails operation are as follows:
Payload Parameter Name
requestID
Value
<372750>
Comments
The request identifier for the ESS process.
Use the service tester to call the web service with the payload. Check the response payload for this ESS request.
Response Payload
Run the base64 decode sample program to convert the Content value from the response payload to 212913.zip file.
<env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="Body-M3Y1Wo0PrQ91vGVfDENtkQ22">
<ns0:downloadESSJobExecutionDetailsResponse
xmlns:ns0="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/types/">
<ns2:result xmlns:ns0="http://xmlns.oracle.com/adf/svc/types/"
xmlns:ns1="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/"
xmlns:ns2="http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/types/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:DocumentDetails">
<ns1:Content>UEsDBBQACAAIAPK68UQAAAAAAAAAAAAAAAAKAAAAMjEyOTEzLmxvZz3PwYrDIBCA4btPMQ8gOJoa
6N5CY6CnDd28gCSTRTCa6gS6b99Syl6/ww8/PWg+mL5+pu42iZ4qh+Q55ARDiAR9KDRzLn+gasys
aKtnja3y+779FtWN4/Q9qpAq+zSTolpVWRdltDlro/LB4kb341WFaw9vbf7lkhPTgz8sYfWxkoR0
xChhcK3u0Wrd2guesHF4aixaHBA761onQRsJBo2Yik91pfLqbXskpkXQZ8qlRTwBUEsHCNkrs2Wz
AAAA4QAAAFBLAQIUABQACAAIAPK68UTZK7NlswAAAOEAAAAKAAAAAAAAAAAAAAAAAAAAAAAyMTI5
MTMubG9nUEsFBgAAAAABAAEAOAAAAOsAAAAAAA==</ns1:Content>
<ns1:FileName xsi:nil="true"/>
<ns1:ContentType>zip</ns1:ContentType>
<ns1:DocumentTitle>ESS_L_212913</ns1:DocumentTitle>
<ns1:DocumentAuthor>FIN_USER1</ns1:DocumentAuthor>
<ns1:DocumentSecurityGroup>Attachments</ns1:DocumentSecurityGroup>
<ns1:DocumentAccount xsi:nil="true"/>
<ns1:DocumentName>212913.zip</ns1:DocumentName>
</ns2:result>
</ns0:downloadESSJobExecutionDetailsResponse>
</env:Body>
Prerequisites
Import the certificate into your local keystore. For more information, see Appendix 5.
Configure the sample web service tester. For more information, see Appendix 5.
Identify the user name and password to call the Print Receivables Transaction process.
Verify user access to the AttachmentsRead role in the UCM. For more information, see Appendix 1.
Verify the end point URL for the web service. For more information, see the Automation web service at
https://<domainname>/finFunShared/FinancialUtilService?WSDL.
Flow Steps
1.
Prepare the payload to call the Print Receivables Transactions ESS process.
To map the ESS parameters and the values for preparing the payload, see Step 5 in the inbound flow example.
The payload input parameters for the submitESSJobRequest operation are as follows:
Payload Parameter Name
jobPackageName
jobDefinitionName
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
paramList
Value
oracle/apps/ess/financials/receivables/
transactions/shared
PrintReceivablesTransaction
204
NEW
TRX_NUMBER
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
#NULL
Default Invoice Template
Default Credit Memo Template
Default Debit Memo Template
Default Chargeback Template
No
Comments
Use the service tester to call the web service with the payload. Check the response for the request ID of the ESS
process.
2.
Value
<372750>
Comments
The request identifier for the ESS process.
Use the service tester to call the web service with the payload. Check the response for the status of the ESS request.
3.
Prepare the payload to retrieve the log file or the out file associated with the request.
The payload input parameters for the downloadESSJobExecutionDetails operation are as follows:
Payload Parameter Name
requestID
Value
<372750>
Comments
The request identifier for the ESS process.
Use the service tester to call the web service with the payload. Check the response for the log/out file associated with
the ESS request.
2.
3.
Figure 7. Use the Manage Duties task to navigate to the Entitlements Server page.
4.
ii.
Enter the user name in the query panel and click Search.
iii.
Select the user name and click Open User in the results region. For example, FINUSER1.
5.
Click the External Roles Assignments tab and verify that the user is granted the Employee role.
Note
You cannot proceed to the next step until the user is granted the Employee role.
6.
7.
8.
Click the Application Role Mapping tab and verify that AttachmentsRead is associated with the user for the
application name IDCCS. If this association does not exist, click the Create icon to grant AttachmentsRead access to
the user.
9.
Verify that the Attachments security group is listed in the UCM Search page.
Figure 10. Search page for UCM to identify whether user has access to Attachments security group.
Appendix 2: Sample Code for preparing data file for Inbound/Outbound Flow
The following example illustrates sample code for preparing a data file for the inbound flow.
Sample File Name: utilEncodeBase.java
import
import
import
import
import
import
import
java.io.ByteArrayOutputStream;
java.io.File;
java.io.FileInputStream;
java.io.FileReader;
java.io.IOException;
java.io.InputStream;
org.apache.commons.codec.binary.Base64;
}
}
The following example illustrates sample code for preparing a data file for the outbound flow.
Sample FileName: utilDecodeBase.java
import
import
import
import
import
import
import
java.io.ByteArrayOutputStream;
java.io.File;
java.io.FileInputStream;
java.io.FileOutputStream;
java.io.FileReader;
java.io.IOException;
java.io.InputStream;
import org.apache.commons.codec.binary.Base64;
public class utilDecodeBase {
public utilDecodeBase() {
super();
}
2.
Value
FBDI
File Based Data Import
<product family>
3.
Click Search.
4.
Select your respective import process from the results pane. For example, Journal Import.
5.
Click the Overview tab on the lower pane to view the UCM account details.
The following table identifies the predefined accounts for the interface table or assets.
Interface Table
Payables Standard Invoice Import
Supplier Bank Account Import
Autoinvoice Import
Receivables Standard Receipt Import
Customer Import
China Value added Tax Invoice Import
BAI2 Format Bank Statements Import
EDIFACT FINSTA Format Bank Statements Import
ISO200022 CAMT053 Format Bank Statements Import
SWIFT MT940 Format Bank Statements Import
Fixed Asset Mass Additions Import
Fixed Asset Mass Adjustments Import
Fixed Asset Mass Retirements Import
Fixed Asset Mass Transfers Import
Fixed Asset Units of Production Import
Intercompany Transaction Import
Journal Import
Chart Of Accounts Segment Values and Hierarchies Import
General Ledger Budget Balance Import
Tax Configuration Content Import
Import Blanket Purchase Agreements
Import Contract Purchase Agreements
Import Purchase Orders
Import Requisitions
Import Suppliers
Import Supplier Sites
Import Supplier Site Contacts
Import Supplier Site Assignments
Project Enterprise Resource Import
Project Unprocessed Expenditure Item Import
Cycle Count Import
Inventory Reservation Import
Inventory Transaction Import
Item Import
Receiving Receipt Import
Shipment Request Import
Predefined Account
fin/payables/import
fin/receivables/import
fin/cashManagement/import
fin/assets/import
fin/intercompany/import
fin/generalLedger/import
fin/budgetBalance/import
fin/tax/import
prc/blanketPurchaseAgreement/import
prc/contractPurchaseAgreement/import
prc/purchaseOrder/import
prc/requisition/import
prc/supplier/import
prj/projectManagement/import
prj/projectCosting/import
scm/cycleCount/import
scm/inventoryReservation/import
scm/inventoryTransaction/import
scm/item/import
scm/receivingReceipt/import
scm/shipmentRequest/import
Description
User Action
COMPLETED
SUCCEEDED
ERROR
ERROR_AUTO_RETRY
WARNING
RUNNING
Request is processed.
CANCELED
BLOCKED
2.
Create a web service client proxy and add the OWSM policy.
3.
2.
Export the certificate from the browser to the file, using the following steps:
i.
ii.
iii.
iv.
Select Details.
v.
vi.
Click Next.
vii.
viii.
Export the certificate from the browser to the file, using the following steps if Internet Explorer is not available on your
machine.
i.
ii.
iii.
Create a <File name>.cer file with begin and end certificate tags and add the certificate content from the
previous step.
3.
2.
3.
4.
Select the Copy WSDL Info Project check box. Specify the default mapping options.
5.
6.
7.
Click Finish.
8.
Once the proxy client code is generated, add the following variables:
jksFPath: The file location that has the certificate to add to the keystore. For example,
D:\fintuilwdestapp\Project5\client.jks
trustStore: The path where the certificates are stored, used during the java installation by default.
Password: Password for the user to sign in to the service. For example, Welcome1.
Note
An example of a message protection policy is policy:oracle/wss_username_token_over_ssl_client.
9.
2.
2.
3.
FinancialUtilServiceSoapHttpPortClient.java
public class FinancialUtilServiceSoapHttpPortClient
{
@WebServiceRef
private static FinancialUtilService_Service financialUtilService_Service;
private static final AddressingVersion WS_ADDR_VER = AddressingVersion.W3C;
// Add the additional variables
private final String jksFPath = "D:\\fintuilwdestapp\\Project5\\client.jks";
private final String jksPassword = "Welcome1";
private final String trustStore = "C:\\ProgramFiles\\Java\\jdk1.7.0_51\\jre\\lib\\security\\cacerts";
private final String trustStorePassword = "";
private final String username = "finuser1";
private final String password = "Welcome1";
private String endpointNonSSLURL = "https://efops-rel9st1-cdrm1-externalfin.us.oracle.com/finFunShared/FinancialUtilService";
private static final QName servicename = new
QName("http://xmlns.oracle.com/apps/financials/commonModules/shared/financialUtilService/","FinancialUt
ilService");
private SecurityPolicyFeature[] securityFeature = new SecurityPolicyFeature[] { new
SecurityPolicyFeature("policy:oracle/wss_username_token_over_ssl_client_policy") };
private FinancialUtilService financialUtilService;
// End add the additional variables
public static void main(String [] args)
{ System.out.println("inside main");
FinancialUtilServiceSoapHttpPortClient f = new FinancialUtilServiceSoapHttpPortClient();
f.invokeServiceWithUsernameTokenMessageProtectionPolicy();
String retStatus = f.invokeUpload();
//long submittedJobId = f.invokeSubmitJob(retStatus);
//f.invokeEssJobStatus(submittedJobId);
//f.invokeDownloadESSJobExecDetails(submittedJobId);
}
4.
<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>
The following are the list of JDeveloper 11g jars to added to the deployment profile:
weblogic.jar : $MW_HOME/wlserver_10.3/server/lib/weblogic.jar
jrf.jar: $MW_HOME/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar
Click Deployment.
Click New.
Select the Include Manifest File (META-INF/MANIFEST.MF) option and specify the value for Main Class.
For example,
oracle.apps.finacial.testUtil.proxy.client.FinancialUtilServiceSoapHttpPortClient
If an ADFdi correction spreadsheet is available, use the spreadsheet to correct the data in the interface table and
resubmit the import process.
If no correction spreadsheet is available, use the purge process to delete all the records from the interface table.
Correct the data in the data file and reupload the file to the UCM account.
Correction Spreadsheet
CorrectImportErrors.xlsx
Import AutoInvoice
ManageInvoiceErrors
Spreadsheet.xlsx
ManageLockboxErrors.xlsx
PrepareSourceLines.xlsx
Journal Import
JournalCorrections.xlsx
UpdateMassFinancialTrans
action.xlsm
UpdateMassRetirements.xls
m
UpdateMassTransfers.xlsm
Steps
In the Invoices work area, navigate to Correct Import Errors in the
Tasks region.
In the Billing work area, navigate to the Review AutoInvoice Errors
table.
Click Number of Errors.
Select the Manage AutoInvoice Lines spreadsheet.
In the Receivables work area, navigate to Receivable Balances.
Note
For Oracle Cloud implementations, you must upload the ZIP file to the content management repository in Oracle Cloud. For
non-Cloud implementations, you can streamline the data integration process by installing the content management
document transfer utility, which uses ODI to transfer the ZIP file.
2.
2.
Import the product-level template as a model folder within the family-level model folder.
3.
Import the product template as a model within the product-level model folder.
4.
5.
6.
7.
Integration projects
ODIZip tool
Execute the package. The package generates the CSV file and compresses it into a ZIP file.
Family level
Product level
Product
The family-level XML file supports all of the Oracle Enterprise Repository assets in the family, for example, Oracle
Fusion Financials or Oracle Fusion Human Capital Management.
Import the family-level XML file into your Oracle Data Integrator repository prior to importing other XML files.
Import one family-level XML file as a model folder for each family of products.
Import the family-level XML file one time; it supports all subsumed product-level model folders.
The product-level XML file supports all of the Oracle Enterprise Repository assets in the product line, for example,
Fixed Assets, General Ledger, or Payables.
Import one product-level XML file as a model folder for each line of products.
Import the product-level XML file as a model folder into your Oracle Data Integrator repository.
Import the family-level XML file before you import product XML files.
Import each product-level XML file as a midlevel model folder within the appropriate family-level model folder.
Import the product-level XML file one time; it supports all subsumed product models.
Import one product XML file as a model for each interface table or set of tables, for example, MassAdditions.
Import the product XML file as a model into your Oracle Data Integrator repository after you import the product-level
XML file.
Import each product XML file as a model within the appropriate product-level model folder.
After you import the product model, connect the model to the correct logical schema.
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. For example, check knowledge modules ensure that constraints on the sources and
targets are not violated, and integration knowledge modules load data to the target tables.
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. 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 contain the sets of rules that define the loading of data from one or more sources to the target.
For the integration interfaces:
The target is the interface table datastore, which is the CSV file from your interface table model.
After you set up the source and target datastores, you map the target fields to the source fields, or map source field values to
target fields or constants.
Worldwide Inquiries
Phone: +1.650.506.7000
Fax: +1.650.506.7200
CONNECT WITH US
blogs.oracle.com/oracle
Copyright 2014, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
facebook.com/oracle
twitter.com/oracle
oracle.com
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 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
means, electronic or mechanical, for any purpose, without our prior written permission.