Time Horizons and Migration

Use

To migrate data properly, you should customize the budget scope in BCS at the same level of detail as in Former Budgeting for availability control. If these two settings are not consistent, the data will not be migrated. This applies to the subject of overall and annual funds, since they are handled differently in FB and BCS.

After setting the time horizons that you want to use for budgeting in Customizing (see “Activities” below), you must decide how to migrate the data to the BCS time horizons you define.

Activities

Predefine your budget scope in BCS, as previously specified in the FB budget profile. For this, go to the Implementation Guide in: Funds Management Government Master Data Fund Create FM Fund Types . In the column “Budget Scope”, specify whether you want to work with overall or annual budgets.
Next, assign the relevant fund type to the funds you have created using transaction FM5I.
If you are only working with annual funds, and have not activated multi-year budgeting in FM Customizing ( Basic Settings ), no maintenance work is necessary, since “annual” will be the default value.

Example

The following table gives an overview of the various migration possibilities, where B = FB Budgeting scope andC = FB Availability control level. For overall funds, the year “0000” is used in FB.

Note that, depending on the kind of data you want to migrate, the migration path will differ.

FB Customizing Settings	Budgeting Data Year Budget	BCS Customizing Settings	SAP Migration Proposal / System Reaction
B: Overall funds C: Overall funds	0000$ 2500	Overall	Via totals migration OR document migration: The full amount will be assigned to the default year: For example, 2004 $ 2500
B: Overall & annual funds C: Overall funds	0000$ 2500 2002$ 1000 2003$ 1000 2004$ 400 2005$ 100	Overall	Via totals migration: The budget of all years before BCS activation will be migrated at once, to the same fiscal year. $ 1000 $ 1000 $ 1000 A message is sent informing you about the difference between overall budget ($2500) and the amount migrated to BCS ($2000). Via document migration: The budget of all BCS years will be migrated to the same year. $ 400 $ 100 $ 100
C: Overall		Annual	Error message on time horizon inconsistency in FB and BCS
B: Overall & Annual C: Annual	0000$ 2500 2002$ 1000 2003$ 1000 2004 $400 2005 $100	Annual	Per fiscal year (depending on user selection). An info message for the delta between the migrated amount and the overall amount is issued for totals migration.
B: Annual C: Annual	2002$ 1000 2003$ 1000 2004 $400 2005 $100	Annual	Migration is done per fiscal year (depending on user selection).
C: Annual		Overall	Error message on time horizon inconsistency in FB and BCS

Note that you can migrate all documents regardless of whether the fiscal year is before or after BCS activation. This is an extended use of the migration report FMKUMIGDOC, which you can use in particular in the context of overall funds containing annual values.

Overall Funds and Availability Control

If you migrate overall funds to BCS, you should first customize availability control in BCS (and, if necessary, the budget structure), in order to be able to retrieve the actuals for previous years. In this case, you should activate BCS availability control from the first year for which actuals data exists for migrated overall funds. Furthermore:

You should (if relevant) define a budget structure for all the years for which actuals data exists for overall funds migrated from Former Budgeting.
After the migration run, you will have to reconstruct AVC for these funds and all fiscal years for which actuals exist, as AVC data is not subject to data migration.
If the actuals of previous years change after migration, they will be checked automatically by AVC, regardless of the fund involved. Therefore, if this occurs for an annual fund, you should also include it in the budget structure and assign a “dummy” tolerance profile to it for the years before BCS activation, in order to not be blocked by BCS for postings relating only to Former Budgeting.

Another option is not to migrate overall funds, but only enter in BCS the residual amount that was not consumed during the Former Budgeting years. If so, you should always update BCS if new actuals occur for previous years, in order to correct the amount of the residual budget.

For further information, see BCS Availability Control .

Overall Funds and Reporting

In Former Budgeting, the amount for an overall fund was stored using fiscal year “0000”. In BCS, this is not supported and the overall amount is the sum of all fiscal year amounts . This has an impact on reporting: for overall funds, you have to aggregate over all fiscal years.Since aggregation rules differ depending on whether you are working with overall or annual funds, you must run the report separately for each kind of fund.

Workaround : You can use a “pseudo fiscal year” as the year for your overall data (for example, the BCS starting year). In this way, you do not need to aggregate several years to determine the overall amount.