Former Budgeting Analysis

Which functionality is the customer currently using in Former Budgeting?

Overall budget

Release

Availability control

Budget structure

Revenues Increasing the Budget

Budget distribution

Cover pools (cover eligibility)

Carryforward of residual budget

Carryforward of open commitments with budget

Local locks

Year of cash effectivity

Others (to be specified)

Which budget subtypes are used in Former Budgeting and how they are used?

Can they be easily mapped to BCS budget types using a 1:1 relationship?

Which specific FB subtypes need to be treated in a different way (for example, FB subtypes for carryover)?

Which budget types are used in Former Budgeting and how they are used?

Can they be easily mapped to BCS processes using a 1:1 relationship?

Which specific budget types need to be treated in a different way?

Which FM update profile is the customer using?

Is the customer using the Budgetary Ledger?

Is the customer using HR integration (Position Budgeting and Control, or Funds and Position Management?)

Does the customer use Batch Input in Former Budgeting?

Has the customer enhanced the FB standard functionality in one of the following ways:

Has the customer implemented Customer Exits or BAdIs in Former Budgeting?

Has the customer implemented any modifications in Former Budgeting?

Has the customer implemented his/her own programs that read from or write data to the Former Budgeting database?

Check the following questions and determine if this applies to the customer. In case of restrictions or missing functionality:

Is there a workaround in BCS?

Can the workaround be applied to this particular customer?

Is the missing functionality essential to the correct implementation of BCS?

Does the customer use document chains?

Time Frame

When does the customer want to switch from Former Budgeting to BCS?

Change at fiscal year end, meaning that BCS data for the new year is directly created in BCS.

Change during the fiscal year, meaning that data for the first BCS year is entered in Former Budgeting.

In case of a switch during the fiscal year, why does the customer want to migrate during the fiscal year?

For capacity/organizational reasons:

Parallel upgrade limits capacity.

Year-end process ties up all capacity.

Other reason(s).

For functional reasons

Customer needs to be able to carry forward budget automatically.

Customer needs to make sure that no budget changes still need to be made in Former Budgeting, and can only decide this during the fiscal year.

Master Data

How is master data used in Former Budgeting?

Does the customer intend to change the master data hierarchy, in order to benefit from the new master data supported by BCS?

Is the fund in Former Budgeting used in the sense of the FM account assignment element (SAP object) “grant”?

Will the customer also implement Grants Management?

Does the customer want to use additional master data in order to store “real” additional information, or will the new master data contain objects that were previously contained in other master data?

How does the customer want to transition to a new master data structure? Note that only new master data (especially new funds) can be created according to the new structure, existing master data stays in the old structure.

Will the customer define budget addresses and posting addresses?

What kind of link has been defined between posting addresses and budget addresses?

Is it easily possible to recreate the budget structure in BCS, in the same way as it was defined in Former Budgeting?

Does the customer’s budget structure change from year to year?

Is it possible for the customer to redefine the budget structure for previous years in BCS (linked to overall budgeting)?

Reporting

Which reporting tool(s) does the customer use?

Does the customer need to report on old data before a specific BCS cutover date?

Is this reporting limited to totals data?

Does the customer want to report on old and new data separately?

Does the customer need to compare old and new data?

Does the customer have to sum up old and new data?

For which detailed data is reporting needed (for example, on the process and budget type)?

Does the customer need to report on budget documents?

Does the customer need to drilldown from totals?

In which cases does the customer look at documents?

How often does the customer look at old documents?

Is this a high-priority necessity?

Can the customer give concrete examples of needed reports referring to old and new data?

Year End and Budget Preparation

When and how does the customer prepare the budget data for the new fiscal year?

Is the budget data for the new fiscal year linked to or based on the previous year’s budget?

Does the customer use residual budget carryover/carryforward?

Can this carryover be done once manually?

Does the customer use carryover of budget for open items?

Can this carryover be done once manually?

Does the customer use the budget copy program to copy budget from one year to another?

What are the customer’s rules for such a copy?

Time Horizons for Budget Data

Does the customer use overall budgets in Former Budgeting?

What is the scenario underlying it?

Is overall budget used in connection with annual budget (within one fund)?

What does the “delta” refer to in this case?

Does the customer have funds that are necessary in order to have the complete data for the entire validity period (“overall funds”)?

If so, what does the term “overall fund” mean for the customer (budget time horizon, availability control, reporting, year-end process, etc.)?

How long is the validity period of such overall funds?

Do overall funds constitute a significant part of all funds in the customer’s organization, or are overall funds more of an exception?