Overview Presentation

2,943 views
2,671 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,943
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
92
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Overview Presentation

  1. 1. Investment Management in PM SAP Best Practices for Chemicals (Russia) SAP Best Practices
  2. 2. Scenario Overview Purpose and Benefits: Purpose  The purpose of to describe business processes related to Investment Management within Plant Maintenance. © SAP 2008 / Page 2
  3. 3. Scenario Overview SAP Applications Required: Required  SAP ECC 6.00 EhP3 Company roles involved in process flows  Plant Maintenance Specialist © SAP 2008 / Page 3
  4. 4. Overview The Investment Management (IM) component provides functions to support the planning, investment, and financing processes for: • Capital investments, such as the acquisition of fixed assets as the result of- house production or purchase • Investments in research and development • Projects that fall primarily under overhead, such as continuing education of employees or establishing new markets • Maintenance programs The term investment, therefore, is not limited only to investments you capitalize for bookkeeping or tax purposes. An investment in this context can be any measure that initially causes costs, and that may only generate revenue or provide other benefits after a certain time period has elapsed (for example, plant maintenance). © SAP 2008 / Page 4
  5. 5. Features Application module IM (Investment Management) Application module PS (Project System) Module IM for overall planning, budgeting and controlling of Investment projects, Maintenance projects and operational maintenance activities Module PS as planning and controlling tool for individual measures Maintenance work orders as cost collector for handling of operational and project-related activities Fully integrated process of Financials, Asset-Accounting, Controlling and Plant Maintenance © SAP 2008 / Page 5
  6. 6. The Asset Life-Cycle Construction Procurement Projection process Decision for Building Investment Assembling EAM Research & Development Operating Production Asset Maintenance retirement Quality assurance © SAP 2008 / Page 6
  7. 7. General Program structure • Shows the structure of the enterprise • Based on technical structure © SAP 2008 / Page 7
  8. 8. Integration IM/PS and PM Investment program Maintenance program Projects Projects Work Work order order © SAP 2008 / Page 8
  9. 9. Invest Program Structure © SAP 2008 / Page 9
  10. 10. Maintenance Program Structure © SAP 2008 / Page 10
  11. 11. Budgeting Maintenance IM-Program Budget Aggregation position assignments by Functional location Planned Actual Costs Values Work order Active availability check Budget © SAP 2008 / Page 11
  12. 12. Process Cost planning Cost planning based on: • Objects - Count / Types Adjustment • Scale of planned measures • Components and services • Estimation of unplanned measures Budget Reporting Compares Modifying Actual Costs: • Workt • Components • other costs © SAP 2008 / Page 12
  13. 13. Example: Scenario Plant Maintenance Program: CH-MAINT Technical structure: BP01 KMA BP01 KMA1 PRO Cost center WBS Work order OP Plan Plan Components Budget Internal labor : Projects Pr 1 BP01-PM-20 Operational Maintenance Pr 1.1 Pr 1.2 Pr 1.3 Ball system 1 Ball system 2 Ball system 3 Plan Settlement to cost centger Cost center K1 K2 K3 PROD © SAP 2008 / Page 13
  14. 14. Fiscal year changing J F M A M J J A S O N D J F M A M J J A S O N D 2006 2007 Program position 2006 Program position 2007 Budget Distrib. Budget year before 600 1000 1000 Year changing Budget new 3000 Whole 3600 distributed Project X Project X 600 Budget 600 Work order 1 + Addition 1000 closed 300 Project Y 1000 Work order 2 closed 100 Work order 3 1000 © SAP 2008 / Page 14
  15. 15. Reporting Program 2006 Example: Availability Budget Act. Obligo Avail. Roll-up Budget Actual Obligo Avail. Program position 1300 800 200 300 assigned operative Objects Work order 1 100 20 - 80 Work order 2 200 180 50 -30 ! Project X 400 150 100 150 Project Y 600 450 50 100 © SAP 2008 / Page 15
  16. 16. Scenario Overview Business Requirement: Support planning, investment, and financing processes for investment programs and maintenance programs Program Program Planning Program Structuring Budgeting (costs) Measure Measure Measure Release of Execution of Close of Structuring Planning Budgeting Measure Measure Measure Investment Fiscal Year Management Changing of Reports Programs © SAP 2008 / Page 16
  17. 17. Process Flow Diagram Event Investment Planning and Old/new Programs Budgeting Approval Year Plant Maintenance Project & Measure Investment Release project Program Create / Change / Release Measures definition Display Measures Structure Assignment of Capital Investment Assign WBS Projects/Maintenance Element to Functional Projects Location to a Maintenance Order Accounting Plan Costs on Investment Budget Investment Budget Projects Program distribution Program © SAP 2008 / Page 17
  18. 18. Legend Symbol Description Usage Symbol Description Usage Comments Comments Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next / to the next / previous page of the previous page Payable Clerk or Sales Representative. This band contains tasks Diagram <Function> can also identify an organization unit or group, common to that Diagram rather than a specific role. role. Connection The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario. Hardcopy / Document: Identifies a Does not correspond to a task printed document, report, or form step in a document; instead, it is Hardcopy / used to reflect a document External Events: Contains events that start or end the Document generated by a task step; this External scenario, or influence the course of events in the shape does not have any outgoing to SAP scenario. flow lines Financial Actuals: Indicates a Does not correspond to a task Flow line (solid): Line indicates the normal sequence Connects two financial posting document step in a document; instead, it is tasks in a Financial used to reflect a document of steps and direction of flow in the scenario. scenario generated by a task step; this Flow line (dashed): Line indicates flow to infrequently- Actuals shape does not have any outgoing process or a used or conditional tasks in a scenario. Line can non-step event flow lines also lead to documents involved in the process flow. Business Activity / Event: Identifies an action that Does not Budget Planning: Indicates a Does not correspond to a task either leads into or out of the scenario, or an outside correspond to a budget planning document step in a document; instead, it is Business Process that happens during the scenario task step in the used to reflect a document Budget generated by a task step; this Activity / document Planning shape does not have any outgoing Event flow lines Unit Process: Identifies a task that is covered in a Corresponds to step-by-step manner in the scenario a task step in Manual Process: Covers a task Does not generally correspond to the document that is manually done a task step in a document; Unit Process Manual instead, it is used to reflect a task Proces that is manually performed, such s as unloading a truck in the warehouse, which affects the process flow. Process Reference: If the scenario references another Corresponds to scenario in total, put the scenario number and name a task step in Process here. the document Existing Version / Data: This block Does not generally correspond to Reference covers data that feeds in from an a task step in a document; Existing external process instead, this shape reflects data Version / coming from an external source; this step does not have any Sub-Process Reference: If the scenario references Corresponds to Data incoming flow lines another scenario in part, put the scenario number, a task step in Sub- name, and the step numbers from that scenario here the document Process Reference System Pass / Fail Decision: This Does not generally correspond to System block covers an automatic a task step in the document; Pass/F decision made by the software instead it is used to reflect an ail automatic decision by the system Process Decision: Identifies a decision / branching Does not that is made after a step has been point, signifying a choice to be made by the end usually Decisio executed. user. Lines represent different choices emerging correspond to a n Proces from different parts of the diamond. task step in the s document; Decisio Reflects a n choice to be made after step execution © SAP 2008 / Page 18

×