Oracle® Hyperion Financial Data Quality Management, Fusion Edition Adapter for Oracle E-Business Suite Financials
Release FIN-C
Readme
E-Business Suite Compatibility and Patches
The FDM Adapter for E-Business Suite Financials is a source adapter that enables FDM users to import data from E-Business Suite Financials into FDM. The adapter also allows the user to drill through from FDM to E-Business Suite Financials to view the source data. The adapter pulls data from two different tables; GL_BALANCES and GL_CODE_COMBINATIONS.
Date Created: 02/26/2009
Adapter Versions: EBS-FIN-C.xml
oraEBSFIN11i_C.dll
Compatibility: See the FDM 11.1.1.2 Readme for FDM and E-Business Suite Financials compatibility information.
The FDM drill through feature supports Oracle E-Business Suite versions 11.5, 12.0.6, and 12.1.1. The following patches are required for Oracle E-Business Suite version 11.5:
· 4396821 and 8307232 (replaces patch 6902648)
Pre-requisite patches for patch 4396821:
· 3262919 - Patch 11i.FWK.H
· 2032040 - WORKFLOW 2.6 FOR APPLICATIONS 11i
· 3180816 - Patch 11i.AD.I
· 2917019 - New Profile Hierarchies: Security, Server and Organization
· 3313291 - AOL JAVA ROLLUP PATCH J
The following patch is required for Oracle E-Business Suite version 12.0.6:
· 8345468:R12.GL.A
Patches are available on the Oracle Support site (metalink.oracle.com)
> To add the FDM adapter for E-Business Suite Financials to an FDM application:
1. From FDM Workbench, open an FDM application.
2. Select the Adapters tab.
3. Select File > Import.
The Open Metadata Import File dialog box is displayed.
4. Browse to find the file named EBS-FIN-C.xml and click Open.
5. Click OK.
The FDM adapter for E-Business Suite Financials is displayed in the list of imported source adapters.
6. Select File > Register Adapter.
The Register Adapter dialog box is displayed.
7. Browse to find the file named oraEBSFIN11i_C.dll and click Open.
8. Click OK.
Important: You must have an Oracle OLE-DB provider installed on the FDM server to enable a connection to the E-Business Suite database.
> To configure the adapter:
1. In FDM Workbench, from the Adapters tab, select the adapter.
2. Right-click and select Options.
The Adapter Options dialog box is displayed. The Options menu enables you to select any of the options and change the option settings.
3. Set the adapter options per the guidelines in the following table:
|
Option Name |
Information Required |
Required for… |
|
Network Alias |
Name or alias of the E-Business Suite Financials database server from which to pull data. |
Pulling data |
|
Schema/Password |
E-Business Suite Financials database schema name and password from which to pull data. |
Pulling data |
|
Set of Books/Ledger ID |
E-Business Suite Financials Set of Books ID from which to pull data. |
Pulling data |
|
Budget Version ID |
E-Business Suite Financials Budget Version ID for balance type of Budget |
Pulling data |
|
Encumbrance Type ID |
E-Business Suite Financials Encumbrance Type ID for balance type Encumbrance. |
Pulling data |
|
File Delimiter |
The delimiter used to create the file generated from the data pull from E-Business Suite Financials. |
Pulling data |
|
Enable Drillback |
Check to enable drill through from FDM to E-Business Suite Financials. |
Drilling through to E-Business Suite Financials |
|
Response ID |
Responsibility ID of the E-Business Suite user. |
Drilling through to E-Business Suite Financials |
|
Function ID |
Function ID of the E-Business Suite Financials user. |
Drilling through to E-Business Suite Financials |
|
Responsibility Application ID |
Responsibility Application ID of the E-Business Suite user. |
Drilling through to E-Business Suite Financials |
|
EBS Web Server Path |
URL of the E-Business Suite Financials Web Server. Enter <ebs server name>:<ebs port number>/OA_HTML/RF.jsp. |
Drilling through to E-Business Suite Financials |
|
EBS Landing Page |
URL for the E-Business Suite Financials landing page. Note: This field is concatenated with the E-Business Suite Web Server Path field. Leave blank. |
Drilling through to E-Business Suite Financials |
|
Use SSL |
Check On/Off box if the E-Business Suite Web server is using SSL. |
Drilling through to E-Business Suite Financials |
|
Prompt for File |
Check to enable file prompt message during FDM Import process. |
Optional |
Important: Due to the nature of the OracleDB structure, values stored in the database are case sensitive. Be sure the data in all Integration Options fields are accurate. Otherwise, they will not return results.
Using the E-Business Suite Financials adapter involves the following steps:
· Map FDM Periods and Categories to E-Business Financials.
· Generate the data from E-Business Suite Financials.
· Set up an import format in FDM to enable FDM to import the data file generated by the adapter.
· Assign the Import Formats to a location.
> Step 1: Map FDM Periods and Categories to EBS.
Note: Adapter options must be set per the guidelines outlined in the previous section of this document.
a) In the FDM Web client, select Metadata > Control Tables.
The Control Tables screen is displayed.
b) From Adapter, select EBS-FIN-C.
c) Map the FDM Periods to the corresponding EBS source periods:
- Use the Target Per (M) column in the control table to map the EBS Period Name.
- Use the Target Per (D) column in the control table to map the EBS Period Type.
- Use the Year Target column in the control table to map the EBS Period Year.
d) Map the FDM Categories to the corresponding EBS Type flags.
Use the Target Category column in the control table to browse for the EBS Balance Type flag.
> Step 2: Generate the data from E-Business Suite Financials:
a) In FDM, create an Import Format group and set the type to Adapter.
See the FDM Administrator’s Guide for information regarding import formats.
b) Select Workflow > Import.
The Import screen is displayed.
c) Click Import to generate the source file from E-Business Suite Financials.
You will use this file to create the import format in the next procedure.
> Step 3: Set up an import format in FDM to enable FDM to import the data file generated by the adapter:
a) Ensure that the required fields (to allow drill through to E-Business Suite Financials) are defined in this import format. Those fields are:
· Set_of_Books_ID (E-Business Suite 11i) or Ledger ID (E-Business Suite R12)
· Period_Name
· Code_Combination_ID
· Currency_Code
· Account_Type
The following lists all forty-six fields that are pulled from E-Business Suite Financials. Any of these fields can be mapped to the target system.
|
1. When using Oracle E-Business Suite release 11i, the adapter pulls data from GL_BALANCES.SET_OF_BOOKS_ID. When using Oracle E-Business Suite release R12, the adapter pulls data from GL_BALANCES.LEDGER_ID. |
|
|
2. GL_BALANCES.CODE_COMBINATION_ID |
25. GL_CODE_COMBINATIONS.SEGMENT20 |
|
3. GL_CODE_COMBINATIONS.CHART_OF_ACCOUNTS_ID |
26. GL_CODE_COMBINATIONS.SEGMENT21 |
|
4. GL_CODE_COMBINATIONS.ACCOUNT_TYPE |
27. GL_CODE_COMBINATIONS.SEGMENT22 |
|
5. GL_CODE_COMBINATIONS.DESCRIPTION |
28. GL_CODE_COMBINATIONS.SEGMENT23 |
|
6. GL_CODE_COMBINATIONS.SEGMENT1 |
29. GL_CODE_COMBINATIONS.SEGMENT24 |
|
7. GL_CODE_COMBINATIONS.SEGMENT2 |
30. GL_CODE_COMBINATIONS.SEGMENT25 |
|
8. GL_CODE_COMBINATIONS.SEGMENT3 |
31. GL_CODE_COMBINATIONS.SEGMENT26 |
|
9. GL_CODE_COMBINATIONS.SEGMENT4 |
32. GL_CODE_COMBINATIONS.SEGMENT27 |
|
10. GL_CODE_COMBINATIONS.SEGMENT5 |
33. GL_CODE_COMBINATIONS.SEGMENT28 |
|
11. GL_CODE_COMBINATIONS.SEGMENT6 |
34. GL_CODE_COMBINATIONS.SEGMENT29 |
|
12. GL_CODE_COMBINATIONS.SEGMENT7 |
35. GL_CODE_COMBINATIONS.SEGMENT30 |
|
13. GL_CODE_COMBINATIONS.SEGMENT8 |
36. GL_BALANCES.CURRENCY_CODE |
|
14. GL_CODE_COMBINATIONS.SEGMENT9 |
37. GL_BALANCES.PERIOD_NAME |
|
15. GL_CODE_COMBINATIONS.SEGMENT10 |
38. GL_BALANCES.ACTUAL_FLAG |
|
16. GL_CODE_COMBINATIONS.SEGMENT11 |
39. GL_BALANCES.BUDGET_VERSION_ID |
|
17. GL_CODE_COMBINATIONS.SEGMENT12 |
40. GL_BALANCES.ENCUMBRANCE_TYPE_ID |
|
18. GL_CODE_COMBINATIONS.SEGMENT13 |
41. GL_BALANCES.PERIOD_YEAR |
|
19. GL_CODE_COMBINATIONS.SEGMENT14 |
42. GL_BALANCES.BEGIN_BALANCE_DR |
|
20. GL_CODE_COMBINATIONS.SEGMENT15 |
43. GL_BALANCES.BEGIN_BALANCE_CR |
|
21. GL_CODE_COMBINATIONS.SEGMENT16 |
44. GL_BALANCES.PERIOD_NET_DR |
|
22. GL_CODE_COMBINATIONS.SEGMENT17 |
45. GL_BALANCES.PERIOD.NET_CR |
|
23. GL_CODE_COMBINATIONS.SEGMENT18 24. GL_CODE_COMBINATIONS.SEGMENT19 |
46. YTD_BALANCE Note: This is derived from the following: GL_BALANCES.BEGIN_BALANCE_DR - GL_BALANCES.BEGIN_BALANCE_CR) + (GL_BALANCES.PERIOD_NET_DR - GL_BALANCES.PERIOD_NET_CR) |
Important: To enable E-Business Suite Financials drill through functionality, when setting up an import format, the PERIOD_NAME value must be stored in Attribute 1. Storing PERIOD_NAME in any other field will cause the drill through to fail.
> Step 4: Assign the Import Formats to a location:
a) Select Metadata > Locations.
b) From the Locations screen, select the location into which you want to import the E-Business Suite Financials data.
c) Select the WorkFlow Behaviors tab.
d) Select the import format created in Step 2a and click Save.
e) Select the Integration Options tab.
f) In the Option 1 field, enter the name of the import format defined in Step 3 and click Save.
The Period Name, Period Type, Period Year, and Actual flag are now pulled from the FDM Control Table.
Tips and Troubleshooting
The adapter was designed to pull the functional currency and STAT. If desired, Stat records can be excluded from the import using the import format. See Chapter 10 and Chapter 19 of the FDM Admin Guide for information on skipping fields in import formats.
Problem: SQL statements do not return results.
Detail: Due to the nature of the OracleDB structure, values stored in the database are case sensitive.
Solution: Ensure the values being specified are identical as those that exist in E-Business Suite Financials.
· If the E-Business Suite application contains multibyte (extended ASCII) characters, the File Encoding option must be set to Unicode for Import to work correctly.
· The adapter has been localized for French, German, and Danish.
· See the FDM 11.1.1.2 Readme for additional information.
Copyright
© 2009, Oracle and / or its affiliates. All rights reserved.
http://www.oracle.com