SAP Vendor Master SAP Vendor Master SAP Vendor Master LOG- -MM MM- -002 002 LOG LOG-MM-002 Aug 25, 2008 Aug 25, 2008 Aug 25, 2008 LaGov LaGov Version 3.1 Updated: 09/14/2008
Agenda Logistics, Ground Rules & Introduction Workshop Objectives Project Overview/Timeline Business Process Review – SAP terms glossary – Process improvement opportunities – SAP concepts & functionality – Leading practices – Enterprise readiness challenges Action Items Questions Friday, November 07, 2008 Friday, November 07, 2008 2 2
Logistics Before we get started ... Friday, November 07, 2008 Friday, November 07, 2008 3 3
Ground Rules Has everybody signed in? Everybody participates – blueprint is not a spectator sport 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 Friday, November 07, 2008 Friday, November 07, 2008 4 4
Project Organization - Functional Teams Finance Leads Logistics Leads Linear Assets Leads Beverly Hodges – Finance Lead Belinda Rogers – Logistics Lead Mark Suarez – Agile Assets Lead Drew Thigpen – Finance Lead Jack Ladhur – Logistics Lead Charles Pilson – Consulting Lead Mary Ramsrud – Consulting Lead Brad Denham – Consulting Lead Procurement Contracting Facilities Maintenance Fleet Maintenance Materials / Inventory Warehousing Mobile Solutions Belinda Rogers Karen Pierce Sterrie Elliott Adam LaTour Sudhir Deshmukh Friday, November 07, 2008 5
Introductions Roles: • Process Analyst and Functional Consultant (Team IBM): Leads and facilitates the discussions; drives design decisions • Documenter (State Employee): Takes 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): Provides additional support for process discussions; addresses key integration touch points • Subject Matter Experts: Advises team members on the detailed business processes and participates in the decisions required to design the future state business processes Around the Room Introductions: 1. Name 2. Position 3. Agency Friday, November 07, 2008 Friday, November 07, 2008 6 6
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 Friday, November 07, 2008 7
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! Friday, November 07, 2008 8
Blueprint Schedule – Tentative Workshop ID Process Area Date LOG-SRM-002 Vendor Registration, Qualification, 9/15 – 9/16 AVL (Approved Vendor List) LOG-MD-003 Catalog Management 9/17 – 9/18 LOG-MM-003 Purchasing Master Data (Info 9/22 – 9/23 records, Source List, Quata Arrangement & Pricing Conditions) LOG-MM-006 & Purchasing Requisitions 9/30 – 10/02 007 Friday, November 07, 2008 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 3. Define Future or To-Be Business Processes based on: • Best Practices inherent in SAP • Intellectual capital from other SAP implementations • State business requirements Friday, November 07, 2008 Friday, November 07, 2008 10 10
Blueprint Objectives (continued) 4. Identify Development Requirements: • Forms • Reports • Interfaces • Conversions • Enhancements • Workflow 5. Understand and communicate any Organizational Impact / Enterprise Readiness Challenges 6. Gather system Security Authorizations and State- wide Training Requirements Friday, November 07, 2008 Friday, November 07, 2008 11 11
Today’s Workshop Objectives Review State of Louisiana Vendor Records briefly. Vendor Master workshop on August 18, 2008 FI-AP-001 covered General and Company Code data in detail along with number ranges, screen layout, account groups and maintenance. As – Is Overview SAP Glossary/Concepts Overview of Vendor Master Concepts: – Usage, Number Ranges, Account Groups, Views – One Time Vendors Friday, November 07, 2008 Friday, November 07, 2008 12 12
Today’s Workshop Objectives (continued) Vendor Master Record Screens Live SAP Material Master screen review Review agreements on number ranges, account groups Next Steps Friday, November 07, 2008 Friday, November 07, 2008 13 13
As-Is Overview As-Is Overview Friday, November 07, 2008 Friday, November 07, 2008 14 14
As-Is Objectives Vendor Systems Overview Key Vendor Information Vendor Attributes Vendor Location / Address Hierarchy As-Is Vendor process for AGPS / CFMS As-Is Vendor processes for DOTD Methods for searching for Vendors in DOTD, AGPS / CFMS, LaPAC, and eCat Current System Alignment 15
16
Key Vendor Information Vendor Identification – Tax I.D. or Social Security Number Vendor status include – Casual, Active, Debarred, Suspend, Inactive Vendor Hold functionality exists in both AFS and AGPS / CFMS - This includes procurement / service documents and payments Vendor can have multiple addresses, contacts, and locations Vendors can register to receive bids by “Label”, “Commodity”, or “Class” 17
Key Vendor Information (continued) AGPS, LaPAC and LA eCat captures if a vendor is a “Small and Emerging Businesses” or a “Small Entrepreneurship” by an FTP file submitted from the Louisiana Economic Development A Vendors bid history is captured in AGPS / CFMS Vendor records house award amounts monthly, quarterly, and yearly Vendors can be designated for a wire, separate checks in AGPS / CFMS Vendor Banking and 1099 information resides in AFS Complaints and notes can be captured for Vendors in AGPS / CFMS 18
Vendor Attributes 19
20
DOTD PIMS and ADDS Vendor Process 21
As-Is Vendor Process AGPS / CFMS DOI – Create new Vendor in AGPS / CFMS Contract Supervisor Add Receive Enter vendor Fax W-9 to vendor Vendor to Is Vendor in completed W-9 information into for completion No AGPS/ Database? from Vendor AGPS/CFMS CFMS Yes End Vendor Receive W-9 for completion Activate vendor in AGPS/CFMS OSRAP 22
Procurement Administrative Vendor Procurement Manager Assistant As-Is DOTD Create/Change Vendor in PIMS 23
DOTD Construction Vendor Web Application 24
As-Is DOTD Create Construction Vendor 25
As-Is DOTD Create Vendor in Web Based System DOTD Create Vendor Process in Procurement Web Based System Procurement Administrative Contact Vendor Receive faxed or Validates vendor regarding mailed web filled out questionable data A application from appropriate fields Assistant Vendor on application Give application to Procurement Receive request to Manager with verify data corrected or verified data A Return to Authenticate Is information Procurement End vendor information No correct? Admin. Assist. to on application End Procurement Manager verify data Yes Lookup vendor in LDED monthly flat File vendor Does Vendor Yes No file to determine if application and exist? vendor is SEBD or validation report SE-HI certified Add vendor, addresses, & Generate Vendor Label Verification Report “commodities” in and validate Procurement Web against application System Vendor Confirm data with Procurement Admin. Assist. 26
Recommend
More recommend
