Rules

The Consolidation Status Monitor tracks changes to these items.

• Reported, periodic, local, untranslated data.
• Intercompany data.
• Local web journal data + Acquisition journals (by currency).
• Any member of any dimension.

You can make changes through Start New Year, a data entry page, Data Loader, OpenLink, web journal entry, a consolidation, Copy Financial Data, Erase Data, Prepare Intercompany Eliminations, or SQL tools.

CSM does not track changes to:

• Previous year-end data (must run Start New Year).
• Off-sheet references in formulas.
• Ownership properties.
• Exchange rates.
• Values when the value is being resubmitted to the database (changes are only tracked if the new value is different from the old value).

CSM tracks local currency.

CSM does not track point consolidations, consolidations with Suppress Leaf Writeback enabled, or consolidations of non-reporting dimension members that are not top-level members in the hierarchy.

CSM tracks changes to:

• The Rate Set attribute for the Version dimension.
• These account attributes: Account Type, Consolidate, Natural Sign, Precision, and Rate.
• These unit attributes: Consolidate, Percent Ownership, and Currency.
• These currency attributes: Precision and Translate Type (when Translation Type changes for a currency, any unit using that currency as its local currency is tracked; the currency is also tracked).
• This rate attribute: Translation Method (when Translation Method changes for a rate, any account using that rate is tracked; the rate itself is not tracked).
• Parent-child relationships in the Unit dimension or a custom hierarchical dimension (adding, deleting, or moving members).

CSM does not track changes to:

• Formulas.
• Architect journals.
• The Unit dimension or custom hierarchical dimensions by adding or reordering members.
• The Schedule dimension by adding, moving, or reordering lines.
• These unit attributes: Elimination Status and Class.
• These schedule attributes: Category, Class, Periodicity, and Required.
• These account attributes: Balanced, Formula Type, and Usage.

When local data is changed, all translated data is impacted for that data slice.

When a leaf node is impacted (by data, consolidation date/time, or structure changes), so are its ancestors.

The status for a data slice is impacted when:

• An approved (Available for Posting) journal with at least one adjustment is submitted.
• A change to an approved journal is submitted (i.e., change to the version, periodicity, or any part of an adjustment line, such as schedule, unit, affiliated unit, amount, currency [for intercompany and acquisition lines], debit/credit, and/or custom dimension). The new journal definition and any previous submitted edits to the journal definition since the last consolidation will show as impacted for all periods in the effective life.
• A new currency value is submitted for a posted Acquisition journal (only the status for the new currency will show as impacted).
• The status of a Working - Not Available for Posting journal is changed to Available for Posting.
• The effective life of an approved or posted journal is extended. For posted journals, only the new or additional periods will show as impacted. Reducing an effective life does not impact data. For approved journals, the entire effective life will show as impacted.
• (PL-BS journals Only) For balance sheet lines, all periods that extend beyond the effective life to the end of the year will show as impacted due to the carry-forward nature of balance sheet lines from one period to the next.

The status will not be impacted for a data slice when:

• A journal is created with no adjustments.
• The journal name or description is changed.
• The status of an approved journal is changed back to Working - Not Available for Posting.
• The effective life of an approved or posted journal is reduced.
• The periodicity or effective life is changed but the effective life range does not include a leaf period of the schedule periodicity.
• An adjustment is deleted from an approved journal or an approved journal is deleted.
• The effective life includes the Opening Balance period. Journals cannot post to the Opening Balance period. If other periods are included in the effective life besides Opening Balance, those periods will show as impacted.

If a report includes a period range and schedules of varying periodicities (not recommended), any cells that are associated with an irrelevant period-schedule combination (such as for a monthly period with a quarterly schedule) will display the text No Status, and the cells are colored gray (or your customized No Status color).

A data slice is impacted when the date of the change occurs after the date of the last consolidation.

The consolidation status is reported by schedule (not by line).

If data is submitted during a consolidation:

• Impacted data is correctly displayed for translated currency.
• Some impacted data may incorrectly display as current data for local currency.

The consolidation status of any member is considered non-confidential. Therefore, a user with no access to a member can view the consolidation status for that member and any of its descendants.

Schedules are displayed by the member order as defined in Architect.