Contribution versions

The contribution versions in the target are prefixed with CO. Automatic journal types have the same code as in the source with one exception; the base value automatic journal type which is displayed as BASEET because ' ' is not a valid name in the target. You can configure the naming convention in the FAP client.

The transformation of automatic journals introduces complexity due to support for cross-ownership in IBM® Cognos® Controller. The challenge is to store values in a summation node in a cube while accommodating the way in which IBM Cognos Controller handles cross-owned companies.

For this transformation the concept of elimination company (EC) is used, which is similar to the Publish to Data Mart function. In Financial Analytics Publisher, the naming convention is to give the same name for the EC company as for the group. For example, for the group named Grp1, the elimination company is also called Grp1. For more information, see The Company dimension. In the Publish to Data Mart function in IBM Cognos Controller the name would have been EC_Grp1.

On a high level, all automatic journals 30 (rebooking of subsidiaries change in equity) and automatic journal 37 (allocations) are by default kept on the company level in the target. Other automatic journals are moved to the elimination company in the target. A server preference (ETYPE_EXCLUDE2) is available to modify this default behavior. By using ETYPE_EXCLUDE2 you state which automatic journal types should remain on the company in the target, instead of being transferred to the elimination company. Note that this does not affect eliminations on groups or cross-owned companies; those journals will always be transferred to the elimination company.

Note: Any modification of the server preference should be done with caution, especially if cross-ownership exists in the company structure.

It is followed by these rules:

  • When company type = K (that is, the sub-group) and VerificationType = K then exclude the row completely from the transformation. This is because these journals are also in a company below (and we do not want them to be stored twice).

Followed by this set of rules:

  1. Transactions (automatic journals) with specific KtypKonc (cross-ownership) move to the EC company.

    For example, in the case of cross-ownership, the ktypkonc would be LEGrp1, and not LE. In situations without cross-ownership, the ktypkonc would be LE or OP.

  2. Transactions with KtypKonc <> " " on sub-groups (that is, automatic journals booked directly on sub-groups) move to the EC company belonging to the group above.
  3. Transactions with KtypKonc = " " - stay on the company (BASE values), unless the server preference says differently.
  4. Automatic journal types 30 and 37 stay always on the company.

    Server preference addition:

    If the server preference is set, automatic journal types in the server preference stay on the company, all other automatic journal types go to the EC company:

    • For example, if you want the automatic journal types 10, 35, and 90 to stay at the company level, the server preference should look like this: ETYPE_EXCLUDE2=10,35,90.
      Note: You must not indicate the automatic journal types 30 and 37 in the server preference as, per default, these automatic journals always stay at the company level.