ORACLE WHITE PAPER MARCH 2014

ORACLE HYPERION FINANCIAL DATA

QUALITY MANAGEMENT, ENTERPRISE
EDITION (FDMEE) – DRILL THROUGH URL
DETAILS
KEY DETAILS
Oracle Hyperion FDMEE
enables EPM users a way to
Oracle Hyperion FDMEE fills the gap between ERP and EPM
drill-through to source ERP data. applications with its simplified integration architecture, including
With the drill-through function,
user can view the GL balances, drill-back to source ERP systems. This whitepaper provides drill-
and the related source journals.
Oracle Hyperion FDMEE
through URL details for users loading data with a file that wish to
supports data loading and drill- drill-through to a source ERP.
through to following ERP
Systems
 E Business Suite The primary audience of this document is a user who is loading
 Fusion Financials
data to an EPM application using a flat file or interface table with
 PeopleSoft Financials
 SAP Financials FDMEE, but desires to also drill-through to a source system. This
 JD Edwards GL will most likely be a user of Planning and Budgeting as a Cloud
 File/Custom
Service V1that is loading a file from an on-premise version of an
Oracle branded ERP or a supported version of SAP.

It is assumed that the reader of this document is familiar with the

functionality of FDMEE, specifically the Import Format.

Drill-through Functionality
FDMEE provides the framework to drill-through from an EPM application
back to a general ledger source. (Drill through is not supported for human
resource data.) Users can drill-through to detail in the source system
through FDMEE from the following products:
 Planning web forms
 Financial Management web forms
 Oracle Hyperion Smart View for Office
 Financial Reporting

When users load data to an EPM application using FDMEE, they can
specify an optional drill region flag. When set to “Yes”, a drill region
definition is passed to the target application, in addition to the actual data, to
indicate that a cell is “drillable”. When drilling through from an EPM
application, a landing page is displayed in a separate workspace tab that
shows all rows that comprise the amount from the selected cell in the EPM
application. From this landing page, the user can open the source document
or continue to drill-through to the defined source system landing page.
 ORACLE WHITE PAPER

Drilling Through to the FDMEE Landing Page

The FDMEE landing page displays general ledger accounts and the
hyperlinked balances that were used to populate the cells in the EPM
application. When you click a hyperlinked data value, you can drill through
to the source system and view the associated journal entries for the selected
general ledger account.
If the FDMEE system is configured to integrate directly from a supported
source system, then the drill URL is configured automatically by FDMEE.
If users are loading data via a file or the open interface table, then the user
must configure the URL manually in the source system definition and the
import format definition. This document explains how to set up the drill
URL definition when using a file or interface table as a data source.

Drill-Through URL Components

The drill-through URL has two major components:
 Server Component – defined for each source system.
 Detail Component – defined automatically if using the predefined
integration, or manually if using file based integration.
In all cases, the user must specify the drill-through source server, and
optional URL details when using file based loads.
The following pages provide the URL details for the currently known drill-
through pages.

2
 ORACLE WHITE PAPER

Oracle E-Business Suite URL Details

Server Component – include the server name and related port
http://<SERVER>:<PORT>
Example:
http://myserver.com:8015
Please note that the server and port details are similar for all URLs
defined in this document, but will not be included for other landing
pages. It is assumed that the server component will be specified for each
landing page, but not documented
Detail Component
/OA_HTML/RF.jsp?
function_id=<InstallSpecific>&CALLING_PAGE=FDM_DRILLDOW
N&resp_appl_id=<FromEBS>&resp_id=<FromEBS>&SOB_ID=<User
Defined>&LED_ID=<UserDefined>&fdm_per=<UserDefined>&fdm_c
cid=<UserDefined>&fdm_currency=<UserDefined>&fdm_balance_type
=<UserDefined>
Sample URL
/OA_HTML/RF.jsp?
function_id=1028696&CALLING_PAGE=FDM_DRILLDOWN&resp_
appl_id=-1&resp_id=-1&SOB_ID=1&LED_ID=1&fdm_per=Jan-
07&fdm_ccid=12842&fdm_currency=USD&fdm_balance_type=A
Function ID
The function ID is EBS system specific, and is generated at the time the
EBS system is installed and configured. The function ID can be queried
from the source EBS system with the following query:
SELECT FUNCTION_ID
FROM fnd_form_functions
WHERE function_name = 'GLAADPAGE'
The function ID tells the EBS system which page to display using the
other included parameters. The value that is returned by the query
should be included in the URL details.
Calling Page
The calling page parameter indicates the origin of the HTTP call. This
should just be hard coded in the URL as FDM_DRILLDOWN
Resp_Appl_ID and Resp_id
These are the application ID and responsibility ID from EBS. These can
be set to -1 if unknown. The EBS system will prompt the user for the
user name, password and responsibility if not provided on initial

3
 ORACLE WHITE PAPER

authentication.
Additional Parameters
SOB_ID = Internal Set of Books ID
LED_ID – Internal Ledger ID
fdm_per = The EBS period name. This value must be the same as the
period name in the EBS system
fdm_ccid = The Code Combination ID (CCID) for the requested account.
fdm_currency = The EBS ledger currency
fdm_balance_type = A for Actual, B for Budget
Values not hard coded in the drill-url can be referenced from the
TDATASEG table using references to the table column names, or to the
column names specified in the import format.

Values not hard coded in the drill URL can be referenced from the
TDATASEG table using references to the table column names, or to the
column names specified in the import format. Drill through parameters that
are different for each row of data, like the CCID must be included in the
input file and mapped to an attribute column in the import format. When
formatting the drill URL, these parameters can be referenced from the
TDATASEG table using the $<TDATASEG_COLUMN>$ notation, or from
the import format using the $$<IMPORT_FORMAT_COL>$$ notation.
Please see the FDMEE admin guide for full details.
A sample that uses import format column name references is as follows:
SOB_ID=<$$sob$$>&LED_ID=<$$ledgerid$$>&fdm_per=<$$period$
$>&fdm_ccid=<$$ccid$$>&fdm_currency=<$$currency$
$>&fdm_balance_type=<$$baltype$$>
This example assumes that the column names in the import format must be
sob, ledgerid, fdm_per, etc.

PeopleSoft Financials URL Details

Detail Component
/
psp/e910p40nt/EMPLOYEE/ERP/c/PROCESS_JOURNALS.INQUIRY
_CRITERIA.GBL?
Page=INQUIRY_CRITERIA&Action=A&INQUIRY=*DEFAULT&DR
ILP=Y&BUSINESS_UNIT=$ATTR1$&FISCAL_YEAR=$ATTR2$&P
ERIOD_FROM=$ATTR3$&PERIOD_TO=$ATTR4$&LEDGER=$ATT
R5$&F1=CLASS_FLD&CLASS_FLD=$ATTR6$&F2=FUND_CODE
&FUND_CODE=$ATTR7$&F3=PRODUCT&PRODUCT=$ATTR8$&
F4=ACCOUNT&ACCOUNT=$ATTR9$&F5=ALTACCT&ALTACCT=

4
 ORACLE WHITE PAPER

$ATTR10$&F6=OPERATING_UNIT&OPERATING_UNIT=$ATTR11
$&F7=BUDGET_REF&BUDGET_REF=$ATTR12$&F8=AFFILIATE
&AFFILIATE=$ATTR13$&F9=PROGRAM_CODE&PROGRAM_CO
DE=+&F10=AFFILIATE_INTRA2&AFFILIATE_INTRA2=+&F11=AF
FILIATE_INTRA1&AFFILIATE_INTRA1=+&F12=DEPTID&DEPTI
D=$ATTR14$

Sample URL
/
psp/e910p40nt/EMPLOYEE/ERP/c/PROCESS_JOURNALS.INQUIRY
_CRITERIA.GBL?
Page=INQUIRY_CRITERIA&Action=A&INQUIRY=*DEFAULT&DR
ILP=Y&BUSINESS_UNIT=US005&FISCAL_YEAR=2003&PERIOD
_FROM=1&PERIOD_TO=1&LEDGER=LOCAL&F1=CLASS_FLD&
CLASS_FLD=+&F2=FUND_CODE&FUND_CODE=+&F3=PRODUC
T&PRODUCT=SERVRS&F4=ACCOUNT&ACCOUNT=400000&F5=
ALTACCT&ALTACCT=+&F6=OPERATING_UNIT&OPERATING_U
NIT=+&F7=BUDGET_REF&BUDGET_REF=+&F8=AFFILIATE&AF
FILIATE=+&F9=PROGRAM_CODE&PROGRAM_CODE=+&F10=A
FFILIATE_INTRA2&AFFILIATE_INTRA2=+&F11=AFFILIATE_INT
RA1&AFFILIATE_INTRA1=+&F12=DEPTID&DEPTID=21500
Fixed Component
Parameters
For identifying values for chartfields, please work with your internal
systems group

PeopleSoft Projects Drill-through URL

Detail Component
/
psp/portal/EMPLOYEE/ERP/c/ANALYZE_PROJECTS.PROJECT_EX
PRESS.GBL?
Page=PROJECT_EXPRESSG&ACTIVITY_ID=100&BUSINESS_UNI
T=$ATTR1$&PROJECT_ID=$ATTR2$&Action=$ATTR3$
Sample URL
/
psp/portal/EMPLOYEE/ERP/c/ANALYZE_PROJECTS.PROJECT_EX
PRESS.GBL?
Page=PROJECT_EXPRESSG&ACTIVITY_ID=100&BUSINESS_UNI
T=HT001&PROJECT_ID=0000000232&Action=U
Fixed Component
The following is fixed text that is required as the start of the details drill
URL and is as follows:
/
psp/portal/EMPLOYEE/ERP/c/ANALYZE_PROJECTS.PROJECT_EX
PRESS.GBL?Page=PROJECT_EXPRESSG&ACTIVITY_ID=100

5
 ORACLE WHITE PAPER

Parameters
BUSINESS_UNIT
PROJECT_ID
Action
Data for these fields should be included in the source file, and mapped to
attribute columns in the TDATASEG table via the import format.
For identifying and fetching various source parameters, please work with
your internal systems group.

PeopleSoft Custom Page Drill-through URL

Overview
It is possible to modify PeopleSoft pages using peopletools to open
pages with passed parameters. This provides the ability to drill through
to a page other than the pre-defined page provided in PSFT 9.0 an up.
For example, if a customer wants to load data from an older version of
Peoplesoft that does not support drill through, a file or open interface
adapter may be used, and then a custom drill url provided. An example
of how to modify a peoplesoft page using people tools may be found on
the following blog or via the PeopleSoft documentation:
http://www.greyheller.com/Blog/creating-optional-parameters-for-a-
peoplesoft-page/

Sample URL – With Additional parameters

Account
Department
Fund Code
Program Code
Budget Reference
Project

URL

https://<SERVER>/psp/fs91prd/EMPLOYEE/ERP/c/PROCESS_JOU
RNALS.INQUIRY_CRITERIA.GBL?
Page=INQUIRY_CRITERIA&Action=A&INQUIRY=*DEFAULT&
DRILP=Y&BUSINESS_UNIT=00502&FISCAL_YEAR=2012&PE
RIOD_FROM=1&PERIOD_TO=1&LEDGER=ACTUALS++
+&CURRENCY_CD=USD&STATISTICS_CODE=+++&

Please note that you can parameterize the URL to pull the appropriate
columns from the TDATASEG table.

6
 ORACLE WHITE PAPER

Fusion Financials drill-through URL (On-Premise Only)

Detail Component
/ledger/faces/InquiryReportWorkarea?fnd=%252FWEB-INF
%252Foracle%252Fapps%252Ffinancials%252FgeneralLedger
%252Finquiry%252Fbalances%252Fui%252Fflow
%252FStandardBalanceFlow.xml%2523StandardBalanceFlow
%3BdrilldownVar%253DY%253BnavModeVar%253DOTH
%253BledgerIdVar%253D1%253BcoaIdVar
%253D101%253BperiodNameVar%253DFeb-03%253BccIdVar
%253D86808%253BledgerCurrencyVar%253DUSD
%253BcurrencyCodeVar%253DUSD%253BcurrencyTypeVar%253DT
%3B%3BFusion%3B%3B
Sample URL
/ledger/faces/InquiryReportWorkarea?fnd=%252FWEB-INF
%252Foracle%252Fapps%252Ffinancials%252FgeneralLedger
%252Finquiry%252Fbalances%252Fui%252Fflow
%252FStandardBalanceFlow.xml%253StandardBalanceFlow
%3BdrilldownVar%253DY%253BnavModeVar%253DOTH
%253BledgerIdVar%253D1%253BcoaIdVar
%253D101%253BperiodNameVar%253DFeb-03%253BccIdVar
%253D86808%253BledgerCurrencyVar%253DUSD
%253BcurrencyCodeVar%253DUSD%253BcurrencyTypeVar%253DT
%3B%3BFusion%3B%3B
Fixed Component
/ledger/faces/InquiryReportWorkarea?fnd=%252FWEB-INF
%252Foracle%252Fapps%252Ffinancials%252FgeneralLedger
%252Finquiry%252Fbalances%252Fui%252Fflow
%252FStandardBalanceFlow.xml%253StandardBalanceFlow
%3BdrilldownVar%253DY%253BnavModeVar%253DOTH%253
Parameters
Ledger ID
Chart of Accounts ID
Period Name
CCID
Ledger Currency
Currency Code
Currency Type

A sample URL starting after the fixed component with the parameters
filled in might look like the following:

BledgerIdVar%253D$$LEDGER$$%253BcoaIdVar%253D$$COA$$
%253BperiodNameVar%253D$$PERIOD$$%253BccIdVar%253D$
$CCID$$%253BledgerCurrencyVar%253D$$CURRENCY$$
%253BcurrencyCodeVar%253D$$CURRENCY$$
%253BcurrencyTypeVar%253DT%3B%3BFusion%3B%3B

7
 ORACLE WHITE PAPER

In this example, the $$ notation was used to indicate that the column
name from the import format is used. Everything after currency type
was left as hard coded values.

JD Edwards EnterpriseOne GL URL Details

Detail Component
/jde/HostedE1Servlet?
OID=P09210A_W09210AA_ZJDE0001&FormDSTmpl=|3|4|5|6|7|8|9|
10|11|&FormDSData=|<LedgerType1>|<LedgerType2>|<SubLedger>|
<SubLedgerType>|<AccountLevelOfDetail>|<ThruDate>|<ThruDate2>|
<CurrencyCode>|<AccountNumber>|
&jdelogoutlink=e1logout&jdecloselink=[Configure Close URL]
Sample URL
/jde/HostedE1Servlet?
OID=P09210A_W09210AA_ZJDE0001&FormDSTmpl=|3|4|5|6|7|8|9|
10|11|&FormDSData=|AA|BA|00000200|A|8|120105|123105| |
*00006373| &jdelogoutlink=e1logout&jdecloselink=[Configure Close
URL]
Fixed Component
/jde/HostedE1Servlet?
OID=P09210A_W09210AA_ZJDE0001&FormDSTmpl=|3|4|5|6|7|8|9|
10|11|
Parameters
The table below provides the JDE source column name for each of the
parameters. Each of these values needs to be stored in a column of the
TDATASEG table so that they can be referenced in the URL during drill-
through, or hard coded if they don’t change. If they need to be
referenced from TDATASEG, then the values need to be included in the
load file.
Parameter Source Column in JDE
LedgerType1 GBLT
LedgerType2
Subledger GBSBL
SubledgerType GBSBLT
AccountLevelOfDetail GMLDA
ThruDate1 (Beginning Date)
ThruDate2 (End Date)
CurrencyCode GBCRCX
AccountNumber GBAID

A sample URL starting after the fixed component with the parameters
filled in might look like the following:
&FormDSData=|$ATTR6$|$ATTR7$|$ATTR8$|$ATTR9$|$ATTR10$|
$ATTR11$|$ATTR12$|$ATTR13$|$ATTR14$|

8
 ORACLE WHITE PAPER

&jdelogoutlink=e1logout&jdecloselink=[Configure Close URL]

* Please work with your internal systems group to identify the required
parameters.
** The ATTR6-ATTR14 specification is only an example – your attributes
may be different based on your mapping.

SAP General Ledger (Classic) Drill-Through URL

Detail Component
/scripts/wgate/webgui/!?sap-system-login-basic_auth=X&sap-
client=800&sap-language=EN&~transaction=FS10N&SO_SAKNR-
LOW=$$ACCOUNT$$&SO_BUKRS-LOW=$$ENTITY$
$&GP_GJAHR=$FISCAL_YEAR$&SO_GSBER=&~okcode=ONLI
Parameters
SO_SAKNR = Account
SO_BUKRS = Entity
GP_GJAHR = Period
SO_GSBER = Business Area (Optional)
The user will also need to specify the correct sap-client number.
 Parameters with $$ are actually the User entered Column Names in
Import Format
 Parameters with $ are the Attribute Column Names in TDATASEG

SAP General Ledger (New) Drill-Through URL – 3 Known URLs

Report GL-FAGLB03
Detail Component
/sap/bc/gui/sap/its/webgui/!?sap-system-login-basic_auth=x&sap-
client=800&sap-language=EN&~transaction=*FAGLB03%20RACCT-
LOW=$$ACCOUNT$$;RBUKRS-LOW=$$ENTITY$
$;RYEAR=$YEAR$;RLDNR=;DYNP_OKCODE=ONLI
Parameters
RACCT = Account
RBUKRS = Entity
RYEAR = Period
RLDNR – Ledger (Optional)
The user will also need to specify the correct sap-client number
 Parameters with $$ are actually the User entered Column Names in

9
 ORACLE WHITE PAPER

Import Format
 Parameters with $ are the Attribute Column Names in TDATASEG

Report S_ALR_87012277
Detail Component
/sap/bc/gui/sap/its/webgui/!?sap-system-login-basic_auth=x&sap-
client=800&sap-
language=EN&~transaction=S_ALR_87012277&SD_BUKRS-LOW=$
$ENTITY$$&SD_SAKNR-LOW=$$ACCOUNT$$&SD_GJAHR-
LOW=$YEAR$&SD_GSB_S-LOW=$$BUSINESS_AREA$
$&SD_CURTP=&SD_RLDNR-LOW=&B_MONATE-
LOW=$ATTR5$&B_MONATE-
HIGH=$PERIOD$&P_GSAU=X&~OKCODE=ONLI
Parameters
SD_BUKRS – Entity
SD_SAKNR – Account
SD_GJAHR – Year
SD_GSB – Business Area
SD_CURTP – Currency Type
B_MONATE – Default Period
P_GSAU – Business Area Allocation
The user will also need to specify the correct sap-client number
 Parameters with $$ are actually the User entered Column Names in
Import Format
 Parameters with $ are the Attribute Column Names in TDATASEG

Report S_PL0_86000030

Detail Component
/sap/bc/gui/sap/its/webgui/!?sap-system-login-basic_auth=x&sap-
client=800&sap-
language=EN&~transaction=S_PL0_86000030&U3_CURTP-
LOW=10&U3_RBUKR-LOW=1000&U3_00011-
LOW=0000792000&PAR_03=0L&PAR_06=2011&PAR_01=05&PAR_
02=05&~OKCODE=ONLI
Parameters
CURTP – Currency Type

10
 ORACLE WHITE PAPER

RBUKR – Entity
Other parameters – contact your SAP systems group.
The user will also need to specify the correct sap-client number.
 Parameters with $$ are actually the User entered Column Names in
Import Format
 Parameters with $ are the Attribute Column Names in TDATASEG

Microsoft Dynamics NAV Web Client (Navision)

Link to Microsoft Documentation
http://msdn.microsoft.com/en-us/library/hh997130%28v=nav.71%29.aspx

Explains how to formulate a drill-through URL for any of the Navision

modules
Detail Component – GL example
/DynamicsNAV71/WebClient/List.aspx?company=CRONUS
%20International%20Ltd.&mode=View&page=20&filter='G/L Account
No.'%20IS%20'$ACCOUNTX$'%20AND%20'Document No.'%20IS
%20'$ATTR1$'

Other drill-through URLs are available, but this is just the GL example.

Parameters
G/L Account No. - Provide mapped account value
Document No. - This will need to be loaded as an attribute. In this
example, ATTR1 was used to hold the document number.

 Parameters with $$ are actually the User entered Column Names in

Import Format
 Parameters with $ are the Attribute Column Names in TDATASEG

EBS R12 AP Drill-through to Journal Entries

So from a Journal header/line
(GL_JE_LINES.JE_HEADER_ID/GL_JE_LINES.JE_LINE_NUM) - you can
invoke the SLA function. It will ask the user to login/select an appropriate
responsibility. The user will then be taken to the SLA drilldown page that will
show the accounting info - from there they can navigate to the AP transaction.

The URL is the following:

11
 ORACLE WHITE PAPER

http://rws3210062.us.oracle.com:8095/OA_HTML/RF.jsp?
function_id=XLA_LINESINQ_GL_DRILLDOWN&jeHeaderId=64524&jeLine
Num=1&jeSource=Payables&searchType=customize
(jeHeaderId, jeLineNum, jeSource are parameter values).

Please note that this is available only for EBS Release 12.1 and above.

Contact Us
For more information about Oracle Hyperion Financial Data Quality Management,
Enterprise Edition, please visit oracle.com or call +1.800.ORACLE1 to speak to an
Oracle representative.
Copyright 2014, Oracle. All Rights Reserved.

This document is provided for information purposes only, and the contents hereof are subject to change without notice. This
document is not warranted to be error-free, nor is it 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.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their
respective owners.

12