Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. 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 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. Line can also lead to documents involved in the process flow. Flow line (dashed): Line indicates flow to infrequently- used or conditional tasks in a scenario. Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario. Role band contains tasks common to that role.
You have as many rows as required to cover all of the roles in the scenario. The other process flow symbols in this table go into these rows. This band can also identify an organization unit or group, rather than a specific role. EUR 500) Procurement Contract Released PO Value or Quantity Contracts Report No Yes Approver Released PO Approval of Purchase Order MRP = Material Requirements Planning, PO = Purchase OrderĦ Legend Symbol Description Usage Comments Symbol Descriptionīand: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. Need for Contract MRP Generated Procurement Needs A Need for Material is Identified Material Arrival at Plant Dock Warehouse Clerk Goods Receipt with Reference to PO Requestor Purchase Requisition Purchase Manager Buyer / Create Procurement Contract Assign Requisition to Contract and Create Purchase Order Monitor Contracts Total Net Order Value > Threshold (e.g.
Target groups are purchasing managers as well as buyers Purchase requisitions and purchase orders are created after the contract, if they don’t exist yet.ĥ Process Flow Diagram Procurement Contract Event Requestor In source determination, contracts replace the purchasing info records and can be assigned in the source list as the fixed source for MRP. Value contracts: A contract in which the purchase of goods or services up to a total value is agreed. Contracts are differentiated as follows: Quantity contracts: An agreement that a company will order a certain quantity of a product during a specified period. Contracts are agreements with the vendor to supply materials or services under negotiated conditions and within a certain period. Procurement Contract This scenario deals with the use of contracts in procurement activities. SAP enhancement package 4 for SAP ERP 6.0 Company roles involved in process flows Buyer Approver (Procurement Manager) Warehouse ClerkĤ Scenario Overview – 3 Detailed Process Description: This scenario deals with the use of contracts in procurement activities Benefits Reduced procurement costs Securing of supplies Transparency of supplier agreements Key process flows covered 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ģ Scenario Overview – 2 SAP Applications Required: Required
1 Procurement Contract SAP Best Practices Baseline PackageĢ Scenario Overview – 1 Purpose and Benefits: Purpose