Entering content frame

InfoCube documentation IM-FA: Assigned Plan and Budget Locate the document in its SAP Library structure

Technical name: 0IMFA_1

Use

The 0IMFA_1 InfoCube is a central, cross-system, optimized database used for analysis. These analyses assist decision-making in company-wide planning, and for investment projects. The queries provided by SAP, numerous predefined templates, and restricted key figures all enable the quick and easy definition of flexible analyses that provide the information you require.

The 0IMFA_1 InfoCube contains the plan, budget and assigned values of investment programs and the objects assigned to them. The objects assigned to investment programs are appropriation requests and measures (that is, orders and projects).

Loading Data

Note the following when loading data for the InfoCube.

Converting the Investment Program Name

The name of the investment program transferred from the OLTP system to the BW system is four characters long. If an investment program name in the OLTP system has more than four characters, you need to rename it in BW Customizing (OLTP system).

For more information, see the documentation in the BW Implementation Guide. Choose Investment Management ® Investment Programs ® Convert Program Name.

Assignment Information

During an update of transaction data in the InfoCube, the system reads information from the order master data tables and the PSA. This information has to be prepared using the appropriate InfoSources.

Information on Assignment of Orders to Projects

You assign orders to projects in the R/3 System in the order master data.

In order for the system to recognize the orders that belong to a project, you need to load the order master data to the BW (since the assignment information is stored in this master data). This is the master data of InfoObjects 0COORDER.

Information on Assignment of Measures and Appropriation Requests to Investment Program

In Investment Management, only transaction data for the following objects (if assigned to an investment program) is transferred to the InfoCube: Orders, WBS elements and appropriation requests.

The assignment information is initially loaded to the PSA using the following InfoSources:

All InfoSources, which supply transaction data for measures and appropriation requests, use the PSA during the update of InfoCube 0IMFA_1. This is to enable them to find the assignment to an investment program position and the percentage distribution of appropriation requests. The values of an appropriation request can be distributed by percentage to requesting organizational units and reasons for investment or environmental investment.

Follow the steps in this order when loading data:

  1. Load the master data of the orders to the BW.
  2. Load all assignment information and percentage distributions of measures and appropriation requests to the PSA.
  3. Ensure that all assignment information has been loaded completely, before you load the transaction data of orders, projects, networks and network activities and network activity elements.

This graphic is explained in the accompanying text

You can automate this process using an InfoPackage Group. Ensure that all objects assigned to the investment program (projects, orders, and orders for the project, networks and network activities) are selected in the InfoPackages. If possible, avoid using selection options.

Interpretation of Assignments to Program during Loading of Data

The data request of an assignment InfoSource can supply the assignments to any number of investment programs.

The system always uses the most current data requests for assignments and distributions for the update.

Example

The following requests are in the PSA:

Request Date Time (clock-time) Selected Investment Program

1 06/17/2000 14:15:51 INVEST/1999

2 17.07.2000 14:12:51 INVEST/1999 and INVEST/2000

Result

Programs INVEST/1999 and INVEST/2000 are updated by the information from Request 1.

The InfoPackage log in the monitor displays:

Aggregational Behavior

It is possible to aggregate the values across different dimensions without counting the same data more than once. This is due to a special layout for the values in the InfoSources and the update rules for the InfoCube. As a consequence, you can easily define informative queries.

Aggregation of Values in Program Hierarchy

The aggregation of the program plan or budget throughout the program hierarchy is formatted in the InfoSources for these values.

For each program position, only the distributable plan value or budget value is supplied, so that it is possible to total values along the hierarchy. The budget value of a program position is calculated by adding values hierarchically.

Example

Program position IT with a value of 1917 has a subordinate position LAPTOPS with a value of 200.

The InfoSource supplies these records: IT: 1717 and LAPTOPS: 200.

Aggregation of Values to WBS Elements

The values on the WBS elements assigned to the investment program are displayed as totals under InfoObject 0WBS_AS_ELE. This InfoObject contains the WBS element assigned to the investment program. Using InfoObject 0WBS_ELEMT you can break down the values according to the WBS element hierarchy (new as of Release 3.0A). You can break the values down further according to cost elements, network activities, networks or orders of the project by branching to a report in the InfoCubes of the project system.

Aggregation of Values over Time

The aggregation of the overall values and annual values (plan and budget) is formatted in the InfoSources for these values.

For plan and budget values, the remaining overall values (that is, not yet distributed funds) are always assigned to approval year 0000, so that the overall value is the total of the annual values.

Example

An object has an overall value of 10000 and the following annual values:

1997: 100

1998: 400

1999: 700

The corresponding InfoSource provides the following records:

0000: 8800

1997: 100

1998: 400

1999: 700

No Aggregation of Cost Element Planning and Overall/Annual Planning on Measures

On measures, plan values can exist as overall and annual values, but also be part of cost element planning (period-specific). This cost element planning represents a refinement of the overall and annual planning. This means that these two planning forms cannot be added together in a query, otherwise the resulting plan values would be too high.

Example

Overall plan value of order:  1 000 000 

Annual planning for 1999:  500,000 

Annual planning for 2000:  200 000 

Cost element planning for 002 / 1999:  140,000 

Cost element planning for 003 / 1999:  350 000 

Values in the InfoCube

0FISCYEAR

0FISCPER3

0AMOUNT

0000

000

300 000

1999

000

500 000

1999

002

140 000

1999

003

350 000

2000

000

200 000

As a result, one column in a query can only show either the plan value from cost element planning or the plan value from overall and annual planning.

The system makes the distinction between the values using the 0FISCPER3 (posting period) InfoObject:

000 Overall and annual plan values

001 to 999 cost element planning by period

Aggregation of Debits and Credits

The formatting of actual values for aggregation using actual debits and credits takes place in the update rules of InfoCube 0IMFA_1.

Example

Measure with debit (charge) of 1000, settlement of 100 to fixed asset, settlement of 300 to cost center

Stored in the InfoCube as follows:

Sender-receiver indicator

Capital/expense

Value

Debit

#

600

Credit

Capital

100

Credit

Expense

300

This formatting makes it possible to have a drilldown for capital and expense for actual values in the queries.

Aggregation of Values in Different Object Types

The formatting of plan and budget values for aggregation using different object types takes place in the update rules of InfoCube 0IMFA_1.

In Investment Management, plan and budget values are managed on the following object types:

The values on the different objects can be distinguished in the IM InfoCube by means of the IM object type, InfoObject 0IM_OBJ.

The values on the investment program position contain the values of its assigned measures and appropriation requests. The same applies to the values of the appropriation request and its assigned measures. The values of the different object types cannot simply be added together in the BW system, since they would otherwise be counted more than once. To prevent this, offsetting data records are created during the update in the IM-InfoCube. These offsetting data records 'cancel' each other out, and thereby prevent the values from being counted more than once.

This graphic is explained in the accompanying text

You want only plan values of measures to appear in one column. Therefore you select Plan as value type and Measure as IM object type. The BW system then displays plan values of measures in this column.

In a second column, you want to enter the plan values from measures and appropriation requests. Therefore you select Plan as value type and the IM object types Measure and Appropriation request. If the system did not create offsetting data records, the BW system would enter plan values in this column that are too high, since the plan values of appropriation requests would be added to the plan values of their assigned measures.

The following types of offsetting data records are updated in the IM InfoCube:

The offsetting data records can also be distinguished by means of the IM object type, InfoObject 0IM_OBJ.

For each combination of objects that you enter in a column, you have to select the appropriate offsetting data record.

Example

If you enter plan values of measures and appropriation requests in one column, then you have to select the offsetting data records for appropriation requests/measures via the IM object type.

The following example shows how the BW system acts when it records plan values from both measures and appropriation requests.

Values of Investment Program in OLTP System

Object

Value

IP1: Investment program

1100

IQ1: Appropriation request

500

ME1: Measure

300

Values in the InfoCube

Prog.Pos.

Object type

Approp. Req.

Measure

Version 1

IP1

IP

   

1100

IP1

#

     

IP1

PQ

   

-500

IP1

IQ

IQ1

 

500

IP1

QM

IQ1

 

-300

IP1

MQ

IQ1

ME1

300

If you choose a breakdown by program position, appropriation request and measure in a query, the following view results:

Values in the Query

Selection for the object type

None

IQ

ME and MQ

Prog.Pos.

Approp. Req.

Measure

Plan

Approp. Req. Plan

Measure Plan

IP1

   

1100

500

300

 

Not assigned

 

600

   
 

IQ1

 

500

500

300

   

Not assigned

200

500

 
   

ME1

300

 

300

Budget Categories

In the OLTP, you can split up plan values and budget values on the investment program into budget categories. The standard system supports the budget categories capital and expense. The breakdown of actual values into these budget categories is automatic.

Instead of using these categories, the customer can define other budget categories in the OLTP – for example, external and internal activity.

If the customer defines their own budget categories, the actual values are assigned to budget categories in the OLTP Information System using customer enhancement AAIP0001.

In BW there is a corresponding customer enhancement, AIBW0001, for the assignment of actual values to budget categories, so that a non-standard distribution of actual values to budget categories is also possible here.

Defining a Group Currency

Using customer enhancement AIBW0002 you can define a group currency. All values loaded from the OLTP system are translated to currency type 30 (group currency) in the update rules and copied to the InfoCube. You can use values in object and controlling area currency from the DataSource to translate these values.

The values in the group currency serve as the basis for strategic investment management in Corporate Investment Management.

Note

Assign customer enhancement AIBW0002 in Transaction CMOD to an enhancement project and define the group currency and the exchange rate type for the currency translation in the program code. Then activate the enhancement project. For more information, see the documentation about customer enhancement AIBW0002.

Comments about Queries

You can define two types of queries on InfoCube 0IMFA_1:

Queries that only report on end node positions

In these queries, End node positions only are selected using the End node indicator characteristic in the filter (for example, see the Available Plan by Periods query). The End node indicator characteristic is a navigation attribute for the program position.

Structure linkIM-FA - Available Plan (by Periods)

Structure linkIM-FA – Appropriation Request Plan by Organizational Units

Queries that report on a complete investment program hierarchy

These queries need to use the program hierarchy as a presentation hierarchy. In BW, we distinguish between the selection hierarchy for data selection and the presentation hierarchy for representing the data in the query. You can enter these hierarchies using the 0H_PROG hierarchy variable when you execute the query.

Structure linkIM-FA - Plan from Program/Appropriation Requests/Measures

Structure linkIM-FA - Budget from Programs and Measures

Structure linkIM-FA: Available Plan

Structure linkIM-FA: Available Budget

Predefined Restricted Key Figures and Templates

The following restricted, business key figures are defined on the InfoCube:

The following templates are available:

InfoSources

For Loading Assignment Information to the PSA:

0IM_FA_IP_6: Structure linkGroup Shares (IM)

0IM_FA_IP_7 Structure linkAssignment of Appropriation Requests

0IM_FA_IP_8 Structure linkAssignment of Orders

0IM_FA_IP_9 Structure linkAssignment of Projects

0IM_FA_IQ_9: Structure linkAppropriation Request: Requesting Organizational Units

For Loading Transaction Data to the InfoCube:

0IM_FA_IP_1: Structure linkProgram Position: Plan

0IM_FA_IP_2: Structure linkProgram Position: Budget

0IM_FA_IQ_1: Structure linkAppropriation Request: Plan (Capital/Expense) and Revenue

0IM_FA_IQ_2: Structure linkAppropriation Request: Preinvestment Analysis Figures (Net Present Value)

0CO_OM_OPA_1: Structure linkInternal Orders: Assigned Values and Cost Element Plan

0CO_OM_OPA_2: Structure linkInternal Orders: Budget

0CO_OM_OPA_3: Structure linkInternal Orders: Overall/Annual Plan Values

0CO_OM_WBS_1: Structure linkWBS Element: Costs

0CO_OM_WBS_2: Structure linkWBS Elem.: Budget

0CO_OM_WBS_3: Structure linkWBS Element: Assigned Values and Cost Element Plan

0CO_OM_NTW_1: Structure linkNetwork: Costs

0CO_OM_NWA_1: Structure linkNetwork Activity: Costs

0CO_OM_NAE_1: Structure linkNetwork Activity Elements: Costs

Characteristics

InfoObject

Description

0APPR_YEAR

Approval year

0CO_AREA

Controlling area

0CURTYPE

Currency type

0METYPE

Key figure type

0PROG_DEF

Program definition (name in OLTP)

0PROG_DEF_S

Program definition

0PROG_POS

Program position

0VERSION

Version

0VTYPE

Reporting value type

0VTDETAIL

Details of value type

0COORDER

Order number (CO order)

0VALUATION

Valuation

0WBS_AS_ELE

WBS assignment (IM)

0WBS_ELEMT

Work breakdown structure element (WBS element)

0IM_OBJ

Object type (IM)

0IM_LEAF

End node indicator (IM)

0IM_SIZE

Scale (IM)

0NEW_OLD

Carryforward/current/forecast indicator

0DB_CR_IND

Sender-receiver indicator

0APPR_REQU

Appropriation request

0REQU_BUSA

Requesting business area

0REQU_CCTR

Requesting cost center

0REQU_DIVIS

Requesting division

0REQU_M_GRP

Requesting material group

0REQU_PRCTR

Requesting profit center

0ENV_REASON

Environmental investment reason

0INV_REASON

Reason for investment

0NPV_REDATE

Value date for net present value

0BUD_CAT

Budget category

0VTSTAT

Statistics indicator for value type

0CAP_EXP

Capital/expense

Time Characteristics

InfoObject

Description

0FISCVARNT

Fiscal year variant

0FISCPER

Fiscal year/period

0FISCYEAR

Fiscal year

0FISCPER3

Posting period

Key Figures

InfoObject

Description

0AMOUNT

Amount

0NPV

Net present value

Units

InfoObject

Description

0CURRENCY

Currency key

 

 

 

Leaving content frame