Oracle® Hyperion Profitability and Cost Management
Error Message Reference
F24157-01
October 2019
EPMPCM-00001: Unknown error.
Cause: A Web Application error occurred, but no corresponding message was found
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00002: Unknown error: {0}.
Cause: A Web Application error occurred, but no corresponding message was found
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00003: Unexpected error.
Cause: An unexpected error occurred.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00004: Failed to get configuration.
Cause: An exception occurred while retrieving the application configuration.
Action: Refer to the server log files for more information.
Level: 1
Type: ERROR
EPMPCM-00005: Audit error.
Cause: An unexpected error occurred while retrieving information required for auditing.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00006: Initialization of audit client failed.
Cause: Unable to access the Audit service.
Action: Verify the configuration for the Foundations Services is correct.
Level: 1
Type: ERROR
EPMPCM-00007: Form validation failed: "{0}".
Cause: Data entered into a field within the Form is invalid.
Action: Enter data in the correct format.
Level: 1
Type: ERROR
EPMPCM-00008: "{0}" is required.
Cause: The field is required for completion of the current form
Action: Enter a value for the required field.
Level: 1
Type: ERROR
EPMPCM-00009: "{0}" must be an integer.
Cause: An integer value must be entered into this field
Action: Enter a numeric value without a decimal.
Level: 1
Type: ERROR
EPMPCM-00010: "{0}" must be less than {1} symbol.
Cause: The length of the value entered into the field is too long.
Action: Reduce the length of the value entered into the field.
Level: 1
Type: ERROR
EPMPCM-00013: Traceability Diagram
Cause: An error occurred while exporting the traceability diagram.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00014: Failed to load version information from "{0}"
Cause: Unable to determine the version for Hyperion Profitability and Cost Management
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00015: SSOFilter configuration: {0} = {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00016: Failed to get RDB connection information from registry
Cause: The Shared Services registry is not valid.
Action: Run the EPM configurator to determine the configuration state for the Profitability application.
Level: 1
Type: ERROR
EPMPCM-00017: Failed to convert object
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00018: Failed to get value for ''''{0}'''' from RegistryHelper
Cause: The Shared Services registry is not valid.
Action: Run the EPM configurator to determine the configuration state for the Hyperion Foundation.
Level: 1
Type: ERROR
EPMPCM-00019: Cannot get WebServer configuration. Please make sure Workspace and web server are configured and then restart Profitability application server.
Cause: WebServer configuration is not available.
Action: Verify that Workspace and web server are configured and then restart the application server where the Profitability service is installed.
Level: 1
Type: ERROR
EPMPCM-00020: Cannot get Essbase configuration from Registry. Please make sure Essbase is configured and then restart Profitability application server.
Cause: The Essbase configuration is invalid in the registry.
Action: Verify that Essbase is configured properly using the Configurator and then restart the application server where the Profitability service is installed.
Level: 1
Type: ERROR
EPMPCM-00021: Application with name ''''{0}'''' already exists.
Cause: The application name is already registered.
Action: Choose a different application name.
Level: 1
Type: ERROR
EPMPCM-00022: Project ''''{0}'''' does not exist.
Cause: The Shared Services Project does not exist.
Action: Choose a different project for the application.
Level: 1
Type: ERROR
EPMPCM-00023: Cannot delete temp file ''''{0}''''
Cause: A temporary file on the file system could not be deleted.
Action: Verify that there are no existing locked files in the operating system and restart the application server where the Profitability service is installed.
Level: 1
Type: ERROR
EPMPCM-00024: Failed to get Essbase connection information from registry
Cause: The Essbase installation has an invalid configuration.
Action: Verify the state of the Essbase installation using the Configurator.
Level: 1
Type: ERROR
EPMPCM-00025: Failed to get HSS connection information from registry
Cause: Hyperion Shared Services has an invalid configuration.
Action: Verify the state of Hyperion Shared Services using the Configurator.
Level: 1
Type: ERROR
EPMPCM-00026: Resource not found for message ''''{0}''''
Cause: A resource bundle file was not found.
Action: Verify the state of the Profitability configuration using the Configurator.
Level: 1
Type: ERROR
EPMPCM-00027: Failed to update registry on application server startup
Cause: Could not successfully update registry
Action: Verify the configuration state for the Hyperion products using the Configurator.
Level: 1
Type: ERROR
EPMPCM-00028: ValidationEngine is not available in the context
Cause: The error cause is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00030: The context parameter cannot be null
Cause: The error cause is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00031: Unexpected authenticationType value: {0}
Cause: Unable to authenticate the SSO Token with Essbase. The SSO Token may be stale.
Action: Verify that SSO Token timeout settings are appropriate for the installation.
Level: 1
Type: ERROR
EPMPCM-00032: Scripts execution time (ms): {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00033: Validation resources are not found
Cause: An error occurred while reading validation XML files.
Action: Restart the application server where the Profitability service is installed.
Level: 1
Type: ERROR
EPMPCM-00034: Validation resources parsing error
Cause: An error occurred while reading validation XML files.
Action: Verify that the Profitability application is installed and configured properly using the Configurator.
Level: 1
Type: ERROR
EPMPCM-00035: Validator error
Cause: An error occurred during validation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00036: Schema type information is not found for the node: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server log files for more information.
Level: 1
Type: ERROR
EPMPCM-00037: Cannot find type to instantiate with node TypeNameInfo: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00038: No NodeUnmarshaller could be found to unmarshall node: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00039: Unexpected error: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00040: Failed to instantiate configuration class {0}.
Cause: The Shared Service registry is invalid.
Action: Verify that the Hyperion Foundation is properly configured using the Configurator.
Level: 1
Type: ERROR
EPMPCM-00042: Command executor failed while executing the following template: {0}
Cause: An SQL statement failed during execution
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00043: Exception getting ''''{0}'''' field value.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00044: Removing of the temporary copy of file has failed. Temporary file is "{0}".
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00045: Failed to initialize DMS Execution Context
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00046: Unique Id generated for this execution is : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00047: Product database rolled back successfully.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00048: Exception when trying to rollback product database connection for execution: {0}
Cause: An exception occurred during rollback of a database transaction.
Action: Refer to the server log files for more information.
Level: 1
Type: ERROR
EPMPCM-00049: Staging database rolled back successfully.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00050: Exception when trying to rollback staging database connection for execution: {0}
Cause: An execption occurred while performing a database rollback operation on the Staging database.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00051: Unknown database type: {0}
Cause: You are running against an unsupported database type.
Action: Reconfigure Profitability for one of the supported database types.
Level: 1
Type: ERROR
EPMPCM-00052: POV is required.
Cause: Point of View was not selected.
Action: Select a valid Point of View and retry the operation.
Level: 1
Type: ERROR
EPMPCM-00053: Stage is required.
Cause: The Profitability application does not have the required number of stages defined.
Action: Define an additional stage for the application.
Level: 1
Type: ERROR
EPMPCM-00054: Layer is required.
Cause: A layer was not selected.
Action: Select a layer and retry the operation.
Level: 1
Type: ERROR
EPMPCM-00055: "{0}" should not contain characters: "{1}".
Cause: The characters identified by the message are not valid for the specified field.
Action: Enter values that are valid for the specified field.
Level: 1
Type: ERROR
EPMPCM-00056: Product Schema mismatch detected. Profitability and Cost Management version {0} requires Product Schema version {1}. Detected schema version: {2}. A recent software upgrade may have been incorrectly applied. Please contact your system administrator.
Cause: The profitability product database was not properly upgraded to match the recent software upgrade.
Action: Run the appropriate upgrade script described in the README included with the recent upgrade.
Level: 1
Type: ERROR
EPMPCM-00057: The host name "{0}" for the SHARED_SERVICES_WEBAPP does not match the name for any installed host component. This is a problem with the installation and/or configuration.
Cause: The host name under which profitability was originally configured has changed or no longer accessible.
Action: Reconfigure and/or reinstall profitability.
Level: 1
Type: ERROR
EPMPCM-00058: Unable to run the query.
Cause: The actual template name we use is "linkTemplate.stg" - but ignore the "st" v.s. "stg" difference.
Action: Retry to run the query.
Level: 1
Type: ERROR
EPMPCM-00150: Incident error
Cause: Refer to the server logs for information regarding the error cause.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00151: Error when processing import for Single Source Calculation Rules:
Cause: The import could not connect to the Stage database or could not successfully execute a SQL command.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00152: Error when processing import of Single Source Calculation Rules:
Cause: An error occurred while importing Single Source calculation rules.
Action: Refer to the import and server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00153: Error when processing import for Multi Source Calculation Rules:
Cause: An error occurred during import of Multi Source Calculation Rules.
Action: Refer to the import and server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00154: Error when processing import of Multi Source Calculation Rules:
Cause: An error occurred during import of Multi Source Calculation Rules.
Action: Refer to the import and server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00155: Error when processing input:
Cause: An error occurred due to incorrect input.
Action: Refer to the user doc for more information.
Level: 1
Type: ERROR
EPMPCM-00156: The Application is not enabled and cannot be used. Enable using the Profitability Applications console.
Cause: The application has not pass validation and needs to be enabled for use.
Action: Use the Profitability Applications console to enable the application.
Level: 1
Type: ERROR
EPMPCM-00200: Permission is set to read-only. Contact the system administrator.
Cause: An attempt was made to add a permission to a read-only collection
Action: Contact the system administrator.
Level: 1
Type: ERROR
EPMPCM-00201: No SSO token available in current context.
Cause: Unable to authenticate the user
Action: Contact the system administrator
Level: 1
Type: ERROR
EPMPCM-00202: Failed to get user information from current context.
Cause: A user was not provided.
Action: Login with a valid user.
Cause: Unable to authenticate the user
Action: Contact the system administrator
Level: 1
Type: ERROR
EPMPCM-00203: User is not authorized for this action.
Cause: The user does not have permission to perform this action.
Action: Contact the system administrator
Level: 1
Type: ERROR
EPMPCM-00204: User is not authorized for the following action: {0} {1}.
Cause: The user does not have permission to perform this action.
Action: Contact the system administrator
Level: 1
Type: ERROR
EPMPCM-00205: SSO token is null or empty
Cause: An error occurred while attempting to authenticate the session.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00206: SSL configuration not found in registry. Using non-SSL configuration
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00207: Failed to initialize CSS API
Cause: A security authentication error occurred.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00208: Session has expired and unable to continue with the process. Refer to EPM documentation for changing the Token Timeout setting in Shared Services Security Options section and submit the process again.
Cause: SSO Token has reached timeout
Action: Refer to EPM documentation for changing the Token Timeout setting in Shared Services Security Options section and submit the process again.
Level: 1
Type: ERROR
EPMPCM-00900: Variable Manager error.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00901: Error add variables: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01000: RDB unexpected error.
Cause: An unexpected error occurred during a database operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01001: No destinations found for assignment rule: {0}.
Cause: There are no destinations found for the assignment rule.
Action: Redefine the assignment rule.
Level: 1
Type: ERROR
EPMPCM-01002: Number of stages is limited to {0}.
Cause: The maximum number of stages has been reached.
Action: In order to create a new stage for this application you must first delete an existing stage for this application.
Level: 1
Type: ERROR
EPMPCM-01005: Failed to load application preferences. Application id: {0}.
Cause: The application preferences could not be retrieved for this application.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01006: Error fetching the list for the given query.
Cause: An error has occurred during a database query.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01007: Error fetching the list for the given native query.
Cause: An error has occurred while executing a database query.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01008: Failed to delete installation from RDB. installationId={0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01009: Failed to delete application preference from RDB. preferenceNameId={0}
Cause: The failure to remove the application preference prevents a successful removal of the application
Action: The RDB administrator needs to manually remove the affected rows.
Level: 1
Type: ERROR
EPMPCM-01010: Failed to delete preference name from RDB. preferenceNameId={0}
Cause: The failure to remove the application preference prevents a successful removal of the application
Action: The RDB administrator needs to manually remove the affected rows.
Level: 1
Type: ERROR
EPMPCM-01011: Preference name "{0}" is not found in the database. Check HPM_PREFERENCE_NAME table.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01012: There are more than one property with name "{0}". Using first value only.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01013: Error loading dimension member properties for dimPropId: {0}, cubeType: {1}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01014: Error loading dimension properties for dimId: {0}, cubeType: {1}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01015: Error loading dimension members
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01016: Error loading installation with id:{0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01017: Error loading installations
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01018: Error loading dimension member group with dimension members {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01019: No driver found for rule based assignment source ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01020: No driver found for assignment source ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01021: Error saving importDbConnection ''''{0}''''
Cause: A database error occurred while saving the Import Configuration.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01022: Error saving installation ''''{0}''''
Cause: A database error occurred while saving information about the installation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01023: Error saving preference ''''{0}''''
Cause: A database error occurred while saving a preference.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01024: Duplicate name.
Cause: The Data Entry view name already exists.
Action: Use a different name for the data entry view.
Level: 1
Type: ERROR
EPMPCM-01025: Dimension member group #{0} has more than one associated driver.
Cause: The Dimension Member tuple is associated with more than one driver.
Action: Remove driver associations from the Dimension Member tuple so that only one remains.
Level: 1
Type: ERROR
EPMPCM-01027: More than one driver dimension found
Cause: Multiple dimensions are designated as the Driver dimension for the stage.
Action: Delete the stage and recreate it so that it has only a single Driver dimension.
Level: 1
Type: ERROR
EPMPCM-01029: Exception when trying to open a connection.
Cause: Unable to connect to the profitability database.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01036: Exception when getting application: ''''{0}''''.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01037: Dimension with id "{0}" not found in application.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01038: SQL Error: {0}
Cause: A database error has occurred during the execution of a SQL statement.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01039: Dimension property ''''{0}'''' not found.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01040: Exception when loading Stage Balancing view. More than one view found for application.
Cause: There are multiple references for the Stage Balance view within the Profitability Temporary Objects metadata.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-01041: Exception when getting stage for application ''''{0}''''
Cause: The stages defined for the application are missing or invalid.
Action: Recreate the stages for the application.
Level: 1
Type: ERROR
EPMPCM-01042: The driver selection is not found
Cause: An error occurred while saving or loading a Driver Selection.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01043: The assignment rule is not found
Cause: An error occurred while saving or loading an Assignment Rule.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01044: Mandatory property ''''{0}'''' not found.
Cause: An error occurred during the save or load of a Program Rule.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-01045: Error loading Dimension Member Groups caused by non unique data. Contact Oracle Support to obtain the clean duplicates script.
Cause: An error occurred during the loading of Dimension Member Groups.
Action: Contact Oracle Support to obtain the clean duplicates script.
Level: 1
Type: ERROR
EPMPCM-01046: Database version: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01047: Database schema upgrade required.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01048: Skipping database schema upgrade.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01049: Performing schema upgrade.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01050: Expected database version: {0} matches current version: {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01051: Expected database version: {0} is less than current version: {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01052: Expected database version: {0} is greater than current version: {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01053: SQL Command: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-01054: Persistence exception caught.
Cause:
Action:
Level: 1
Type: ERROR
EPMPCM-01055: Unable to disconnect.
Cause:
Action:
Level: 1
Type: ERROR
EPMPCM-01056: Conversion Error.
Cause:
Action:
Level: 1
Type: ERROR
EPMPCM-01057: Connection Exception:
Cause:
Action:
Level: 1
Type: ERROR
EPMPCM-01058: Failed to convert float value, Exception:
Cause:
Action:
Level: 1
Type: ERROR
EPMPCM-02000: Unexpected error from Essbase.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02001: Essbase Database Not Found.
Cause: The Essbase application could not be found.
Action: If the Essbase application was removed you will need to recreate it using the appropriate deploy database operation from within Profitability.
Level: 1
Type: ERROR
EPMPCM-02002: Cannot connect to Essbase Server.
Cause: The Essbase server cannot be accessed.
Action: Restart the Essbase server and verify that it is accessible.
Level: 1
Type: ERROR
EPMPCM-02003: Error disconnecting from Essbase Server.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02004: Error setting base member ''''{0}'''' for member: ''''{1}''''
Cause: An error occurred during an update of the essbase database.
Action: Verify that the dimension for the member is correct in the cube.
Level: 1
Type: ERROR
EPMPCM-02005: Application or database name is null
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02007: Could not create alias table ''''{0}''''
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02008: Error creating application ''''{0}'''' on the Essbase server
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02009: Unexpected attribute type: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02010: Error creating database ''''{0}'''' on the Essbase server
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02011: Error creating dimension ''''{0}''''
Cause: An error occurred while trying to create a dimension in Essbase.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02012: Error deleting application ''''{0}'''' in Essbase
Cause: An error occurred while trying to delete an Essbase application.
Action: Verify that the Essbase application is not locked. You may also need to restart the Essbase service. Refer to the server logs for more information
Level: 1
Type: ERROR
EPMPCM-02013: Error associating base dim ''''{0}'''' to attribute dimension ''''{1}''''
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02014: Error creating attribute dimension ''''{0}''''
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02015: Error saving outline
Cause: An error occurred while saving an Essbase outline.
Action: Verify that the Essbase outline is not locked. You may also need to restart the Essbase service. Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02016: Error getting list of applications from the server
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02017: Error getting list of databases from the server
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information
Level: 1
Type: ERROR
EPMPCM-02018: Error opening outline
Cause: An error occurred while opening an Essbase outline.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02019: Outline not set
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02020: Cannot set outline auto configure property
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02022: Error copying object ''''{0}'''' to the server.
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02023: Error deleting object ''''{0}''''
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02024: Error running calculation script ''''{0}''''
Cause: An error occurred while running a profitability calculation script.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02025: Error loading file ''''{0}'''' from server
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02027: Error validating script: ''''{0}''''
Cause: The calculation script has errors.
Action: Verify the contents of the calculation script located on the Essbase server. Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02028: Error executing script: ''''{0}''''
Cause: An error occurred during the execution of a calculation script.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02031: Error getting information for file ''''{0}'''' of type ''''{1}''''
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02032: Cannot remove Essbase Databases for application removal.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02033: Failed to set cube as active, error code {0}
Cause: An error has occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02034: Failed to begin update in Essbase, error code {0}
Cause: An error has occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02035: Failed to finish update in Essbase, error code {0}
Cause: An error has occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02036: Failed to send data to Essbase, error code {0}
Cause: An error has occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02037: Not connected to Essbase
Cause: Unable to access the Essbase server.
Action: Verify that the Essbase server is available and restart it if necessary. Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02038: Error running MDX query.
Cause: An error occurred while running an MDX query in Essbase.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02039: Mdx result contains more than one value
Cause: An MDX query returned an invalid result.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-02040: Error setting root member to dynamic calc for dimension {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02041: Error setting ess dimension in MDBDimension
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02042: Error setting root member formula: {0} for dimension: {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02043: Error setting hierarchy {0} to dynamic
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02044: Error setting alias for root member of dimension: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02045: Error setting UDA: {0} for root member of dimension: {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02046: Error setting consolidation type for member: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02047: Error setting formula for member: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02048: Error adding child: {0} to member: {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02049: Error setting member solve order for member: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02050: Error updating property values for member: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02051: Error setting dynamic calc for member: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02052: Error setting member property share option to {0} for member: {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02053: Error getting parent name
Cause: An error occrred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02054: Possible duplicate attribute member: {0} found in the same attribute dimension: {1}. This is not supported.
Cause: Multiple members in the Attribute dimension have the same name.
Action: Remove the redundant members in the Attribute dimension from the source so that each member has a unique name. Then redploy the profitability application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-02055: Appropriate attribute member: {0} not found in the attribute dimension: {1}
Cause: The Essbase outline has invalid references.
Action: Verify that the source profitability application dimension model is valid and redeploy. Then retry the operation.
Level: 1
Type: ERROR
EPMPCM-02056: Error associating attribute member: {0} to base member: {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02057: Error setting alias for member: {0}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02058: Error setting UDA: {0} for member: {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02059: Error setting two pass calc to {0} for member {1}
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02060: Error setting hierarchy type for member: {0} to: {1} | --------------------------
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02061: Cube is null
Cause: An error occurred while accessing the Essbase cube
Action: Verify that Essbase is available and restart if necessary. Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02062: An error occurred during outline creation
Cause: An error occurred while creating the Essbase outline.
Action: Verify that the outline for the application is not locked within Essbase and restart Essbase if necessary. Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02063: Traceability error
Cause: The Traceability graph generated an invalid MDX query.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-02064: Error deleting alias tables
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02065: Error deleting alias tables
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02066: Error cleaning dimension
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02067: Error getting Traceability nodes.
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02068: Error getting Traceability stages.
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02069: Error loading data into Essbase.
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02070: Error trying to connect to Essbase.
Cause: An error occurred while trying to connect to Essbase
Action: Verify that Essbase is available and restart the Essbase service if necessary.
Level: 1
Type: ERROR
EPMPCM-02071: Error adding child: {0} to root member of dimension: {1}.
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02072: Not possible to restore data. Some dimension was removed from Essbase cube or new dimension was added to Essbase cube after last backup.
Cause: A dimension was added or removed from the Essbase cube after the most recent backup.
Action: Redeploy the Essbase cube from within Profitability so that it matches the Profitability dimension model.
Level: 1
Type: ERROR
EPMPCM-02073: Incorrect file name : "{0}".
Cause: An error occurred during an Essbase operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02074: Incorrect outline structure. Some of dimensions should be dense and have actual size less or equal then {0} for successful export.
Cause: The Dimension Storage Type for some dimensions in the outline is incorrect.
Action: Correct the Dimension Storage Type for dimensions and redeploy the dimension model to profitability. Then retry the operation.
Level: 1
Type: ERROR
EPMPCM-02075: Number of errors that occurred during loading data in cube "{0}" of application "{1}" equals {2}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02076: Import failed. Essbase cube: "{0}"; Essbase application: "{1}".
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02077: Export failed. Essbase cube: "{0}"; Essbase application: "{1}".
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02078: Error deleting Essbase artifacts: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02079: An attempt to get application locale has failed. Essbase application: "{0}".
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02080: Export has not been performed. The reporting cube has no data. Essbase cube: "{0}"; Essbase application: "{1}".
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02081: Import has not been performed. Data file is not found. Essbase cube: "{0}"; Essbase application: "{1}".
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02082: Artifacts deletion has not been performed. Data file is not found. Essbase cube: "{0}"; Essbase application: "{1}".
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-02084: Essbase Registry error.
Cause: The Essbase Registry is either invalid or not available.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02085: Error setting comment for member: {0} to: {1}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02100: Essbase error: {0}.
Cause: An Essbase exception occurred.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-02110: Concurrent Calculation is on but calculation scripts were generated for non-concurrent calculation. Regenerate calculation scripts or turn off Concurrent Calculation.
Cause: There is an incompatibility between the Concurrent Calculation option and the Calculation Script generation
Action: Regenerate the Calculation Scripts or turn off Concurrent Calculation.
Level: 1
Type: ERROR
EPMPCM-02111: Concurrent Calculation is off but calculation scripts were generated for concurrent calculation. Re-generate calculation scripts or turn on Concurrent Calculation.
Cause: The Concurrent Calculation option is not compatible with the calculation script generation.
Action: Re-generate calculation scripts or turn on Concurrent Calculation.
Level: 1
Type: ERROR
EPMPCM-02112: The Essbase database for this application does not exist. Go to Manage Database and deploy the Essbase database before attempting this operation.
Cause: The Essbase application could not be found.
Action: If the Essbase application was removed you will need to recreate it using the appropriate deploy database operation from within Profitability.
Level: 1
Type: ERROR
EPMPCM-03000: Web unknown error.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03001: Missing action/instance ID: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03002: Command name was not found in catalogue. Expected command name: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03003: Default catalogue not found.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03004: No command name available in the context.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03005: Starting Profitability and Cost Management v. {0} (build {1}).
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-03011: No POV dimension member group.
Cause: The selected Point of View does not exist. It is possible that it was deleted in a separate session.
Action: Select a different point of view.
Level: 1
Type: ERROR
EPMPCM-03016: Could not perform any operation. Please contact EPMA or HPM system administrator for help to take next step accordingly or deploy again.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03017: Method ''''{0}'''' failed to handles a throwable: {1}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03018: Cannot load application information. InstanceId: {0}
Cause: The application being accessed does not exist within the Profitability database.
Action: Select a different Profitability application.
Level: 1
Type: ERROR
EPMPCM-03019: Error executing 'RenderResponse' command
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03020: WebResponse serialization failed
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03021: DynaType instance isn''t found in DynaTypeRegistry: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03022: Wrong form object. Method name to dispatch is not specified: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03023: Web error : execute recursive
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03024: Could not find dispatch: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03025: No http session available in the context
Cause: There is a network or other system error that is preventing communication between the client and the server.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03026: The context parameter cannot be NULL
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03027: Image could not be located: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03028: Rolling back current transaction because of an exception
Cause: A database exception occurred.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03029: Registry exception occurred
Cause: There was an error with the Hyperion registry.
Action: Verify Hyperion products are installed and configured properly using the Configurator.
Level: 1
Type: ERROR
EPMPCM-03030: HSS Registry Helper exception.
Cause: An exception has occurred while accessing the Shared Services registry.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03031: Exception while processing errors during LCM import\export.
Cause: An error has occurred during LCM import or export.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-03032: Profitability service start up complete and application is running.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-03033: Removing inactive serialization execution rights
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-03034: Finished removing serialization execution rights.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-03035: Error occurred while removing serialization execution rights
Cause: An issue with the database set up and configuration
Action: Review specific message and contact the DBA for your system.
Cause: Internal implementation error.
Action: Contact Oracle Support and provide this error message.
Level: 1
Type: ERROR
EPMPCM-03036: Application registration required for all applications
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-03037: All applications registered successfully.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-03038: Critical error detected while registering current application.
Cause: A serious and unkown error occurred
Action: Send the HPCM log file to Oracle Support
Level: 1
Type: ERROR
EPMPCM-03039: Aborting automated application registration. Please use Profitability Applications Console to reregister applications.
Cause: The automated application reregistration did not complete successfully
Action: Use Profitability Applications Console to reregister each application.
Level: 1
Type: WARNING
EPMPCM-03040: Registering application {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04000: Unexpected error in business logic.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-04002: Driver selection already exists.
Cause: The Driver selection is already defined for the dimension tuple.
Action: No action is necessary.
Level: 1
Type: ERROR
EPMPCM-04003: Unsupported xml encoding in assignment rule.
Cause: The assignment rule is invalid.
Action: Delete the assignment rule and recreate it.
Level: 1
Type: ERROR
EPMPCM-04004: Application does not exist: {0}.
Cause: The selected profitability application does not exist.
Action: Choose a different profitability application for the operation.
Level: 1
Type: ERROR
EPMPCM-04005: Stage id {0} is not found.
Cause: The selected stage does not exist. It was possibly deleted in a separate session.
Action: Navigate away from the page and then return to refresh the stages. It may also be necessary to logout of the profitability application and then log back in.
Level: 1
Type: ERROR
EPMPCM-04007: Driver formula is missing.
Cause: The formula for the driver is empty or invalid.
Action: Review the driver formula for errors.
Level: 1
Type: ERROR
EPMPCM-04008: Validation failed for the following rules: {0}.
Cause: The error cause is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-04009: The formula provided has incorrect number of variables. Expected: {0}, found: {1}.
Cause: The formula has an incorrect number of variables.
Action: Edit the formula to remove the invalid variables.
Level: 1
Type: ERROR
EPMPCM-04010: Template contains unequal variables with the same name: {0} and {1}.
Cause: The formula contains 2 variables of the same name but with different attributes.
Action: Edit the formula to remove the invalid variables.
Level: 1
Type: ERROR
EPMPCM-04011: Dimension member id {0} is not found.
Cause: A referenced Dimension Member no longer exists.
Action: Redeploy the application.
Level: 1
Type: ERROR
EPMPCM-04012: Driver ''''{0}'''' has no layer selected.
Cause: The defined driver is invalid.
Action: Delete and recreate the driver.
Level: 1
Type: ERROR
EPMPCM-04013: Incorrect filter type: {0}
Cause: A Driver filter is invalid.
Action: Delete and recreate the filter.
Level: 1
Type: ERROR
EPMPCM-04014: It is not allowed to start import for target application with appId = {0} in the context of application with appId = {1}
Cause: You are trying to run an import for an application that is different than the application in which you are currently active
Action: Navigate to the appropriate application and run the import from there.
Level: 1
Type: ERROR
EPMPCM-04015: More than one measure dimension found.
Cause: The dimension model for this application has multiple dimensions of type Measure.
Action: Edit the model source for this application and remove the redundant Measure dimensions. Then redeploy the application.
Level: 1
Type: ERROR
EPMPCM-04016: No Valid Assignment Value.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04017: Error creating SQL Server document.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04018: Error creating Oracle document.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04019: DB Vendor Platform: {0} not supported.
Cause: You are running profitability against a database type that is not supported.
Action: Reinstall and configure profitability to run on a supported database type.
Level: 1
Type: ERROR
EPMPCM-04021: Driver id {0} is not found.
Cause: The selected Driver no longer exists. It is possible that it was deleted in a separate session.
Action: Select a different driver for the operation.
Level: 1
Type: ERROR
EPMPCM-04022: Stage Rule id {0} is not found.
Cause: The selected Stage Rule no longer exists. It is possible that it was deleted in a separate session.
Action: Select a different Stage Rule for the operation.
Level: 1
Type: ERROR
EPMPCM-04023: Import of assignments completed successfully for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04024: Error when processing import of assignments.
Cause: An error occurred during the import of Assignments.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-04025: Exception when trying to clean temporary staging in product database for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04026: Copy of assignments from staging to temporary staging in product database started for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04027: Copying assignments from staging to temporary staging in product database completed successfully for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04028: Begin update of status column from temporary staging in product database to staging database, for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04029: Updation of status column from temporary staging in product database to staging database completed successfully for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04030: Invoking native procedure to process import of assignments for execution: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04031: Error when processing import of assignments for execution: {0}. Exception message returned from database is: {1}
Cause: An exception occurred during the import of assignments.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-04032: Bulk copy of assignments data completed successfully for execution: {0}, when copying POV information.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04037: Import Configuration Name is ''''{0}''''.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04038: Begin processing import artifact: ''''{0}''''.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04039: Done processing import artifact: ''''{0}''''.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-04040: Assignment is not found.
Cause: The selected Assignment no longer exists. It is possible that it was deleted in another session.
Action: Select a different assignment for the operation.
Level: 1
Type: ERROR
EPMPCM-04041: This assignment rule was used in Bulk Edit to create driver exceptions or assignment rule selections. It cannot be deleted until those references are deleted first. You can use the assignment rule again in a bulk edit deletion operation to remove them if they are no longer needed.
Cause: The selected assignment rule was used to create driver exceptions or assignment rule selections.
Action: Delete the driver exceptions and assignment rule selections associated with this Assignment Rule before trying to delete it again.
Level: 1
Type: ERROR
EPMPCM-04042: The point of view you are trying to edit does not exist.
Cause: The selected point of view no longer exists. It is possible that it was deleted in a separate session.
Action: Select a different point of view for your operation.
Level: 1
Type: ERROR
EPMPCM-04043: Unable to proceed with import because 2 stages have identical dimensions but with a different dimension order.
Cause: Unable to proceed with import because 2 stages have identical dimensions but with a different dimension order.
Action: Verify and change the dimension member in the stages
Level: 1
Type: ERROR
EPMPCM-05001: Measure ''''{0}'''' is not found
Cause: The selected Measure dimension name does not exist in the model.
Action: Choose a different Measure dimension name for the operation.
Level: 1
Type: ERROR
EPMPCM-05002: Stage Balance View does not exist for application ''''{0}''''.
Cause: The required permissions have not been granted to the product schema.
Action: Please review the Product Schema section of the HPCM Administrators Guide.
Cause: The tables registered within the Model Data Schema are defined incorrectly.
Action: Please the Model Data Repository validation to identify the source of the issue.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-05003: Error creating Stage Balancing Report query.
Cause: An error occurred while creating the Stage Balancing Report query.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-05004: ERROR: Unable to create Stage Balance View due to inconsistent Data Precision and Scale for Measure columns on the source table ''{0}''.
Cause: The Measure columns on the source table have inconsistent data precision and scale.
Action: Alter the source table so that the Measure columns have consistent data precision and scale and then rerun the operation.
Level: 1
Type: ERROR
EPMPCM-05005: ERROR: Unable to create Stage Balance View: The Source Stage table ''''{0}'''' requires the SELECT privilege ''with grant option''.
Cause: The source stage table in the Data Model schema has not been granted to the Profitability product schema with the grant option.
Action: Grant select on the source stage table in the Data Model schema to the profitability Product schema with grant option.
Level: 1
Type: ERROR
EPMPCM-05006: Warning: Potential problem for Stage Balance View creation: The HPCM Product User may not have the ''''{0}'''' privilege on the Model Data schema.
Cause: The profitability Product schema does not have the required privilege for the Model Data schema.
Action: Grant the privilege to profitability Product schema and retry the operation.
Level: 1
Type: ERROR
EPMPCM-05007: Warning: Potential problem for Stage Balance View creation: The HPCM Product User may not have the Create View privilege.
Cause: The profitability Product schema does not have the Create View privilege.
Action: Grant the Create View privilege to the Product schema.
Level: 1
Type: ERROR
EPMPCM-05008: ERROR: Cannot calculate Destination Measure Balances.
Cause: A database error occurred while attempting to create the Stage Balance view.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-05009: Point of View was deleted by another user
Cause: Trying to delete POV group which is not present
Action: Refresh the screen
Level: 1
Type: ERROR
EPMPCM-05010: The query generated for the rule is too large for Essbase
Cause: Trying to query a rule that is too large for Essbase
Action: Select the Summary Only option
Level: 1
Type: ERROR
EPMPCM-05011: The query requires at least two context dimensions
Cause: The driver basis has overridden all dimensions, including POV and system dimensions
Action: Do not override at least 2 dimensions to run this report
Level: 1
Type: ERROR
EPMPCM-06000: Validation failed.
Cause: The cause of the error is unknown.
Action: Contact Oracle support for more information
Level: 1
Type: ERROR
EPMPCM-06001: Assignment rule validation successful.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06002: Stage is not found: {0}.
Cause: The Assignment Rule definition is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06003: Dimension is not found: {0}.
Cause: The Assignment Rule definition is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06004: Dimension member is not found: {0}.
Cause: The Assignment Rule definition is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06005: Attribute is not found: {0}.
Cause: The Assignment Rule definition is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06006: UDA is not found: {0}.
Cause: The Assignment Rule definition is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06007: Assignment rule validation started.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06008: Assignment rule validation finished.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06009: Dimension member does not exist in the destination dimension at level 0. Dimension Member: {0}. Destination Dimension : {1}.
Cause: A Dimension Member referenced in the Assignment Rule no longer exists.
Action: Resave the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06066: Invalid assignment rule ''''{0}'''' selection. Dimension member does not exist in the destination dimension at level 0. Dimension Member: {1}. Destination Dimension : {2}.
Cause: A Dimension member referenced in the Assignment Rule no longer exists.
Action: Resave the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06067: Same as source dimension ''''{0}'''' is not found in the previous stages.
Cause: The Assignment Rule is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06010: Dimension is not part of the source stage: {0}. Dimension Name: {1}.
Cause: The Assignment Rule is invalid.
Action: Delete and re-create the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06011: Unexpected number of dimensions: {0}. Destination stage has {1} dimension(s).
Cause: The Assignment Rule is invalid.
Action: Delete and recreate the Assignment Rule.
Level: 1
Type: ERROR
EPMPCM-06042: Assignment rule for the first stage is not allowed.
Cause: The Assignment Rule is defined on the first stage.
Action: Delete the Assignment Rule and recreate it an a stage that is not the first stage.
Level: 1
Type: ERROR
EPMPCM-06012: Point of View already exists.
Cause: The selected point of view already exists.
Action: No action is necessary.
Level: 1
Type: ERROR
EPMPCM-06013: Duplicate assignment.
Cause: The selected assignment already exists.
Action: No action is necessary.
Level: 1
Type: ERROR
EPMPCM-06014: Duplicate driver name: {0}
Cause: The driver already exists.
Action: No action is necessary.
Level: 1
Type: ERROR
EPMPCM-06015: Invalid assignment: destination cannot be the same as source.
Cause: The source and destination stage for an assignment cannot be the same stage.
Action: Select a different destination or source stage and save the assignment.
Level: 1
Type: ERROR
EPMPCM-06016: Assignment rule selection cannot be saved. Cause: The source node context selected has explicit assignments defined.
Cause: The selected source node context has explicit assignments.
Action: Delete the explicit assignments for the selected source node and then save the Assignment.
Level: 1
Type: ERROR
EPMPCM-06017: Assignment cannot be saved. Cause: There are assignment rule selections already defined.
Cause: Assignment Rule Selections and explicit Assignments cannot both exist for the same Stage, Dimension Members and Point of View combination.
Action: Remove the Assignments or Assignment Rule Selections and re-try the save.
Level: 1
Type: ERROR
EPMPCM-06018: Duplicate assignment rule name: {0}
Cause: The Assignment Rule name already exists.
Action: Use a different name and try the save again.
Level: 1
Type: ERROR
EPMPCM-06019: Dimension member group #{0} has more than one associated driver.
Cause: The dimension tuple has multiple associations for the same Driver name.
Action: Remove the redundant driver associations for the dimension member tuple.
Level: 1
Type: ERROR
EPMPCM-06020: Duplicate stage name: {0}
Cause: The stage name already exists.
Action: Choose a different name for the stage.
Level: 1
Type: ERROR
EPMPCM-06021: Stage does not have dimensions: {0}
Cause: A Stage must have at least one dimension to be valid.
Action: Add at least one dimension to the stage before attempting to save the stage definition.
Level: 1
Type: ERROR
EPMPCM-06022: Validation of staging credentials failed.
Cause: The connection information to the stage schema is invalid.
Action: Provide valid connection information to the stage schema and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06044: Duplicate table name: {0}
Cause: The table name is already registered for the profitability application.
Action: Choose a different name for the table registration.
Level: 1
Type: ERROR
EPMPCM-06045: Duplicate calculation rule name "{0}""""
Cause: The calculation rule name already exists.
Action: Choose a different name for the Calculation Rule.
Level: 1
Type: ERROR
EPMPCM-06046: Validation of calculation rule "{0}" failed. The length of description should be less than 255 characters
Cause: The description for the Calculation Rule is greater than 255 characters.
Action: Limit the description to less than or equal to 255 characters for the Calculation Rule.
Level: 1
Type: ERROR
EPMPCM-06047: Validation of calculation rule "{0}" failed. The length of tag should be less than 255 characters
Cause: The import file has illegal tags for the calculation rule. This can occur when the import file has been manually modified.
Action: Re-export the calculation rule from the source application and then try the import again.
Level: 1
Type: ERROR
EPMPCM-06048: Validation of calculation rule "{0}" failed. The calculation sequence should be greater than 1 and less than or equal to 9999.
Cause: The calculation sequence for the calculation rule in the import file has invalid values. This can occur when the import file is manually modified.
Action: Re-export the calculation rule from the source application and re-try the import.
Level: 1
Type: ERROR
EPMPCM-06049: Validation of calculation rule "{0}" failed. The pov dimension members are not valid.
Cause: The point of view selected for the Calculation Rule does not exist.
Action: Create the missing point of view and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06068: Unknown calculation rules type "{0}"
Cause: The Calculation Rule defined in the import file is invalid.
Action: Export the Calculation Rules from the source system again and retry the import.
Level: 1
Type: ERROR
EPMPCM-06069: Validation of calculation rule "{0}" failed. The driver "{1}" does not exist.
Cause: The driver referenced in the Calculation Rule does not exist.
Action: Create the driver and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06070: Validation of calculation rule "{0}" failed. The source assignment rule "{1}" is invalid.
Cause: The source assignment rule referenced in the Calculation Rule does not exist.
Action: Create the source assignment rule and re-try the operation.
Level: 1
Type: ERROR
EPMPCM-06071: Validation of calculation rule "{0}" failed. The destination assignment rule "{1}" is invalid.
Cause: The destination assignment rule referenced in the Calculation Rule does not exist.
Action: Create the destination assignment rule and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06072: Validation of calculation rule "{0}" failed. There are more than 5 source assignment rules
Cause: The Calculation Rule references more than 5 source assignment rules.
Action: Remove the extra source assignment rules so that a maximum of 5 remain for the Calculation Rule and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-06073: Validation of calculation rule "{0}" failed. There are more than 5 destination assignment rules
Cause: The Calculation Rule references more than 5 destination assignment rules.
Action: Remove the extra source assignment rules so that a maximum of 5 remain for the Calculation Rule and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-06074: Validation of calculation rule "{0}" failed. The driver type "{1}" can not be assigned.
Cause: The Driver type of the assigned driver is not Calculation Measure
Action: Remove the driver from the Calculation Rule.
Level: 1
Type: ERROR
EPMPCM-06075: The calculation rule "{0}" will not be imported as it already exists.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06076: The import of calculation rule "{0}" failed because it contains two or more drivers which has the same destination measure member.
Cause: The Calculation Rule in the import file is associated with multiple drivers with the same measure member.
Action: In the source for the import file verify that the Calculation Rule is defined correctly, export the Calculation Rule and then retry the import.
Level: 1
Type: ERROR
EPMPCM-06078: The validation of calculation rule "{0}" failed because it contains more than 5 drivers.
Cause: The Calculation Rule contains more than 5 drivers.
Action: Remove the extra drivers and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06079: The POV does not exist.
Cause: The selected point of view does not exist. It is possible that it was deleted in another session.
Action: Choose a different point of view and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06080: The artifact "{0}" is empty.
Cause: The source import file has an entry for an empty artifact.
Action: Export the artifacts from the source system and then retry the import.
Level: 1
Type: ERROR
EPMPCM-06081: The calculation rule ''''{0}'''' cannot be saved. A calculation rule of type ''Calculated Measures'' can not refer to the drivers which write to the same destination measure.
Cause: The Calculation Rule references multiple drivers that write to the same destination measure.
Action: Edit the calculation rule so that each referenced driver writes to a different destination measure and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-06091: Given Rule is null
Cause: Received an empty Rule object and cannot continue with the process
Action: Review the hpcm.log file for actual cause of the error
Level: 1
Type: ERROR
EPMPCM-06092: Calculation Rule does not exist. It may have been deleted in another session.
Cause: It is possible that the Calculation Rule has been deleted by another user
Action: Refresh the screen and try the operation again
Level: 1
Type: ERROR
EPMPCM-06094: Given Target POV is null
Cause: Received an empty POV object and cannot continue with the process
Action: Review the hpcm.log file for actual cause of the error
Level: 1
Type: ERROR
EPMPCM-06095: Rule Set does not exist. It may have been deleted in another session.
Cause: It is possible that the Rule Set has been deleted by another user
Action: Refresh the screen and try the operation again
Level: 1
Type: ERROR
EPMPCM-06096: The calculation Rule Set "{0}" already exists.
Cause: The given Rule Set name already exists for the POV
Action: Provide another Rule Set name and resubmit the operation
Level: 1
Type: ERROR
EPMPCM-06097: Given Rule Set is null
Cause: Received an empty Rule Set object and cannot continue with the process
Action: Review the hpcm.log file for actual cause of the error
Level: 1
Type: ERROR
EPMPCM-06083: Validation failed.
Cause: The same as source validation failed for the Assignment Rule.
Action: Alter the assignment rule definition to pass validation.
Cause: Unable to validate the Assignment Rule.
Action: Alter the assignment rule definition to pass validation.
Level: 1
Type: ERROR
EPMPCM-06043: Cannot open contribution report from stage "{0}" to "{0}" because the stage does not support intrastage allocations.
Cause: The stage has incorrect intrastage designation.
Action: Edit the stage so that it has the correct intrastage designation.
Level: 1
Type: ERROR
EPMPCM-06050: Validation of driver "{0}" failed. Driver basis type is null or empty.
Cause: The Driver does not have a basis type.
Action: Edit the Driver so that it has a basis type and save it. Then retry the operation.
Level: 1
Type: ERROR
EPMPCM-06061: There are assignments of the rule on the stage {0}. You must set a stage that occurs after the stage {0}.
Cause: You are trying to change the stage for the assignment rule to a stage that is not allowed.
Action: Use a different stage with an order that occurs after the source stage and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06064: Column used in a data filter does not have a valid registration: {0}
Cause: The data filter on the assignment rule is invalid.
Action: Delete and recreate the data filter for the assignment rule.
Level: 1
Type: ERROR
EPMPCM-06065: Duplicate Rule name. Calculation Program Rule name {0} already exists for the current Point of View
Cause: Saving a Rule with a name that already exists for another Rule in the same Point of View.
Action: Change the Rule name.
Level: 1
Type: ERROR
EPMPCM-06102: Duplicate Rule Set name. Calculation Program Rule Set {0} already exists for this point of view
Cause: Saving a Rule Set with a name that already exists for another Rule Set in the same point of view.
Action: Change the Rule Set name.
Level: 1
Type: ERROR
EPMPCM-06200: Duplicate import configuration name: "{0}" in application: {1}
Cause: The import configuration name already exists for the application.
Action: Choose a different name for the import configuration.
Level: 1
Type: ERROR
EPMPCM-06300: No dimensions selected for the Model View.
Cause: At least one dimension must be selected to create a model view
Action: Select the dimension before saving the model view
Level: 1
Type: ERROR
EPMPCM-06301: Model View has invalid dimension : {0}
Cause: The dimension that was used in the Model View has been deleted
Action: Review and correct the Model View information
Level: 1
Type: ERROR
EPMPCM-06303: Model View is null.
Cause: Received an empty Model View object and cannot continue with the process
Action: Review the hpcm.log file for actual cause of the error
Level: 1
Type: ERROR
EPMPCM-06305: Model View with name {0} already exists for the current application.
Cause: Saving a Model View with a name that already exists for another Model View in the same Application
Action: Change the Model View name.
Level: 1
Type: ERROR
EPMPCM-06400: No POV dimension member group found.
Cause: The selected point of view does not exist.
Action: Select a different point of view.
Level: 1
Type: ERROR
EPMPCM-06401: Source measures dimension member is null or empty.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-06402: Source measures dimension member not found.
Cause: The source measure dimension member does not exist. It is possible that it was deleted from the model.
Action: Retry the operation.
Level: 1
Type: ERROR
EPMPCM-06501: The dimension "{0}" no longer exists in the application.
Cause: A dimension that existed when the Smart View query was created no longer exists.
Action: Edit the Smart View query to remove the invalid dimension and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06502: The member "{0}" no longer exists in the dimension "{1}".
Cause: A dimension member referenced in the Smart View query no longer exists.
Action: Remove the member from the Smart View query and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06503: The query does not contain any selection for the dimension "{0}".
Cause: A dimension in the Smart View query has no member selection.
Action: Select a member for the dimension and retry the operation.
Level: 1
Type: ERROR
EPMPCM-06504: Duplicate query name: {0}.
Cause: The Smart View query name already exists.
Action: Choose a new name.
Level: 1
Type: ERROR
EPMPCM-06505: Error getting measures or allocation type dimension
Cause: The measures or allocation type dimension doesn't exist for this application
Action: Validate and redeploy your application in EPMA
Level: 1
Type: ERROR
EPMPCM-06601: There are no dimensions of type "Point of View" defined for this application. An application must have at least 1 Point of View dimension.
Cause: The dimension model being deployed does not have any Point of View dimensions.
Action: Add at least one Point of View dimension to the model source and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06602: Point of View dimension order is incorrectly defined. Point of View dimensions must have a POV dimension order of 1-4 with out any gaps.
Cause: The Point of View dimensions in the model view source do not have consecutive order values.
Action: Edit the order for the Point of View dimensions in the model source so that the order is consecutive from 1-4 with no gaps.
Level: 1
Type: ERROR
EPMPCM-06603: The "{0}" dimension does not have the member NoMember as the last generation 2 member.
Cause: The last generation 2 member of the dimension is not named NoMember.
Action: Edit the dimension so that the last generation 2 member is named NoMember and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06604: There are no business dimensions defined for this application.
Cause: The application being deployed does not have any dimensions designated as business dimensions.
Action: Edit the model source so that there is at least one business dimension for the application and redeploy.
Level: 1
Type: ERROR
EPMPCM-06605: The dimension "{0}" has shared or duplicate members inside the primary hierarchy. The duplicate member names are "{1}"
Cause: The first generation 2 member of the dimension is considered the primary hierarchy and cannot have any shared or duplicate members.
Action: Edit the first generation 2 member of the dimension so that there are no shared or duplicate members and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06622: The dimension "{0}" has duplicate members. The duplicate member names are "{1}"
Cause: The Master cube has duplicate dimension member names for a dimension.
Action: Remove the duplicate member names and re-try the application deploy.
Level: 1
Type: ERROR
EPMPCM-06606: Dimension "{0}" was selected to deploy but does not have a DIMTYPE user defined attribute specified for it.
Cause: You have selected a dimension to deploy that does not have a Dimension Type designated for it in the Essbase Master cube.
Action: Assign one of the allowed Dimension Type values as a User Defined Attribute for the dimension and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06607: Application "{0}" does not have a single Measures type dimension.
Cause: The application being deployed does not have a dimension of type Measure.
Action: Edit the Essbase Master cube so that one dimension has been designated with the Measure Dimension Type and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06608: Application "{0}" does not have a single Allocation Type dimension.
Cause: The application being deployed does not have a dimension of type Allocation Type.
Action: Edit the Essbase Master cube so that one dimension has been designated with the Allocation Type Dimension Type and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06609: Application with name "{0}" already exists.
Cause: The application name being deployed already exists.
Action: Choose a different application name for the application deploy.
Level: 1
Type: ERROR
EPMPCM-06610: Invalid application name: "{0}".
Cause: The application name selected for deploy is null or blank.
Action: Specify a non-blank application name for the deploy.
Level: 1
Type: ERROR
EPMPCM-06611: Multiple Point of View dimensions share the same Point of View dimension order.
Cause: Multiple dimensions within the Essbase Master cube have been designated with the same Point of View order.
Action: Verify that each of the Point of View dimensions in the Essbase Master cube has a unique order value as part of the Dimension Type assigned to it and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06612: The Point of View dimension "{0}" is already deployed with a Point of View order number that does not match the number in this deploy.
Cause: The Point of View order for the Dimension in the Essbase Master cube does not match the Point of View order of the Dimension when it was originally deployed.
Action: Edit the Point of View order for the Dimension in the Essbase Master cube so that it matches the order of the dimension that is deployed.
Level: 1
Type: ERROR
EPMPCM-06613: Dimension "{0}" does not have a user defined Dimension Type attribute defined for it in Essbase.
Cause: The Dimension selected to be deployed does not have a Dimension Type designation.
Action: Assign the Dimension a Dimension Type User Defined Attribute in the Essbase Master cube and redeploy the application.
Level: 1
Type: ERROR
EPMPCM-06614: The deployed Dimension Type for Dimension "{0}" does not match the dimension type of this dimension in the source (Essbase Master Cube or file).
Cause: The Dimension Type of the Dimension in the source (either Essbase Master Cube or file) does not match the Dimension Type in the deployed application.
Action: Edit the Dimension in the source so that the assigned Dimension Type matches the Dimension Type in the deployed application.
Level: 1
Type: ERROR
EPMPCM-06615: Dimension "{0}" is not valid in this application because dimensions of type ''AllocationType'' are not valid in an application of type ''Profitability-Detail''.
Cause: You have selected a Dimension of type Allocation Type to deploy for a Detailed Profitability application.
Action: Do not select Dimensions of type Allocation Type when deploying a Detailed Profitability application.
Level: 1
Type: ERROR
EPMPCM-06616: The following Point of View members became non-Level 0 but are used in defined Point of Views: "{0}". Please delete the Point of Views before redeploying.
Cause: Members in Point of View dimensions in the Essbase Master cube have changed level such that they invalidate existing Point of Views defined in the profitability application.
Action: Delete the Point of Views defined in the profitability application that reference members that have changed level in the Essbase Master cube.
Level: 1
Type: ERROR
EPMPCM-06617: The following Point of View members are being deleted but are used in defined Point of Views: "{0}". Please delete the Point of Views before redeploying.
Cause: Members in Point of View dimensions in the Essbase Master cube that are referenced in existing Point of Views in the application have been removed.
Action: Delete the Point of Views defined in the profitability application that reference members that have been removed in the Essbase Master cube.
Level: 1
Type: ERROR
EPMPCM-06618: Cannot delete dimension members "{0}" which belong to the source or destination measures dimension and where there are existing drivers defined that reference one of those members. To delete these members, first delete all existing Drivers that reference the members and then redeploy the application.
Cause: Measure members referenced in drivers have been removed from the Essbase Master cube.
Action: Delete drivers that reference removed Measure Members from the application.
Level: 1
Type: ERROR
EPMPCM-06619: Dimension Name "{0}" is invalid. The first character of the name must be a letter.
Cause: A Dimension from the Essbase Master cube with an invalid name has been selected for deploy.
Action: Edit the Dimension in the Essbase Master cube so that the first character of the name is a letter.
Level: 1
Type: ERROR
EPMPCM-06620: Application "{0}" does not have a Rule type dimension.
Cause: Essbase Master Cube does not have a Rule type dimension
Action: Create a dimension of Rule type and redeploy the application
Level: 1
Type: ERROR
EPMPCM-06621: Application "{0}" does not have a Balance type dimension.
Cause: Essbase Master Cube does not have a Balance type dimension
Action: Create a dimension of Balance type and redeploy the application
Level: 1
Type: ERROR
EPMPCM-06623: Dimension "{0}" has no members.
Cause: The dimension has no members in the source (Essbase Master Cube or Application Library).
Action: Add one or more members to the dimension and try the operation again.
Level: 1
Type: ERROR
EPMPCM-06624: Dimension "{0}" has shared members that are descendants of the first generation 2 member of this dimension.
Cause: A shared member that is a descendant of the first generation 2 member of a dimension was found.
Action: Remove the shared member or move it to be a descendant of a different generation 2 member of the dimension and try the operation again.
Level: 1
Type: ERROR
EPMPCM-06625: Dimension "{0}" has shared members but an incorrect Hierarchy Type. It should be Dynamic or Multiple Hierarchies Enabled.
Cause: Dimensions with shared members must have a Hierarchy Type of Dynamic or Multiple Hierarchies Enabled.
Action: Update the Hierarchy Type for the dimension so that it meets one of the two required conditions and try the operation again.
Level: 1
Type: ERROR
EPMPCM-06626: Dimension Member "{0}" has invalid Parent Name "{1}".
Cause: The specified Dimension Member has an assigned parent name in the import for which there is no member.
Action: Correct the parent name in the import and try the operation again.
Level: 1
Type: ERROR
EPMPCM-06627: Dimension Member "{0}" is a shared member but a reference member was not found.
Cause: The specified Dimension Member does not have a reference member with the same name and earlier order with storage that is not shared.
Action: Correct the reference member in the import file and try the operation again.
Level: 1
Type: ERROR
EPMPCM-06628: Outline has shared members but the MasterCube outline is set to false for Allow Duplicate Member Names.
Cause: When deploying from a Master Cube with shared members, Allow Duplicate Member Names must be set to true.
Action: Correct the Master Cube to enable Duplicate Member Names and re-try the deploy.
Level: 1
Type: ERROR
EPMPCM-06629: Dimension "{0}" has invalid name or invalid file header.
Cause: The dimension name is too long. This can be caused by an invalid header where there are no commas separating the property fields, or the dimension name could just be too long.
Action: Correct the file header used in the import and verify that the dimension name is the correct length and try the operation again.
Level: 1
Type: ERROR
EPMPCM-06630: Dimension {0} in the Source for Rule {1} does not have a member selected.
Cause: All dimensions must be selected with at least one member before enabling the Rule
Action: Select the above dimension.
Level: 1
Type: ERROR
EPMPCM-06631: Dimension {0} in the Destination for Rule {1} does not have a member selected.
Cause: All dimensions must be selected with at least one member before enabling the Rule
Action: Select the above dimension.
Level: 1
Type: ERROR
EPMPCM-06632: Offset for Rule {0} does not have a Level 0 member selected for at least one dimension.
Cause: At least one level 0 member must be selected to use the offset functionality
Action: Select a level 0 member.
Level: 1
Type: ERROR
EPMPCM-06633: Driver for Rule {0} does not have a member selected for at least one dimension.
Cause: At least one level 0 member must be selected to use the driver functionality
Action: Select a level 0 member.
Level: 1
Type: ERROR
EPMPCM-06634: Dimension {0} in the Target for Rule {1} does not have a member selected.
Cause: All dimensions must be selected with at least one member before enabling the Rule
Action: Select the above dimension.
Level: 1
Type: ERROR
EPMPCM-06635: Some dimensions have multiple members selected.
Cause: Multiple members are not allowed for Driver or Offset.
Action: Select single dimension member.
Level: 1
Type: ERROR
EPMPCM-06649: Only level 0 member allowed in offset. members {0} in dimensions {1} are not level 0 member.
Cause: Only level 0 member allowed in offset.
Action: Select Only level 0 member in offset.
Level: 1
Type: ERROR
EPMPCM-06650: The number must be greater than or equal to 0.01 Allocated Amount Percentage. Value as a percentage to be allocated for this rule
Cause: allocation Amount Percent is less than zero.
Action: Select allocation Amount Percent which is greater than zero
Level: 1
Type: ERROR
EPMPCM-06686: Allocated Amount Value cannot be 0.
Cause: Allocated Amount Value cannot be 0.
Action: Select allocation Amount value which is not zero
Level: 1
Type: ERROR
EPMPCM-06636: Following Dimension is no longer available for use:{0}.
Cause: Dimension has been deleted in the Essbase.
Action: Review the Artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06637: Dimension {0} has invalid member {1}.
Cause: One or more Dimension Member(s) have been deleted in the Essbase.
Action: Review the Artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06638: Dimension {0} has invalid non level-0 member {1}.
Cause: Dimension has invalid non level-0 member.
Action: Review the Artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06639: Dimension {0} has one or more invalid Member(s).
Cause: One or more Dimension Member(s) have been deleted in the Essbase.
Action: Review the Artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06640: Warning: The root member for Dimension {0} is set as Label Only, so Member {1} will not consolidate to the top of the dimension.
Cause: Dimension has invalid non Primary Root Hierarchy members.
Action: Review the Artifact and make necessary changes
Level: 1
Type: WARNING
EPMPCM-06641: Dimension {0} is selected in both Rule Set Context and Global Context. To avoid the redundancy, save the Rule Set or remove the member selection from Global Context
Cause: Same dimension is selected in both the Rule Set Context and Global Context
Action: Remove the dimension selection either from the Rule Set Context or the Global Context
Level: 1
Type: ERROR
EPMPCM-06642: Validation has failed due to invalid dimension members
Cause: There are one or more dimensions with invalid members
Action: Review each dimension and select correct dimension members
Level: 1
Type: ERROR
EPMPCM-06643: Dimension {0} is selected in both Rule and Rule Set Context. To avoid the redundancy, save the Rule or remove the Member selection from Rule Set Context
Cause: The same dimension is selected in both the Rule and Rule Set Context
Action: Remove the dimension selection from either the Rule or the Rule Set Context
Level: 1
Type: ERROR
EPMPCM-06644: Dimension {0} is selected in both Rule and Global Context. To avoid the redundancy, save the Rule or remove the Member selection from Global Context
Cause: The same dimension is selected in both the Rule and Global Context
Action: Remove the dimension selection from either the Rule or the Global Context
Level: 1
Type: ERROR
EPMPCM-06645: Validation has failed due to one or more invalid Dimension(s)
Cause: One or more dimensions have been deleted in the Essbase.
Action: Review the Artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06646: Validation has failed due to invalid member {0}
Cause: There are one or more dimensions with invalid members
Action: Review each dimension and select correct dimension members
Level: 1
Type: ERROR
EPMPCM-06647: Calculation segment dimension is not selected or invalid
Cause: Invalid calculation segment dimension selection
Action: Review the artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06648: Dimension {0} selected as calculation segment dmension is no longer available for use.
Cause: Calculation segment dimension has been deleted in the Essbase.
Action: Review the Artifact and make necessary changes
Level: 1
Type: ERROR
EPMPCM-06651: Impact Analysis For Dimension "{0}"
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06652: There are {0} new members in this deployment.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06653: There are {0} deleted members in this deployment.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06654: There are {0} reparented members in this deployment.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06655: Member Name "{0}": Old Parent Name "{1}": New Parent Name "{2}"
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06656: New Member Name "{0}"
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06657: Deleted Member Name "{0}"
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06658: There are {0} members that moved from Level0 to non-Level0
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06659: Member Name "{0}" moved to non-Level0.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06660: Impact Analysis for Assignment Rule Selections
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06661: Impact Analysis for Explicit Assignments
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06662: Impact Analysis for Drivers
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06663: Impact Analysis for Assignment Rules
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06664: {0} Assignment Rule Selections Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06665: {0} Explicit Assignments Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06666: {0} Drivers Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06667: {0} Assignment Rules Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06668: Deleted dimension members with Assignment Rule Selections
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06669: Deleted dimension members with Explicit Assignments
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06670: Deleted measure dimension members referenced in Drivers
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06671: Deleted dimension members referenced in Assignment Rules
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06672: Drivers Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06673: Assignment Rules Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06674: Re-leveled Members with Explicit Assignments
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06675: Count in Point of View "{0}" is {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06676: Impact Analysis for Global Contexts
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06677: Impact Analysis for Rule Sets
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06678: Impact Analysis for Rules
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06679: Impact Analysis for Model Views
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06680: Impact Analysis for Manage Queries
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06681: {0} Global Contexts Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06682: {0} Rule Sets Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06683: {0} Program Rules Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06684: {0} Model Views Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06685: {0} Manage Queries Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06691: Impact Analysis for Point of View: Year:{0}, Period:{1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06692: Global Contexts Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06693: Rule Sets Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06694: Program Rules Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06695: Model Views Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06696: Queries Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06697: Deleted dimension members referenced in Global Context
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06698: Deleted dimension members referenced in Rule Set : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06699: Deleted dimension members referenced in Program Rule : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06700: Deleted dimension members referenced in Model View : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06701: Deleted dimension members referenced in Queries : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06702: Global Context is not Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06800: Given Dataset is null
Cause: Received an empty Dataset object and cannot continue with the process
Action: Review the hpcm.log file for actual cause of the error
Level: 1
Type: ERROR
EPMPCM-06703: Dimension file has invalid members
Cause: Dimension validation failed
Action: Verify the dimension flat files
Level: 1
Type: NOTIFICATION
EPMPCM-06704: Application information is not available in the import file
Cause: Imported file not contains the application.xml file
Action: Verify the selected file
Level: 1
Type: NOTIFICATION
EPMPCM-06705: Invalid Application type in the import file
Cause: Imported file application type should be Management Ledger
Action: Verify the selected file
Level: 1
Type: NOTIFICATION
EPMPCM-06706: File does not have content to import : ''''{0}''''
Cause: File does not have content to import
Action: Verify the selected file
Level: 1
Type: NOTIFICATION
EPMPCM-06710: Impact Analysis for Analysis Views
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06712: {0} Analysis Views Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06713: Deleted dimension members referenced in Analysis View : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06714: Impact Analysis for Scatters
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06716: {0} Scatters Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06717: Deleted dimension members referenced in Scatter : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06718: Impact Analysis for Whales
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06720: {0} Whales Impacted
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06721: Deleted dimension members referenced in Whale : {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-06750: Invalid arithmetic operator(s) {0} found in the Formula. Valid operators are =+-*/;
Cause: Invalid symbols used in the Formula of Custom rule
Action: Use valid operators for Formula
Level: 1
Type: ERROR
EPMPCM-06751: Multiple = operators are found in the formula
Cause: Multiple = symbols are used in the formula
Action: Use only one = in the formula
Level: 1
Type: ERROR
EPMPCM-06752: Invalid formula, the = operator is not found in the formula
Cause: = operator is not found in the formula
Action: Must use one = operator in the formula
Level: 1
Type: ERROR
EPMPCM-06753: Invalid member {0} used in the result section of the formula, the member should be from result dimension.
Cause: Non result members used in the result section of formula
Action: Use only level-0 result member for result section of the Formula
Level: 1
Type: ERROR
EPMPCM-06754: Invalid member {0} used in the result section of formula, the member has to be a level-0 member.
Cause: Non level-0 members used in the result section of formula.
Action: Use only level-0 result member in the result section of formula
Level: 1
Type: ERROR
EPMPCM-06755: Invalid member {0} used in the result section of formula. Tuple is not allowed in result Section of the formula.
Cause: Tuple is not allowed in the result section of formula
Action: Use only level-0 member from result dimension in the Result section of formula
Level: 1
Type: ERROR
EPMPCM-06756: Invalid member {0} used in the target section of formula. Single member must be a member from Result Dimension and Tuples must include a member from the Result Dimension.
Cause: Either Single member references can only be members from Result Dimension OR Tuples must include a member from the Result Dimension
Action: Use Result Dimension member in target section of the formula
Level: 1
Type: ERROR
EPMPCM-06757: Duplicate members found for {0}. Need to Partially qualify the member with a dimension name or use a Fully Qualified Name.
Cause: Duplicate members are found for the given member name.
Action: Need to Partially qualify the member with a dimension name or use a Fully Qualified Name.
Level: 1
Type: ERROR
EPMPCM-06758: Dimension {0} in the Target tab for Rule {1} does not have a member selected.
Cause: All dimensions must be selected with at least one member before enabling the Rule
Action: Select the above dimension.
Level: 1
Type: ERROR
EPMPCM-06759: No member used in the result section of formula.
Cause: No member used in the result section of formula
Action: Use a valid non level-0 member from result dimension
Level: 1
Type: ERROR
EPMPCM-06760: No member used in the target section of formula.
Cause: No member used in the result section of formula
Action: Give a valid member in target section of the formula
Level: 1
Type: ERROR
EPMPCM-06761: Invalid member(s) {0} used in Target section of the Formula. Tuples must not contain more than one member from the Same Dimension.
Cause: The Tuple has more than one member from one dimension
Action: Use only one member from one Dimension in a tuple of Target of the Formula
Level: 1
Type: ERROR
EPMPCM-06762: The Formula is empty for the Rule {0}.
Cause: The Formula is empty for the Rule.
Action: The Formula should not be empty for the Rule.
Level: 1
Type: ERROR
EPMPCM-06763: Target section of the formula has a blank member selected
Cause: Target section of the formula has a blank member.
Action: Target section of the formula should have valid member.
Level: 1
Type: ERROR
EPMPCM-06764: Result section of the formula has a blank member selected
Cause: Result section of the formula has a blank member.
Action: Result section of the formula should have valid member.
Level: 1
Type: ERROR
EPMPCM-06765: Import for dimension {0} is not allowed because it is a seeded dimension.
Cause: The Dimension name referenced in the import file is the same as a seeded dimension.
Action: Rename the dimension in the import file and try again.
Level: 1
Type: ERROR
EPMPCM-07001: This source node has a driver association with a driver with priority sequence that conflicts with the natural order of intra-stage cost flow. Source Node: {0}, Previous Source Node: {1}.
Cause: This source node has a driver association with a driver with priority sequence that conflicts with the natural order of intra-stage cost flow
Action: Edit the Driver so that the priority sequence no longer conflicts.
Level: 1
Type: ERROR
EPMPCM-07002: Reciprocal Assignment sources possibly involved in a loop. Source Nodes: {0}.
Cause: The Assignment sources being calculated are defined in a loop.
Action: Correct the Assignment sources so that they are no longer looping.
Level: 1
Type: ERROR
EPMPCM-07003: Intra-Stage source involved in a possible loop. Source Node: {0}.
Cause: The Assignment sources being calculated are defined in a loop.
Action: Correct the Assignment sources so that they are no longer looping.
Level: 1
Type: ERROR
EPMPCM-07004: Reciprocal Source node has no other out-going assignments. This node and its Reciprocal node will be ignored. Source Node: {0}. Reicprocal Source Node: {1}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-07005: Calculation Script Generation Failed.
Cause: An error occurred during Calculation script generation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07006: Create Block optimization is set to on. Please make sure that the Measures dimension is set to DENSE. If the Measures dimension is not set to DENSE, calculation might result in incorrect numbers.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-07007: Number of variables with ''Destination'' location exceeds 10 for Driver: ''''{0}''''. This is not supported. Rules based calc script for sources using this driver will not be generated.
Cause: Number of variables with ''Destination'' location exceeds 10 for the Driver.
Action: Correct the Driver.
Level: 1
Type: ERROR
EPMPCM-07008: Source: "{0}" has rules assigned and the driver associated doesn''t have at least one variable on either destination or assignment. This might result in a lot of destination nodes to be allocated to, depending on the rule. The "{1}" script might take a while to run.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-07009: The operation is not allowed. Cannot add child element: body generation complete.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07010: The operation is not allowed. Cannot end current element.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07011: The operation is not allowed. Cannot set suffix: already complete. Current state: {0}.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07012: The operation is not allowed. Cannot set prefix: prefix already complete. Current state: {0}.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07013: The operation is not allowed. Cannot FIX dimension member {0}. The FIX() statement is already rendered.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07014: The operation is not allowed. Cannot restart: current script element is not complete. Current state: {0}.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07015: Parameter tuple can not be NULL.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07016: The function cannot take {0} function as parameter.
Cause: The calculation script is invalid.
Action: Redefine the calculation and retry the operation.
Level: 1
Type: ERROR
EPMPCM-07501: Deploying Essbase Cube Failed.
Cause: An error occurred while deploying the Essbase cube.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07502: Outline Creation Failed.
Cause: An error occurred while creating the Essbase outline.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07503: Building POV Dimension Hierarchy Failed.
Cause: An error occurred during cube deployment
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07504: Attribute type is not set for dimension: {0}.
Cause: Unable to set the Attribute Type for the Dimension in the target Essbase cube.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07505: Building Business Dimension Hierarchy Failed.
Cause: An error occurred while building a dimension hierarchy in the Essbase cube.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07506: Building Measures Dimension Hierarchy Failed.
Cause: An error occurred while building the Measure dimension in the Essbase cube.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07507: Setting Dimension Member Properties Failed.
Cause: An error occurred while deploying the cube to Essbase.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07508: Building Attribute Dimension Hierarchy Failed.
Cause: An error occurred while deploying the cube to Essbase.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07509: Error Closing Essbase Outline.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-07510: Application or database does not exist: Essbase cube: ''''{0}''''. Essbase application: ''''{1}''''.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-07511: Building Dimension Failed for Dimension: ''{0}'', Dimension Type: ''{1}''
Cause: Error building dimensions for Essbase deployment
Action: Redeploy in EPMA and validate model
Level: 1
Type: ERROR
EPMPCM-07750: Calculation Script Run Failed.
Cause: An error occurred while running a calculation script.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-07751: Ledger Allocation or Custom Calc Script Run Failed.
Cause: The Allocation or Custom Calculation script failed in Essbase.
Action: Need to correct calculation scripts.
Level: 1
Type: ERROR
EPMPCM-07752: Parameter ''{0}'' cannot be null.
Cause: For Ledger Calculation, either Execution Type, Rule Set or Rule parameters cannot be null.
Action: Pass the valid parameter for Execution Type, Rule Set or Rule.
Level: 1
Type: ERROR
EPMPCM-07753: Result Dimension member not found in Result Section of Formula.
Cause: Result Dimension member not found in Result Section of Formula.
Action: Need to enter the one level 0 member of Result Dimension in Result Section of Formula.
Level: 1
Type: ERROR
EPMPCM-07754: Invalid dimension member ''{0}'' Found or dimension member ''{0}'' entered in Invalid format.
Cause: Invalid dimension member Found in Formula.
Action: Need to enter the valid dimension member in valid format.
Level: 1
Type: ERROR
EPMPCM-07755: Copy allocation data Failed.
Cause: The Custom Calculation script to copy allocation data failed in Essbase.
Action: Need to correct calculation scripts.
Level: 1
Type: ERROR
EPMPCM-07756: Potential source count is Zero for Rule ''''{0}''''.Ignoring Calculation For this rule.
Cause: Filter defined on Source selections is resulting zero members.
Action: Need to correct source selections of Rule.
Level: 1
Type: WARNING
EPMPCM-07757: Potential Destination count is Zero for Rule ''''{0}''''.Ignoring Calculation For this rule.
Cause: Filter defined on destination selections is resulting zero members.
Action: Need to correct Destination selections of Rule.
Level: 1
Type: WARNING
EPMPCM-07758: Number of updated cells count is Zero for Rule ''''{0}''''.
Cause: Souce or Driver Data is missing.
Action: Need to load source/driver data.
Level: 1
Type: WARNING
EPMPCM-07759: Specified Source Allocation Amount Value is Zero for Rule ''''{0}''''.
Cause: User Specified Source Allocation Amout Value as Zero.
Action: User need to correct Specified Source Allocation Amout Value.
Level: 1
Type: WARNING
EPMPCM-07760: Cube Deploy is not allowed until Application is enabled.
Cause: Application is not enabled.
Action: User need to Enable the application.
Level: 1
Type: ERROR
EPMPCM-08000: Finished genealogy calculation for stages {0}. {1} cells updated. Time elapsed: {2} ms.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08001: Could not calculate genealogy for reciprocal pair ''''{0}'''' at stage ''''{1}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08002: Reciprocal values not found for node ''''{0}''''
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-08003: Got 0 value for stage record ''''{0}''''. Ignoring link for this node.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08004: Dimension Members list is empty for stage ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08005: Attempt to set element state to ''''{0}''''. Current state is ''''{1}''''. The state will not be changed
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08006: NaN or infinity found on {0} - {1} - {2}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08007: Error on reading data.
Cause: An exception occurred while reading data from the Essbase cube.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-08008: No value found for {0}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-08009: Generator context cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-08010: Aggregation is not allowed for multistage calculations.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-08011: Empty descriptions list.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-08012: Incorrect number of stages in description: {0}.
Cause: An incorrect number of stages was specified for the genealogy operation.
Action: Specify a stage combination that has at least one intermediate stage between the first stage and last stage. For example: 1-3 is acceptable, but 1-2 is not.
Level: 1
Type: ERROR
EPMPCM-08013: Number of stages is less than 4.
Cause: The number of stages specified for the genealogy operation is less than 4.
Action: Specify at least 4 stages for the genealogy operation.
Level: 1
Type: ERROR
EPMPCM-08014: Details level should be IGeneratorContext.DETAILS_LINK.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-08015: There is should be at least one intermediate stage between {0} and {1}.
Cause: The stage combination specified for the genealogy operation is invalid.
Action: Specify a stage combination that has at least one intermediate stage between the first stage and last stage. For example: 1-3 is acceptable, but 1-2 is not.
Level: 1
Type: ERROR
EPMPCM-08016: Node value missing for : ''{0}''. Ignoring the Genealogy calculation Paths which contain this node.
Cause: This node is being considered as the middle node for genealogy because it has data suggesting incoming assignments.
Action: Need to check the direct allocation calc involving this node.
Level: 1
Type: WARNING
EPMPCM-09000: Error when processing LCM request
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09115: Unknown error occurred during jaxb context creation
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09010: Import of stage: {0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09011: Import of driver: {0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09012: Import of POV failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09013: Import of preference: {0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09014: Import of driver selection rule: {0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09015: Import of driver selection exception: {0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09016: Import of regular assignment :{0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09017: Import of assignment rule:{0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09018: Import of assignment rule selection:{0} failed.
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09020: No dimension member with name: {0} found in dimension : {1}.
Cause: The table being imported references a Dimension Member name which does not exist in the target application.
Action: Edit the dimension source model for this application to provide the missing member and redeploy the application. Then retry the import.
Level: 1
Type: ERROR
EPMPCM-09026: No dimension with name: {0} found.
Cause: The table being imported references a Dimension name which does not exist in the target application.
Action: Edit the dimension source model for this application to provide the missing dimension and redeploy the application. Then retry the import.
Level: 1
Type: ERROR
EPMPCM-09031: Driver dimension is not set for stage: {0}.
Cause: The stage does not have a Dimension designated as the Driver dimension.
Action: Designate a Driver dimension for the stage and retry the operation.
Level: 1
Type: ERROR
EPMPCM-09034: Application id is missing.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09035: Unknown LCM action: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09036: Error performing action: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09037: Application not found.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09038: Unknown artifact: {0}.
Cause: The artifact type being imported is not a valid artifact type for the target application. It is possible that the export file was edited manually thus causing this problem.
Action: Recreate the export file again from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09039: Parsing artifact query failed.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09040: Incorrect format of input file on line: {0}.
Cause: The source file being imported is invalid.
Action: Recreate the import file by exporting the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09041: Error importing drivers
Cause: An error occurred while importing.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09042: Driver type "{0}" not found
Cause: The Driver entry in the import file has an invalid Driver type for this application.
Action: Create the import file again by reexporting from the source application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-09043: Artifact stream contains {0} zero bytes.
Cause: The import file is invalid.
Action: Create the import file again by reexporting from the source application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-09044: Artifact query is empty.
Cause: The import file is invalid.
Action: Create the import file again by reexporting from the source application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-09045: Cannot get application id from request
Cause: An error occurred during export.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09046: Error building artifact XML
Cause: An error occurred during export.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09048: Import of POV "{0}" failed. POV state "{1}" not found.
Cause: The Point of View entry in the source import file has an invalid state assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09049: Import of driver "{0}" failed. Driver type "{1}" not found.
Cause: The Driver entry in the source import file has an invalid Driver Type assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09050: Import of driver "{0}" failed. Driver basis type "{1}" not found.
Cause: The Driver entry in the source import file has an invalid Driver Basis Type assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09051: Import of driver "{0}" failed. Layer "{1}" not found.
Cause: The Driver entry in the source import file has an invalid Layer assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09052: Import of application preference "{0}" failed. Application preference name not found.
Cause: The Application Preference name referenced in the import source file does not exist in the target application. The Profitability version from which the source import file was created does not match the Profitability version of the target application.
Action: Verify that the Profitability version for the source import file matches the Profitability version of the target application.
Level: 1
Type: ERROR
EPMPCM-09053: Import of assignment rule "{0}" failed. Stage "{1}" not found.
Cause: The Assignment Rule being imported references a stage that does not exist for the application. It is possible that a previous import of the stages for this application was not successful.
Action: Create the stage required by the Assignment Rule and retry the import.
Level: 1
Type: ERROR
EPMPCM-09054: Import of stage "{0}" failed. Dimension "{1}" not found.
Cause: The import stage table data refers to a Dimension name that does not exist in the target application.
Action: Correct the dimension name in the stage table data and re-try the import.
Level: 1
Type: ERROR
EPMPCM-09055: Failed to import {0} out of {1} artifacts.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09056: Import of driver "{0}" failed. No layer found.
Cause: The Driver entry from the source import file does not have a valid Layer assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09057: Parser error. Bad formatted token: {0}
Cause: The source import file is invalid.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09058: Error importing application
Cause: An error occurred during import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09059: Error parsing XML
Cause: The source import file is invalid.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09060: Error initializing document builder.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09061: Error creating document.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09062: Required field "{0}" is missing when validating stage.
Cause: The source import file is invalid.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09063: Import of assignment rule "{0}" failed. No stage found.
Cause: The assignment entry in the import file is invalid because there is no stage assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09064: Import of POV "{0}" failed. No POV state found.
Cause: The Point of View entry in the import file is invalid because there is no Point of View State assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09065: Import of driver "{0}" failed. No driver type found.
Cause: The Driver entry in the import file is invalid because there is no Driver Type assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09066: Import of driver "{0}" failed. No driver basis type found.
Cause: The Driver entry in the import file is invalid because there is no Driver Basis Type assigned to it.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09177: No acceptable first level folder found.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09178: Type of the destination application is not appropriate for a Detailed artifact.
Cause: The application type of the source import file does not match the application type of the target application.
Action: Choose a target application that is of the same type as the import file.
Level: 1
Type: ERROR
EPMPCM-09175: LCM Import will not set a Source Measure Dimension to a dimension that is not defined for the Destination Application.
Cause: The Source Measure Dimension Application Preference entry in the import file references a Dimension that does not exist in the target application.
Action: Create the Dimension in the dimension model and redeploy the application. Then retry the import.
Level: 1
Type: ERROR
EPMPCM-09176: LCM Import will not set a Destination Measure Dimension to a dimension that is not defined for the Destination Application.
Cause: The Destination Measure Dimension Application Preference entry in the import file references a Dimension that does not exist in the target application.
Action: Create the Dimension in the dimension model and redeploy the application. Then retry the import.
Level: 1
Type: ERROR
EPMPCM-09068: Parser error. Value of the field "{0}" has incorrect format.
Cause: The source import file is invalid.
Action: Recreate the import file by exporting from the source application and then retry the operation.
Level: 1
Type: ERROR
EPMPCM-09074: LCM operation completed. Total artifacts processed: {0}. Total time taken: {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09075: The import file name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09076: The Export Template params are ''''{0}'''' , ''''{1}'''' , ''''{2}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09085: Staging data import failed.
Cause: An exception occurred during Staging import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09087: Staging Import table is ''''{0}'''';
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09088: Table: ''''{0}'''' missing in staging database.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09289: Program import failed for the following reasons: ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09299: Program import partially failed for the following reasons: ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09300: Check logs for detail system errors. Program import partially failed for the following RuleSets & Rules: ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09101: Deployment completed.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09102: Application deployment SUCCEEDED.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09103: Application deployment FAILED.
Cause: An error occurred during application deployment.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09104: Creating dimensions
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09105: Deleting dimension members
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09106: Counting generation and level numbers for dimension: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09107: Deploying attributes for dimension: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09108: Deploying dimension: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09109: Dimension Synchronization to EPMA failed for application id: {0}.
Cause: An error occurred during Dimension Synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09110: Cloning dimension copies for application ''''{0}'''' failed.
Cause: An error occurred during dimension synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09111: Error deleting cloned dimensions for ''''{0}''''
Cause: An error occurred during dimension synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09112: Population of cloning eligible dimensionCopies failed.
Cause: An error occurred during dimension synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09113: Population of Stage Prefixed and Non-Prefixed dimension copies failed.
Cause: An error occurred during dimension synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09114: Application unregistration failed. Ignoring error as in re-register mode.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09120: Application deletion succeeded: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09121: Application deletion failed with exception: {0}
Cause: An exception occurred during application deployment.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09122: Application reregistration failed with exception: {0}
Cause: An exception occurred during application deployment.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09123: Application Deployment Status
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09124: Deployment succeeded for application {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09125: Deployment failed for application {0}
Cause: Application deployment was not successful.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09126: Attribute dimension member is not found: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09127: The next POV members became non level-0 but are used in available POV: {0}. Delete the POV first and try again
Cause: Members referenced in existing Point of Views are now non-level 0 in the source dimension model.
Action: Delete the referenced Point of Views from the application and try the operation again.
Level: 1
Type: ERROR
EPMPCM-09128: You are going to delete POV dimension members "{0}" that are used in available POV. Delete POV first and try again
Cause: Members referenced in existing Point of Views have been deleted from the source dimension model.
Action: Delete the referenced Point of Views from the application and try the operation again.
Level: 1
Type: ERROR
EPMPCM-09129: You are going to delete Point of View dimension(s) "{0}" that are used in defined Point of Views. Delete defined Point of Views first and try again
Cause: The Point of View dimension(s) being deleted are referenced in defined Point of Views.
Action: Delete the defined Point of Views and then re-try the operation.
Level: 1
Type: ERROR
EPMPCM-09130: You are going to add POV dimension(s) "{0}" but there are some already defined POVs. Delete existing POV first and try again
Cause: Existing Point of Views in the application will become invalid due to the Point of View dimension structure changes in the source dimension model.
Action: Delete all of the existing Point of Views from the application and then try the application deploy again.
Level: 1
Type: ERROR
EPMPCM-09131: You are going to delete dimensions "{0}" that are used in available stages. Delete stages first and try again
Cause: Dimensions used in existing stages in the application have been removed from the source dimension model.
Action: Delete stages that reference the dimensions and then try the application deploy again.
Level: 1
Type: ERROR
EPMPCM-09132: Dimension(s) "{0}" of type Regular are referenced in existing Point of Views. Delete the Point of Views and try again
Cause: Dimenisons marked with the Regular type are used in existing Point of Views for the application.
Action: Delete the existing Point of Views and try the application again again.
Level: 1
Type: ERROR
EPMPCM-09133: Initialization of web services for data synchronization failed.
Cause: A web service error occurred during data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09134: Initialization of dimension server object failed for hss app name ''''{0}''''.
Cause: An exception occurred during EPMA data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09135: Setting non-stage dimensions invisible in data sync app for hss application name ''''{0}'''' failed.
Cause: An exception occurred during EPMA data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09136: Setting non-prefixed dimensions visible in data sync app for hss application name ''''{0}'''' failed.
Cause: An exception occurred during EPMA data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09137: Setting non-stage dimensions visible before clone in data sync app for Shared Services application name ''''{0}'''' failed.
Cause: An exception occurred during EPMA data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09138: Exception in deployer servlet; Sending error status to call back URL.
Cause: An error occurred during application deploy.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09139: Cloning of dimensions for hss application id: {0} failed.
Cause: An error occurred during data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09140: Application Deletion succeeded: No actions needed because application does not exist.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09141: The parameter "app_name" is empty
Cause: An error occurred during application deploy.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09142: The parameter "cluster" is empty
Cause: An error occurred during application deploy.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09143: Application deployment FAILED:
Cause: Application deploy was not successful.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09144: Warning: Driver measure "{0}" is deleted. Driver formulas which refered the measure were updated with default measures.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09145: Data Entry view [{0}] member "{1}" not found in Model, skipping.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09146: Error adding Data Entry view [{0}] :
Cause: An exception occurred during the deploy for saving a Data Entry view.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09147: Error creating standard view:: {0}.
Cause: An exception occurred during the deploy for saving a Data Entry view.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09148: Exception while posting request to Call Back URL : {0}.
Cause: An error occurred during application deployment.
Action: Verify that the EPMA server is running. It may be necessary to restart it.
Level: 1
Type: ERROR
EPMPCM-09149: You are deleting dimensions "{0}" which are user-defined measures. Delete the user-defined measures in your application first and try again
Cause: You are deleting dimensions in an Application of type Detail that are referenced in a registered table as a Measures dimension.
Action: Reregister the table to remove the Measure dimension references and then try the deploy again.
Level: 1
Type: ERROR
EPMPCM-09150: Application deployment SUCCEEDED. There were Model Data Registration artifacts that were deleted to complete this deployment: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09151: Cannot delete dimension members "{0}" which belong to the source or destination measures dimension and where there are existing drivers defined. To delete these members, first delete all existing Drivers in your application and then redeploy the application. Any existing model data registrations of deleted measure members will be removed automatically by the deploy.
Cause: You are deleting dimension members referenced in existing Drivers.
Action: Delete the existing drivers that reference the dimension members and try the application deploy again.
Level: 1
Type: ERROR
EPMPCM-09152: Cannot delete dimensions "{0}" because they are registered in Table Registration.
Cause: Dimensions referenced in table registration are being deleted.
Action: Reregister the tables to remove the references to the dimensions and try the application deploy again.
Level: 1
Type: ERROR
EPMPCM-09153: Cannot deploy because attribute dimension names "{0}" have an invalid first character. Only lowercase and uppercase letters can be used as the first character for an attribute dimension name.
Cause: The attribute dimension names have an invalid first character.
Action: Correct the attribute dimension name first character to be a lowercase or uppercase letter.
Level: 1
Type: ERROR
EPMPCM-09154: Application is not an Enterprise Performance Management Architect application. Skipping data synchronization.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09155: Performing post deployment activities.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09200: Null or empty task name
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09201: No job found for task ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09202: Unknown action ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09203: Error processing calculation scripts
Cause: An exception occurred during calculation script execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09204: Error creating taskflow. Reregister the application and try the operation again.
Cause: An error occurred while trying to create the taskflow to run a job. This can occur if the Application registration is not current with the Profitability service.
Action: Reregister the application and try the operation again.
Level: 1
Type: ERROR
EPMPCM-09205: Error initiating taskflow ''''{0}''''
Cause: An exception occurred during taskflow execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09206: Error importing staging.
Cause: An exception occurred during Staging import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09207: Error clearing ASO cube.
Cause: An exception occurred while clearing the ASO cube.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09208: Error copying dimensions.
Cause: An exception occurred during data synchronization.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09209: Error copying POV.
Cause: An exception occurred during the copy Point of View operation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09210: Error deploying cubes.
Cause: An exception occurred during cube deployment.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09211: Error generating genealogy script.
Cause: An exception occurred during genealogy execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09212: Error copying data.
Cause: An exception occurred during Data Transfer.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09213: Error processing the TaskFlow XML.
Cause: An exception occurred during Taskflow execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09214: Error encountered trying to send http request.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09215: Error executing task {0}.
Cause: An exception occurred during Taskflow execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09216: Error parsing taskfow xml:: {0}.
Cause: An exception occurred during Taskflow execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09217: Error saving job log with id: {0}, message: "{1}", log level: {2}
Cause: An exception occurred during job execution.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09218: Error exporting application data.
Cause: An exception occurred during application export.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09219: Error importing application data.
Cause: An exception occurred during application import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09220: It's not possible to reload data if the cube is replaced.
Cause: The reload data option is incompatible with the cube replace option.
Action: Modify the deploy options so that they are compatible and re-try the operation.
Level: 1
Type: ERROR
EPMPCM-09221: Can't get CES localized messages, use default.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09222: Error expanding bulk edit into staging table.
Cause: An exception occurred during Bulk Edit expansion.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09223: Error importing bulk edit from staging table.
Cause: An exception occurred during Bulk Edit import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09224: Error deploying application.
Cause: An exception occurred during application deploy.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09225: Action successfully completed, ecid: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09226: Action failed, ecid: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-09227: Error clearing POV.
Cause: There were errors during the operation
Action: Review the hpcm.log file for actual cause of the error
Level: 1
Type: ERROR
EPMPCM-09228: Error deleting POV.
Cause: There were errors during the operation
Action: See the hpcm.log file for more details
Level: 1
Type: ERROR
EPMPCM-09229: Unable to remove existing application locks for current Server.
Cause: Failed to remove rows from the database.
Action: Stop Profitability service and remove rows from HPM_SERIAL_APP_LOCK.
Level: 1
Type: WARNING
EPMPCM-09230: Wait for permission for serial execution.
Cause: Another process is performing an action that must be performed serially.
Action: No action required.
Level: 1
Type: NOTIFICATION
EPMPCM-09231: Maximum allowed wait time exceeded (TIMEOUT).
Cause: The duration of time spent waiting exceeded the defined timeout
Action: Increase the timeout interval or tune the performance.
Level: 1
Type: ERROR
EPMPCM-09232: Attempted to construct invalid coordinator.
Cause: There is an internal error with the software
Action: Contact Oracle Support and provide this error message.
Level: 1
Type: INCIDENT_ERROR
EPMPCM-09233: Error processing data load
Cause: An exception occurred during Essbase data load.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09234: Error processing enable application
Cause: An exception occurred during enable application.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09235: Error during Import Template.
Cause: An exception occurred during Import Template.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09236: Error during Export Template.
Cause: An exception occurred during Export Template.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09238: Changing the status of the interrupted job to Failure.
Cause: An interrupted job was detected during service startup.
Action: The service already changed the status to Failed, so no further action is required.
Level: 1
Type: WARNING
EPMPCM-09239: The interrupted job cleanup process is disabled.
Cause: The disable installation preferrence is set.
Action: Remove the instalation perferrence or set the value equal to the N character to enable the process.
Level: 1
Type: WARNING
EPMPCM-09970: Failed to audit driver import event
Cause: An exception occurred during audting.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09971: Failed to audit stage import event
Cause: An exception occurred during auditing.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09972: Exception during starting audit client occurred
Cause: An exception occurred during auditing.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09973: Exception during stopping audit client occurred
Cause: An exception occurred during auditing.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09974: Audit for {0} {1} not supported.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09975: AuditRecord cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09976: Both new and old stages cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09977: Both new and old drivers cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09978: Both new and old POV member groups cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09979: Both new and old driver associations cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09980: Both new and old assignments cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09981: Both new and old assignment rule names cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09982: Action type should be 'export' or 'import'.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09983: Error getting bean property: {0}.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09984: Both new and old calculations cannot be null.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09985: An error occurred during jaxb unmarshalling xml
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09986: An error occurred during jaxb unmarshaller creation
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09987: An error occurred during jaxb marshalling java object to xml
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09988: An error occurred during jaxb marshaller creation
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09989: The input Stream parameter cannot be null
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09990: The output Stream parameter cannot be null
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09991: an error processing the given property
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-09992: Import of POV "{0}" failed. Any POV member from "{1}" not found.
Cause: An error occurred during Point of View import.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10000: No Assignment Rule found for the following parameters: ''''{0}''''
Cause: The Assignment Rule is invalid.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10001: The Assignment Rule ''''{0}'''' doesn''t have any Dimension Selection
Cause: The Assignment Rule does not have any Dimension selection.
Action: Edit the Assignment Rule and add a dimension selection. Then retry the operation.
Level: 1
Type: ERROR
EPMPCM-10002: The Assignment Rule has a Filter type ''''{0}'''' that can not be supported by the Detail Pofitability Engine
Cause: The Filter Type for the Assignment Rule is invalid for Detailed Profitability.
Action: Delete the invalid filter for the Assignment Rule and retry the operation.
Level: 1
Type: ERROR
EPMPCM-10003: Calculation process definition missing for the current period and layer
Cause: Calculation Process seeded data is missing from the Profitability database for this application.
Action: Redeploy the application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-10004: Stage table is not registered for Detailed Profitability application.
Cause: A table referenced in a stage is no longer registered in the Profitability application.
Action: Reregister the table and then try the operation again.
Level: 1
Type: ERROR
EPMPCM-10100: The destination table must have a primary key constraint.
Cause: The table being registered does not have a primary key constraint.
Action: Create a primary key constraint for the table and retry the registration.
Level: 1
Type: ERROR
EPMPCM-10101: The WORKING column must be present on the destination table.
Cause: The destination table does not have a column named WORKING of numeric data type.
Action: Add a column named WORKING with a numeric data type to the table and reregister the table.
Level: 1
Type: ERROR
EPMPCM-10102: The WORKING column on the destination table must be numeric datatype.
Cause: The WORKING column on the destination table is not of numeric data type.
Action: Alter the WORKING column on the destination table so that it is numeric data type.
Level: 1
Type: ERROR
EPMPCM-10103: The HPM_POV_DIM_MEM_GRP column must be present on the destination table or the user must register all POV columns on the destination business object.
Cause: The Destination table does not have one of the required Point of View columns.
Action: Add either the HPM_POV_DIM_MEM_GRP column or register all of the Point of View columns on the destination table.
Level: 1
Type: ERROR
EPMPCM-10104: The HPM_POV_DIM_MEM_GRP column on the destination table must be numeric datatype.
Cause: The HPM_POV_DIM_MEM_GRP column on the destination table is not numeric data type.
Action: Alter the HPM_POV_DIM_MEM_GRP column so that it is numeric data type.
Level: 1
Type: ERROR
EPMPCM-10105: The source stage dimension ''''{0}'''' is no longer registered on the source stage table or the joined lookup tables.
Cause: The dimension referenced on the source stage is not present on the source stage or joined lookup table.
Action: Add the dimension to the source stage table or joined lookup tables and reregister the table.
Level: 1
Type: ERROR
EPMPCM-10106: The destination stage dimension ''''{0}'''' is no longer registered on the destination stage table or the joined lookup tables.
Cause: The dimension referenced on the destination stage is not present on the destination stage or joined lookup table.
Action: Add the dimension to the destination stage table or joined lookup tables and reregister the table.
Level: 1
Type: ERROR
EPMPCM-10107: The column associated with the dimension ''''{0}'''' no longer exists on the table.
Cause: A Stage dimension is not referenced on any of the registered business object in Model Data Registration.
Action: Add the dimension to a registered business object in Model Data Registration.
Level: 1
Type: ERROR
EPMPCM-10108: The measure member ''''{0}'''' is defined more than once on the lookup table ''''{1}'''' and its joined business object ''''{2}.''
Cause: There are multiple references for a Measure dimension member in Model Data Registration for the same lookup table and joined business object
Action: Verify that each measure dimension member is referenced only once for a given lookup table and joined business object.
Level: 1
Type: ERROR
EPMPCM-10109: The dimension ''''{0}'''' is defined more than once on the lookup table ''''{1}'''' and its joined business object ''''{2}.''
Cause: The same dimension is registered multiple times on a lookup table or its joined business object.
Action: Verify that a each generic dimension is registered only once for a given lookup table or its joined business object.
Level: 1
Type: ERROR
EPMPCM-10110: The stage dimension column ''''{0}'''' for the destination table or its joined lookup tables must have the same column datatype as the ID column in the HPM_DIMENSION_MEMBER table.
Cause: A registered dimension column on the destination table does not have the correct data type.
Action: Verify that the data type for each registered dimension column on the destination stage table has a data type which is identical to the ID column on the HPM_DIMENSION_MEMBER table.
Level: 1
Type: ERROR
EPMPCM-10111: The column associated with the measure member ''''{0}'''' no longer exists on the table.
Cause: A registered measure member column no longer exists on the physical database object used in the Model Data Registration.
Action: Add the missing column to the database object used for that Model Data Registration.
Level: 1
Type: ERROR
EPMPCM-10115: The HPM_POV_DIM_MEM_GRP column must be present on the source table or the user must register all POV columns on the source business object.
Cause: The Destination table does not have one of the required Point of View columns.
Action: Add either the HPM_POV_DIM_MEM_GRP column or register all of the Point of View columns on the source table.
Level: 1
Type: ERROR
EPMPCM-10116: The HPM_POV_DIM_MEM_GRP column on the source table must be numeric datatype.
Cause: The data type for the HPM_POV_DIM_MEM_GRP column on the source table is invalid.
Action: Alter the source table so that the HPM_POV_DIM_MEM_GRP column has a numeric datatype.
Level: 1
Type: ERROR
EPMPCM-10117: The HPM_POV_DIM_MEM_GRP column on the source table must be numeric datatype.
Cause: The HPM_POV_DIM_MEM_GRP column on the source table is not numeric data type.
Action: Alter the HPM_POV_DIM_MEM_GRP column on the source table so that it is numeric data type.
Level: 1
Type: ERROR
EPMPCM-10118: Dimension ''''{0}'''' of the source stage must be registered upon the table associated with the source stage.
Cause: A dimension on the source stage is not registered on the source table for that stage.
Action: Register all dimensions of the source stage on the source table.
Level: 1
Type: ERROR
EPMPCM-10119: Source stage must have a stage table associated with it.
Cause: The Source stage does not have an associated Source table.
Action: Edit the Source stage so that it has an associated Source table.
Level: 1
Type: ERROR
EPMPCM-10120: Destination stage must have a stage table associated with it.
Cause: The Destination stage does not have a destination table associated with it.
Action: Edit the Destination stage so that it has an associated destination table.
Level: 1
Type: ERROR
EPMPCM-10121: Dimension ''''{0}'''' of the destination stage must be registered upon the table associated with the destination stage.
Cause: A dimension from the destination stage is not registered on the destination table.
Action: Verify that all dimensions on the destination stage are registered on the destination table.
Level: 1
Type: ERROR
EPMPCM-10122: Column ''''{0}'''' is used as a source stage dimension and is not a part of the source table index.
Cause: A column on the source table is registered as a Dimension column, but is not part of a unique index on that table.
Action: Verify that all columns registered as type Dimension are included in a unique index for the source table.
Level: 1
Type: ERROR
EPMPCM-10123: Column datatype mismatches between joined columns. Column name is ''''{0}'''', fact column type is ''''{1}'''', lookup column type is ''''{2}''''
Cause: A column name designated as a join column between a lookup table and a fact table does not have the same data type on each table.
Action: Verify that any column name designated as a join column exists on both tables and has the same data type.
Level: 1
Type: ERROR
EPMPCM-10124: There is missing data in the lookup table ''{0}'' in the column ''{1}''
Cause: The fact table that joins with the lookup table reference Lookup values that do not exist in the Lookup table.
Action: Add the missing Lookup values to the Lookup table or delete the rows from the fact table with the incorrect reference.
Level: 1
Type: ERROR
EPMPCM-10125: Unknown error: {0}
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10126: One or more measures referenced in a driver formula are not registered. Run Model Validations for Drivers to identify the unregistered measures.
Cause: One or more measure members referenced in a driver formula are not registered in Model Data Registration.
Action: Run Model Validations for Drivers to identify the unregistered measures.
Level: 1
Type: ERROR
EPMPCM-10127: Formula is not valid.
Cause: An exception occurred while reading a driver formula.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10128: No column on the Destination stage table is registered as a measure column that maps to the Assign To Destination Measure for the Driver ''''{0}''''.
Cause: The Assign to Destination Measure for a given Driver is not registered as a measure column on the Destination stage table.
Action: Register a measure column on the Destination stage table for the Assign To Destination Measure of the Driver.
Level: 1
Type: ERROR
EPMPCM-10129: Primary key for the Destination stage table is not registered.
Cause: The unique index to be used as the primary key for the Destination stage table is not registered in Model Data Registration.
Action: Edit the registration for the destination table so that an index is designated as the primary key.
Level: 1
Type: ERROR
EPMPCM-10131: Destination table is not defined.
Cause: There is no destination stage table associated with the Destination stage, or the specified destination stage table is no longer registered in Model Data Registration.
Action: Verify that the destination stage has a valid destination stage table.
Level: 1
Type: ERROR
EPMPCM-10132: Exception when creating a synonym {0} for the table {1} in the schema {2}. Error details are: {3}.
Cause: An exception occurred while attempting to create a synonym.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10133: Cannot find a measure column on the source stage table that matches the measure component ''{0}'' on the source tuple.
Cause: The source table is missing a Measure column.
Action: Add a column for the missing measure and re-register the source table.
Level: 1
Type: ERROR
EPMPCM-10134: There is a non-synonym database object, i.e. a table or a view with the same name as the synonym being created. Change the synonym name.
Cause: An error occurred while attempting to create a database synonym.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10135: There is already a synonym with the same name in the database. But the synonym in the database references a wrong database object. It points to the object ''''{0}'''' in the schema ''''{1}''''.
Cause: There is an existing synonym of the same name that points to a different database object than the object.
Action: Drop the existing synonym of the specified name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-10136: No jobs found.
Cause: Delete job has been called but no jobs have been specified to be deleted.
Action: Retry the operation and verify that there are jobs selected for delete.
Level: 1
Type: ERROR
EPMPCM-10137: View ''''{0}'''' is invalid or does not exist.
Cause: A Model Data Registration object references a database view that does not physically exist in the database or has errors.
Action: Verify that the view referenced in the Model Data Registration is a valid view in the database.
Level: 1
Type: ERROR
EPMPCM-10138: View ''''{0}'''' contains a join. Views with a join in the primary select clause cannot be registered as a Destination table.
Cause: The database view referenced in Model Data Registration contains a join in the primary select clause.
Action: Recreate the view so that there is no join in the primary select clause.
Level: 1
Type: ERROR
EPMPCM-10139: View ''''{0}'''' contains an illegal keyword. Views with UNION, GROUP BY, DISTINCT, MINUS, EXCEPT and INTERSECT cannot be registered as a Destination table.
Cause: The database view referenced in Model Data Registration contains unsupported keyword or keywords.
Action: Recreate the view so that the unsupported keywords are no longer present in the view definition.
Level: 1
Type: ERROR
EPMPCM-10140: Short Name property value ''''{0}'''' of dimension ''''{1}'''' should be unique over existing ''Reporting Dimensions''.
Cause: The designated short name is assigned to multiple Reporting dimensions for this application.
Action: Assign a unique short name for each Reporting dimension.
Level: 1
Type: ERROR
EPMPCM-10141: Short Name property value ''''{0}'''' of dimension ''''{1}'''' should be unique over existing ''Attribute Dimensions''.
Cause: The designated short name is assigned to multiple Attribute dimensions for this application.
Action: Assign a unique short name for each Attribute dimension.
Level: 1
Type: ERROR
EPMPCM-10142: Destination measure ''''{0}'''' in the driver definition does not have a valid registration.
Cause: There is no registered column on the destination stage table for a destination measure referenced in a driver.
Action: Register a column for the destination measure on the destination stage table.
Level: 1
Type: ERROR
EPMPCM-10143: Measure member ''''{0}'''' in the driver formula does not have a valid registration.
Cause: The driver formula references a Measure member name that is not registered for the business object.
Action: Register the Measure member name on the business object specified in the formula.
Level: 1
Type: ERROR
EPMPCM-10147: The dimension ''''{0}'''' on the source stage table or its joined lookup tables is no longer registered in the dimension model.
Cause: The designated Dimension is no longer present in the dimension model.
Action: Verify that the dimension exists in the dimension model and redeploy the Profitability application.
Level: 1
Type: ERROR
EPMPCM-10148: The dimension ''''{0}'''' on the destination stage table or its joined lookup tables is no longer registered in the dimension model.
Cause: The designated Dimension is no longer present in the dimension model.
Action: Verify that the dimension exists in the dimension model and redeploy the Profitability application.
Level: 1
Type: ERROR
EPMPCM-10149: No source stage exists. Create a source stage.
Cause: There is no stage defined for the Profitability application.
Action: Define as source and destination stage for the Profitability application.
Level: 1
Type: ERROR
EPMPCM-10150: No destination stage exists. Create a destination stage.
Cause: The Profitability application only has a single stage defined.
Action: Define two stages for the Profitability application. The second stage is the destination stage.
Level: 1
Type: ERROR
EPMPCM-10151: The dimension member ''''{0}'''' on the source stage table is no longer registered in EPMA.
Cause: A dimension member that maps to a registered column on the source table has since been removed from the Dimension model.
Action: Re-register the source table to remove the invalid column.
Level: 1
Type: ERROR
EPMPCM-10153: The source measure dimension ''''{0}'''' must be one of the dimensions associated with source stage.
Cause: The Source Measures Dimension specified on Model Data Registration is not a dimension of the Source stage.
Action: Add the dimension to the Source stage.
Level: 1
Type: ERROR
EPMPCM-10155: Registered table column ''''{0}'''' does not exist in the source table ''''{1}.''
Cause: A column registered on the source table no longer physically exists on the database table. This can occur when if the column was dropped from the table after model data registration was completed.
Action: Unregister the column from the table using Model Data Registration.
Level: 1
Type: ERROR
EPMPCM-10156: Registered table column ''''{0}'''' does not exist in the target table ''''{1}.''
Cause: A column that was registered for a table has since been physically removed from the table in the database.
Action: Re-register the table to remove the invalid column.
Level: 1
Type: ERROR
EPMPCM-10157: Registered table column ''''{0}'''' does not exist in the lookup table ''''{1}.''
Cause: A column that was registered for a lookup table has since been physically removed from the table in the database.
Action: Re-register the lookup table to remove the invalid column.
Level: 1
Type: ERROR
EPMPCM-10158: Measure column ''''{0}'''' of ''''{1}'''' table has invalid registration. Destination measure columns should be mapped only by destination measure dimension members.
Cause: The measure column on the table does not map to a member of the Destination measures dimension.
Action: Modify the registration for the column so that it maps to a member of the Destination measures dimension.
Level: 1
Type: ERROR
EPMPCM-10159: None of the destination measure dimension members has a mapping to a registered column.
Cause: None of the members in the destination measures dimension is mapped to a registered column.
Action: Register a measure column that maps to a member of the destination measures dimension using Model Data Registration.
Level: 1
Type: ERROR
EPMPCM-10160: Override Total Driver Value measure ''''{0}'''' in the driver definition does not have a valid registration.
Cause: The measure member specified for Override Total Driver Value does not map to any column in Model Data Registration.
Action: Modify the Override Total Driver Value measure member so that it maps to a member with a registered column.
Level: 1
Type: ERROR
EPMPCM-10161: Assign To measure ''''{0}'''' is not allowed to be mapped to a column on a lookup table.
Cause: The Assign To Measure member of a driver maps to a lookup table column.
Action: Modify the Assign To Measure member so that it maps a fact table column.
Level: 1
Type: ERROR
EPMPCM-10162: Short Name property value ''''{0}'''' length should not exceed 10 symbols for ''Reporting Dimensions''.
Cause: The Short Name property length for a Reporting dimension is greater than 10 characters.
Action: Modify the Short Name property for all Reporting dimensions so that the length is less than or equal to 10 characters.
Level: 1
Type: ERROR
EPMPCM-10163: Short Name property value ''''{0}'''' length should not exceed 30 symbols for ''Attribute Dimensions''.
Cause: The Short Name property length for an Attribute dimension is greater than 30 characters.
Action: Modify the Short Name property for all Attribute dimensions so that the length is less than or equal to 30 characters.
Level: 1
Type: ERROR
EPMPCM-10164: Source measures are not allowed in object calculation drivers.
Cause: An Object Calculation driver contains a reference to a Source measure member.
Action: Remove references to Source measure members from the Object Calculation driver.
Level: 1
Type: ERROR
EPMPCM-10165: No Model Data Schema is selected. Select one before continuing.
Cause: The Model Data Schema property in Model Summary - Model Level Preference is not specified.
Action: Select a Model Data Schema for the application in the Model Summary - Model Level Preference page.
Level: 1
Type: ERROR
EPMPCM-10168: The system table ''''{0}'''' does not exist in the currently selected Model Data Schema. Ensure that all stage tables exist in the selected Model Data Schema prior to calculation.
Cause: The table specified for the stage does not physically exist in the Model Data Schema. This occurs when the table is dropped from the Model Data Schema after registration was completed.
Action: Recreate the missing table or modify the stage so that it points to a valid registered table.
Level: 1
Type: ERROR
EPMPCM-10169: Comment length should not exceed 255 symbols.
Cause: The specified comment is greater than 255 characters.
Action: Verify that the comment is less than or equal to 255 characters.
Level: 1
Type: ERROR
EPMPCM-10170: The product schema does not have UPDATE privileges on the destination stage table ''''{0}.''
Cause: The Profitability product schema does not have UPDATE privileges on the destination stage table in the model data schema.
Action: Grant the UPDATE privilege on the destination stage table to the Profitability product schema.
Level: 1
Type: ERROR
EPMPCM-10171: The product schema does not have SELECT privileges on the table ''''{0}.''
Cause: The Profitability product schema does not have SELECT privileges on the specified table.
Action: Grant the SELECT privilege on the specified table to the Profitability product schema.
Level: 1
Type: ERROR
EPMPCM-10172: The HPCM Product User may not have the ''''{0}'''' privilege on the Model Data Schema.
Cause: The Profitability product user is missing the specified privilege.
Action: Grant the specified privilege to the Profitability product user.
Level: 1
Type: ERROR
EPMPCM-10173: The HPCM Product User may not have the CREATE VIEW privilege.
Cause: The Profitability product user is missing the specified privilege.
Action: Grant the specified privilege to the Profitability product user.
Level: 1
Type: ERROR
EPMPCM-10174: All of measure columns on the table ''''{0}'''' are not of the same precision and scale.
Cause: Registered measure columns on the specified table do not have identical precision and scale.
Action: Alter the specified table so that all registered measure columns have identical precision and scale.
Level: 1
Type: ERROR
EPMPCM-10175: There are no measures mapped on the source stage table ''''{0}.''
Cause: The specified source stage table has no registered measure column.
Action: Register a measure column for the specified source stage table.
Level: 1
Type: ERROR
EPMPCM-10176: There are two driver measures mapped to the destination stage table column ''''{0}''''.
Cause: The Driver measure for multiple drivers map to the same registered destination stage column.
Action: Verify that each Driver measure maps to a unique destination stage column.
Level: 1
Type: ERROR
EPMPCM-10177: There are no drivers in the sequence range for calculation rule ''''{0}.''
Cause: There are no drivers selected within the start and end sequence range of the specified calculation rule.
Action: Edit the specified calculation rule so that at least one driver is designated in the sequence range.
Level: 1
Type: ERROR
EPMPCM-10178: There are no enabled calculation rules to calculate.
Cause: None of the calculation rules for the application are enabled.
Action: Verify that at least one calculation rule is enabled and then retry the calculation.
Level: 1
Type: ERROR
EPMPCM-10179: The product schema does not have SELECT with GRANT OPTION privileges on the table ''''{0}.''
Cause: The Profitability product schema does not have the SELECT with GRANT OPTION privilege on the specified table.
Action: Grant the SELECT with GRANT OPTION privilege to the Profitability product schema on the specified table.
Level: 1
Type: ERROR
EPMPCM-10180: The LCM export of Calculation Rules being imported is incorrect.
Cause: The Calculation Rules being imported have failed validation.
Action: Refer to the LCM import validation errors for more information.
Level: 1
Type: ERROR
EPMPCM-10181: The first sequence priority is greater than last sequence priority
Cause: The first sequence priority value is greater than the last sequence priority.
Action: The first sequence priority value must be less than the last sequence priority.
Level: 1
Type: ERROR
EPMPCM-10182: Invalid sequence priority values
Cause: The first and/or last sequence priority values are null for a Calculation Rule..
Action: Verify that there is a valid number assigned to both the first sequence and last sequence values for each Calculation Rule.
Level: 1
Type: ERROR
EPMPCM-10184: Illegal value for driver sequence, the sequence value should be greater than 1 and less than 2147483647.
Cause: The driver sequence is invalid.
Action: Verify that the driver sequence is a number between 1 and 2147483647.
Level: 1
Type: ERROR
EPMPCM-10185: The Data Filter has invalid expressions.
Cause: The Data Filter for an Assignment Rule has invalid expressions.
Action: Verify that the Data Filter for the Assignment Rule contains only valid expressions.
Level: 1
Type: ERROR
EPMPCM-10186: The Short Name ''''{0}'''' is not a legal Short Name. Short Names cannot be Database Reserved words, cannot have non-alphanumeric characters, and the first character cannot be a number.
Cause: The specified Short Name contains illegal characters or is a database reserved word.
Action: Verify that all Short Names are not database reserved words, have only alphanumeric characters and the first character is not a number.
Level: 1
Type: ERROR
EPMPCM-10187: No sources were found during model calculations.
Cause: None of the executions steps (sources to be processed) exist.
Action: Verify if source assignment rules matches any rows in the source stage table.
Level: 1
Type: WARNING
EPMPCM-10188: No destinations were updated during model calculations.
Cause: None of the executions steps (destinations to be processed) exist.
Action: Verify if destination assignment rules matches any rows in the destination stage table.
Level: 1
Type: WARNING
EPMPCM-10189: Sources must be allocated using the suboptimal Single Pool Same as Source SQL strategy.
Cause: Rule performance optimizer detected a configuration that requires Single Pool Same as Source SQL strategy.
Action: Refer to the Configuration Guidelines for Detailed Profitability Applications for performance tuning advice.
Level: 1
Type: NOTIFICATION
EPMPCM-10190: Sources allocated using the optimized Bulk Same as Source SQL strategy.
Cause: Rule performance optimizer chose the optimized Bulk Same as Source SQL strategy.
Action: Refer to the Configuration Guidelines for Detailed Profitability Applications for performance tuning advice.
Level: 1
Type: NOTIFICATION
EPMPCM-10191: Invalid member group found within the assignment rule.
Cause: Invalid member or filter found within member selection.
Action: Alter the assignment rule definition to include valid members of filters.
Level: 1
Type: ERROR
EPMPCM-10192: The specified dimension is not registered as a stage dimension
Cause: One of the dimensions referenced within the assignment rule is not registered as a stage dimension.
Action: Alter the assignment rule definition to include a valid stage dimension.
Level: 1
Type: ERROR
EPMPCM-10193: Expected same as source dimension column missing.
Cause: Same As Source Dimension Column not found within Model Data Registration.
Action: Review both Calculation Rules and Model Data Registration for inconsistencies.
Level: 1
Type: ERROR
EPMPCM-10194: Dimension table generation strategy not configured.
Cause: Unable to configure the hierarchy table performance optimization.
Action: Confirm the Reporting Tables are available within Database Management.
Level: 1
Type: ERROR
EPMPCM-10201: Null passed as attribute name.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10202: Invalid template group.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10203: Null passed as template group name.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10204: Template Group already exists.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10206: Null value passed as template name.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10207: Invalid template name
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10300: Process task xml is not valid. The task type is ''''{0}''''
Cause: Seeded data for the specified task type is invalid.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-10301: HPM job record not found. Job id: ''''{0}''''.
Cause: A job record is missing from the database.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10303: Only jobs with status 'Running' can be stopped.
Cause: The status of the selected job is not appropriate for termination.
Action: Select a different job or wait until the job status is set to Running.
Level: 1
Type: ERROR
EPMPCM-10304: Job was interrupted by user. Task Flow ID : ''''{0}''''.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10305: Calculation Pre script failed.
Cause: An exception occurred during execution of a user script designated to run prior to the calculation.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10310: Task ''''{0}'''' is not found.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10311: Strategy method must be defined for subclass.
Cause: Significant internal implementation error.
Action: Contact Oracle support immediately with this error message.
Level: 1
Type: INCIDENT_ERROR
EPMPCM-10312: SQL Generation Strategy must be chosen.
Cause: Significant internal implementation error.
Action: Contact Oracle support immediately with this error message.
Level: 1
Type: INCIDENT_ERROR
EPMPCM-10313: Dimension Hierarchy Tables are required by SQL Generation. Deploy the Reporting Tables and Views from the Manage Database screen.
Cause: One or more of the required Dimension Hierarchy Tables are missing.
Action: Deploy the Reporting Tables and Views from the Manage Database screen.
Level: 1
Type: ERROR
EPMPCM-10314: Unable to load the Dimension Hierarchy Tables. Deploy the Reporting Tables and Views from the Manage Database screen.
Cause: One or more of the required Dimension Hierarchy Tables are missing.
Action: Deploy the Reporting Tables and Views from the Manage Database screen.
Level: 1
Type: ERROR
EPMPCM-10315: Insertion of dashborad preference "{0}" failed. Dashboard preference name not found.
Cause: The Dashboard Preference name referenced does not exist in the HPM_PREFERENCE_NAME table.
Action: Verify that the Dashboard Preference name matches the row in the HPM_PREFERENCE_NAME table.
Level: 1
Type: ERROR
EPMPCM-10316: Dashboard Name already exists for the given Application
Cause: The Dashboard with following name and application ID already exists.
Action: Either set the Dashboard Id of already existent Dashboard with same name and Application Id or change the name or Application Id.
Level: 1
Type: ERROR
EPMPCM-10317: Analytic Item Name already exists for the given Application
Cause: The Analytic Item with following name and application ID already exists.
Action: Either set the Analytic Item Id of already existent Analytic Item with same name and Application Id or change the name or Application Id.
Level: 1
Type: ERROR
EPMPCM-10318: Security Filter Name already exists
Cause: The Security Filter with following name and application ID already exists.
Action: Either set the Security Filter Id of already existent Security Filter with same name and Application Id or change the name or Application Id.
Level: 1
Type: ERROR
EPMPCM-10319: Invalid filter assignment. You cannot assign filter to yourself.
Cause: The current login was trying to assign filter to themselves.
Action: If you want to assign filter to this login try with other admin user.
Level: 1
Type: ERROR
EPMPCM-10320: The entity has no assigned filters and therefore has full data access.
Cause: The entity has no assigned filters.
Action: If you want to assign filter to this login try with other admin user.
Level: 1
Type: ERROR
EPMPCM-10321: Client Error
Cause: The status of HttpClient executeMethod is not OK.
Action: Check if given AppName is correct and it has Financial Reports in it.
Level: 1
Type: ERROR
EPMPCM-10350: Duplicate driver operation type name: {0}
Cause: There is duplicate data in the Calculation Configuration seed data.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-10400: Bulk Edit terminated: No Sources provided for Bulk Edit Id ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10401: Bulk Edit terminated: No Model Context exists for Bulk Edit Id ''''{0}''''
Cause: The Bulk Edit cannot proceed because there is missing metadata for the application.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00100: No parameters passed on invocation.
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00101: All the expected parameters are not passed on class invocation. The list of parameters to be passed in order are as below:
Cause: The cause of the error is unknown.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-00102: Exiting Java program with status {0}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00103: The version being upgraded from is not a valid starting point: {0}
Cause: The Profitability version of the environment being upgraded is not appropriate for the upgrade being run.
Action: Refer to the Upgrade documentation to verify requirements for the environment to be upgraded.
Level: 1
Type: ERROR
EPMPCM-00104: Verified that the version being upgraded from is a valid starting point.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00105: Upgrade from version lower than 11.1.1.3.XX is not supported.
Cause: You are running the upgrade for an environment that is not at the appropriate version.
Action: Refer to the upgrade documentation for more information.
Level: 1
Type: ERROR
EPMPCM-00106: This is not a supported from version: {0}
Cause: You are running the upgrade for an environment that is not at the appropriate version.
Action: Refer to the upgrade documentation for more information.
Level: 1
Type: ERROR
EPMPCM-00107: Detected a valid upgrade from version of 11.1.1.4.XX.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00108: Detected a valid maintenance install version of 11.1.2.X.XX.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00109: Detected an Oracle Hyperion Profitability and Cost Management database version that is not at the correct 11.1.1.4.XX version level.
Cause: You are running the upgrade for an environment that is not at the appropriate version.
Action: Refer to the upgrade documentation for more information.
Level: 1
Type: ERROR
EPMPCM-00110: Detected an Oracle Hyperion Profitability and Cost Management database version that is not at the correct 11.1.2.X.XX version level.
Cause: You are running the upgrade for an environment that is not at the appropriate version.
Action: Refer to the upgrade documentation for more information.
Level: 1
Type: ERROR
EPMPCM-00111: Invalid existing product version passed: {0}
Cause: The cause of the error is unknown.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-00112: No applications are available in Oracle Hyperion Profitability and Cost Management database to apply EPMA metadata changes.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00121: Applying EPMA metadata changes for application: {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00113: Imposing the uniqueness of Import Configuration name with in an application.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00114: Imposing the uniqueness of Import Configuration name with in an application completed successfully.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00115: Updating Model Preferences to migrate from Essbase physical host names to Essbase cluster names.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00116: Migrating from Essbase physical host names to Essbase cluster names completed successfully.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00117: Updating Model Preferences to migrate from APS physical host names to APS nodes.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00118: Migrating from APS physical host names to APS nodes completed successfully.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00119: No Essbase Cluster name could be found for the following Essbase host name: {0}. Please select the appropriate cluster name using Model Preferences screen.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-00120: No applications found which use connection type as APS to connect to Essbase . So, no changes made to the database for APS node name re-hosting.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10501: Starting task ''''{0}'''' in taskflow ''''{1}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10502: Task ''''{0}'''' for ''''{1}'''' finished. Duration (ms): {2}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10503: Task ''''{0}'''' for ''''{1}'''' failed. Duration (ms): {2}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10504: Clear Caluclation Data job is started for application ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10505: A detailed profit calculation started for the ''''{0}'''' application
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10506: The model point of view is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10507: The data point of view is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10508: The processing option for this calculation are as follows.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10509: Create Contribution Detail checkbox selected, The disk storage used by detailed contribution information may be large.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10510: Starting task ''''{0}'''' for the application ''''{1}'''' in the taskflow ''''{2}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10512: Create detailed calculated driver tables checkbox selected
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10513: Pre-script name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10514: Post-script name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10515: Pre-script not selected
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10516: Post-script not selected
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10517: Abort taskflow if any POV fails checkbox selected
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10531: A cube deployment started for the ''''{0}'''' application
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10532: The cube type is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10533: The replace cube option is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10534: A data export started for the ''''{0}'''' application
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10535: The Essbase application type is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10536: The data file name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10537: The rule file name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10538: A data import started for the ''''{0}'''' application
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10539: The delete archived artifacts is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10520: Application Name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10523: Dimension Name is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10524: Number of potential assignments detected is {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10525: The number of assignments with valid sources is {0}
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10527: Source table has {0} no registered measure dimension columns. The Stage Balance View will not be created for this calculation.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10528: Starting task ''''{0}'''' in the taskflow ''''{1}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10529: Run a single calculation rule sequence check box is selected, the Sequence Number is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10530: Run a single calculation rule sequence check box is not selected
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10601: Data POV is ''''{0}''''
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10602: The Measure column {0} must be associated with a Measure Dimension Member
Cause: The specified column is registered as a Measure column but does not map to a valid member of the Measure dimension.
Action: Edit the registration for the specified column so that it maps to a valid Measure member.
Level: 1
Type: ERROR
EPMPCM-10700: Bulk Edit Source Rules are ''''{0}'''';
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10701: Bulk Edit Destination Rules are ''''{0}'''';
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10702: Bulk Edit mode is Add Assignments;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10703: Bulk Edit mode is Remove Assignments;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10706: Bulk Edit Drivers are ''''{0}'''';
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10707: Bulk Edit Source Rules are Entire Stage;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10708: Bulk Edit Destination Rules are All;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10709: Bulk Edit Drivers are All;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10710: Bulk Edit mode is Remove Drivers;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10711: Bulk Edit mode is Add Drivers;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10730: Deploy Reporting Views Started;
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-10750: Duplication of Application failed;
Cause: An error occurred while duplicating an application.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10751: Reregister of Application failed;
Cause: An error occurred during application reregistration.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-10752: Deletion of Application failed;
Cause: An error occurred during application deletion.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-20000: Invalid application name: ''''{0}''''.
Cause: The specified application name is not valid.
Action: Specify a valid application name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20001: Invalid import configuration name: ''''{0}'''' associated with application: ''''{1}''''
Cause: The specified import configuration name does not belong to the application.
Action: Specify an import configuration name that belongs to the application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20002: Invalid layer name: ''''{0}''''.
Cause: The specified layer name is not valid.
Action: Specify either Cost or Revenue as the layer name.
Level: 1
Type: ERROR
EPMPCM-20003: Invalid dimension member group combination: ''{0}'', ''{1}'', ''{2}'', ''{3}''.
Cause: The input dimension member combination is not valid.
Action: Correct the input dimension member combination.
Level: 1
Type: ERROR
EPMPCM-20004: Invalid stage name: ''''{0}''''.
Cause: The specified stage name does not exist for the application.
Action: Create the stage in the application and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20006: Invalid Data Options selection. Please select either 'Archive Data Before Deploy' or 'Archive Data and Reload After Deploy'.
Cause: The user has selected invalid Data Options.
Action: Select either 'Archive Data Before Deploy' or 'Archive Data and Reload After Deploy' as the Data Option and the retry the operation.
Level: 1
Type: ERROR
EPMPCM-20007: Invalid Data Options selected. 'Archive Data Before Deploy', 'Archive Data and Reload After Deploy' or 'Delete Data Archive After Reload' cannot be selected when 'Replace Database' is selected.
Cause: Invalid Data Options selected.
Action: Verify that the Replace Database option is compatible with the selected Data Options.
Level: 1
Type: ERROR
EPMPCM-20008: POV information not specified.
Cause: A Point of View was not specified.
Action: Specify a Point of View and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20009: Application name not specified.
Cause: An Application name was not specified.
Action: Specify an Application name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20010: Import configuration name not specified.
Cause: An Import Configuration name was not specified.
Action: Specify an Import Configuration name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20011: Layer name not specified.
Cause: A Layer name was not specified.
Action: Specify a Layer name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20012: No genealogy calculation paths specified.
Cause: No genealogy calculation paths were specified.
Action: Specify a genealogy calculation path and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20013: No selections made to copy POV data.
Cause: One or more of the required options for the Copy POV data service was not specified.
Action: Specify all required options for the Copy POV data service and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20014: Stage name not specified.
Cause: A stage name was not specified.
Action: Specify a stage name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20015: Cube type not specified.
Cause: A Cube type was not specified.
Action: Specify a Cube type and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20016: Parameter ''''{0}'''' cannot be null.
Cause: A required parameter for the web service was not specified.
Action: Refer to the server logs for more information.
Level: 1
Type: ERROR
EPMPCM-20017: More than one POV group retrieved for the specified dimension member group ''''{0}''''.
Cause: The cause of the error is unknown.
Action: Contact Oracle Support for assistance.
Level: 1
Type: ERROR
EPMPCM-20018: Preference Value not specified.
Cause: Preference value is not specified.
Action: Specify a Preference Value and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20019: Application type not specified.
Cause: An Application Type was not provided for the operation.
Action: Provide an Application Type for the operation.
Level: 1
Type: ERROR
EPMPCM-20020: Invalid option(s) selected when performing Copy POV for a Detailed Profitability application. Only Driver Selections, Assignments and/or Stage Object Calculations can be selected.
Cause: The Copy POV web service was invoked with invalid options.
Action: Allowed options for the Copy POV web service include only Driver Selections, Assignments and/or Stage Object Calculations. Reselect one or more allowed options and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20021: Invalid Calculation Rules option selected for a Standard Profitability application.
Cause: One of the selected options is not allowed for use with Standard Profitability.
Action: Verify that the options selected for the operation are allowed for Standard Profitability applications and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20022: Invalid operation for application type: ''''{0}''''
Cause: An option has been selected that is not allowed for the given application type.
Action: Verify that the options selected for the operation are allowed for the application type and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20023: No Bulk Edit operation specified.
Cause: The web service call does not specify any Bulk Edit operations.
Action: Verify that a Bulk Edit operation is specified and retry.
Level: 1
Type: ERROR
EPMPCM-20024: Source assignment rules not specified.
Cause: No source assignment rules are specified for the web service call.
Action: Specify one or more source assignment rules for the web service and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20025: Destination assignment rules not specified.
Cause: No destination assignment rules are specified for the web service call.
Action: Specify one or more destination assignment rules for the web service and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20026: Drivers not specified.
Cause: No drivers are specified for the web service call.
Action: Specify one or more drivers for the web service and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20027: Destination assignment rules specified for Add/Remove Drivers.
Cause: Destination Assignment Rules have been specified for an Add/Remove Drivers operation.
Action: Verify that the web service is called with allowable options and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20028: Drivers specified for Add/Remove assignment rules.
Cause: Driver were specified for an Add or Remove Assignment rule operation.
Action: Do not specify Drivers when running an Add or Remove Assignment rule operation.
Level: 1
Type: ERROR
EPMPCM-20029: Source/Destination Assignment rules specified when 'Remove All' option is selected.
Cause: You have specified contradictory options for the web service call.
Action: If the Remove All option is specified, you cannot also specify individual Source/Destination Assignment rules. Correct the web service options and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20030: Drivers specified when 'Remove All' option is selected.
Cause: You have specified contradictory options for the web service call.
Action: If the Remove All option is specified, you cannot also specify individual Drivers. Correct the web service options and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20031: More than one driver specified for 'Add Drivers' operation.
Cause: Multiple drivers were specified for the Add Driver web service call.
Action: Specify a single Driver and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20032: Invalid selection of 'Remove All' flags for Add Drivers/Assignment rules operation.
Cause: You have specified contradictory options for the web service call.
Action: The Remove All option cannot be selected when calling the web service for Add Drivers/Assignment rules.
Level: 1
Type: ERROR
EPMPCM-20033: Invalid assignment rule name: ''''{0}''''
Cause: You have specified an invalid assignment rule name for the web service call.
Action: Specify a valid assignment rule name for the web service call and retry.
Level: 1
Type: ERROR
EPMPCM-20034: Invalid driver name: ''''{0}''''
Cause: A you have specified an invalid driver name for the web service call.
Action: Specify a valid driver name for the web service call and retry.
Level: 1
Type: ERROR
EPMPCM-20035: ''''{0}'''' is not a valid source assignment rule.
Cause: You have specified an invalid name for source assignment rule.
Action: Specify a valid source assignment rule name for the web service call and retry.
Level: 1
Type: ERROR
EPMPCM-20036: ''''{0}'''' is not a valid destination assignment rule.
Cause: You have specified an invalid name for destination assignment rule.
Action: Specify a valid destination assignment rule name for the web service call and retry.
Level: 1
Type: ERROR
EPMPCM-20037: Driver: ''''{0}'''' of type: Object Calculation cannot be selected for Bulk Edit operation.
Cause: You have specified an invalid Driver for the Bulk Edit operation.
Action: Specify a Driver of a type that is not Object Calculation for the web service call and retry.
Level: 1
Type: ERROR
EPMPCM-20038: Invalid reporting dimension name: ''''{0}''''
Cause: The dimension name or short name specified does not map to a valid dimension for this application.
Action: Specify a dimension name or short name that is valid for the application and retry.
Level: 1
Type: ERROR
EPMPCM-20039: Model data schema is not defined for application: ''''{0}''''.
Cause: The specified application does not have a model data schema defined.
Action: Define a model data schema for the application and retry.
Level: 1
Type: ERROR
EPMPCM-20040: No reporting dimension available for application: ''''{0}''''.
Cause: No reporting dimensions have been defined for the specified application.
Action: Designate one or more reporting dimensions for the application and retry.
Level: 1
Type: ERROR
EPMPCM-20041: Short name missing for dimension: ''''{0}''''.
Cause: The specified dimension does not have an assigned Short Name.
Action: Designate a Short Name for the dimension and retry.
Level: 1
Type: ERROR
EPMPCM-20042: Model POV is not defined.
Cause: You did not specify a Model Point of View for the web service call.
Action: Specify a Model Point of View and retry.
Level: 1
Type: ERROR
EPMPCM-20043: No Data POV(s) are defined.
Cause: You did not specify a Data Point of View for the web service call.
Action: Specify a Data Point of View and retry.
Level: 1
Type: ERROR
EPMPCM-20044: Create Contribution Detail, Create Detailed Calculated Driver Tables or Run a single Calculation Rule sequence cannot be specified when 'Execute Calculations' is not selected.
Cause: You have specified contradictory options for the web service call.
Action: You must selected 'Execute Calculations' if you specify one or more of the following options: Create Contribution Detail, Create Detailed Calculation Driver Tables or Run a Single Calculation Rule Sequence. Verify that the web service options are compatible and retry.
Level: 1
Type: ERROR
EPMPCM-20045: Preference Name not specified.
Cause: Preference name is not specified.
Action: Specify a Preference name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20046: Invalid REST API Version ''{0}''.
Cause: Invalid REST API Version.
Action: Specify valid version and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20047: Invalid dimension member name: ''''{0}''''.
Cause: You have specified an invalid dimension member name for the web service call.
Action: Specify a valid dimension member name and retry.
Level: 1
Type: ERROR
EPMPCM-20048: Select either the Cost or Revenue layer.
Cause: You have specified an invalid Layer for the web service call.
Action: Specify either Cost or Revenue for the Layer and retry.
Level: 1
Type: ERROR
EPMPCM-20049: Select at least one delete parameter (Driver Selections or Assignments).
Cause: The Clear Point of View web service is being invoked without specifying a parameter for what is to be cleared.
Action: Specify the appropriate delete parameter (Driver Selections, Driver Exceptions, Assignment Rule Selections, Assignments or Calculation Rules) and retry.
Level: 1
Type: ERROR
EPMPCM-20050: Select the stages to be affected.
Cause: No stages were specified for the operation.
Action: Specify one or more stages and retry.
Level: 1
Type: ERROR
EPMPCM-20051: No calculation rule sequence is specified when Run a single calculation rule sequence is selected.
Cause: The option to Run a Single Calculation Rule Sequence was selected without specifying a sequence.
Action: Specify a Calculation Rule Sequence and retry.
Level: 1
Type: ERROR
EPMPCM-20052: Calculation rule sequence is specified when Run a single calculation rule sequence is not selected.
Cause: A Calculation Rule Sequence value was specified without selecting to Run A Single Calculation Rule Sequence.
Action: Specify to Run A Single Calculation Rule Sequence and retry.
Level: 1
Type: ERROR
EPMPCM-20053: The calculation sequence should be greater than 1 and less than or equal to 9999.
Cause: The specified Calculation Rule Sequence is an invalid value.
Action: Specify a value between 1 and 9999 for the Calculation Rule Sequence and retry.
Level: 1
Type: ERROR
EPMPCM-20054: Clear POV can only clear data for the Source Stage of a Detailed application.
Cause: An invalid Stage was specified for a Clear Point of View operation.
Action: Only the Source Stage can be specified for a Detailed Profitability application Clear Point of View operation. Specify a valid Source Stage and retry.
Level: 1
Type: ERROR
EPMPCM-20055: Invalid Rule Set name: ''{0}''.
Cause: The Rule Set name is not available in the system for the given artifact
Action: Provide the correct Rule Set name and resubmit the operation
Level: 1
Type: ERROR
EPMPCM-20056: Invalid Rule name: ''{0}''.
Cause: Rule name is not available in the system for the given artifact
Action: Provide the correct Rule name and resubmit the operation
Level: 1
Type: ERROR
EPMPCM-20057: POV must be in draft status in order to perform this operation.
Cause: Destination POV is not in draft status
Action: Provide the correct destination pov with draft status and resubmit the operation
Level: 1
Type: ERROR
EPMPCM-20058: REST API Version {0} is not authorized for your installation.
Cause: This feature is not authorized
Action: This feature needs to be enabled in the feature authorization list
Level: 1
Type: ERROR
EPMPCM-20059: No selections made to clear POV data.
Cause: One or more of the required options for the Clear POV data service was not specified.
Action: Specify all required options for the Clear POV data service and retry the operation.
Level: 1
Type: ERROR
EPMPCM-20101: LCM Import will not import Model Data Schema preferences as the Model Data Schema is already set.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-20102: LCM Import will not import tables if they are already registered.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-20103: LCM Import will not import table joins if they already exist.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-20106: LCM Import will not import Calculation Process Definition if it already exists.
Cause:
Action:
Level: 1
Type: NOTIFICATION
EPMPCM-20107: Invalid model view name: ''''{0}''''.
Cause: The specified model view name is not valid.
Action: Specify a valid model view name and retry the operation.
Level: 1
Type: ERROR
EPMPCM-09303: Driver is used in Calculation Rules.
Cause: You are changing the driver type but the Driver is used in existing Calculation Rules.
Action: Remove the existing Calculation Rules and retry the import.
Level: 1
Type: ERROR
EPMPCM-09326: Table ''''{0}'''' is not found in user schema.
Cause: The specified table does not exist in the user schema.
Action: Create the table in the user schema and retry the import.
Level: 1
Type: ERROR
EPMPCM-09330: Table ''''{0}'''' is not registered.
Cause: The specified table is not registered in Model Data Registration.
Action: Register the table in Model Data Registration and retry the import.
Level: 1
Type: ERROR
EPMPCM-20200: ''{0}''
Cause: Error loading data to Essbase
Action: Correct error in the filename mentioned and load again
Level: 1
Type: ERROR
EPMPCM-20250: User preference was not set for the dimension {0}. Please select a user preference prior to running this analytic.
Cause: User preference was not set, but was chosen in the analytic
Action: Set the user preference and run the analytic again
Level: 1
Type: ERROR
EPMPCM-20251: Year must be selected in the Analysis View if Period is selected.
Cause: The Year dimension must be selected in the Analysis View if a member is selected for the Period dimension.
Action: Make a selection for the Year dimension and run the analytic again.
Level: 1
Type: ERROR
EPMPCM-20252: Year dimension and Current Year must be selected in Application Settings - Calendar prior to running.
Cause: The Year dimension and Current Year have not been selected in Application Settings - Calendar.
Action: Set the Year dimension and Current Year and re-try the operation.
Level: 1
Type: ERROR
EPMPCM-20253: Unexpected Essbase Error While Creating Filter ''''{0}''''.
Cause: The cause of the error is unknown.
Action: Refer to the essbase server logs for more information.
Level: 1
Type: ERROR
EPMPCM-20254: Unexpected Essbase Error While deleting Filter ''''{0}''''.
Cause: The cause of the error is unknown.
Action: Refer to the essbase server logs for more information.
Level: 1
Type: ERROR
EPMPCM-20255: User/group ''''{0}'''' does not exist or does not have access to the cube.
Cause: User/group doesn't exist or doesn't have access to the cube.
Action: Need to create user/group and give access to the cube.
Level: 1
Type: ERROR
EPMPCM-20256: The member selection for the dimension ''''{0}'''' does not exist.
Cause: The selected member does not exist.
Action: Run validations for more information.
Level: 1
Type: ERROR
EPMPCM-30000: Potential Source Count {0} is exceeding the Upper Limit {1}.
Cause: Potential Source Count is exceeding the upper limit.
Action: User need to unselect some of the source member selections.
Level: 1
Type: ERROR
EPMPCM-30001: Potential Destination Count {0} is exceeding the Upper Limit {1}.
Cause: Potential Destination Count is exceeding the upper limit.
Action: User need to unselect some of the destination member selections.
Level: 1
Type: ERROR
Oracle Hyperion Profitability and Cost Management Error Message Reference
F24157-01
Copyright © 2019, Oracle and/or its affiliates. All rights reserved.
Primary Author: EPM Information Development Team
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
To provide feedback on this documentation, send email to epmdoc_ww@oracle.com, or, in an Oracle Help Center topic, click the Feedback button located beneath the Table of Contents (you may need to scroll down to see the button).
Follow EPM Information Development on these social media sites:
LinkedIn - http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051
Twitter - http://twitter.com/hyperionepminfo
Facebook - http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642