Crown Packaging Presentation v1.1
Crown Packaging Presentation v1.1
Organisational scope
• Divisions
• Food
• Speciality and aerosols (to be confirmed)
• Up to 200 users
• One team – all follow the same processes
Geographical scope
• 15 countries / 15 legal entities
• Ireland, UK, Poland, Germany, France, Spain, Portugal, Italy, Hungary, Greece, Switzerland, Russia, Morocco,
Ghana, Ivory Coast, Madagascar (to be confirmed).
• One go-live
• Primary project location: Switzerland
Integration scope
• Phase 1: No integration in scope
Functional scope for Phase 1
Scope Element Scope Scope Element Scope
Solution scope Highlighted exclusions
Account and Activity management Included Sales Quotes (using standard SAP form) Excluded
Opportunities Management (Sales contracts) Included Sales Orders Excluded
People Collaboration (native; for C4C users) Included Campaign Management Excluded
Outlook integration Included JAM integration (external collaboration) Excluded
Products Included Partner Channel Management Excluded
Pricing (within C4C / not integrated) Included Sales Quota Planning Excluded
Sales Forecasting Included Sales lead management Excluded
Sales Territory Management Included Full service Management (processing of tickets) Excluded
Competitor Insight Included Migration of historical transactional data (not in-process) Excluded
Mobile integration Included Integration to SAP & third party applications Excluded
Approval Levels & Notification rules Up to 2 levels Modifications beyond standard field extensions Excluded
• Starting point is a working solution based on industry standards and best practices. This means less custom
solutions and less blueprinting.
• SAP will make configuration changes in the solution rather than presenting design decisions in a design
document.
• Activation and configuration is based on built-in configuration tools and accelerators and less coding.
• More agile approach throughout the project with shorter iterations based on end-user feedback and
adjustment – less waiting before the users sees something that works.
• High level of involvement of customer resources ensures lowest possible cost and efficient knowledge
transfer during project
Project plan and effort estimate
Week
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 TBA
Project phases
Prepare
Explore
Realise (Build)
Realise (Test)
Deploy
Post Go-Live support
Sponsor Sponsor
SAP Global
Service Center
Project Project
SAP Hosting
Project Team
Manager Manager
SAP Cloud
Support
Key Consultant(s)
Users
End
Users
Customer roles
Systems/Network Subje
ct Ma End Users perform
Specialists own Exper tter
ts tasks within the SAP
the network
connectivity and/or cloud solution after the
integration with the go-live
SAP cloud solution Examples are employees
recording time or sales
Examples are SAP ERP representatives
or infrastructure experts
SAP ERP
Invoice
• Real-time integration of master data (accounts, prospects, contacts, products)
• Real-time integration of transactional data (opportunity real-time pricing, quote and sales order requests, quote to sales order request)
• PDF display of ERP sales documents in C4C opportunity and quote. PDFs are generated on-the-fly.
• Recent orders update
• Real-time integration of work ticket to billing request
• Additional real-time master data integration for currency conversion rates, account hierarchy, sales org hierarchy etc.
• Pricing: Real-time call to ERP SD pricing supporting the full pricing flexibility of ERP SD.
SAP Cloud for Customer– SAP ERP
Multiple Integration Touchpoints
Cloud for Customer SAP HANA Cloud Integration or SAP ERP 6.0
SAP NetWeaver PO/PI
REAL-TIME MASTER DATA SYNCHRONIZATION
Unidirectional from ERP for account hierarchy, products,
sales org, currency conversion rates
Bi-directional option for Accounts, Contacts
iFlows are the standard integration User defined functions required for standard
content from SAP integration delivered. Customers can
iFlows run on HCI and Netweaver PI customize them.
Each iFlow contains logical and iFlows contain predefined mappings with
technical routings 100+ fields mapped and several user
defined functions and routing rules.
Technical Prerequisites
SAP Cloud for Customer supports most common changes without coding and
provides powerful cloud development tools for unique needs.
1. Scoping and
2. Personalizing
configuring
1 2
Core
5. Customizing
5 Solution
3 3. Adapting
4
4. Extending
Extending SAP Cloud for Customer
C4C
Integrations
Customer Specific Solutions - Back-end integrations
- Native - Defined interfaces
- Built with SDK - E.g., SnapEngage, Marketo CRM
- Run on SAP Cloud OnPremise, ERP
- Specific to customer
Software Development Kit