Sample FDM URL Template

<server-name>—The name or IP address of the server and the port to which you want to connect.

<app-name>—The FDM target application name. This value should match the FDM administrator-assigned identifier given to the particular data set or repository within the product. For example, for the Comma sample application that ships with Oracle Hyperion Financial Management, Fusion Edition, the value would be comma.

<target-app-name>—The name of the Essbase application from which the drill-through request is originating.

<server-ds>—The name or IP address of the Essbase Server that is hosting the Essbase application and database from which the drill-through request to FDM is originating.

<app-ds>—The name of the Essbase application from which the drill-through request is originating.

<database.ds>—The name of the Essbase database from which the drill-through request is originating.

<alias-ds>—The name of an alias table to use in the drill-through request. Use Default if no alias table is required.

Product.id.$$Product-VALUE$$—The Point-Of-View (POV) dimension and the dimension member value, in this case, a value from the Product dimension. Essbase Studio automatically generates the dimension name as a part of the variable that is associated with the given dimension. Upon execution of the drill-through report, the name of the variable, $$Product-VALUE$$ will be substituted by the actual value from the POV; for example Cola.

If a dimension is called by a different name in the FDM source, you must make that substitution manually in the drill-through syntax. For example, if the “Product” dimension is called the “Items” dimension in FDM, you must substitute Items for the dimension name Product in the Essbase Studio-generated syntax, as follows:

http://<server-name>/HyperionFDM/AuthorizedPages/IntersectionSummaryByLocation.aspx?fdmAppName=<app-name>&fdmTargetAppName=<target-app-name>&attribute=system.ds.essbase&attribute=server.ds.<server-ds>&attribute=app.ds.<app-ds>&attribute=database.ds.<database.ds>&attribute=alias.ds.<alias-ds>&sso_token=$$CSS-TOKEN$$&attribute=Items.id.$$Product-VALUE$$&attribute=Market.id.$$Market-VALUE&rcp_version=1.5.0

Note that all visible dimensions in a target FDM report must be specified in the FDM URL syntax, even if, for example, you are only interested in the information in one dimension in the report.

All visible dimensions in a target FDM report must be specified in the FDM URL syntax, even if, for example, you are only interested in the information in one dimension in the report. By default, the Sample FDM Template syntax picks up all intersections you specified in the Context tab of the drill-through report editor and adds them to the template syntax statement. If there are any remaining dimensions in the target FDM report, you must also include those in your syntax statement