s/4hana finance at aker solutions –one year later -konomisjefens dag 10 mai 2017... · s/4hana...
TRANSCRIPT
© 2017 Cognizant © 2017 Cognizant
10th May, 2017
S/4HANA Finance at Aker Solutions – one year laterAksel Oland, Solution Architect S/4Finance, CognizantPetter Natås, Finance Process Improvement, Aker Solutions
© 2017 Cognizant 2
“Implementing S/4HANA Finance has significantly changed our way of
working with Financial information. The Single source of truth for Financial data & real time reporting has increased
the transparency both locally and globally”
Petter Nataas, Head of Finance Process Improvement, Aker Solutions
© 2017 Cognizant
14,000EMPLOYEES
20COUNTRIES
50LOCATIONS
175YEARS OF EXPERIENCE
Aker Solutions creates solutions to unlock energy safely and sustainably for future generations
© 2017 Cognizant 4
S/4HANA Finance – Why?
SingleSourceofTruth1. Onesourcefor
financialandmanagementaccounting
2. Realtimereportingw/oreplicationtoSAPBW
HighestGranularity1. Lineitembased
andextensible2. Notlimitedby
totalsorpre-configuration
ReportingandAnalysis1. Fastandflexible2. Self-service
analytics
1
2
Closingonthefly1. Acceleratedmonth-
endclosingprocessesandpostings
2. Intra-monthprocessesandsimulations
4
3
UserExperience1. Powerfuluser
interfaces2. (Availabilityon
multipledevices) 5
© 2017 Cognizant 5
The S/4HANA Business Case• Need for improved and more efficient processes and tools
– S/4HANA Finance is the enabler on the system side.
From:§ Local processes§ Local master data § Individual local reporting § Control locally§ Lack of transparency
centrally
To:§ Automated group reporting§ Self service reporting§ Real time reporting§ Transparency centrally§ Utilizing Global Shared
Service§ Single source of truth for
financial data
Transition from local to central
Key enablers:1. Global master data
harmonization2. Global process
harmonization3. Common platform:
S/4 HANA Finance
© 2017 Cognizant 6
The S/4HANA project at Aker Solutions, Kværner and Akastor
2014 June - Sept
HANA Business case development and
approval
2015 Jan - June
HANA Technical Migration, including
SP upgrade
2015 June
HANA migration on consolidated ERP
system
2015 July –
Start of S/4HANA Finance Migration project
2015 Oct - Dec
Rollout first wave of Fiori apps (HCM)
Rollout NWBC 5.0
2015 Dec -
Establishment of new infrastructure for custom-and self service reporting
2016 April - Nov
S/4HANA Finance Migration of all three
ERP systems
2017 May
S/4HANA Finance 1605 upgrade
2017 Feb - April
Functional assessment with AKSO business
HANA platform migrationGo-Live
Fiori NWBC 5.0
HANA live, Lumira and
Analysis
S/4HANAFinance Go-live
S/4HANA 1610assessment
© 2017 Cognizant 7
The S/4HANA Finance Timeline
Q3 2016Q2 2016Q1 2016Q4 2015Q3 2015Q2 2015
Suite on HANA
• 12 migrations, 3 support pack upgrades• Multiple patches of miscellaneous components, 300+ OSS
notes• Core project team of 9 persons• Productive migrations:
• Akastor Live 24. April 2016• Aker Solutions 18. Sept 2016• Kvaerner November 2016
SFIN 2.0Migration
UX & Reporting
Q1 2017
© 2017 Cognizant 8
S/4HANA Finance - 1 year later
High Granularity offers new Insight- drill-down on all dimensions and all levels
Speed; global numbers available on the fly- Dramatically increased financial transparency
“IT” Cost savings:- Operational reporting moved
from BW to ERP- Much lower development cost
for new reports Increased data integrity - No data redundancy (ACDOCA!)
© 2017 Cognizant 9
Live Demo
© 2017 Cognizant Slide
10
S/4HANA Finance (work in progress)
• SAPGUI Integration• Fiori Notifications• Fiori Elements/Overview
pages
Fiori
• Full-text Search of +100 business objects• Flexible search visualization for filtering• Navigate to factsheet / transaction
Search
• Intuitive chart based multidimensional drill-down analysis on real-time data sources
Analysis
© 2017 Cognizant 11
Live Demo
© 2017 Cognizant 12
S/4HANA - Important considerations and lesson learned
§ Key Enablers § Global master data harmonization§ Global process harmonization
§ Important to align end-user expectation (wow effect takes time to get..)- Skilled and dedicated resources – ability to scale resources to project needs on the fly
§ You need to be able to handle “constant changes”§ In depth analysis needed to understand possible implications - e.g. S/4Finance implications on existing functionality (cash management/Planning)
§ Added complexity to development and application support§ Think about size vs licences (archiving)
- SFIN increase amount of data
§ Shift in competence required in “new technology”
© 2017 Cognizant 13
S/4HANA 1610 assessment (Proof of Concept)Objective: Gain competence on 1610 and verify flow-efficiency improvement in the Aker Solutions processes
Act
iviti
esO
utpu
t
Agreement on long-list
Project structure established
Workshops (starting 1st / 2nd week Febr) with key stakeholders at Akso:- Identify business prioritises - Discuss key findings from
exploration phase- Agree on potential
improvement areas in HANAS/4 1610 rel.
Agreement on short-list and first draft of business
case
Set up project structure Agree on potential improvement areasDiscuss key findings Final report and
presentation
Final report
- Short-list of potential improvement areas
- Assess flow- efficiency potential for the individual improvement areas
Set up project governance
- Project Manager appointed- Team members appointed
(AKSO and Cognizant Oil & gas)
- SteeCo members agreed
Final business case report - Main value drivers identified,
including estimated benefits- Main Risks - High-level estimates on
transformation project
3 weeks
Key findings in exploration phase
- Establish business case framework
- System Test Migration- Cognizant Oil & Gas HANAS/4
exploration phase (starting 3rd week Jan)- Review simplification list- Discussion on potential improvement areas in 1610 release
3 weeks
Exploration phase
Long-list of potential improvement areas . Presentation and status
update SteeCo
1-2 weeks1 week 1-2 weeks
Short list of potential improvement areas . Presentation and status
update SteeCo
1 43 52
© 2017 Cognizant 14
S/4HANA 1610 - main findings so farMain benefits within the UX & Reporting area
Current functionality replaced with new products; high impact on license cost, development cost and integration
Simplification list should drive behavior in existing systems (e.g. avoid new implementation of things no longer strategic in S/4HANA in existing ERP)
There are strict “show stopper” limitations for system conversions (add-ons, business functions etc)
69 85
195249
5393
1511 1610
Change of existing functionality
Functionality not available in SAP S/4HANA (with or without functional equivalent)
Not the target architecture (functionality still available)
There are ~440 Simplification items (as of 1610 FPS1), up from ~300 in release 1511S/4HANA (on premise) has a yearly release cycle with quarterly feature packs, that will add new items to the simplification list
© 2017 Cognizant
Thank you
15
© 2017 Cognizant 16
Appendix
© 2017 Cognizant 17
Example: Granularity: Available “GL” Reporting Dimensions
© 2017 Cognizant 18
Example: Project Reporting
• Speed - All Projects Inception to Date (100 million ACDOCA records)
• Old World: Report Painter report: 15 hours (this is calculated – not possible to run in one-go)
• New World: Analysis for Office based on embedded BW with HANA Live: 110 Seconds
• High Granularity • Enables insight to action