Show TOC

Function documentationAutomatic Adjustments Locate this document in the navigation structure

 

You use automatic adjustments when generating consolidation entries for a group of entities, such as eliminations, adjustments, reclassifications, and minority calculations

The automatic adjustments process is handled by a stored procedure called SPRUNCONSO. This procedure is typically launched using the logic statement:

*RUN_STORED_PROCEDURE=SPRUNCONSO(parameters list)

Example:

*RUN_STORED_PROCEDURE = SPRUNCONSO([%APP%],[%CATEGORY_SET%],[%GROUPS_SET%],[%SCOPETABLE%],[%LOGTABLE%])

The driving elements of this procedure are:

  • The consolidation METHOD by which each ENTITY is consolidated into a GROUP.

  • The consolidation RULE assigned to each ACCOUNT to consolidate.

  • The ELIMINATION mechanism, as controlled by each RULE (in turn driving the behavior of each ACCOUNT).

The whole process is as follows:

Each source ACCOUNT is assigned a set of DESTINATION ACCOUNTS and a RULE of behavior through the definitions entered in the Automatic Adjustments business rule table.

For information on required properties of the Data Source dimension, see Setting up a legal consolidation application set.

The following table describes the values you can enter for the automatic adjustment rules.

Field Name

Description

Adjustment ID

The identifier for the adjustment rule.

Source data source

This field may contain the following values:

  • Blank (all DATASRC members)

  • A valid base level or parent member ID from the DATASRC dimension

  • A list of members of the DATASRC dimension, as defined by filtering the members using a value of the DIMLIST property (or any property whose name begins with DIMLIST) in such dimension.

Destination data source

This field must contain a valid base level member ID of the DATASRC dimension having the property DATASRC_TYPE = A (Automatic elimination)

Group type filter

The CONSO_TYPE property value from the Groups (Currency) dimension. If, for example, you have the GROUP GROUP1 with conso_type = A, all the Automatic Eliminations with Blank are available for all groups. The Automatic Eliminations with Group_filter member = A are available for GROUP1 and all groups with Group filter member = A.

Adjustment type

This field may contain the following values:

  • Blank: A generic ELIM rule

  • E: Equity - This value indicates that this rule is used on the entities using an Equity method, for example, having a method of type E

  • P: Proportional - This value indicates that this rule is used on the entities using a Proportional method, for example, having a method of type P)

  • N: New - This value indicates that this rule is used on the entities just entering into the consolidation perimeter, for example, having a method of type N)

  • L: Leaving - This value indicates that this rule is used on the entities that are leaving the consolidation perimeter, for example, having a method of type L)

In case this field has a nonblank value, there are never details associated with it in the clcELIM table.

Adjustment level

This field must contain an integer value ranging from 0 to 99 and can be used to order the sequence of execution of the various ELIM rules, if desired.

Entity property filter

This field is only used for intercompany eliminations. If this field contains a value, the system looks for the existence of a corresponding PROPERTY in the ENTITY dimension, and only performs the elimination if the ENTITY. The INTCO partner has the same value in this property.

Other dimension filter

This field can be used to define a filter controlling the region where the elimination can be applied. It can contain the following values:

  • Blank (No Filter)

  • An expression defining one or more filters. These can be applied to any combination of the following information:

    • The SIGNEDDATA amount (example: SIGNEDDATA> 10)

    • Any ACCOUNT of the OWNERSHIP cube (example: METHOD = 85)

    • Any ACCOUNT of the OWNERSHIP cube as defined in Prior period (example: PPOWN <>0, where PPOWN is Prior period’s POWN account)

    • Any ACCOUNT of the OWNERSHIP cube as assigned to the INTER_COMPANY partner (example: I_POWN < POWN)

The filters can be concatenated with the AND operand. Alternatively, any valid SQL expression filtering the values in any desired way can be used. In this case the syntax must strictly comply with SQL requirements, for example single quotes around the members IDs.

Forced destination members

This field can be used to enforce the destination member of any dimension existing in the MAIN cube.

This field may contain the following values:

  • Blank (No Change)

  • An expression enforcing the value for one or more dimensions of the MAIN cube. Each dimension must be separated by a comma (example: CATEGORY=BUDGET, ENTITY= NewYorkBranch)

Remark

A description of the rule.