sap01

Views:
 
Category: Education
     
 

Presentation Description

sap o1 overview slides

Comments

Presentation Transcript

Stock Transfer with Delivery SAP Best Practices Baseline Package (Malaysia):

Stock Transfer with Delivery SAP Best Practices Baseline Package ( Malaysia ) SAP Best Practices

Scenario Overview – 1:

Scenario Overview – 1 Purpose Transfer material requested automatically by MRP or manually by a buyer from one plant to another within the same company code Benefits Transparent view of outstanding stock transfers, stock-in-transit Efficient Processing of internal stock transfers Purpose and Benefits

Scenario Overview – 2:

Scenario Overview – 2 SAP ECC 6.0 EhP3 SAP Applications Required Stock transport requisition (with MRP) Changing stock transport purchase order (with MRP) Stock transport order (without MRP) Delivery for stock transport order Delivery due list Picking confirmation Goods Issue Receiving transferred material Buyer Production Planner Warehouse Clerk Key P rocess F lows C overed Company R oles I nvolved in P rocess F lows

Scenario Overview – 3:

Scenario Overview – 3 Stock Transfer with Delivery The stock transfer process begins with a requirement to transfer material from one plant to another within the same company code. This request, in the form of a stock transfer requisition, may be created in the procuring plant automatically by MRP or manually by a buyer. There are no master data requirements beyond the material master to support the stock transfer process. The material master must exist in both the procuring (receiving) plant and the providing (shipping) plant. Also, stock transfer purchase orders are not subject to approval like other purchase orders. A buyer validates the accuracy of the stock transfer purchase requisition and converts it into a stock transfer purchase order. A warehouse clerk at the shipping plant monitors the materials due to be shipped and creates deliveries as required. Once a delivery is created, a pick list is generated for the materials. A warehouse clerk gathers the materials and confirms the picked quantities. Once the delivery is complete, the delivery quantities are issued, appropriate documentation is generated, and the goods are shipped, ending the process for the shipping plant. Goods are received at the receiving plant referencing the delivery number on the shipping documents. Inventory is received into storage based on fixed parameters proposed from the material master which can be changed at time of transactional data capture i.e. purchase order creation or goods receipt. Detailed Process Description

Process Flow Diagram:

Warehouse Clerk Event Purchaser Display Stock/Requirement List Need for material Material Arrival at Plant Dock Daily Shipment Worklist, Enough Inventory Process Stock Transport Requisition Delivery Delivery Note End of Process Change Stock Transport Order Create Stock Transport Order Delivery (w/o MRP) w/o MRP Accurate? Pick List Goods Receipt Process DeliveryDue List for Pos (Create Outbound Delivery) GR Print Picking Confirmation Delivery Note Post Goods Issue Check Status of Stock Transfer Production Planner Yes NO Material Document MRP = Material Requirements Planning, GR = Goods Receipt Stock Transfer with Delivery Process Flow Diagram

Legend:

Legend 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 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 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 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 Hardcopy / Document Financial Actuals Budget Planning Manual Process Existing Version / Data System Pass/Fail Decision Symbol 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. 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. 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 <Function> External to SAP Business Activity / Event Unit Process Process Reference Sub-Process Reference Process Decision

Copyright 2009 SAP AG All rights reserved:

Copyright 200 9 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, xApps, xApp, SAP NetWeaver, Duet, SAP 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.

authorStream Live Help