EPM Vitals Book 20-min demo
Guide Chapters

Product support / Chapter 07

7. Application Workspace

Use the Application workspace to turn snapshots and application context into reusable review evidence.

The Application workspace focuses on understanding the EPM application structure. It is the best starting point when the team has an application snapshot or export package.

7.1 Application Profile

Use Application Profile to build a reusable profile from an application snapshot, export package, or Oracle EPM Pull. Other modules can use this profile for assisted config generation, metadata review, impact analysis, and business logic exploration.

Application Profile Setup
Application Profile Setup

Inputs:

  • Profile name.
  • Input source: Upload Snapshot or Oracle EPM Pull.
  • Application snapshot or export package when uploading a local file.
  • Oracle EPM Base URL, username, and password when using Oracle EPM Pull.
  • Parser profile, often left as auto when available.
  • Optional output parsed workbook setting.

Key buttons:

  • Test Connection / Build Export Plan
  • Pull Profile-only Snapshot
  • Run in background
  • Initialize Application
  • Delete Profile
  • Download Workbook

Recommended upload workflow:

  1. Enter a clear profile name.
  2. Upload the application snapshot or export package.
  3. Select the parser profile.
  4. Click Initialize Application.
  5. Review the detected provider, status, dimensions, member rows, and warning summary.
  6. Download the parsed workbook if you need evidence or offline review.
  7. Reuse the Application Profile in Configure Wizard, Impact Chain, Business Logic Explorer, Metadata Catalog, and Mapping Review.

Recommended Oracle EPM Pull workflow:

  1. Enter a clear profile name.
  2. Select Oracle EPM Pull.
  3. Enter the Oracle EPM Base URL, username, and password.
  4. Click Test Connection / Build Export Plan.
  5. Review the profile-only export plan. The plan is designed to include profile metadata while excluding Essbase Data.
  6. Click Pull Profile-only Snapshot.
  7. After the snapshot is pulled, click Initialize Application for an immediate build, or click Run in background if the profile build may take longer.
  8. Review the Application Profile result and use Run History if you need to inspect background job status later.

Oracle EPM Pull behavior:

  • EPM Vitals remembers up to five recent Base URLs. Click the Base URL field or its selector to choose a remembered URL.
  • EPM Vitals does not store Oracle EPM passwords.
  • The export plan uses selected migration artifacts, not a full snapshot pull.
  • Essbase Data is always excluded from the profile-only pull.
  • Security and Groups and Membership are excluded by default because they may contain sensitive access information that is not required for most profile context.
  • Typical included areas are Core metadata, Document Repository, Data Management definitions, and Calculation Manager definitions.
  • The generated temporary snapshot name is based on the username and timestamp to avoid exposing EPM Vitals branding in Oracle EPM.
Application Profile Result
Application Profile Result

Outputs:

  • A reusable Application Profile in the local Application Library.
  • A parsed workbook where enabled.
  • Structured application context for downstream modules.

Best practices:

  • Use one profile per meaningful application version or migration milestone.
  • Use sanitized or non-production snapshots for support discussions.
  • Reinitialize a profile when the source application export has materially changed.
  • Prefer Oracle EPM Pull when you need a profile-only package and want to avoid pulling Essbase Data.

7.2 Snapshot Reader

Use Snapshot Reader to parse a snapshot and export a structured workbook. This is useful when you need a readable inventory of an application package without necessarily creating a reusable profile.

Snapshot Reader Scope
Snapshot Reader Scope

Inputs:

  • Snapshot ZIP, XML, or CSV package depending on provider support.
  • Provider selection or detected provider.
  • Parser profile for Oracle EPM where applicable.
  • Export scope settings.

Common export scope options:

  • Inventory.
  • Application Settings.
  • Dimensions.
  • Variables.
  • FDMEE.
  • Artifacts.
  • FCCS.

Key buttons:

  • Run Snapshot Reader
  • Download Workbook

Recommended workflow:

  1. Upload the snapshot file.
  2. Confirm the detected provider.
  3. Select the export scope.
  4. Click Run Snapshot Reader.
  5. Review summary metrics such as provider, application, dimensions, warnings, member rows, integrations, rules, and analysis mode.
  6. Download the workbook.
Snapshot Reader Result
Snapshot Reader Result

Outputs:

  • Snapshot inventory workbook.
  • Warnings or review notes.
  • Local run record.

7.3 Impact Chain

Use Impact Chain to inspect what may be affected by a member, rule, integration, form, report, or other application object.

Impact Chain Object Picker
Impact Chain Object Picker

Inputs:

  • Application Profile.
  • Logic index or profile-local evidence index where available.
  • Object search term or selected object.

Key buttons:

  • Load Logic Index
  • Build / Rebuild Logic Index
  • Run Impact Chain Analysis
  • Download Impact Chain Report

Recommended workflow:

  1. Select an Application Profile.
  2. Load the logic index.
  3. Search for the object you want to analyze.
  4. Select the correct object and context.
  5. Click Run Impact Chain Analysis.
  6. Review upstream and downstream evidence.
  7. Download the impact report.
Impact Chain Result
Impact Chain Result

Typical use cases:

  • Check what a member change may affect.
  • Review rule migration impact.
  • Understand which forms, integrations, or calculations reference an object.
  • Prepare evidence before making structural application changes.

7.4 Business Logic Explorer

Use Business Logic Explorer to search, inspect, and explain business logic evidence in an Application Profile.

Business Logic Explorer Result
Business Logic Explorer Result

Inputs:

  • Application Profile.
  • Object type or search keyword.
  • Selected object or calculation item.

Key buttons:

  • Load Application Profile
  • Reload Application Profile
  • Explore Logic
  • Back
  • Evidence
  • Open in Object Query

Recommended workflow:

  1. Load an Application Profile.
  2. Search for an account, member, form, rule, or other supported object.
  3. Select an object from the result list.
  4. Click Explore Logic.
  5. Review the business logic summary, calculation range, conditions, and evidence.
  6. Use Evidence to inspect supporting rows.
  7. Use Open in Object Query when you need to continue investigation in the object explorer.
Business Logic Evidence
Business Logic Evidence

Outputs:

  • Business logic summary.
  • Evidence references.
  • Topology or relationship view where available.
  • Review-ready explanation of how selected logic is connected.

7.5 Migration Readiness

Use Migration Readiness to review whether application artifacts or profiles are ready for migration planning.

Inputs:

  • Baseline profile, candidate profile, or related migration package.
  • Readiness scope where available.

Recommended workflow:

  1. Select the baseline and candidate context.
  2. Run the readiness review.
  3. Review blockers, warnings, and review items.
  4. Download the readiness result.

Outputs:

  • Migration readiness summary.
  • Blocking items.
  • Warning items.
  • Review queue and workbook evidence.