Professional Documents
Culture Documents
1
Agenda
Overview of Electrotherm
Our Understanding
Business Units
Landscape
SAP and Non SAP Components
Infrastructure
Modules implemented
Modules Not Implemented
Functionalities Not Explored
SAP Assessment Observations
Types of SAP Deployment
Generic Comparison
ET Specific Comparison
About Customer
Our Understanding
4
Business Units
• Multiple Divisions /Business Units
• Around 25 plants
• Warehouses/Depots
• Multiple company codes
• First Level Maintenance and Support done by In-house Team for all landscape
Modules
• Implemented in SAP • Implemented Non SAP
• ECC • Salesforce for Presales and
• FI Business development of
• CO Projects
• Asset management • Internal 3rd Party Apps for
• Sales and Distribution Quality Assurance and
• Material Management approval
• Project Systems • Internal 3rd Party App for
• Plant Maintenance Customer Service
• Customer Service(Without Warranty
Management)
• Quality Management
• Production Planning
10
Current Strengths
Overall operations
Overall operations Project presales is
are stabilized in
are stable in mapped * ( in 3rd
Steel Pipe
Finance module Party application)
business unit
Gate entry
Users are In house hosting
customization is
extensively using ensures near to
stable and being
the SAP system zero latency
used properly
Current Pain Areas
Transactional analytics is not effective and accurate from current version of SAP
GST Mapping needs validation and transactional processing needs manual review each time
SAP Assessment Observations
Sales Organization structure revamp is needed
Order to Cash cycle considering project contracts needs to be reorganized as Contract creation, release order creation
process has some inefficiencies and therefore reporting is not accurate
Some processes in overall logistics modules are not available ,will need mapping for example Customer master, material
master harmonization and governance , order to cash variations of projects, exports and after sales warranty
management , Scheduling agreement in procurement
MRP planning is not active because of overall configuration and process mapping, master data issues, needs to activate
live MRP in new SAP S/4HANA environment
Overall Analytics is not available , to be enabled on both levels Operational as well as Regular Analytics
SAP Assessment Observations
Business Planning for sales, Operations, financial planning is not in current environment, looking at current scope, diversity and growth ,is
highly recommended to be used
Enterprise Asset management recommended for next generation functionality availability in current Plant maintenance environment
Need Reorganization of Workflow between Projects, SD,PP and MM to eliminate Open Reservations etc.
Entire Concept to Cash cycle of projects to be incorporated in SAP using S/4HANA customer management, Field service, Project presales,
Workspace management, and S/4HANA Planning, Finance and logistics capabilities to provide deeper insights into capex heavy project
operations
Modules/Tools can be used are SAP S/4HANA, S/4HANA Customer management, S/4HANA Embedded Analytics(BI) , S/4HANA Simple
Logistics with SCM functions, SAP S/4HANA Integrated Business planning modules, SAP S/4HANA Embedded TM and S/4HANA Embedded
BPC
Restructuring of Profit Centres
PS Costing restructuring
TYPES OF DEPLOYMENT OF SAP S/4HANA
SAP ECC
Generic Comparison
Conversion using SUM, DMO Tools Migration using SLT Service from SAP Brownfield Migration
• Upgrade database using DMO • System Transformation using SAP’s • Approach of brownfield or Greenfield
• Upgrade application using SUM Landscape transformation services implementation
• No change in business process or • Can convert multiple system • Modeling of system and processes as
business models Landscape to S4H based Landscape per S4H
• Adoption of Existing systems • Can be used for phase wise part by part • Use of new business models
• Suitable for Organizations not looking conversion • Use of new business processes with
to disrupt business users and functions • Expensive approach advanced applications replacing old
• Lot of uncertainty as existing Data • Need SAP or SAP approved expertise in one
models are changed ,many SLT • Customization only for gaps against
functionalities are retired • Utilization of Full potential of S4H will S4H processes
• Changes to existing configurations are take long time • Conversion of Data to S$H enabled
not possible as this is a technical • Will require big governance or • Historical data to remain in old model
conversion activity Architecture team to take care of end and systems
• As is process is created without custom to end transformation • Additional efforts in reporting
code upgrade in S/4HANA from ECC • Additional landscape maintenance
efforts for historical and archived data
• Not suitable for customers using
industry solutions where functionality
is yet to be released
Index Observation Possible in Possible only with Remarks
System Brownfield
conversion Migration Approach