Reuse of Additional Financial Data 

Use

You use this function so that in the context of a Version you can also use defined Additional Financial Data in other versions. As a result, you only need to enter the additional financial data once. This reduces the effort if you work with several version combinations within a Consolidation Area.

Prerequisites

You can use additional financial data across different consolidation areas only if the individual consolidation areas have different version combinations. However, if the Role ‘Fixed in Consolidation Area’ is assigned to the characteristic dimension and the characteristic has a different value for each consolidation area, additional financial data can only be saved cross-version for each consolidation area (and not across several consolidation areas).

Features

You can have read and write access to the same additional financial data with several version combinations. Use the concept of special versions for additional financial data for this. This concerns the data streams inventory data, supplier data, investments and equity (see also Data Basis).

To reuse additional financial data, in the Process view of the workbench, choose Master Data ® Versions ® Special Version ® Definition and (assuming they do not exist) create special versions for supplier data (D4), investments (D5) and equity (D6).

By defining Rules you determine the standard behavior for objects to which the special version is assigned. For the Version Type: Additional Financial Data enter which assignment between special version and version should be predefined for inventory data, supplier data, investments, and equity.

If you work with several special versions, you need to make the setting All Values for at least one of the assigned characteristics.

Using Assign to Combinations, you can define for individual version combinations to which special version they should be assigned (provided that you want an assignment that differs from standard behavior). Using Storage of Additional Financial Data, you define how the special version types should be assigned to the version combinations defined earlier.

If you delete additional financial data that is used more than once, this automatically has an effect on all version combinations in which the additional financial data is used.

Example

You want to transfer additional financial data that you want to use for consolidation in different versions (plan vs. actual, German HGB vs. U.S. GAAP). Your data model contains two characteristics: V1 (consolidation version) and V2 (accounting principle). In Customizing of the data basis, you have assigned both characteristics to the role Version.

You define the values 001 (actual) and 002 (plan) for characteristic V1, the values ‘U.S. GAAP’ and ‘German HGB’ (Master Data ® Versions)  for characteristic V2. You have also created the version combinations (001, U.S. GAAP), (001, German HGB) and (002, U.S. GAAP) (Master Data ® Versions ® Version Combinations).

Now you create the special version SV1 for supplier data (Master Data ® Versions ® Special Versions ® Definition). Here in the lower left area of the screen you add an entry with the value SV1 as a subentry of D4 (supplier data). Proceed in the same way for the special versions D5 (investments) and D6 (equity).

Now define the (standard) rules for the additional financial data (Master Data ® Versions ® Special Versions ® Rules). Process the nodes supplier data, investments, and equity under Additional Financial Data in the lower left area of the screen.

Select All Values for V1 and V2 and assign SV1. As a result, the standard behavior is defined. All version combinations now refer to the special version SV1.

Now you can make a special setting (that differs from the standard behavior) for the version combination (001, U.S. GAAP) by assigning combinations.

Under Storage of Additional Financial Data you define in which version combination from V1 and V2 data should be saved physically for the special version ‘SV1’. For example, you could choose the version combination (001, German HGB).

If you now use flexible upload to transfer supplier data for a version combination into the system, you can check for which version combinations this data is available using the database list of supplier data.