Ramp Up Experience SAP Solution Manager 7.2 @ Zalando
1. Ramp - U p
E xp eri en ce
S A P S o l u t i o n M a n a g e r 7 . 2
T o m D a m m e r
2 2 . 0 7 . 2 0 1 6
2. 2
ZAL AND O AT A GLANCE
~3billion EURO
net sales 2015
50%return rate across
all categories
~160
million
visits
per
month
~18
millionactive customers
>150,000
product choices
10,000+
employees in
Europe
15
countries
>1,500
brands
4. 4
HIGHLIGHTS @ ZAL ANDO
FEBRUARY
Zalando expands its assortment to
include apparel
APRIL
The Zalando Lounge is launched in
Germany
SEPTEMBER
Launch of the self-developed shop
platform
DECEMBER
First creation of a private label
MARCH
The first Zalando magazine is
published
MAY
First international launch of Zalando
Lounge in France, 5 countries will
follow
JULY
First self-operated fulfillment center in
Brieselang
DECEMBER
Launch of the partner program in
Germany
MAY
Designer collaboration with
Kaviar Gauche
JULY
A new technology team starts working
in Dortmund
DECEMBER
Zalando breaks even in the core
regions Germany, Austria and
Switzerland
Opening of the first custom-designed
logistics center in Erfurt
Launch of the first smartphone app in
Germany
OCTOBER 2008
Foundation of the company
SEPTEMBER 2009
Zalando develops its first television
advertisement
2010 2011 20122008 - 2009
5. 5
HIGHLIGHTS @ ZAL ANDO
MAY
The 2,000th employee is hired in Erfurt
JULY
More than one million downloads of
the app in Germany
Beginning of operations in the second
custom-designed logistics centre in
Mönchengladbach
DECEMBER
Zalando becomes a private German
stock corporation (AG)
JANUARY
Launch of the iPad app in Germany
MARCH
Designer collaboration with Eleonora
Carisi
After Germany, Austria, Belgium, the
Netherlands and France, the partner
program is launched in Italy
MAY
Zalando transforms into a Societas
Europaea (SE)
SPRING/SUMMER
International apps are rolled out
OCTOBER
Zalando goes public
MARCH
Zalando had a very successful year
2014 with group revenues of about
EUR 2.2bn
APRIL
Opening of Zalando’s first international
tech hub in Dublin
MAY
Zalando launches styling platform
ZALON
JUNE
Zalando admitted to the MDAX
AUGUST
Opening of Zalando’s second
international tech hub in Helsinki
DECEMBER
Internationalization of Zalando’s
logistics network starting in Stradella
2014 2015 20162013
MARCH
Zalando had a very successful year
2015 with group revenues of about
EUR 3bn
MAY
Opening of the third national Zalando
outlet in Köln
6. S A P C O M P E T E N C E C E N T E R
6U N S E R E G E S C H I C H T E
2012 2013 2014 2015
SAP components SAP
FI/CO
SAP PI
SAP FI-CA
SAP HCM
SAP Solution
Manager
SAP Treasury
SAP BW on
HANA (FI-CA,
FI)
SAP BW on HANA
(CO, HCM)
SAP Liquidity planning
SAP FCCO
SAP ERP on HANA
SAP CRM SSF
SAP CC
employees
1 3 10 20
SAP User 50 200 450 1000
SAP FI-CA
datavolumes
380 GB 2 TB 4 TB
30.08.2016
7. Landscape Overview
7
Installation
Service Provider
Christoph Höltl
Configuration
Zalando
Tom Dammer
FI
Landscape
HANA DB
HR
Landscape
Sybase DB
BW
Landscape
HANA DB
CRM
Landscape
Sybase DB
PI
Landscape
Sybase DB
New Installation of SAP Solution Manager 7.2 Sybase DB
ITSM, ChaRM, Fiori
8. - Release 7.10 SAP SAP Solution Manager - many modifications
- Gain experience on a new installation
- Cost estimation, use case
- Fresh and clean configuration
Why not HANA?
Service Provider monitored Zalando systems
Cost Hardware
Service Provider will migrate the SAP Solution Manager to release 7.2, Zalando
will get access to Fiori Monitoring apps
Migration experience
Migration of the old SAP Solution Manager 7.1 (non-productive)
Reasons for a New Installation
8
New Installation of SAP Solution Manager 7.2 Sybase DB
10. Experience – System Preparation
10
SAP Solution Manager
No direct access to
Internet
Create manually
SOAP Runtime No Solution
Change Proxy Server
Settings
Service Provider
KBA 2289984
Solution
12. ABAP – JAVA Systems
Business Object – Cluster
Experience – Managed System Configuration
12
FI - ERP
EHP7
HANA DB
HR
ERP EHP 7
Sybase DB
BW
NW 7.5
HANA DB
CRM 7.0
EHP 3
Sybase DB
PI
NW 7.3
Sybase DB
BI Platform 4.2
SAP SQL Anywhere
Windows 2012 / R2
Assign Automatically Diagnostics-relevance could not
set.
Incident is send to SAP
13. - Zalando Change Control Management is based on the SAP Standard
- Copy Transaction Types into the Customer Namespace
- Status Dependent Customizing with Integration into ITSM
- Audit Compliant Customizing
Change Control Management
13
Request for
Change
Urgent Change
6 Change
Managers
Transport in PRD
The tester role
cannot be the
same as the
developer role
14. Change Control Management
14
No Downgrade
Protection and
Retrofit
Copy Transaction
types
Status Management, PPF, Text Management,
Approval Procedures
SAP Standard
Reporting
will be established
15. - Update ST-PI in Managed Systems
- TMS Configuration, By Release 7.10 SAP Solution Manager Already Defined
- Set Project Assignment of Requests as Mandatory
- Generate RFC
- Template User
- Create Users and Business Partners
- Assign Business Partner to IObject
- Create Landscape and Change Cycle
ChaRM – Managed System Setup
15
16. Set Project Assignment of Requests as Mandatory
ChaRM – Administrations Cockpit
16
Check RFC
Connection
Attribute Definition
via Administration
Cockpit
17. BP_USER_GEN
Assign Business Partner to IObject
ChaRM – Assign Business Partner to IObject
17
User are applied
via LDAP
BP will be created
automatically and
updated for the
respective systems
Job runs periodically
18. ChaRM – Create Landscape and Change Cycle
18
Solution Configuration(SLAN)
Solution Administration was very simplified.
Zalando has defined 6 solutions:
CRM
BW
HR
FI 100
FI 300
SAP Solution Manager
Creating branches and logical components in the Solution
Administration
19. ChaRM – Change Cycle
19
Define and Unlock Change Cycle and Task List
20. ChaRM – Process at Zalando
20
Requirement
ITSM
Change Request
Approval
Urgent Change Import in QAS
Test
Consultant,
Department
Released for
import in PRD
Import by
Change Manager Zalando must respond quickly to urgent
changes.
Therefore, the process for a quick import into
the PRD has been configured.
Especially FI-CA, Bank communication and
interfaces to our shop need to set fast go live
process in ChaRM.
6 Change Manager are authorized to import
into PRD.
In emergencies, it is also possible that SAP
CC Consultants can import into PRD.
A Change Manager need to approve the
emergency change.
22. ITSM – Configure Manually
22
- Specify Impact, Urgency, and Priority remain the SAP Standard
- TREX is enabled
- SLA configuration remain the SAP Standard
- Status, Text, Partner and Date Profiles remain the SAP Standard
- The automatic closing of incidents is disabled. Requests from the Department
- Zalando does not use Knowledge Articles
- Zalando does not use Categorization Schemes
23. ITSM – PPF Actions and Notification
23
ZMIN
BRFPLUS Supportteam
Compared to
7.10
24. ITSM – E-Mail Delivery
24
Support Team
E-Mail Distributor
Status New
ZI_CRM_IM_SHOR
T_TEXT_LINK_FO
RM
Reporter
Support Team
ZI_CRM_IM_FULL_
DATA_FORM
33. Problems
33
- Guided Procedure: Permissions Errors after SP02 with the role SAP_RCA_DISP (2138636)
- Hub Connectivity: Could not create a connection to SAP(2289984)
- BI Platform 4.2 Could not assign Diagnostic - relevant (SAP Ticket still open)
- Solution Administration: (SLAN) A Solution can not be deleted.
- Closing a ITSM ticket: Deactivation of AI_CRM_IM_PROC_CHECK
34. Planning
34
- Configuration of Business Process Monitoring in the SAP Solution Manager (Service
Provider)
- Migration of Release 7.10 SAP Solution Managers auf 7.2 (gain experience)
- Configuration of Test Management and Custom Code Management.
- Job Monitoring.
- HANA und BI Monitoring
- BW Reporting in our SAP BW System
- E-Mail Inbound Configuration – 80% Done
37. This presentation and its contents are strictly confidential. It may not, in
whole or in part, be reproduced, redistributed, published or passed on to
any other person by the recipient.
The information in this presentation has not been independently verified. No
representation or warranty, express or implied, is made as to the accuracy
or completeness of the presentation and the information contained herein
and no reliance should be placed on such information. No responsibility is
accepted for any liability for any loss howsoever arising, directly or
indirectly, from this presentation or its contents.
DISCLAIM ER
37