The EPMA metadata is extracted to a text file.

If enabled, it pushes the data to Essbase via Essbase Analytic Link for FM.

The EPMA application metadata is used to create an FM application on the FM server.

The application is sent out to a star schema for use by Essbase and other products.

When you redeploy an application, the application metadata is merged or replaced based on the changes made since the last deployment.

You can select specific objects to migrate or all objects to migrate.

Migrating applications from development to production in disconnected environments, where there are two instances of Shared Services, is not supported.

Life Cycle Management will migrate both objects and data.

Life Cycle Management will generate an XML file that can be modified and used for importing to target applications.

The only role necessary to perform LCM activities is Application Administrator.

Intercompany transactions are eliminated at the first common parent.

Intercompany transactions can be processed for both open and closed periods.

Matching tolerances can be set by percent, dollar amount, or both.

Eliminations are processed during both Calculation and Consolidation processes.

I/C reports are available to display transactions by status-Matched, Mismatched, or Unmatched.

Periods

Accounts

Entities

Currencies

Value

Security classes are grouping mechanisms for assigning security access to sets of related members, documents, or other objects.

Access levels for security classes include metadata, read, promote, and none.

Security classes are assigned to FDM locations in addition to FM objects.

Security classes cannot be created in EPMA by creating a Security Class dimension and associating it.

Security classes are created in Classic FM under Load Tasks.