WM View WM View WM View in SAP Material Master in SAP Material Master in SAP Material Master and WM Structure and WM Structure and WM Structure LOG- -MD MD- -005 005 LOG LOG-MD-005 September 23, 2008 September 23, 2008 September 23, 2008 LaGOV LaGOV Version 4.00 Updated: 09/22/2008
Agenda Logistics, Ground Rules & Introduction Workshop Objectives Project Overview/Timeline Business Process Review – As Is Process Discussions – SAP terms glossary – Process improvement opportunities – SAP concepts & functionality – Leading practices – Enterprise readiness challenges Action Items Questions 2
3 Before we get started ... Logistics
Ground Rules Has everybody signed in? Everybody participates – blueprint is not a spectator sport Silence means agreement Focus is key – please turn off cell phones and close laptops Challenge existing processes and mindsets Offer suggestions and ideas Think Enterprise Ask questions at any time One person at a time please Creativity, cooperation, and compromise 4
Introduction Roles Process Analyst and Functional Consultant (IBM) – lead and facilitate the discussions and drive design decisions Documenter (State Employee) – take detailed notes to support the formal meeting minutes to be sent by the Process Analyst to all participants for review and feedback Team Members (LaGov) – provide additional support for process discussions, address key integration touch points Subject Matter Experts – advise team members on the detailed business process and participate in the decisions required to design the future state business process Round the Room Introductions Name Position Agency 5
Project Phases Five Key Phases Preparation Realization Preparation Business Blueprint Go Live Support Project Final and • Strategy & Approach Defined • Development & Unit Testing • Go-Live Support • Project Team Training • Integration Testing • Performance Tuning • End-User Training Materials • Business Process Definition • User Acceptance • Development Requirements • Technical Testing • End-User Training • Conversion 6
Tentative Project Timeline Tentative implementation dates are planned as follows: Functionality Tentative Implementation Date Budget Prep October 2009 DOTD February 2010 Core Modules All Agencies July 2010 Additional Modules January 2011 May – June 2008 July 2008 August – Dec 2008 January 2009 Project Start-Up Phased deployment will be Blueprint confirmed/updated before completion of Blueprint activities! 7
Blueprint Schedule - Tentative Please refer to the handout for the upcoming Blueprint Sessions 9
Blueprint Objectives 1. Review and discuss the current or As-Is Business Processes: • Which helps to drive out the business requirements business requirements • As well as the integration points integration points with other processes 2. Define Master Data • Address key integration points • Support organizational requirements • Consistent and appropriate use of data fields 10 Friday, November 07, 2008 10 10
Blueprint Objectives 3. Define Future or To-Be Business Processes based on: • Best Practices inherent in SAP • Intellectual capital from other SAP implementations • State business requirements 4. Identify Development Requirements: • Forms • Reports • Interfaces • Conversions • Enhancements • Workflow 11 Friday, November 07, 2008 11
Blueprint Objectives 5. Understand and communicate any Organizational Impact / Enterprise Readiness Challenges 6. Gather system Security Authorizations and State- wide Training Requirements 12 Friday, November 07, 2008 12 12
Today’s Workshop Objectives TOPICS TO BE DISCUSSED Warehouse Management vs Inventory Management Basic Warehouse Management (WM) topics WM structure WM views of Material Master Records 13
KEY DECISIONS Storage Locations that require Warehouse Management Storage Types Storage Sections Storage Bins Key fields in WM Material Master View Bin Numbering UOM Min/Max Levels 14
Project Scope Systems to be Replaced DOTD – PIMS (Purchasing Inventory Management System) DPS – VENICE WILDLIFE & FISHERIES – PARADOX 15
16 AS-IS Process Flow
17
18
19
20 GLOSSARY
SAP Glossary Storage Location – An organization unit that allows the differentiation of material stocks within a plant. The storage location is hierarchically situated between the plant and the warehouse number. Warehouse – An organizational division of a plant for the purpose of maintaining materials that are stored in different places. Storage Type – A physical or logical subdivision of a complex warehouse, distinguished by the warehouse procedures used or its organization form or function. E.g. Bulk, fixed, high rack, etc. Storage Section – Logical or physical subdivision of a storage type. A number of storage bins can be grouped together into one storage section according to different criteria (with the same characteristics) selected by the user. E.g. Fast moving, slow moving, etc. Storage Bin – Smallest addressable unit of space in a warehouse (often referred to as a “slot”). Since the address of a storage bin is frequently derived from a coordinate system, the bin is referred to as a coordinate; for example, 02-04-03 refers to row 02, stack 04, level 03. Transfer Requirement – Request to transfer materials, at a particular time, from a source storage bin to a destination storage bin within a warehouse complex. 21
SAP Glossary Transfer Order – Instruction to move materials from a source storage bin to a destination storage bin within a warehouse complex at a specific point of time. A transfer order consists of items that contain the quantity of material to be moved and specifies the source and destination storage bins. Storage Unit – A logical grouping of one or several amounts of material which can be managed within a warehouse as a unit that belongs together. Each storage unit has a number which identifies it. Picking – The process of issuing and grouping certain partial quantities (materials) from the warehouse on the basis of goods requirements from the Sales or the Production department. Picking can take place using transfer orders or pick lists. Picking Strategy – A procedure whereby the system searches for a suitable quant within a storage type for a pick. As a rule, a certain picking strategy is defined for each storage type, for example FIFO or LIFO. These strategies optimize the flow of materials within the warehouse. Pick List – A document that specifies items to be removed from a storage bin for goods issue. Among other things, it contains pick quantity, item number and description. Posting Change – Primarily a change in information about the stock itself. A posting change generally refers to a bookkeeping change – a change in information – about a particular material. For most posting changes, the goods themselves remain in the same physical location. E.g. Releasing stock from inspection. 22
SAP Glossary Putaway Strategy – A procedure in which the system looks for a suitable bin in a storage type for stock putaway. A putaway strategy can be defined for each storage type to search for the next empty bin that guarantees the optimization of warehouse storage and material flow. Cycle Counting – A physical inventory procedure in which the materials are counted at regular intervals during a fiscal year. These intervals, or cycles, depend on the cycle counting indicator set for the relevant material. Stock Transport Order – A purchase order used to request or instruct a plant to transport material from one plant to another (that is, to effect a long distance physical stock transfer) within the same corporate enterprise. The stock transport order allows delivery costs incurred as a result of the stock transfer to be charged to the material transported. Cross-docking – A procedure for processing goods in a distribution center or warehouse. The goods are brought directly from goods receipt area to goods issue without being put away. One step Process - The goods are moved directly from Goods Receipt (GR) to Goods Issue (GI) OR Two step Process - The goods are first moved to a storage type designated for cross-docking 23
Recommend
More recommend
