Business and Essbase Technical FAQ

What Essbase version does FreeForm use?

Oracle Fusion Cloud Enterprise Performance Management uses Oracle-managed Oracle Essbase with Hybrid BSO support. Check current service information and whether Hybrid mode is enabled for the application.

How do FreeForm and OCI Essbase work together?

Treat them as separate services. Design a supported data-transfer process and configure client connections for each target. A shared client does not make them a shared database or provide automatic synchronization.

What migration approach is recommended for Essbase cubes?

Inventory the model, calculations, integrations, and security; check compatibility; then create and validate a test FreeForm application from a supported source. Reconcile data and calculations before production use. An outline (OTL) carries structure, so data must be imported separately.

How do I investigate whether processing performance is hardware related?

Oracle manages the infrastructure. Customers should diagnose performance with service reports, job results, and application design review, and engage Oracle Support when necessary. A support request does not guarantee a particular hardware increase.

Reference: EPM Cloud Performance Policies

Does a database refresh refresh all cubes at once?

Yes. Refreshing the application database refreshes every cube. Plan the operation with users and run it immediately or schedule a database-refresh job.

Are there size limits?

FreeForm has documented model limits and service governors. Performance also depends on dimensionality, data density, calculations, and concurrent workload.

Are slowly changing attributes supported?

Validate the specific varying-attribute or slowly changing attribute requirement against supported FreeForm metadata and migration behavior.

Are hybrid cubes supported?

Yes. FreeForm supports Hybrid BSO and ASO designs. ASO is a separate storage option, not a Hybrid BSO cube. An import from a non-Hybrid source can retain non-Hybrid BSO behavior, so verify the resulting application.

Are multiple FreeForm applications supported in one environment?

Plan separate applications in separate environments. A multi-cube FreeForm application contains up to 12 cubes; connected navigation across environments does not create multiple applications inside one environment.

Can I load metadata through Data Integration?

Yes, including for ASO-only FreeForm applications. For ASO-only metadata loading, register an EPM local application with All Input Cubes, then a Dimension application, and configure the integration.

Do you lose any Planning application features?

Unlike Planning, FreeForm does not provide sandboxes, approvals, or the predefined rolling forecast features. Task Manager is documented separately and is available. Choose the business process according to the required workflow and modeling capabilities.

Can Groovy be used?

Yes. Use supported Cloud EPM Groovy APIs and business rules. Validate cube-specific operations and execution privileges rather than assuming that arbitrary server-side code or external Essbase extensions are supported.

Can Planning Migration files be used like Essbase OTL?

A Planning snapshot is not an Essbase outline creation source. Use the documented FreeForm creation process for supported Essbase sources. Ordinary Migration import is supported for snapshots from an existing FreeForm application, not as a shortcut for converting an Essbase application.

Can multiple outline or migration files be imported?

When creating an application from an Essbase source, use a single-cube outline export. When using the Migrate option, use a snapshot. Additional cubes can be added later.

How can dimensions from legacy Hyperion Planning be uploaded?

For a FreeForm redesign, prepare metadata for supported import or use the web dimension editor or Smart View. Evaluate Custom Planning separately when migrating a Planning application.

Can the database be refreshed from Smart View?

Yes, using the supported administration extension and the appropriate privileges. Follow the instructions for Oracle Smart View for Office for Office or Mac and Browser; an ordinary worksheet refresh retrieves grid data and is not a database refresh.

How is security configured?

Assign roles and artifact permissions, then configure member and cell-level security where appropriate. Default Ancestor Access supports None, Read, Write, and Display in ad hoc grids and the Member Selector. Display shows ancestor members with #NoAccess for their data; test effective access with a representative user.

How are dimensions managed?

Use the web dimension editor, supported metadata imports, or Smart View administration tools. Oracle Fusion Cloud Enterprise Data Management is a separate metadata-governance service and integration option. Refresh the database when structural changes require it.

Can FreeForm backups migrate to Planning or Financial Consolidation and Close applications?

Do not use a FreeForm snapshot to convert the application to another business process. A target Planning or Financial Consolidation and Close implementation needs its own supported model and artifacts; separately designed data integration is different from whole-application migration.

Are business rule scripts portable?

Creating a FreeForm application from a supported Essbase outline can convert calculation scripts to graphical rules.

Does OTL migration support all Essbase versions?

No. The migration from an on-premises is supported only from a single cube application from Essbase release 11.1.2.4.xxx or later. Check the source structure and restrictions; the version threshold does not guarantee compatibility with every feature.

Are there Data Integration dimension requirements?

Yes. Data Integration registration needs Account, Period, and Scenario classifications, even though FreeForm itself does not impose those native dimensions. Configure period and category mappings. ASO registration has additional requirements; follow the target-specific instructions.

Can data be imported after app creation?

Yes. Load or reload data with supported native imports, Essbase data load rules, or Data Integration. An OTL supplies structure and needs a separate data load; a supported source snapshot can include data. Loading data after creation is separate from importing an Essbase source to create the application.

How is the EPM Integration Agent used?

Use the Integration Agent as part of a configured Data Integration workflow to extract data from supported on-premises or other data sources. It requires source connectivity and integration setup; it is not an Essbase server administration replacement.

How is tuning handled?

Oracle operates the service; administrators remain responsible for efficient model, calculation, form, and integration design. Review reports and job timings, validate changes in test, and use supported settings and diagnostics rather than expecting unrestricted Essbase configuration access.

Is transparent, linked, or replicated partitioning supported?

Use documented data movement facilities such as data maps and Smart Push where applicable. These copy data and should not be described as native Essbase replicated partitions.

Is MaxL supported?

Use documented Cloud EPM automation interfaces for service operations. MaxL may be used on the source Essbase system to export migration data; this is different from running MaxL against FreeForm.

Are MDX functions supported?

Yes. The MDX Query Editor defines form rows, columns, and slice members. A data export API also queries a selected cube and returns a JSON grid without requiring a saved form. Adapt and validate Essbase queries against the target cube and supported features.

What import and export methods are preferred for large databases?

Choose a supported native data import/export option, Essbase load-rule pipeline job, or Data Integration workflow according to source format, transformations, cube type, and volume. Essbase data load rules can reuse existing file-based loading logic. Benchmark a representative load, inspect errors, and reconcile totals.

How do I migrate logic implemented in CDFs? Is a CDF-to-Groovy migration tool planned?

Automatic CDF conversion is not a documented FreeForm migration path. Assess each CDF and redesign the required logic using supported rules or Groovy APIs. Essbase snapshots containing CDFs or CDF references cannot be used as FreeForm creation sources.

Can I reuse Essbase data load rules with FreeForm?

Yes. Use the Data Load Essbase Rules File pipeline job to reuse an Essbase data load rules file and its source data file without rebuilding the load as a Data Integration definition. Select the target Cube and upload the rules file and data file to the inbox through the File browser. Set Recreate Rule to Yes after changing the rules file; No reuses the existing rule, creating it if absent.

SQL-based loading is not supported: remove SQL from the rule and supply extracted data in a separate file. This support concerns data loading and does not imply support for Essbase dimension-build rules, direct relational SQL execution, or MaxL access.

Where do I create a FreeForm application?

Select the FreeForm business process on the EPM landing page, then use the supported application creation workflow. You can also create the application through the supported Smart View template procedure.

Can I create a multi-cube application from an Excel template?

Yes. Use PlanningApplicationTemplate_FreeForm.xlsx through supported Smart View administration capabilities. The current template supports any combination of up to 12 ASO and BSO cubes and replaces the older single-cube ASO and BSO templates.

Must FreeForm contain the standard Planning dimensions?

No. Model dimensions for the use case. Separately check the classifications and calendars required by Data Integration, IPM, and other features before finalizing the design.

What should I know before converting a Classic form to MDX?

Saving an existing Classic form in the MDX Query Editor replaces that Classic form. Opening an MDX form in the Classic Editor removes MDX-related updates. Preserve a copy before conversion, validate the query, and test the saved form as the intended user.

How do I validate an Essbase migration?

Review creation jobs for errors, import data when using an OTL, configure users and permissions, and reconcile the result. Test calculations, data editability, and critical analysis workflows before production use. Resolve reserved names, oversized names, and unsupported source features first.