Introducing
Prezi AI.
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
Loading content…
Loading…
A Methodology for Implementing SAP Variant Configuration
119
Transcript
Plan the Project
Build a Team
Create Golden Client
Define Implementation Sequence
Define Naming Convention
- Make your model easier to understand at a glance
- Examples:
- Procedures = PR_...
- Selection Conditions = SC_...
- Preconditions = PC_...
- Constraints = CK_...
Define Shared Data Process
- Your project may have more than one modeler
- Communication is important to ensure different people are not changing the same data
- Make sure that everyone knows when data is being moved between systems
Perform Testing
Remember to have entry and exit criteria for each of these test phases!!!
Perform Cutover
Practice makes perfect
- Do it over and over until everyone knows their steps
- Use ALE, load programs, and/or third party tools to load VC data
- Confirm that everything loaded correctly
Post Go-live Considerations
- Remember that the project team will need to provide support
- Once things are settled, plan out the next phases by repeating these steps
- Celebrate!
A Methodology for Implementing
Variant Configuration in SAP
Define
the
Scope
Plan
the
Project
Steering
Committee
- Add all the tasks required
- characteristics
- classes
- config profiles
- interface design
- super BOMs
- super routings
- Define the timeline for each task
- Define what can realistically be achieved
- Do not underestimate the time required (could be 300+ hours per configurable material)
- Define all the tolls to be used (ECC, IPC, third-party, etc.)
- List any interfaces required
Project
Manager
Development
Core Team
(Modelers)
Extended Team
(SD, MM, PP, FI/CO, IT)
Integration
Production
VC (separate
system or client)
Legend
Transports
VC Data
- Only modelers have access
- No transaction data allowed
- No manual VC changes allowed in other systems
Support Data (change numbers, materials, etc.
Front
End
Back
End
- More Characteristics
- Super BOM
- Super Routing
- Characteristics
- Classes
- Config Profiles
- Interface Design
- Variant Pricing
- Conventions can get more sophisticated
- Include KMAT names
- Include basic words
- Examples
- PR_CABINET_SET_WIDTH
- PR_CABINET_CALC_HEIGHT
- Decide on standard for abbreviations
- Make it easier to decipher characteristic names, dependencies, etc. without reading the description
- Examples:
- Height = HT
- Width = WT
- Connector = CONN
Back End
Integration
Front End
- Create Sales Orders
- Check Configuration
- Check Costing
- Convert Sales Orders to Production Orders
- Check BOMs
- Check Routings
- Test End-to-end Process
- Check COPA Results
- Check financials
- Check Various Processes
Choose a template
Presentations from around the world
Learn more about creating dynamic, engaging presentations with Prezi