444 Scen Overview en In

Equipment and Tools Management for Construction

SAP Best Practices for Engineering, Construction, and Operations(India)SAP Best Practices

SAP 2010 / Page *Scenario Overview Purpose Addresses the unique requirements of self performing construction companies, building contractors and equipment distributors by handling the industry-specific business processes such as equipment planning, -processing, -settlement and evaluation of resources (equipment and materials) including performance measurement. Benefits Improve the availability and tracking of equipmentManage the increasing administrative workload Reduce handling and administration costIntroduce most flexible prices and account determination Optimize equipment utilizationImprove the visibility of profitability, TCO and return on asset and equipment

Purpose and Benefits:

SAP 2010 / Page *Scenario OverviewEnhancement Package 4 for SAP ERP 6.0DIMP-Extension (Switch Framework)

Equipment AdministratorProject ManagerWarehouse Clerk

Time-based Equipment Process Time-based Equipment Process including 3rd Party Rental Equipment Performance Based Equipment ProcessNon-Consumable Material ProcessConsumable Material Process

Company Roles Involved in Process Flows:SAP Applications Required:Key Process Flows Covered:

SAP 2010 / Page *Scenario OverviewTime-based Equipment Process This business process describes the planning, dispatching and settlement of time based equipment. Time based equipment can be single- or multipart equipment, which are shipped via an ETM shipping document and are settled due to time/days they have been on a recipient/location and its quantity. The shipping document allows the tracking of each equipment (single- and multipart). A time based equipment is settled periodically with a fixed price, whereas it is not relevant, how often an equipment has been used (in operation). A typical time based equipment is a crane. The time based equipment process starts with an equipment request of a project manager or foreman. He needs a crane with a certain specification (e.g. Hook high max. 20 mtr.) for a certain period. The project manager or foreman can either enter an ETM requisition note directly by himself or he calls the equipment manager/administrator (responsible for all equipment) and he than will enter the requirement in the system. After the equipment manager has assigned the request to an equipment, it will be send out to the project. Typically month end the settlement and billing run takes place.

Detailed Process Description:

SAP 2010 / Page *Scenario OverviewPerformance Based Equipment Process This business process is used to record performed equipment hours, used amount of fuel and oil (e.g. liter), amount of kilometers etc. for a project and to settle performance based equipment (PBE). PBEs are settled due to its performed hours respectively its quantity. Performance based equipment - mostly very expensive single equipment are send out to a construction side via a shipping document (for tracking), but parallel to this a performance based equipment document (PBE document) is entered to control the usage of single equipment. A typical performance based equipment is an excavator. The performance based equipment process starts analogue to the time based equipment process with an equipment request of a project manager or foreman. He needs an excavator with a certain specification (e.g. Power 50 kW) for a certain period. The project manager can either enter an ETM requisition note directly by himself or he calls the equipment manager/administrator (responsible for all equipment) and he than will enter the requirement in the system. After the equipment manager has assigned the request to an equipment, it will be send to the project. Daily or weekly depending on organization rules - the performed equipment hours are entered via a PBE document to the project/recipient. After all PBE documents for the period have been entered, the settlement can run, which will recognize, that beside the shipping document for the same time a PBE document exists and would treat it dependent. After the settlement list has been created and checked for its correctness through the project manager or foreman the billing run takes place.


SAP 2010 / Page *Scenario OverviewNon-Consumable Material ProcessThis business process is used if standard material, called non-consumable material e.g. site facilities, ladders etc. has to be shipped from a warehouse to a recipient (debtor master with enhanced ETM view) together with equipment in one ETM shipping document or has to be taken out of a magazine In both ways, non-consumable material is given back to the magazine or the warehouse via ETM shipping document after it has been used. This saves time and costs for transports and administrative effort. Magazines are a kind of little project warehouses on big construction sites/projects.The process in ETM is called sales and repurchase of non consumable material to and from a recipient/project - to and from a warehouse. This means, construction sites buy non consumable material for a fixed price and after the non consumable material is given back to either the magazine or the warehouse a reduced value will be credited to the project (automated repurchase process).When the periodically settlement takes place, projects get debited for the received material and credited for the returned material. So the project pays a kind of provision fee for the usage of the material. Generally the settlement of non consumable material is based on quantity and not on the time period like time based equipment!The cost charging and automated repurchase of non-consumable material is fully automated handled via ETM! Detailed Process Description:

SAP 2010 / Page *Scenario OverviewConsumable Material ProcessThis business process is used for shipping standard material, called consumable material (e.g. concrete or nails) together with equipment in one ETM shipping document to reduce transport- and handling costs for projects in construction industry. The cost charging is done by SAP standard Sales and Distribution (SD) and Material Management (MM). ETM only overtakes - logistically seen - the delivery of consumable material.No settlement takes place in ETM for consumable materials!


Process Flow Diagram Time-based Equipment Process Create Requisition NoteEventECO Equipment Administrator (DIMP)Create Acquisition Shipping DocumentReturn Equipment to Construction Yard/WarehouseCEM Sales Order Settlement Check Log for CEM SD SettlementProject Manager ECO (DIMP)Assign Equipment and Create Shipping DocumentDisplay Sales OrderEquipment RequestEndProcessCost AllocateCreate Billing DocumentDisplay Billing DocumentInternal SettlementDisplay Sales OrderCreate Billing DocumentDisplay Billing DocumentExternal Settlement

Process Flow Diagram Time-based Equipment with Third-Party Equipment Rental ProcessCreate Requisition NoteEventECO Equipment Administrator (DIMP)Create Purchasing Requisition for Rental EquipmentInvoice VerificationCreate EquipmentCreate Equipment BOMProject Manager ECO (DIMP)Convert Purchase Requisition to Purchase OrderEquipment RequestEndProcessEquipment Available?YesNoRun Time-Based Equipment Process(in this scenario)

Process Flow DiagramPerformance based Equipment Process Create ETM Requisition NoteEventECO Equipment Administrator (DIMP)Assign Requisition Note to EquipmentCheck Document List for PBECreate Sales OrderCheck Log for CEM SD SettlementProject Manager ECO (DIMP)Create PBE DocumentDisplay Sales OrderEquipment RequestEndProcessInternal or External Cost Allocate?Create Billing DocumentDisplay Billing DocumentInternal Cost AllocationDisplay Sales OrderCreate Billing DocumentDisplay Billing DocumentExternal Invoice

SAP 2009 / Page *Process Flow Diagram Non-consumable Material Process (internal) Stock Overview in MMEventECO Equipment AdministratorCurrent Stock for Material In ETMDisplay Shipping DocumentCurrent Stock for Material In ETMCreate Second ETM Shipping Document for AcquisitionWarehouse ClerkCreate First ETM Shipping Document for AcquisitionDisplay Sales OrderMaterial RequestInternal or External Repurchase?Create Billing DocumentDisplay Billing DocumentDisplay Sales OrderCreate Billing DocumentDisplay Billing DocumentStock Overview in MMStock Overview in MMProject Manager ECOInitial Stock Posting for Non-Consumable MaterialDisplay Shipping DocumentCurrent Stock for Material In ETMCreate Sales OrderCheck Log for CEM SD SettlementSales or Repurchasing?Internal or External Sales?Display Sales OrderCreate Billing DocumentDisplay Billing DocumentDisplay Sales OrderCreate Billing DocumentDisplay Billing DocumentExternalInternalExternalInternal

Process Flow Diagram Consumable Material Process (internal) Stock Overview in MMEventECO Equipment AdministratorCurrent Stock for Material In ETMDisplay Shipping DocumentCurrent Stock for Material In ETMWarehouse ClerkCreate ETM Shipping Document for AcquisitionMaterial RequestStock Overview in MMProject Manager ECOInitial Stock Posting for Consumable Material

SAP 2010 / Page *Legend

External to SAPBusiness Activity / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / DataSystem Pass/Fail Decision

SymbolDescriptionUsage CommentsBand: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.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.Role band contains tasks common to that role.External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.Connects two tasks in a scenario process or a non-step event

Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the document

Unit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in the document

Process Reference: If the scenario references another scenario in total, put the scenario number and name here.Corresponds to a task step in the document

Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario hereCorresponds to a task step in the document

Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond. Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

SymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous page

Hardcopy / Document: Identifies a printed document, report, or form Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates a financial posting document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesBudget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesManual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.

SAP 2010 / Page *Copyright 2010 SAP AGAll Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of 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 software vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C 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 and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.

See template 020_Scenario_Oververview.zipTemplate Pool SAP Business All-in-One Documentation Templates 020_Scenario_Overview.zip

Sample data are to be deleted and replaced (red entries)See template 020_Scenario_Oververview.zipTemplate Pool SAP Business All-in-One Documentation Templates 020_Scenario_Overview.zip

Sample data are to be deleted and replaced (red entries)










This slide is optional.Since the process flow diagram is later required in development process (scenario overview), it can reuse some effort in development, if the diagram ist created in blueprint/specification phase. The diagram visualizes the process flows and is a great tool to discuss the process with the stakeholders.









444 Scen Overview en In

Documents

Transcript of 444 Scen Overview en In