Transcription
S/4HANA Conversion with Integration to SAP Cloud for CustomerExperiences from SAP internal Validation ProjectBernd Fleddermann, SAPEduard Stelle, SAPSeptember 2018PUBLICV1.0
Bernd FleddermannC/4HANA Expert ServiceGlobal DeliverySAP SEDietmar-Hopp-Allee 1669190 Walldorf, GermanyEduard StelleC/4HANA Expert ServiceGlobal DeliverySAP SEDietmar-Hopp-Allee 1669190 Walldorf, Germany 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC2
Agenda Introduction and Overview on S/4HANA Conversion Project The conversion phases and the relevant conversion steps Final Assessment and major Differences 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC3
Introduction and Overview on S/4HANA Conversion Project
S/4 Conversion ProjectSAP Validation requested the C4C Expert Service team to runa conversion of an SAP ERP system to S/4HANA integratedwith SAP Cloud for Customer Project Start February 2018 Technical and functional checks with main focus on SAP Cloud forCustomer integration Create a task list and process description Experts from SAP ERP and S/4HANA performed the technicaltransformation steps in the on-premise system 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC5
ConsiderationsThe conversion project was conducted on an SAP internal testlandscape with a predefined functional and integration scope The required steps and processes in a customer specificenvironment may vary from the described processes and requiresdedicated and individual planning and test Future developments might impact the conversion activities asdescribed This presentation focuses on the SAP Cloud for Customerintegration and their relevant activities. The setup on the SAP ERP,S/4HANA side requires also extensive activities described indedicated guidelines To plan and perform the conversion activities in a productivecustomer environment it is recommended to get support from SAPERP, S/4HANA (conversion) experts and SAP Cloud for Customerexpert service 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC6
S/4HANA Conversion with Cloud for Customer Integration – Scope OverviewMaster Data ViewSAP Hybris Cloud for CustomerCurrencyconv. ratesSales al ountHierarchyRegisteredProductVan asuringPointERP or S/4HANA OPCurrencyconv. ratesSales stomerMaterial InfoVan . ntMeasuringPointAccounts/Prospect Standard prospect block in Cloud for Customer (through scoping option) Prospect scenario: link ERP customer to former Cloud for Customer prospect Segment filter to filter out specific sales organization from account data Filter BAdI in ERP to filter out customer with customer Name “DoNotReplicate”Blue boxes/arrows are the scopeused for the Conversion projectBasis of the diagram isthe standard scope ofC4C-ERP integration Integration of ERP Cockpit Mashup Extension in the account record on both sides 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC7
S/4HANA Conversion with Cloud for Customer Integration – Scope OverviewTransaction ScenariosSAP Hybris Cloud for CustomerOpportunityOnlinePricing fornet valueOnlinePricing withATPBlue boxes/arrows are the scopeused for the Conversion projectOnlinePricing withATP & CreditLimit CheckServiceContractSalesQuoteSalesOrderBasis of the diagram isthe standard scope ofC4C-ERP integrationWork TicketTimeReportCreate follow-up BusinessTransaction DocumentERP or S/4HANA OPInternal Order / Reference to omerInvoiceBilling RequestTime Sheet(CATS)OpportunitySales OrderContract Opportunity Pricing Bi-Directional Replication Bi-Directional Replication Follow up Quote External Pricing External Pricing Follow up Attachment Order Attachment Document Flow Document Flow Print Preview Print Preview 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Sales Order ExtensionInvoiceRevenueGoods Issues from Technical StockServiceFacadeAdv. ShipmentCostGoods IssueCostCostTimesheet (CATS)SalesOrderPurchaseRequisitionPurchaseOrder8
S/4HANA Conversion with Cloud for Customer Integration – Scope DetailsMaster Data View – major differencesMajor integration differences btw. SAP ERP and C/4Hana IDOC based Integration with SAP ERP customers is substituted by SOAP based Business Partner Integration Different Integration Framework in S/4HANA (e.g. to replace customer filter BAdIs) Different iFlows in the MiddlewareBlue boxes/arrows are thescope used for the Conversionproject No ERP Cockpit available in S/4HANA ID Mapping for Business Partner and customer in C4C in parallel 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICRed boxes/arrows are usedto mark differences betweenERP and S4 integration9
The conversion phases and the relevant conversion steps
Customer Vendor Integration (CVI)IMPLEMENTATION SCENARIOSProcess Scenarios in S/4HANABP uploadMigration CockpitData S/4 HANABPCVISynchronizationCVI ConfigurationS/4 sECC toS/4HANAConversionHandover fromPreparationSelect 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICCustomersVendorsContacts(KN*, nConversionCustomersVendorsContacts(KN*, LF*)Post Processing / Test11
S/4HANA Conversion with Cloud for Customer IntegrationSystem SetupRecommendationRun complete transformation on a test landscapefully copied from production Documentation of conversion steps effort and duration (especially downtimes) corrective measures to plan and schedule productive transformation Adjust BAdIs and iFlows where necessary SAP Cloud for Customer Release 1802 Test of adjusted artifacts SAP Cloud Platform Integration Import adjusted and tested artifacts from Test toProd Integration Packages SAP Hybris Cloud for Customer Integration with SAPERP – Version 1711 SAP Hybris Cloud for Customer Integration with SAPS/4HANA – Version 1802 SAP ERP SAP S/4HANA OnPremise 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC12
S/4HANA Conversion with Cloud for Customer IntegrationProcess OverviewHandover fromPreparationSelectSynchronizationConversion (S/4)Set upS/4 CAsSetup Scoping & BADIs for S/4 Hana Integr.C4C up with limitationsERPCAsClean Message Queues(if relevant)C4CCPIOutboundmessagesnot processedTest boundmessagesERPMappingContentPost Processing / TestCleanQueuesS/4CAsC4C Biz.DowntimeNo MessageExchangeImport iFlows fromTest (in Prod)Setup ID Mappingfor Biz PartnerS/4MappingContentSetup S/4iFlows (in Test)CleanQueuesClean Message Queues(if relevant)ERP techn.DowntimeS/4 Biz. DowntimeSetup C4CIntegrationInitial Load ofBizPartnerERPAPIsERP S/4ERP Biz Downtimerecommended-CVI enhancementsCVI Configuration- Activate BizFunction- Define Number assgmnt.- Check CustomizingERP 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICSynchronizationCockpitCompletion Check- Pre-Check- SUMActivateBP- Cust/VendorTest allIntegrationScenariosS/4APIsTestS/4HANA13
S/4HANA Conversion with Cloudfor Customer IntegrationSAP ERP Up and running Primarily configuration of Customer VendorIntegration (CVI) module incl. numberassignmentPreparation PhaseC4C Up and running Check number of unprocessed message atleast in the productive system and startmessage clarification (in case of large numberof unprocessed messages) 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Plan and prepare the SAP ERP & S/4HANA conversionsteps along the guidelines Test System: Document effort, duration and issues to planand schedule productive conversion14
S/4HANA Conversion with Cloudfor Customer IntegrationSAP ERP Downtime recommended synchronizing customers to business partnersthrough CVISynchronization PhaseC4C Up and running with limitations No processing of outbound messages to SAPERP. Unprocessed messages need to be restarted when SAP ERP is active againTest System Document effort, duration and issues to planand schedule productive conversion 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Plan and prepare the SAP ERP & S/4HANA conversionsteps along the guidelines Test System: Document effort, duration and issues to planand schedule productive conversion15
S/4HANA Conversion with Cloudfor Customer IntegrationSAP ERP Downtime required Resolving unprocessed messages Technical transformation of the SAP ERPsystem to S/4HANAC4C Business Downtime required Resolving all unprocessed messages Disconnect Biz Users and other sourcescausing messages to and from C4C Activate scoping and BADIs for S/4HANArelevant integration scenarios (for exampleprospect block) Setup S/4 Communication Arrangements(to catch up any potential message caused byhidden processed not deactivated before)Conversation Phase Plan and prepare the SAP ERP & S/4HANA conversionsteps along the guidelines Test System: Document effort, duration and issues to planand schedule productive conversionCPI (Prod Environment only) Import validated iFlows from Test Environment 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC16
S/4HANA Conversion with Cloudfor Customer IntegrationSAP S/4HANA Downtime required Activation of BP Customer/Vendersynchronization Setup C4C Integration Initiate Initial Load of Business Partner to C4C(after the integration scenarios had been reestablished)Post Processing PhaseCPI (Test Environment only) Setup S/4HANA iFlows and implementcustomer specific adjustments where relevantC4C Business Downtime required Receive Initial Load of Business Partner tobuild up new ID Mapping Plan and prepare the SAP ERP & S/4HANA conversionsteps along the guidelines Test System: Document effort, duration and issues to planand schedule productive conversionTest integration scenarios before reactivatingthe systems 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC17
S/4HANA Conversion with Cloud for Customer IntegrationReduced Cloud for Customer Downtime ApproachHandover fromPreparationSelectSynchronizationConversion (S/4)Set upS/4 CAsSetup Scoping & BADIs for S/4 Hana Integr.C4C up with limitationsERPCAsClean Message Queues(if relevant)C4CCPIOutboundmessagesnot processedPost Processing / TestTest wntimeC4C up withNo MessageExchangeERPMappingContentImportiFlows fromTest in ProdSetup ID Mappingfor Biz an Message Queues(if relevant)ERP techn.DowntimeS/4 Biz. DowntimeSetup C4CIntegrationInitial Load ofBizPartnerERPAPIsERP S/4ERP Biz Downtimerecommended-CVI enhancementsCVI Configuration- Activate BizFunction- Define Number assgmnt.- Check CustomizingERP 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICSynchronizationCockpitCompletion Check- Pre-Check- SUMActivateBP- Cust/VendorTest allIntegrationScenariosS/4APIsTestS/4HANA18
S/4HANA Conversion with Cloudfor Customer IntegrationCloud for Customer uptime possible with limitedfunctionality during conversion and postprocessing Set up S/4HANA CommunicationArrangements in C4C to log upcomingoutbound messages in the Message Monitor Outbound messages will not be processed No synchronous messages (e.g. externalpricing; document flow; fact sheets, etc.) Some transactional documents which requireconfirmations remains in read-only untilconfirmation message is received Logged messages need to be restarted onchronological order when the connectivity isback Changes on C4C business partner must be redone when connectivity is back (no messageprocessing possible) 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLICReduced C4C Downtime Plan and prepare the SAP ERP & S/4HANA conversionsteps along the guidelines Test System: Document effort, duration and issues to planand schedule productive conversion19
Conversion in Test vs. Productive EnvironmentTestSome integration artifacts (e.g. iFlows, BADIs, PDI logic)can be setup and tested in Test and imported to ProdProdDocument conversion stepsduring test conversionSome conversion phases in Prodshorter as the necessary steps aredocumented from test and artifactschanges copied over 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC20
Final Assessment and major Differences
Final Assessment The conversion project must carefully be planned with expertinvolvement (S/4HANA, CVI, C4C Integration) The total transformation time depends on different factors Know How Customer/Vendor/BP set up complexity (e.g. number ranges) Data volume Customer specific enhancements/extensions We recommend to run the conversion with a complete set ofproductive data and a productive like setup in a specific testenvironment (Sandbox) before Adjustments on integration artifacts (e.g. iFlows, BADIs) need tobe tested and imported from Test to Prod Conversion steps and durations need to be tested and loggedduring test and used to plan the productive conversion anddowntime management 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC22
Main Differences encounteredfrom Cloud for Customer Perspective Business Partner Model deviates from Customer/Vendor Model Numbering Replication Messages and message structure for BizPartner The integration with the new Business Partner leads to two external IDsfor accounts in Cloud for Customer which can be different Some UIs and reports show only one external ID In the Account/Contact UI a new facet can be added “Mapping forIntegration” to see all external IDs ERP cockpit no longer available in S/4HANA Need to be substituted by alternate S/HANA approaches (e.g.standard mashup available in C4C with 1808) Different Integration Framework in S/4HANA S/4HANA has differences in the supported integration scenarios. SAPnote 2293815 – “S/4HANA Enterprise Management: Information aboutIntegration Scenarios with SAP Cloud for Customer” lists the supportedscenarios. 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC23
LinksBlog post with further /Blog post as pdf -1d7d-0010-87a3-c30de2ffd8ff.htmlopenSAP course on System Conversion to SAP S/4HANAhttps://open.sap.com/courses/s4h11Blog on alternate mashup integration approached to substitute ERP Cockpit with S/4HANA Fiori -html/SAP S/4HANA Cookbook – Customer/Vendor Integration (further updates AP omer%20Vendor%20Integration.pdfConversion Guide for SAP S/4HANA /CONV OP1610.pdf 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC24
Thank you.Contact information:Bernd FleddermannC/4HANA Expert ServiceGlobal DeliverySAP SEDietmar-Hopp-Allee 1669190 Walldorf, Germany
ERP and S4 integration Major integration differences btw. SAP ERP and C/4Hana IDOC based Integration with SAP ERP customers is substituted by SOAP based Business Partner Integration Different Integration Framework in S/4HANA (e.g. to replace customer filter BAdIs) Different iFlows in the Middleware No ERP Cockpit available in S/4HANA
