08_im_en

8/16/2019 08_im_en

http://slidepdf.com/reader/full/08imen 1/10

8/16/2019 08_im_en


© Copyright 200 2 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.

Microsoft ®, WINDOWS ®, NT ®, EXCEL ®, Word ®, PowerPoint ® and SQL Server ® are registered trademarks of Microsoft Corporation.

IBM ®, DB2 ®, OS/2 ®, DB2/6000 ®, Parallel Sysplex ®, MVS/ESA ®, RS/6000 ®, AIX ®, S/390 ®, AS/400 ®, OS/390 ®, andOS/400 ® are registered trademarks of IBM Corporation.

ORACLE ® is a registered trademark of ORACLE Corporation.

INFORMIX ®-OnLine for SAP and Informix ® Dynamic Server TM

are registered trademarks of Informix SoftwareIncorporated.

UNIX ®, X/Open ®, OSF/1 ®, and Motif ® are registered trademarks of the Open Group.

Citrix®

, the Citrix logo, ICA®

, Program Neighborhood®

, MetaFrame®

, WinFrame®

, VideoFrame®

, MultiWin®

and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C ®, World Wide Web Consortium,Massachusetts Institute of Technology.

JAVA ® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT ® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other products mentioned are trademarks or registered

trademarks of their respective companies.Design: SAP Communications Media

8/16/2019 08_im_en


8 IM InvestmentManagement 1

8.1 IM-FA CapitalInvestments 1

8.1.1 Planning and Budgeting in Any Currency(new) 1

8.1.2 IM-FA-IA AppropriationRequests 3

8.1.2.1 Transfer of Appropriation Requests toMeasures (Extended) 3

8.1.2.2 Enhancement of Field Transfer From ARequest in WBS Element (new) 3

8.1.2.3 IM-FA-IA-MD Master Data8.1.2.3.1 BAdI: Checking Appropriation Requests

(neu) 48.1.3 IM-FA-IP Investment

Programs 48.1.3.1 Reorganization of Investment Programs

(New) 48.1.4 IM-FA-IE Investment

Orders 5

8.1.4.1 Settlement of Investment Support forAssets Under Construction 5

8.1.4.2 IM-FA-IE-BU Order Budgeting8.1.4.2.1 Change to Budget Monitoring with

Orders/WBS Elements 68.1.5 IM-FA-PR Projects as

Investment Measures 68.1.5.1 IM-FA-PR-BU Project

Budgeting 68.1.5.1.1 Change to Budget Monitoring with

Orders/WBS Elements 6

8.1.6 IM-FA-IS InformationSystem 7

8.1.6.1 Depreciation Forecast and Primary CostPlanning (Extended) 7

SAP System Table of Contents SAP AG ______________________________________________________________

______________________________________________________________ SAP AG

8/16/2019 08_im_en


8 IM Investment Management

8.1 IM-FA Capital Investments

8.1.1 Planning and Budgeting in Any Currency (new)

Use

International groups often use one uniform company code currency (group currency) in CO. However, itmay be necessary to plan and budget in the respective local currency as the majority of costs will be

incurred in the local currency. The local currency is usually the corresponding company code currency.Previously only budgeting of jobs (orders and projects) was possible in the local currency.

From Release 4.70, you can also budget investement programs in the local currency. In addition, it ispossible to plan investment programs, appropriation requests and jobs directly in the local currency.

As was previously the case for orders and projects, plan and budget values for investment programs andappropriation requests are also saved in both the controlling area and local currencies defined in themaster record of each object. If you change or re-specify the exchanged rates used, it is now possible torecalculate the values in the local currency using the values in the controlling area currency, andvice-versa.

In reporting for IM, it is even possible to calculate evaluations in any report currency (plan, budget and

assigned values). If the values are available in the specified report currency, they are issued unchanged. If they are not available, they are converted from the controlling area currency into the report currency.

Effects on Existing Data

Before Release 4.70, the plan values for appropriation requirements, were only saved in the controllingarea currency. This was also the case if a local object currency was specified in the master record for theappropriation requirement. From Release 4.70, the plan values for appropriation requirements are alwayssaved in the controlling area and local currencies. Therefore, you must adjust appropriation requests thatwere created in an earlier release and use a local currency that varies from the local object currency. Theeasiest way to do this is to use the program RAIMCRC2 to recalculate the plan values in the local objectcurrency for appropriation requests whose plan values are in the controlling area currency (transactionIMCRC2, menu path: Financial Accounting -> Investment Management -> Appropriation Requests ->Tools -> Recalculate Currency Plan for Appropriation Requests ). Before you run the program, select therelevant option in the Process Control section of the initial screen.

Effects on Customizing

Adjustment of Planning and Budget Profiles

To enable the planning of investment programs, appropriation requests and jobs in a transaction currencydifferent to the controlling area currency, you must adjust the relevant planning profiles.

To enable the budgeting of investment programs in a transaction currency different to the controlling areacurrency, you must adjust the relevant budget profiles.

In the planning currency (or budgeting currency) section of the planning (or budget) profile, you must

______________________________________________________________ SAP AG 1

SAP System ______________________________________________________________

8/16/2019 08_im_en


define the transaction currency in which planning (or budgeting) is to be executed:

o Only in the controlling area currency (default),

o Only in the object currency(= local currency defined in object master record ) or

o In a transaction currency chosen at the start of planning/budgeting(this option is not possible for appropriation requests).

In the planning or budget profiles, you must also define the exchange rate types to be used for theconversion of total values that are not dependent on the fiscal year.

To adjust the planning profiles, use the process steps:

Maintain Planning Profiles (investment programs)

Maintain Planning Profile for Cost Planning (appropiation requests)

To adjust the budgeting profiles, use the process steps:

Define Budget Profiles for Investment Programs (investment programs)

Exchange Rate Types

In the fiscal-year-dependent data of the CO planning versions, you must also define the exchange ratetypes to be used for conversion of plan values that are not dependent on the fiscal year.

For conversion of fiscal-year-dependent budget values and fiscal-year-dependent plan values of appropriation request variants not yet assigned to a plan version, each exchange rate type is taken fromthe fiscal-year-dependent data of the CO planning versions 0.

As the plan or budget values are stored in the transaction, controlling area, and local currencies, theexchange rates used must enable the conversion of the transaction currency into the controlling area andlocal currencies. Where necessary, the exchange rates used must be extended.

To enter the exchange rate types, use the process step:

Define Versions (investment programs)

Change Planning or Budget Currency

If you always planned or budgeted existing investment programs/measures in the controlling areacurrency, it is not subsequently possible to change the planning or budget currency to the object currencyin the planning or budget profiles. This conversion is not prevented in Customizing, but leads to an errorwhen you next plan or budget existing investment programs/measures. Alternatively, you can convert theplanning or budget currency into the transaction currency in the planning or budget profiles, and set theobject currency indicator as default.

A similar restriction does not exist for appropriation requests. You can change the planning currency inthe planning profile at any time.

Use the process step under "Adjust the Planning and Budgeting Profiles".

Detailed Planning

When you call up detailed planning from structure-based cost planning or revenue planning, the standardSAP planning profiles are used, to which the standard SAP planning layouts are assigned. These planningprofiles cannot be changed in the planning transactions. Import the standard SAP planning layouts1-401-IM, 1-402-IM, 1-403-IM, 1-701-IM, 1-702-IM and 1-703-IM using the transaction OKBF from

______________________________________________________________ SAP AG 2

SAP System ______________________________________________________________

8/16/2019 08_im_en


client 000 in your client.

To execute the import, choose the process step:

Import Standard Planning Layouts.

Reporting Currency for IM Reporting

In IM reporting, if you want to be able to specify a reporting currency that is different to the controllingarea and object currencies used in the investment program items or subordinate appropriation requestsand measures, another exchange rate type is required for the due conversion of plan, budget, or valuesinto the reporting currency. You define this exchange rate type in Customizing for the program type forthe investment program to be reported ( Group Reporting ).

To enter additional reporting currencies, use the process step:

Define Program Types (investment programs)

See also

For more information on the new functions, see the application help for the relevant transactions, or thecorresponding IMG documentation.

8.1.2 IM-FA-IA Appropriation Requests

8.1.2.1 Transfer of Appropriation Requests to Measures (Extended)

Use

From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , you can use an operative or standard WBS as atemplate when creating projects from appropriation requests. It is also possible to create several projectsfrom a request, as long as they do not use measure replacement.

From SAP R/3 Core 4.70 (SAP_APPL 470) , you can distribute the plan values or the costing of a requestto several measures, independent of the measure type (order or project).

See also

For more information on the transfer of appropriation requests to measures, see the SAP Library underFinancials -> Investment Management -> Appropriation Requests -> Transfer to a Measure to be

Implemented .

8.1.2.2 Enhancement of Field Transfer From A Request in WBS Element (new)

Use

______________________________________________________________ SAP AG 3

SAP System ______________________________________________________________

8/16/2019 08_im_en


From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you have the enhancement (user exit) AAIR0006,in which you can intervene in the transfer of request data from the WBS element during creation of aWBS element from an appropriation request.


To call up the development of your own enhancements, use:

Enhancement for Field Transfer From Request in WBS Element

See also

Details are described in the enhancement documentation.

8.1.2.3 IM-FA-IA-MD Master Data

8.1.2.3.1 BAdI: Checking Appropriation Requests (neu)

Use

From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the new Business Add-In (BAdI)APPREQUEST_UPDATE enables you to implement user-defined checks for appropriation requests. TheBAdI provides methods for checking data before saving or status changes. These methods provide

complete information about master data and the status of appropriation requests.There is also a method in which you can update additional user-defined data when saving a request.


To implement this BAdI, use the following step in the Implementation Guide for (IMG) InvestmentManagement:

BAdI: Check Request Master Data

See also

For more information, see the definition docmentation for the BAdI.

8.1.3 IM-FA-IP Investment Programs

8.1.3.1 Reorganization of Investment Programs (New)

Use

Starting in SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , you can automatically and consistentlydetach closed measures and appropriation requests from the program positions they are assigned to. Thisis particularly important if you want to set the deletion flag on the measures or appropriation requests,

______________________________________________________________ SAP AG 4

SAP System ______________________________________________________________

8/16/2019 08_im_en


since this is not possible if they are still assigned to an investment program position.

To reach the new function, in the Easy Access Menu choose Accounting -> Investment Management ->Programs -> Periodic Processing -> Reorganization .

This new function removes a serious limitation that previously existed with regard to archiving measuresand appropriation requests when they were assigned to investment program positions. Archiving this kindof measure and appropriation request (or, more precisely, setting the deletion flag necessary forarchiving) was not possible until the investment program they were assigned to was completely deleted.This in turn required that all of the measures and appropriation requests related to the investment programhad already been closed. Since long-term measures were often not closed until several years after theinvestment program was created, there was an unnecessarily long wait before archiving of measures andappropriation requests could take place.

Effects on System Administration

If you want to set deletion flags for closed measures or appropriation requests in connection witharchiving, but they are still assigned to investment program positions, you first have to perform areorganization of all existing investment programs.

See also

For more information, examples, and a detailed description of how to perform the reorganization, refer tothe application help in the transaction.

8.1.4 IM-FA-IE Investment Orders

8.1.4.1 Settlement of Investment Support for Assets Under Construction(Extended)

Use

From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can also settle investment support fromindependent assets under construction (AUC), and from AUC that belong to investment measures postedto the AUC during the settlement year.

Previously, you could only post investment support to completed assets in the year of capitalization.

When determining the proportion of investment support to be transferred for partial capitalization ordistribution to several receivers, it is assumed that investement support posted to the AUC during the yearof capitalization also refers to asset acquisitions during the year of capitalization.

If the investment support that you post to AUC refer to prior-year acquisitions, you must use thetransaction type Kxx for the investment support measure xx.


If you used transaction type Ixx to post to the AUC investment support that refers to prior-yearacquisitions, delete these postings and repost them using the relevant transaction type Kxx.


______________________________________________________________ SAP AG 5

SAP System ______________________________________________________________

8/16/2019 08_im_en


Check whether a transaction type Kxx is also created for the investment support measures used. (Usuallythese transaction types are created automatically when you set up the investment support measure.) To dothis, use the process step

Check Transaction Types for Support Measures.

8.1.4.2 IM-FA-IE-BU Order Budgeting

8.1.4.2.1 Change to Budget Monitoring with Orders/WBS Elements

UseAs of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , there is a change to Customizing related tomonitoring budgets using statistical orders or WBS elements. Until now, you had to specify inCustomizing for Asset Accounting or Investment Management that the asset accounting transaction typewas relevant for the budget. This IMG activity has now been replaced by the new central controls foradditional account assignment in Asset Accounting.


The previously existing control using the Budget relevant indicator is automatically migrated to the newstructure during the upgrade.

See also

For more infomation, also see the Release Information on the subject of New Account AssignmentObjects.

8.1.5 IM-FA-PR Projects as Investment Measures

8.1.5.1 IM-FA-PR-BU Project Budgeting

8.1.5.1.1 Change to Budget Monitoring with Orders/WBS Elements

Use

As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , there is a change to Customizing related tomonitoring budgets using statistical orders or WBS elements. Until now, you had to specify inCustomizing for Asset Accounting or Investment Management that the asset accounting transaction typewas relevant for the budget. This IMG activity has now been replaced by the new central controls foradditional account assignment in Asset Accounting.


The previously existing control using the Budget relevant indicator is automatically migrated to the newstructure during the upgrade.

______________________________________________________________ SAP AG 6

SAP System ______________________________________________________________

8/16/2019 08_im_en


See alsoFor more infomation, also see the Release Information on the subject of New Account AssignmentObjects.

8.1.6 IM-FA-IS Information System

8.1.6.1 Depreciation Forecast and Primary Cost Planning (Extended)

Use

From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , changes have been made to the reduction of thedepreciation simulation basis for planned investments to be capitalized in project structure planning fordepreciation forecasts and primary cost planning.

Previously, capitalization postings were only included for WBS elements with depreciation simulationdata. Now however, the depreciation simulation basis of a WBS element is also transferred usingcapitalization postings to hierarchically subordinate WBS elements without their own depreciationsimulation data.

Internal orders without depreciation simulation parameters, which are assigned to WBS elements, aretreated in the same way as WBS elements without depreciation simulation parameters.

This increases the accuracy of the depreciation forecast (reports RASIMU01/RASIMU02) and primarycost planning (reports RAKOPL01/RAKOPL02).

If no hierarchically subordinate WBS element has depreciation simulation data, the actual values aredisplayed during maintenance of depreciation basis data.

______________________________________________________________ SAP AG 7

SAP System ______________________________________________________________

Documents

08_im_en