Validating Metadata

About Validate Metadata

Use the Validate Metadata setting (formerly called Autocorrect Errors) as part of the database refresh process to scan for and automatically resolve member identity (ID) mismatches between the business process and Oracle Essbase.

Caution:

Selecting Validate Metadata might add additional time to the refresh process.

In certain cases, the identity of a member changes in a way that causes it to be not fully recognized in the multi-dimensional database used by the application. When a member’s identity is not fully correctly established within all parts of the system, it could sometimes cause hierarchy issues like incorrect member ordering, or it could miss children underneath that member, or miss some siblings, or miss certain properties, and so on. Selecting Validate Metadata detects such members and automatically resolves their identity, allowing these members as well as their hierarchies along with properties and siblings, to be fully and correctly recognizable and usable within all the parts of the system.

Viewing the Report Detailing Member Movement and Deletion

After making member ID corrections, members might be deleted or moved. A report file detailing any member movement (to a different parent) or deletion is generated and placed in the Outbox in a csv (comma-delimited) file format. Review the report to reaggregate some of the stored parent members where the child hierarchy may have changed.

For example:

The system generates a CSV file to the Outbox folder, and the filename is automatically generated with the application name followed by _autocorrect.csv; for example, vision_autocorrect.csv. This file is overwritten on each run.

After running the Refresh Database job with the Validate Metadata setting, you can download the export file from the Outbox.

To download files:

1. Click Application, and then click Jobs.

2. Under Recent Activity, click the job.

3. At the top of Job Details, click the export file option to select a download location.