Scenario Overview – 1 Purpose and Benefits: Purpose Benefits

Slides:



Advertisements
Ähnliche Präsentationen
EH&S Abhängigkeiten SAP Best Practices for Chemicals (Germany)
Advertisements

EH&S Datenmodell SAP Best Practices for Chemicals (Germany)
ES Community Definition Group – Bundle for Customer Billing and Payment In-Person Meeting April 29, 2008 Ratingen, Germany.
Änderungsnummer anlegen SAP Best Practices Baseline Package
SAP Best Practices Prepackaged Industry & Cross-Industry Know-How
Unternehmensstruktur Übersicht
Arbeitspaket Layouts und CRM Übersicht (Layouts)
Arbeitspaket zur Go-Live Vorbereitung Inhalt
SAP AG 2011, Introduction to SAP Business One 8.8, GTM Rollout Services Page 1 SwissAddOn Installation und Setup Allgemein: Zur Abdeckung Schweiz-spezifischer.
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Organizational Change Administration with Funds or Grants Management (978) SAP Best Practices.
Batch Management SAP Best Practices Baseline Package
Service with Time and Material Based Billing SAP Best Practices Baseline package SAP Best Practices.
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Internal Projects SAP Best Practices Baseline package SAP Best Practices.
Cost Center Accounting with Funds Management Overview
Enterprise Structure Overview
Process Flow Diagram Create Standard Cost for Individual Material
Credit Memo Processing SAP Best Practices Baseline package
How Unit Tests drive The Code (draft) Vasil Penchev Diana Kalcheva Date.
Leave Of Absence Administration with Funds or Grants Management (979)
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Customer Consignment Processing SAP Best Practices Baseline Package
Lean Campaign Management SAP Best Practices for CRM
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Accounts Receivable SAP Best Practices Baseline Package
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Serial Number Management SAP Best Practices Baseline Package
Service with Fixed Price Billing SAP Best Practices Baseline package
Employee Separation Administration with Funds or Grants Management (980) SAP Best Practices.
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Activate Document Splitting SAP Best Practices Baseline Package
Sales Processing using Third Party (w
Returns and Complaints SAP Best Practices Baseline Package
Segment Reporting SAP Best Practices Baseline Package
Accounts Payable SAP Best Practices Baseline Package
Rebate Processing: Free Goods SAP Best Practices Baseline Package
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Batch Recall SAP Best Practices Baseline Package
Retroactive Payroll Processing with Funds or Grants Management (987)
Cost of Sales Accounting SAP Best Practices Baseline Package
Sales Order Processing with Delivery from other Plant SAP Best Practices for Consumer Products and Wholesale Industries V1.604 (Colombia) SAP Best.
General Ledger SAP Best Practices Baseline Package
Prerequisite Process Steps SAP Best Practices Baseline Package
General Ledger Accounting with Funds Management Overview SAP Best Practices for Public Sector US V1.603.
Internal Order for Marketing and Other Overhead Planning SAP Best Practices Baseline Package SAP Best Practices.
Logistik Stammdatenaufbau Handel SAP Best Practices Baseline V1.604.
Overhead Cost Accounting – Actual SAP Best Practices Baseline Package
Services Stammdatenüberblick SAP Best Practices Baseline V1.604.
Create Customer Master SAP Best Practices Baseline Package
FMLA Processing with Funds or Grants Management (989) SAP Best Practices.
Budget Maintenance with Budget Control System Overview SAP Best Practices for Public Sector US V1.603.
Lean Warehouse Management SAP Best Practices Baseline Package
Free-of-Charge Delivery SAP Best Practices Baseline Package
Period-End Closing Projects SAP Best Practices Baseline package
Procurement without QM SAP Best Practices Baseline Package
Sales Scheduling Agreement with Configured Materials (362) SAP Best Practices for Fabricated Metals V1.603 (France) SAP Best Practices.
Sales Returns SAP Best Practices for CP V1.603 (RU)
Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Purchased Material Price Planning SAP Best Practices Baseline Package SAP Best Practices.
Leave of Absence (LOA) Administration SAP Best Practices for Public Sector (Canada)
E-Service: Service Request Management SAP Best Practices for CRM
Service with Time and Material based Billing SAP Best Practices Baseline package for Philippines V1.604 SAP Best Practices.
Consumable Purchasing SAP Best Practices Baseline Package
Data Extraction for SAP Business Objects Spend Performance Management.
 Präsentation transkript:

Purchasing with JIT Delivery Schedules (230) SAP Best Practices for Discrete Manufacturing V1.603

Scenario Overview – 1 Purpose and Benefits: Purpose Benefits This scenario focuses on a order-to-invoice cycle. It describes an outbound process in a typical repetitive manufacturing environment. Benefits Streamlined demand flow from customer to supplier High integration of customer’s and supplier’s supply chain managed by cumulative quantities Shorter process times Reduction of inventories to a minimum Key process flows covered Create basic customer contract called scheduling agreement Update scheduling agreement with forecast and JIT delivery schedules Display item due for delivery and create outbound delivery for available parts Enable traceability via batch or serial number assignment WMS controlled picking; packaging according to customer‘s packing instruction Invoice items and transfer to accounting

Scenario Overview – 2 SAP Applications Required: Required SAP ECC 6.0 Company roles involved in process flows Buyer Warehouse Clerk Accounts Payable Accountant 1

Scenario Overview – 3 Detailed Process Description: Purchasing with JIT Delivery Schedules The scenario Purchasing with JIT Delivery Schedule focuses on one option for the purchasing of materials: The purchasing process with delivery schedules. This scenario is starts with the creation of a customer contract called scheduling agreement. This agreement will be updated, released and transmitted to the supplier. After goods receipt the invoicing of the items and the transfer to accounting is performed.

Process Flow Diagram Purchasing with JIT Delivery Schedules Event Beginning of Planning Cycle Periodic Plan Revision Strategic Planner Logistics Planning (144) Production Planner Repetitive Manufacturing with Kanban Supply into production (233) Shop Floor Specialist Set KANBAN to “empty” (233; 4.3.1.1) Set KANBAN to “full” (233; 4.3.1.2) Buyer Create Scheduling Agreement Release Scheduling Agreement Transmit Scheduling Agreement Ware-house Clerk Goods Receipt Accounts Payable Accoun-tant 1 Invoice Verification Additional Processes Outgoing Payment (158) Period-End Closing “General” Plant (181) CO-PA =Profitability Analysis, MRP = Material Requirements Planning, GI/GR = Goods Issue/Goods Receipt

Legend Symbol Description Usage Comments Symbol Description 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. 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 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. 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. 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 Symbol Description 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 Budget Planning: Indicates a budget planning document Manual 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. Diagram Connection <Function> Hardcopy / Document External to SAP Financial Actuals Business Activity / Event Budget Planning Unit Process Manual Process Process Reference Existing Version / Data Sub-Process Reference Process Decision System Pass/Fail Decision

Copyright 2008 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. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed 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. 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. 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 Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten.