Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

OwnerKUTANI-ext, Karunakar 
Stakeholders


Issue

The current Syensqo CRM architecture is comprised of multiple instances of the salesforce.com application requires a robust CRM system to support its sales lifecycle and currently relies on multiple customized instances of Salesforce (Core CRM and ICareICARe). This includes various integrations with These instances are integrated with various backend systems (PRS, ICare- PF1, Core- WP1) and pointed point solutions (Pardot, Dynasys, Gensuite, Qualtrics, Qliksense, etc.,), which are currently generating some challenges with data consistency, scalability, efficiency, and integration.Furthermore, the current digital customer journey architecture, is reliant . However, the existing architecture, built on a heavily customized Salesforce environment , with numerous bespoke interfaces, and disparate technologies. This is currently impeding Syensqo's ability to deliver a seamless and personalized customer experience, thereby hindering business growth and competitiveness.

Core CRM interface provider.pdf

Core CRM interfaces consumer.pdf

Recommendation

It is recommended that Syensqo transition from the Salesforce.com application to SAP CX, leveraging its comprehensive customer engagement platform to unify marketing, sales, and customer service efforts. With SAP CX, Syensqo can harness advanced capabilities such as AI-powered customer insights, real-time personalization, and seamless omnichannel engagement to deliver exceptional customer experiences.

Additionally, SAP CX's integrated suite and native connectivity with S4 HANA will streamline data management with the intention to lower the Total Cost of Ownership (TCO) and drive sustained growth and success. By adopting SAP CX, Syensqo can create a cohesive and efficient customer engagement strategy, building strong relationships and long-term success.

Background & Context

Syensqo's current customer relationship management (CRM) processes are supported by a complex architecture involving multiple applications, including two Salesforce instances, On-Premises and Cloud applications, and various manual and system interfaces. The various functions implemented, and their current challenges are detailed below.

  • The management of Customer Master Data is marked by diverse creation and onboarding processes for corporate groups and customers, which are dispersed across multiple teams, including the transformation centre, data operations teams, and service teams. These processes employ custom interfaces that lack real-time synchronization, relying on manual intervention at every stage, leading to inefficiencies and potential data inconsistencies.
  • Although lead and opportunity lifecycles follow established sales cycles, custom logic is applied for lead scoring, lead assignments, revenue projections, and realized net sales tracking, relying on manual data entry, which can lead to inefficiencies and potential errors.
  • The pricing process is a complex, multi-platform system with varying GBU adoption. It integrates SAP ECC historical data and Dynasys forecasts into BW, generating Integrated Contribution Margin (ICM) insights, Customer Product Combination (CPC) price recommendations, and Contribution Margin improvements via Dataiku. The process involves custom objects for reviewing, committing, and custom interfaces for replicating prices to backend SAP.
  • OneQuote is a custom application that manages the quotation process, including creation, product configuration, pricing, approvals, and customer communications, although it has not been adopted by all Global Business Units (GBUs). Quotation validity dates and price validity dates differ, with the latter having a longer horizon to minimize the impact of policy changes on customer orders. While OneQuotes themselves are not replicated to ECC, their price conditions are replicated, and open orders are adjusted manually during policy revisions.

Composites GBU uses the ECC Quotation process, which differs from OneQuote due to material group level differences. The outputs of OneQuote and ECC Quote vary significantly in detail and format across GBUs. For forecasting, quotes from both systems integrate with Dynasys, and quote reporting is done in Celonis (Composites) and Cliksense (TS and Novecare).

  • Complaints, whether linked to sales orders or not, follow a guided process: registration, investigation, commercial response, customer communication, and closure. The process integrates with Gensuite for root cause analysis and resolution, and Qualtrics for customer feedback. However, quality inspections, returns handling, and credit memos are not linked back to the complaint. Custom functions facilitate acknowledgments and communications between internal and external teams, improvements are needed to connect all related processes.
  • Sample management and tracking is a complex process that requires enhancement. Currently, some GBUs have an interface integrating Salesforce, SAP, and CMC (third-party sample provider) for automated sample transmission and information sharing. This interface needs to be replicated across all GBUs using CMC services for compliance purposes. The sample order process involves manual screening, resulting in inefficiencies. Commercial samples management is entirely manual, relying on emails for inventory management, material records, and transactions. This leads to significant communication challenges and wastes time. A standardized approach is essential for capturing orders, communicating with production and R&I, and managing outbound logistics to end customers (both billable and non-billable).

Given the complexities and challenges identified in Syensqo's current CRM processes, including multiple applications, custom interfaces, and manual intervention, it is clear that a transformation is necessary. This KDD aims to explore potential solutions that will integrate and standardize CRM processes, providing a single customer view, efficient workflows, and automated processes, leading to improved efficiency, accuracy, and customer satisfaction.

Assumptions

SAP S4/HANA will be the ERP (Enterprise Resource Planning) application that will enable the management and execution of customer records, sales contracts, sales orders, logistics, warehousing, transportation, billing and rebates. The recommended solution must integrate with S4/HANA to ensure seamless business process execution and master data integrity.

Orders generated from the Additive Manufacturing webshop and Small Customer Webshop account for only 4% of total orders for 2023. We understand that there are on-going discussions to put the AM webshop on hold by year-end, hence a comprehensive analysis has not been done on these two webshops.

Convergence solution built on Salesforce is evaluated in a separate KDD

Constraints

No constraints identified; further updates may be determined during detailed design phase. 

Impacts

  • Data Mapping: Mapping data fields from Salesforce to SAP accurately to ensure all critical data is transferred correctly.
  • Custom Development: Existing developments in Salesforce need to be reviewed and potentially deploy/enhance standard features in SAP
  • Interface Redesign: Existing interfaces between Salesforce and other systems may need to be redesigned to work with SAP
  • Training Programs: Implementing comprehensive training programs for users to ensure they are proficient with SAP

Business Rules

There are currently no known rules identified, but we will revisit and update if any emerge during the detailed design phase

is creating challenges related to process and data consistency, scalability, and integration complexity.

These inefficiencies are hindering Syensqo’s ability to deliver a seamless and consistent customer experience, while also misaligning with the company’s strategic goals of simplification, agility, and innovation. 

There are 3 KDDs in the CRM space.

  • KDD040 - CRM Platform Approach was created to determine if a single instance, greenfield approach is required for the CRM platform
  • KDD061 - Sales Contract Authoring was created to understand how the contract authoring will be executed
  • This KDD "CRM Platform" was created to determine which CRM tool/platform will be used.


Recommendation

Aligning with KDD040's recommendation of "Greenfield CRM implementation with Single Instance for all GBUs", we propose implementing Salesforce as the single-instance CRM and CX solution for all GBUs, to deliver a seamless customer experience, efficient processes, and consistent data management through a unified platform.

Highlights of the recommended Option B - Implement Salesforce and integrating Salesforce CRM capabilities with SAP S/4HANA

  1. Incumbent Advantage: Salesforce is the incumbent solution and the associated business familiarity, operational excellence skills and IT experience are already aligned with this platform.
  2. Change Impact of Alternative Solutions: The alternative solution of the SAP CX platform has a very different UX and functional flow.
  3. Change Management Risk: The change management impact of moving away from Salesforce  would be very high and the risk profile would also be very high. The unique UX and functional flow of the SAP CX would necessitate major process overhauls and retraining efforts.
  4. Best of Breed: The consensus from independently market analysts is that the Salesforce CRM platform is better than the SAP offering (and likely the best in the market)
  5. Enhanced SAP S/4HANA Integration:  Salesforce's native integration with SAP S/4HANA has undergone significant enhancements over time, providing a more efficient connection. To fully leverage this standard integration, existing custom interfaces will be removed or adjusted to align with standard offerings supporting a more streamlined data exchange and optimized business processes integration.
  6. Native Integration with Icertis: The Icertis contract authoring platform integrates effortlessly with Salesforce, providing a streamlined and embedded connection. This integration leverages the full potential of both solutions, enhancing contract management efficiency, accuracy, and visibility. (see KDD061 - Sales Contract Authoring )
  7. Functional Coverage:  Synesqo's functional requirements are thoroughly met by Salesforce's extensive capabilities. SAP CX has no functional capabilities over and above the capabilities of Salesforce. That is, Salesforce has all the functional requirements that Syensqo needs.

Resolution

CRM system next step - decision.pdf


Background & Context

Syensqo's current customer relationship management (CRM) processes are supported by a complex architecture that involves multiple applications, including two Salesforce instances, On-Premises and Cloud applications, and various manual and automated system interfaces. The various functions implemented, along with their current challenges, are detailed below in the following exports from the LeanIX enterprise architecture tool: Core CRM interface provider.pdf and Core CRM interfaces consumer.pdf

  • The management of Customer Master Data is characterized by diverse creation and onboarding processes for corporate groups and customers, which are dispersed across multiple teams, including the transformation centre, data operations teams, and service teams. These processes utilize custom interfaces resulting in inefficiencies and potential data inconsistencies.
  • Although lead and opportunity lifecycles follow established sales cycles, custom logic is applied for lead scoring, lead assignments, revenue projections, and realized net sales tracking.
  • The pricing process is a complex, multi-platform system with varying GBU adoption. It integrates SAP ECC historical data and Dynasys forecasts into BW, generating Integrated Contribution Margin (ICM) insights, Customer Product Combination (CPC) price recommendations, and Contribution Margin improvements via Dataiku. This process utilizes custom objects for reviewing and committing, as well as custom interfaces for replicating prices to backend SAP.
  • OneQuote is a custom application that manages the quotation process, including creation, product configuration, pricing, approvals, and customer communications. However, it has not been adopted by all Global Business Units (GBUs). Quotation validity dates and price validity dates differ; the latter has a longer horizon to minimize the impact of policy changes on customer orders. OneQuote data is not replicated to ECC, its price conditions are replicated, and open orders are adjusted manually during price policy revisions.
  • The Composites GBU uses the ECC Quotation process, which differs from OneQuote due to material group level differences. The outputs of OneQuote and ECC Quote vary significantly in detail and format across GBUs. For forecasting purposes, quotes from both systems are integrated with Dynasys, but quote reporting is done in different tools.
  • Complaints follow a guided process that includes registration, investigation, commercial response, customer communication, and closure. This process integrates with Gensuite for root cause analysis and resolution, as well as Qualtrics for customer feedback. However, quality inspections, returns handling, and credit memos are not linked back to the complaint. Custom functions facilitate acknowledgments and communications between internal and external teams, and to connect all related processes.
  • Sample management and tracking is a complex process, with some GBUs having an interface that integrates Salesforce, SAP, and CMC (a third-party sample provider) for automated sample transmission and information sharing. However, this interface needs to be replicated across all GBUs using CMC services for compliance purposes. The sample order process involves manual screening, which results in inefficiencies. Moreover, commercial samples management is entirely manual, relying on emails for inventory management, material records, and transactions, leading to significant communication challenges. A standardized approach is essential for capturing orders, communicating with production and R&I, and managing outbound logistics to end customers (both billable and non-billable).

Given the complexities and challenges identified in Syensqo's current CRM processes - including multiple applications, custom interfaces, and manual intervention - it is clear that a transformation is necessary. This KDD aims to explore potential solutions that will standardize CRM processes, providing a single customer view, efficient workflows, and automated processes. This will lead to improved efficiency, accuracy, and customer satisfaction.


Assumptions

  • SAP S/4HANA will serve as the ERP (Enterprise Resource Planning) application for managing and executing customer records, sales contracts, sales orders, logistics, warehousing, transportation, billing, and rebates.
  • Orders generated globally from ecommerce solutions (Salesforce + SAP) represent only 4% of total orders for 2023 (excluding Esker and Elemica).
  • Salesforce also features a custom solution called Convergence, tailored for vendor management and procurement processes. As this capability is not customer-facing, it is addressed in KDD002 - Procurement Contract Lifecycle Management
  • KDD052 - Sales Pricing Process focuses on pricing strategy, optimization, approval processes, and execution.


Constraints

No constraints identified; further updates may be determined during detailed design phase. 


Impacts

  • Data Mapping: Mapping data fields from Salesforce to SAP accurately to ensure all critical data is transferred correctly.
  • Custom Development: Existing developments in Salesforce need to be reviewed and potentially deploy/enhance standard features in SAP.
  • Interface Redesign: Existing interfaces between Salesforce and other systems may need to be redesigned to work with SAP.
  • Training Programs: Implementing comprehensive training programs for users.


Business Rules

There are currently no known rules identified, but we will revisit and update if any emerge during the detailed design phase.


Options considered

Option A - Transition from Salesforce to SAP CX and integrate with SAP S/4HANA

Objective: This option utilizes a comprehensive SAP solution, encompassing the full SAP stack(i.e., SAP Sales and Service Cloud V2 & S/4HANA), to empower and streamline business processes. The primary benefit of this approach is that it leverages native/standard integration across all SAP products, thereby eliminating the need for duplicate data entry, ensuring alignment of enterprise structure and master data, and providing end-to-end traceability and transparency from 'Lead to Cash'.

Approach:

  • The integrated master data management of SAP CX and S/4HANA creates a unified customer platform, delivering a seamless experience through real-time data replication, tailored corporate group management, and GBU segmentation, as well as team assignments, centralized organization management, and enhanced security.
  • The Lead and Opportunity lifecycles are streamlined with guided selling processes and real-time customer insights, providing a unified lead-to-cash cycle. This streamlined approach enables accurate sales revenue tracking and forecasting without the need for multiple system integrations. Moreover, machine learning-based lead intelligence and customer and relationship insights help identify high-quality leads and predict conversion likelihood.
  • SAP CX streamlines the quotation process, encompassing guided selling, quotation configuration, pricing, and discounting, as well as

Options considered

Option A - Transition from Salesforce to SAP CX and integrate with S4 HANA

Leverages a full SAP solution to enable the business processes. The key advantage of this solution is the use of standard integration across all SAP products. This reduces the need for double-data entry, misalignment of enterprise structure and master data and streamlines the business processes providing a full traceability and transparency from “Lead to Cash”.

  • The integrated master data management of SAP CX and S4/HANA creates a unified customer platform, delivering a seamless experience through real-time data replication, tailored corporate group management and GBU segmentation, team assignments, centralized organization management, and enhanced security.
  • The Lead and Opportunity lifecycles are streamlined with guided procedures, automatic team assignments, and integration for revenue projections and realised sales. This enables a unified lead-to-cash cycle, allowing for accurate sales revenue tracking and forecasting without the need for multiple system integrations. Additionally, AI-based lead scoring uses machine learning to analyse customer data, predicting conversion likelihood and enabling businesses to identify high-quality leads.
  • The pricing solution offers analytics capabilities to support informed pricing decisions, including pricing analysis for customer-product combinations, manufacturing cost analysis, pricing trend identification, order book comparison, blocked order detection, and financial indicator comparison. It also provides sales, volume, cost, and margin evolution analysis, active contract and flexibility metric display, and enables business users to access and maintain pricing information in S/4 for accurate quoting, driving revenue growth and profitability.
  • SAP CX streamlines the quotation process, including guided selling, quotation configuration, pricing and discounting, approval workflows, customer-specific pricing, quote validity, and quote versioning. By integrating with S4 HANA, businesses S/4HANA, sales quotations can access real-time data, automate data synchronization, and simplify order-to-cash processing.  Ultimately, this seamless integration This integration ultimately provides a single source of truth for customer, product, and pricing data, increasing efficiency and accuracy in throughout the quotation-to-cash process.
  • Contract Management provides a centralized repository for storing and managing contracts, automated workflows for approval and notification processes, and real-time tracking of contract validity periods, product information, and pricing.  Additionally, S4 HANA Additionally, S/4HANA provides advanced analytics and reporting capabilities, enabling real-time insights into contract performance and enabling supporting data-driven decision making.
  • The complaint management streamlines the process is streamlined by integrating it with sales orders, quality inspections, returns handling, and credit memos. The guided process covers automates registration, investigation, commercial response, and tracking, as well as customer communication , and closure, with automation of acknowledgments and communications between teams. Additionally, SAP CX and S4 HANA S/4HANA integrate with Qualtrics for customer feedback, providing a closed-loop process. Machine learning enhances case resolution with features of similar case matching, automated summaries, categorization, email translation, and sentiment analysis. 
  • Sales order management standardize standardizes and automate automates the sample order process, eliminating manual screening and inefficiencies. S4 HANAS/4HANA's inventory management and logistics capabilities will efficiently manage outbound logistics to for end customers /and distributors.

The diagrams below outline the business processes that will be supported by Option A. Option A - E2E Lead to Cash - Market to Order and Manage Customers & Channels.pdf

Current ApplicationFunctional CapabilityTo be ApplicationPardotSoftware to manage marketing programs including occasional emails, distribution of educational and promotional content. SAP CXDataikuOptimization tool to propose price recommendations based on historical and forecast data for each Customer Product Combination (CPC), incorporating forward-looking ICM capabilities. Additionally, it functions as a lead assignment and scoring toolS4/HANA for
SAP CX for Lead scoring and assignmentsDynasysSales Forecasting & Demand Planning tool, where monthly volumes (in kg) are calculated in the datahub based on the 1st target delivery date and the annual volumes entered in CRM (received in the CRM file)KinaxisPricing Data LakePricing datalake is a pilot use case within the wider plan of Syensqo's Data Ocean architecture. Pricing data lake hosts the data required for price transparency, setting, optimization and execution.SAP AnalyticsQlikSenseQlik Sense is a complete data analytics solution where Customer 360, Pricing Transparency, Opportunity and Contract dashboards are built.SAP Analytics cloudGensuiteApplication used for root cause analysis and taking corrective and preventive actions. S4 HANAMappyMappy analyse GBU's sales and with help of artificial intelligence (AI), based on existing mappings, it suggests new mappings for not mapped data.SAP CX & S4 HANAWP1/PF1Operational & Transactional systemsS4 HANACollaborate & ConnectSpeciality Polymers (SpP) Portal for distributors to track orders, product search, request samples and download technical documents. Retain and connect to CXMSP(MySyensqoPortal)NovaCare (NC) Portal for authorized distributors to access product catalogues, request samples, download technical/marketing documents and raise complaintsRetain and connect to CXQualtricsIt’s a Survey Platform to construct surveys, distribute them to respondents, and report on the results.Qualtrics is SAP product and natively integrated with SAP CXAODocsAODocs  is a document management system that integrates with Google Drive and provides central ownership of documentsRetain and integrate with SAP CX

 Option B - Harmonize Salesforce by removing non-CRM features and integrating CRM capabilities with S4 HANA

Leverage Salesforce for CRM and migrate non-CRM functions to S4 HANA, consolidating core ERP functions. Integrate Salesforce and S4 HANA for seamless process and data integration, enabling end-to-end business process execution and a unified view.

Key enhancements:

  • Streamline processes by retaining Prospect creation and Customer conversion in Salesforce, eliminating PRS, and integrating with S4 HANA for real-time data replication.
  • Align GBU segmentation with S4 HANA's organization structure and map team assignments to S4 HANA's business partner concepts.
  • Continue using Salesforce for lead and opportunity management, and revenue projection maintenance, while leveraging S4 HANA for opportunity dashboards, forecasting, and realized sales/revenue data.
  • Implement Price Transparency dashboards in S4 HANA for sales revenue, price analysis, forward costing, and contract information.
  • Maintain integration with Dataiku for price optimizations and migrate sales price setting to S4 HANA.
  • S4 HANA will provide pricing information for Onequote, ensuring accuracy and consistency.
  • Centrally manage contracts in S4 HANA, simplifying processes and reducing errors.
  • Integrate Salesforce with S4 HANA for case management, quality notifications, and corrective actions.
  • Track feedback in Qualtrics, with reporting in both Salesforce and S4 HANA.
  • Manage samples in Salesforce, integrating with S4 HANA for logistics and fulfilment.

The diagrams below outline the business processes that will be supported by Option B. Option B - E2E Lead to Cash - Market to Order and Manage Customers & Channels.pdf

Option C - Maintain Salesforce in its current state and integrate it with S4 HANA

Retain Salesforce, its custom solutions, and third-party application integrations in their current state, while establishing integration with S4 HANA. Continue using S4 HANA as a logistics execution tool, and redesign existing ECC interfaces to connect with S4 HANA, incorporating necessary modifications.

  • Retain Salesforce for Prospect and Customer conversion and maintain PRS as the central system for corporate master data management, integrating with S4 HANA for data synchronizations. Align GBU segmentation with S4 HANA's organization structure, map team assignments, and retain data governance tools like Mappy and Gridbuddy.

  • Utilize Pardot for lead generation, and integrate with Salesforce for nurturing and conversion. Continue using Salesforce for opportunity management, revenue projections, and manual sales tracking using S4 HANA reports. However, leverage S4 HANA for opportunity dashboards and forecasting, providing a unified sales performance view.

  • Implement Price Transparency dashboards in S4 HANA for sales revenue, price analysis, and forward costing, integrating with Dataiku for price optimization. Continue using Salesforce for sales price setting and execution, replicating accepted quotations to S4 HANA for pricing determinations. Update document flow from S4 HANA to Salesforce for Quote to Cash integration.

  • Salesforce will remain the contract management hub, integrating contract data with S4 HANA and reporting tools for comprehensive contract and customer 360 dashboards. Salesforce will handle case management and approvals, while Gensuite tracks corrective and preventive actions. Integrate Salesforce cases with S4 HANA for commercial responses and returns, and manage returns and replacements in S4 HANA, syncing updates back to Salesforce. Feedback tracking will remain in Qualtrics, with reporting visible in both Salesforce and S4 HANA.

  • Salesforce will manage and approve samples, integrating with S4 HANA for logistics and fulfillment. Third-party integrations will remain in Salesforce, with S4 HANA updates flowing in for tracking and monitoring purposes.

The diagrams below outline the business processes that will be supported by Option C. Option C - E2E Lead to Cash - Market to Order and Manage Customers & Channels.pdf.pdf

Evaluation

Option A - Transition from Salesforce to SAP CX and integrate with S4 HANA

Option B - Harmonize Salesforce by removing non-CRM features and integrating CRM capabilities with S4 HANA
Option C - Maintain Salesforce in its current state and integrate it with S4 HANA
Functional Capability

(plus) SAP option is richer in functionality.

(plus) Salesforce has better ease of use.

(plus) Salesforce has better ease of use.

Alignment with "Simplification principle"

(plus) SAP roadmap includes additional standard integration between the SAP applications. 

(minus) The Salesforce option requires a higher number of custom developments due to the complexity of integrating S4/HANA and Salesforce.

(minus) The number of custom developments is significantly higher in the Salesforce option due to complex integration between S4/HANA and Salesforce.

Native Integration with S4/ HANA

(plus) Standard integration is now available to support Syensqo's business process.

(minus) Salesforce and S4/HANA integration would have to be custom developed regardless.

(minus) Salesforce and S4/HANA integration would have to be custom developed regardless.

Implementation Cost

(minus) Change Management and Training costs are higher in SAP, since Salesforce is already in place in most regions.

(plus) Build on the current Salesforce investment, and only the interfaces that need updating or replacing will be impacted, minimizing disruption.

(minus) Salesforce and S4/HANA integration would have to be custom developed regardless.

License Cost

(plus) Offers an opportunity to lower license 
costs due to Syensqo's Strategy “SAP First”.

(plus) Yet to be confirmed.

(plus) Yet to be confirmed.

Infrastructure Cost

(plus) Equally the same, as both leverage a combination of S4/HANA and Cloud applications. 

(plus) Equally the same, as both leverage a combination of S4/HANA and Cloud applications. 

(plus) Equally the same, as both leverage a combination of S4/HANA and Cloud applications. 

Maintenance Cost

(plus) Leveraging pre-built integration content and unified support structures provided by SAP significantly reduces maintenance cost.

(plus) Only the interfaces directly integrated with S4/HANA require updates, while the remaining integrations within the Salesforce ecosystem will remain unaffected and continue to function as usual

(minus) Higher in Salesforce due to large number of interfaces between S4/HANA and Salesforce. Any updates or changes in one system may necessitate adjustments in the integration setup.

Upgrades

(plus) Upgrades are typically rolled out automatically, with SAP ensuring backward compatibility and minimal disruption.

(minus) Coordinating upgrades and ensuring compatibility between the two systems can be challenging and time-consuming.

(minus) Coordinating upgrades and ensuring compatibility between the two systems can be challenging and time-consuming.

See also

Image Removed


Option B - Implement Salesforce and integrating Salesforce CRM capabilities with SAP S/4HANA

Objective: This option utilizes Salesforce's CRM platform and capabilities to consolidate the current multi-tenant landscape into a unified Salesforce environment, in line with KDD040's recommendation for a "Greenfield CRM implementation with a Single Instance for all GBUs." Additionally, any non-CRM functions that can be transitioned to S/4HANA will be migrated to streamline core CRM functions. This approach will necessitate integration between Salesforce and S/4HANA to facilitate an efficient Lead to Cash execution process and enhance end-to-end business process execution and reporting capabilities.

Approach:

  • Streamline master data processes by retaining Prospect creation and Customer conversion in Salesforce, eliminating PRS, and integrating Salesforce with S/4HANA for real-time data replication. Align GBU segmentation with S/4HANA's organizational structure and map team assignments to S/4HANA's business partner concepts, reducing interfaces and enhancing efficiency.

  • Continue using Salesforce for lead and opportunity management, and revenue projection maintenance. However, leverage S/4HANA data for forecasting and realized sales/revenue data, ensuring an accurate view of sales performance.

  • Price setting will continue in Salesforce, integrated with Dataiku for price optimizations. Salesforce will remain the platform for price execution via quotation creation. Once quotations are released, prices will be replicated to S/4HANA. Furthermore, Salesforce quotations will be replicated to S/4HANA to ensure end-to-end Quote-to-Cash process integration. To enhance visibility, Price Transparency dashboards will be implemented using S/4HANA data, covering sales revenue, prices, forward costing, orders, and contract information.

  • Operational Contract management will be centralized in S/4HANA, simplifying processes, reducing errors, and boosting efficiency. S/4HANA will serve as the single source of truth, providing accurate and visible data for informed decision-making. The contract dashboard and KPIs will be driven by S/4HANA data, offering real-time insights and performance metrics. Additionally, necessary metadata required for contract database management will be replicated from S/4HANA to Salesforce.

  • Salesforce will handle case management and approvals, integrating with S/4HANA for quality notifications and corrective actions. S/4HANA will manage investigation outcomes, including returns and settlements, and update Salesforce cases for tracking. Feedback tracking will remain in Qualtrics, with reporting in both Salesforce and S/4HANA for a unified view.

  • Salesforce manages and approves samples, then integrates with S/4HANA for logistics and fulfilment. Third-party integrations remain in Salesforce, with S/4HANA updates flowing in for tracking and monitoring purposes.


Evaluation


Option A - Transition from Salesforce to SAP CX and integrate with SAP S/4HANA

Option B - Implement Salesforce and integrating Salesforce CRM capabilities with SAP S/4HANA
Best of Breed

(minus) Robust alternative with SAP integration, but lagging in innovation and breadth.

(plus) Best-of-breed CRM leader in innovation and have robust ecosystem.

Product Maturity

(minus) SAP CX V2, is a relatively new and untested player in the CRM market. SAP CX V2 is still in the process of building its reputation and demonstrating its capabilities to deliver successful outcomes.

(plus) Salesforce is a mature and well-established Customer Relationship Management (CRM) platform, with an impressive track record of successful implementations for over a decade. 

Alignment with "Simplification principle"

(plus) Moving to SAP CX aligns with simplification, as it unifies processes across SAP platforms, streamlining the technology landscape.

(plus) Single Instance model using standard processes and integration.

(minus) Unifying multiple instances will simplify the landscape; however, the process simplification could present challenges, as the underlying data structures, workflows, and data models are unique to each application.

Alignment with "Standardization principle"

(plus) Full alignment with SAP S/4HANA, providing standardized processes across the GBU's through a unified platform.

(minus) Salesforce can be standardized to an extent, but the bespoke developments around Pricing and OneQuote solutions have intricate dependencies and customizations that may challenge full standardization.

System Integration

(plus) High integration with SAP S/4HANA due to integration content being provided by SAP.

(plus) Salesforce's native integration with SAP S/4HANA has undergone significant enhancements over time, providing an improved and more efficient connection.

Implementation Time

(minus) Transitioning to SAP CX and integrating it with SAP S/4HANA will take time, including data migration, system setup, and full alignment with business processes.

(plus) Harmonizing Salesforce and integrating it with SAP S/4HANA will require less time than a complete system change.

User Training & Change Management

(minus) Significant training and change management required to transition to SAP CX and adapt to new processes.

(plus) Users need to adjust to the streamlined Salesforce system, but they are already familiar with the platform.

Cost of Implementation

(minus) Transitioning to SAP CX and deep integration with SAP S/4HANA involves substantial costs (licenses, migration, customization, etc.).

(plus) Lower than the costs of a full transition, including system optimization and integration efforts.

Long-term Scalability

(plus) SAP CX offers excellent scalability, especially when integrated with SAP S/4HANA, allowing for growth in users, data, and complex workflows.

(minus) Salesforce can scale, but integration with SAP S/4HANA may present some limits as complexity grows.

Customization Flexibility

(minus) Customizing SAP CX can be more complex compared to Salesforce. Though it provides extensive flexibility, customizing it requires specific SAP expertise and can take more time due to its tight integration with SAP S4HANA and alignment with enterprise-wide processes.

(plus) Salesforce is highly customizable, offering flexibility to align with evolving business needs and complex workflows.

System Maintenance

(plus) Simplifies troubleshooting and maintenance as both SAP CX and S/4HANA are from same vendor. System updates and performance optimizations can be handled more cohesively. 

(plus) Harmonizing Salesforce reduces maintenance complexity with some effort to manage integration with SAP S/4HANA.

Risk of Disruption

(minus) Transitioning to a new system (SAP CX) poses a high risk of operational disruption during implementation.

(plus) Some disruption during the streamlining and integration process, but users remain on Salesforce, reducing the overall risk.

Customer Experience Impact

(minus) While it delivers a better end-to-end experience with deeper integration between CRM and S/4HANA the transition phase would affect customer service consistency.

(plus) Offers the best balance between optimizing the CRM experience and minimizing disruption, ensuring smoother transitions with a positive long-term impact on customer experience.


Change log

Change History
limit10

Change log

change-history


Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals