133 erp605 process_overview_en_xx
Download as PPT, PDF1 like453 views
This document describes the key steps and roles involved in procurement contracts. It outlines the benefits of contracts such as reduced costs and secured supplies. The main steps are creating basic quantity or value contracts, generating purchase requisitions and orders, approving orders, monitoring contracts, receiving goods and invoices, and making payments.
133 erp605 process_overview_en_xx
- 1. Procurement Contract SAP Best Practices
- 2. Purpose, Benefits, and Key Process Steps Purpose This scenario deals with the use of contracts in procurement activities. Benefits Reduced procurement costs Securing of supplies Transparency of supplier agreements Key Process Steps Creating a basic agreement (quantity contract) Creating a purchase requisition Assigning requisition and creating purchase order Approval of purchase orders Contract monitoring Goods receipt Invoice receipt by line item Outgoing payment © 2011 SAP AG. All rights reserved. 2
- 3. Required SAP Applications and Company Roles Required SAP Applications Enhancement package 5 for SAP ERP 6.0 Company Roles Purchaser Purchasing Manager Warehouse Clerk Accounts Payable Accountant © 2011 SAP AG. All rights reserved. 3
- 4. Detailed Process Description Procurement Contract This scenario deals with the use of contracts in procurement activities. Contracts are agreements with the vendor to supply materials or services under negotiated conditions and within a certain period. Contracts are differentiated as follows: Quantity contracts: An agreement that a company will order a certain quantity of a product during a specified period. Value contracts: A contract in which the purchase of goods or services up to a total value is agreed. In source determination, contracts replace the purchasing info records and can be assigned in the source list as the fixed source for MRP. Target groups are purchasing managers as well as buyers Purchase requisitions and purchase orders are created after the contract, if they do not exist yet. © 2011 SAP AG. All rights reserved. 4
- 5. Process Flow Diagram Procurement Contract Create Procurement Contract P s nuocc A t t na nuocc A t MRP Generated Procurement Needs A Need for Material is Identified © 2011 SAP AG. All rights reserved. Material Arrival at Plant Dock Assign Requisition to Contract and Create Purchase Order Purchase Requisition Procurement Contract es uoher a W gn sa hcr u P i kr e C l r e ga na M r esa hcr u P t nev E Need for Contract Total Net Order Value > Threshold (e.g. EUR, USD, 500) Monitor Contracts No Value or Quantity Contracts Report Released PO Yes Released PO Approval of Purchase Order Goods Receipt with Reference to PO GR/IR PPV Small differences Use tax of actual payable amount Invoice Receipt by Line Item Accounts Payable (158) MRP = Material Requirements Planning, PO = Purchase Order 5
- 6. Legend Description Usage Comments Band: 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. <Function> Symbol Role band contains tasks common to that role. l an e x E r t PAS o t External Events: Contains events that start or end the scenario, or influence the course of events in the scenario. Unit Process Process Reference SubProcess Reference Process Decision 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 scenario Does 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 scenario Usage Comments To next / From last Diagram: Leads to the next / previous page of the Diagram Flow 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 lines Financial 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 lines Budget Planning: Indicates a budget planning document Diagram Connection Hardcopy / Document 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. Business Activity / Event Description 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 lines Manual Process: Covers a task that is manually done 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. Symbol 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. Corresponds 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 here Corresponds 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 © 2011 SAP AG. All rights reserved. Financial Actuals Budget Planning Manual Process Existing Version / Data System Pass/Fail Decision 6
- 7. © 2011 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 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 BusinessObjects Explorer, StreamWork, 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. © 2011 SAP AG. All rights reserved. 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 Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. 7