Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Inside SAP Cloud ERP

Inside SAP Cloud ERP artwork

Episode 117: Connect44's Journey to SAP S/4HANA Cloud Public Edition: Part 1 – Starting the Transition from SAP Business ByDesign

Feb 12, 202518 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Learn from Connect44’s transition to SAP S/4HANA Cloud Public Edition, highlighting their strategic transformation journey in the telecommunications industry In this episode of Inside SAP S/4HANA Cloud, Yannick Peterschmitt explores the early stages of Connect44’s journey from SAP Business ByDesign to SAP S/4HANA Cloud Public Edition. The podcast features Xenopol Oprea, Product Manager at telecoms infrastructure provider Connect44, and Raphael Finck, CEO of SAP partner Snap International. They discuss the challenges, best practices, and experiences of the initial phases of this major project. Learn about the key considerations in selecting the right partner, the importance of a cloud mindset, and the role of SAP Digital Discovery Assessment in optimizing business processes. Tune in to hear how Connect44 is navigating this significant transition and the insights gained so far. And stay tuned for more episodes with Connect 44 and Snap in the future. What topic would you like us to discuss next? Send an email to insides4@sap.com. Show Notes: Download the transcript PDF Learn more about the transition from SAP Business ByDesign to SAP S/4HANA Cloud Public Edition: Unlock S/4HANA Cloud Public Edition: Why Key Users Are Crucial in Moving | SAP Community Check our enablement assets for SAP S/4HANA Cloud: https://chart-bdmaicr0au.dispatcher.eu2.hana.ondemand.com/index.html Visit the SAP S/4HANA Cloud Public Edition Community: https://pages.community.sap.com/topics/s4hana-cloud

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Welcome to the podcast Inside SAPS for HANA Cloud. There is no customer success without product success and project success. I'm Yanni Peter Schmidt from SCP, and I'm joined today by Sinapol Opera, the product manager from telecoms infrastructure provider Connect 44, and Rafael Fink from the SAP partner Snap. What is the story? Connect 44 decided to transition from SAP Business by Design to SAP SFANA Cloud Public Edition, having recently begun that project.

So we'll be creating a series of podcasts where they will be sharing the journey. And this is very exciting, the first episode. Welcome, guys. Welcome, Sena Paul. Welcome, Raphael. So the first question goes to Sena Paul and I will call you Sena as this is your nickname. Hi, Sena, can you please tell us a little more about Connect 44? Thank you. Connect 44 Group was founded in 2000 in Lutsen, Switzerland as a telecommunications consulting agency.

It has grown into one of Europe's largest independent managed services companies with over 1300 telecom experts across 12 European countries and we also have a delivery operations centre in Malaysia. We are delivering and offering flexible and efficient solutions with outstanding results and the telecom industry evolves. We provide a full range of services including network planning, construction

management, supporting networks and fiber companies to the telecom site providers. Thanks a lot and questions to Rafael from Connect 44's partner Snap. Rafael, this is your second episode, so a few people might remember the story, the transition story where you supported our customer Felina from SV by design to SCPS Final Cloud Public Edition. But it's great to have you on again. For those who did not listen yet to the previous episode where you were on, would you mind introducing yourself Rafael? Yes, thank you.

I'm the CEO of Snap International. This is a company that we founded nine years ago based in Slovakia and Tongari and we opened also this year our office in Switzerland. And yes, it's a second transition we are making from by Design, completely different story, still the same starting point by design implementation that was a little bit difficult and to be started to work with Connect 44 four years ago more or less where we took over the project from the previous implementation partner, we supported by design. And due to the very fast growing

from Connie 44 minus acquisition, they asked us to continue the journey with them and to transition them to the new platform which is As for an app of Cloud edition. Good. So as you said, the story sounds similar, but actually it's a different one. So questions to say. Now we have Rafael from your partner Snap here today. So what were your consideration in selecting your partner? Because this is your trusted advisor, your friends or however you call it, along the project and beyond the project? Indeed. Well, the story starts somewhere in February 2020 when we

actually approach SNAP in order to help us on developing, developing some of the SAP is by design add-ons. And let's say our collaboration has grown into a trusted relationship with them and they delivered for us solutions that meet our changing needs. They also helped us to navigate to some of the system complexities and they provided the tailor solutions and in some of the cases also innovative ones. I will say that this partnership goes beyond technology and I think we are creating a flexible

future ready business ecosystem to align with Connect 44 goals and Snap goals. This is great to hear. So Rafael, you've been ANCP by Design partner for a few years already and this is your second SCPS 1A cloud public edition implementation if I'm not mistaken, correct me if I'm wrong. What practices did you bring from the previous project like Felina and additional questions? What challenges did you foresee because you have this experience already? Then to start a little bit one

step back, that means we even participated with Connect 44 to the selection of the solution. And when they decided to move away from by divine, it was not a given that they are going to waste for public that the trust relationship was so strong that we even presented them some alternative. Of course, we had a buy in and we wanted them to select this for a public because we knew it's a right solution for them than having the experience of having implemented the Femina in the past successfully. Of course, we came with toolbox with a tool to help the migration and we are talking

about the I flow. We also were able to understand correctly what is that challenge they're coming from by design, which is a suit in a box. S for an Apublic is a little bit a different architecture, but together Connect 44 decided to also take the similar approach. That means they are not going only for S for an Apublic, they are also putting a success factor in the journey and concur in the journeys. They just recently signed also for Concur. That means they already have this approach of having one platform, one SAP platform to support all their business.

Then when we think about the challenge from failing out, it was difficult because they made one implementation and just after the good lives, they decided to move to another implementation. That was the biggest challenge with Connect 44. They had the time to prepare and the goal I was 5 or 6 years ago with By Design. They use By Design. They grew probably faster than expected and that's the main reason that I saw for the change. And they really came with a strong approach to stick to the standard and to implement best practices. That's the main difference

between the two project. OK. OK. Interesting question, Susena. So of course, we're super happy and thankful if you've chosen AC PS platform with LOB solution like SuccessFactors in addition to SAPS final cloud public edition, but you've only recently started if I'm not mistaken. So when did you start exactly the project and how far have you got until today? Well, the project has been started somewhere in the end of the previous year. We started actually very anxious to have, let's say, the future

already taking shape in front of our eyes. So currently we are in the realisation phase. We completed the explore phase where the fit to standard workshops were carefully laying the system's foundation. Our partner is setting up the prototype system and currently we are adjusting standard configurations to fit our specific needs. This together with Snap, of course some fine tuning for the operational details. But yeah, while this system takes shape, we are also staying flexible for any last adjustments.

Our team is focused actually in getting every detail right. I would say that we are also on schedule, which is quite good for a project. It's an implementation that runs smoothly and we are confident that we will hit our project milestones as planned. And this is great to hear and we will certainly support you. Moving on. I understood that it was not a given to go to another cloud ERP from SAP after the by design. Rafael made that clear and you had to go through the digital discovery assessment process,

which is part of the Discover and Prepare phases. What has been your respective experience with the DDA assessment? I would say that it was like an assessment for a strategic check up for our business processes, helping us identifying key gaps between our current system and As for HANA public cloud capabilities. Of course, the key takeaways were the founder misalignments in the current processes to identify opportunities for optimization and also to match our business goals with Sup.

As for HANA public cloud features, I would also have to mention the next steps in aligning our processes with the system by redesigning the processes where needed internally, using S for HANA Public Health strengths and also ensuring a smooth and effective digital transformation. Rafael, you want to comment as well here? Absolutely. The difference and where the DDA is really helping us as a partner is that of course we need to understand the scope and the requirement of the customer, but it's much less relevant than in the non premise approach.

We already use the DDA as a scope of the project where we, as Sena said, we validate that the process are a good fit. And after there is a next step, when we are in the next phase where we make the fit to stand out, we will view more in detail all the scope items that we already covered during the DDA. Some of them are getting removed, some of them are getting added. And then after when we enter the realization phase and we enter a little bit in a few weeks from now, the testing phase, we will validate everything, but always with the same mindset is to stick to the best practice of

SAP. And that's an I mentioned where Connect 44 needs to change the process, They will. This is working well in the context of Connect 44 because they came from a lot of acquisition with different company having different best practices, having different process and it's really they're using this opportunity to standardize everything across the company. Thanks for bringing that, I prefer with the mindset because there's definitely no way around following the SCP activate methodology which is the default for all SAP. As for Anna Cloud Public Edition projects, what we really care

about as well is the let's say the entire experience which includes 2. The system provisioning. So I'd like to hear your feedback about system provisions and all the activities during the prepare phase. Maybe Rafael, you can start this time. The system provisioning is is pretty smooth. That means like always a customer gets all the access. What is a big asset of the methodologies activate material is to get a starter system and that's a big difference to a by design implementation. For example, that means we get a

starter system with SAP data with all the scope items that we have identified during the TDA. And of course, we can also load some connect 44 data to make the fit to stand out more personal, more understandable by the key user and the development system and the test system and getting provisioned as early as possible in the project to anticipate as much as possible as a configuration step. Thanks, Rafael. So now what is your point of view on all these activities and the provisioning all what's happening in the prepare phase? I fully agree with Rafael, but I can also add that for us it was

also a step where we actually focus on setting a strong foundation for our project. We created the detailed project plan using Cloud ILM with clear timelines, key milestones, resource allocation and deliverables. Also, finally, we brought together a right team. Members from finance, operations, IT and other departments clearly defined their roles and responsibilities in the project. We talked just before about this cloud mindset and I'd like to dig with the two of you a bit

deeper into that because you're now in the explore phase that is including the fit to standard workshop. So we look at, you know, the end to end business processes that are mapped to scope items and the objective is to make sure that this end to end business processes work for your company. OK. But of course every company has a restore and you were working with by design before and some processes might have been different and therefore work perfectly for you in the past at Connect 44.

So why change if it works so well in the past just because the new products telling us that the order to cash process is slightly different, right. So what challenges did you have in in stealing the cloud mindsets in the project stakeholders and really thinking more about, you know, end user acceptance, end user adoption of the new system? Of course, our challenge was with our colleagues adopting a clown mindset. They were used in using custom systems and they were unsure if standard functionality from the

future system will actually meet all business needs. Of course, it's a big adjustment. We are focusing on showing the benefits and the standard approach, highlighting how SA PS regular updates improve the system, increase scalability and have a lower maintenance cost. Another concern was the long term cost of a cloud solution. We addressed this with clear data showing that it's actually reducing maintenance costs and uses resources more efficiently. Obviously, everything was not perfect in the previous solution

with By Design. When you are a company which has 200 employee and you grow in few years to a company like on a 44 with 1200 employee, they started to face some performance challenge, especially in the reporting area. And then they started to reconsider all what they need as an information system globally, including time recording, including tool, additional advance for project management, including more advanced HR functionality. And that's why they went with S4 plus success factor plus Funcur and so on. And they realized already doing

just in the starter system when we loaded some data to demonstrate that the reporting functionality are much, much more faster in in S4 than what they experienced today in By Design. And that's a good segue to the next question. I wanted to ask the data, right? The products Access team has created accelerators specifically built for the business by design to SAPS for Anna Cloud public edition transitions. Numbers of high flows were developed as part of this accelerator package. I'd like to ask about your

experience so far and maybe Rafael, you have a bit of history. You can tell because you might have done that without those accelerators. Now you have this to expedite some part of the project. What is your point of view here? But I can say very proudly is that some of these accelerator, we developed them jointly with the SAP team in Waldorf and we were using them partly on the previous project because we are still developing them, the Connex 44. We use them in this species Iflow for all the data migration, which makes the work

much lighter on the customer side. Of course, they still have to clean the data in by design, but we take care of the export of the data, of the mapping of the data for the new platform in SCPI using the iflow. We even developed some additional Iflows that were not part of the standard package that we shared with SAP to include that. That means this is for me a guarantee of the success of the data migration because there is no rework in Excel of any data. All the mapping effort is done today in SCPI. Thank you.

So now you want to add on this one. What was your experience with these accelerators? Do they deserve the name of accelerator? Indeed, they deserve the name of accelerators because it it really helps us in order to be have, let's say, a more organised way of migrating the data and also a clear mapping is helping us on anticipating exactly where every detail will fit. So yeah, that's a major plus for us. Nice. Nice to hear that. So we're close to the end of the

podcasts. We want to pause now before we probably record next episode. After the explore phase comes the real AS phase, the deploy phase and the run phase. So I'd like the two of you to tease a little bit what's going to come next to make sure that our audience listening today really, really want to come back and understand and learn from you gals about what's been achieved during the real life phase, the deploy phase, and of course, the wrong phase starting with you, Senna. Well, for us, it's actually the

most exciting part of the project. My colleagues will have their hands on the test system testing actually, which will help us on actually projecting the future final system. And also we'll provide quite an extended knowledge for those which will have, let's say, the pleasure to have their hands on the test system. And they will get prepared in order to train the rest of our colleagues in the next phase. But yeah, as I said, the most expected phase of the project for my colleagues.

I can understand that. Rafael, what is your point of view here? What are you expecting? In three weeks from now, we will have the data loaded for this I flow in the test system of Connect 44 and the key user will really start to go through the test scripts that we prepare together. And then we will know if Senna is still saying that we are on track for like the 1st of June this year. And yeah, I'm very excited about this next step. And so are we, Sina. Rafael, thanks so much. It was great to have you again, Rafael, to have you for the first time.

Sina. We're of course looking forward now to learning from you along the next phases of the project. Thank you for joining this episode. If you like it as much as I did and have ideas about the next relevant topic for this podcast, please send us an e-mail to insides4@sap.com. TuneIn next time and be inside SAP S4. Anna Cloud, goodbye.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. TechEd #10: How Joule Studio and n8n Orchestrates Enterprise AI

    Nov 20, 202616 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets into one of the most significant partnerships in the SAP ecosystem right now. Host Yannick speaks with Vladimir Shakhov, Strategic...

    • Apple Podcasts

    Credit the people on this episode

  2. TechEd#9: How AI Transforms Cloud ERP Migrations

    Nov 18, 202614 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode takes a refreshingly grounded, practitioner-first look at what AI in SAP really means in the field today. Host Fernanda speaks with Wouter Lemaire, independent...

    • Apple Podcasts

    Credit the people on this episode

  3. TechEd #8: The Benefit of Laying the Groundwork for AI

    Nov 16, 202615 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP brings something the series hasn't had yet: the perspective of an actual large enterprise customer architect, not a consultant or partner....

    • Apple Podcasts

    Credit the people on this episode

  4. TechEd #7: The Hidden Risk in Every SAP Transformation — Organizational Change Management

    Nov 13, 202618 minAudio

    Recorded live at SAP TechEd, this episode of Inside SAP Cloud ERP zooms in on the dimension of SAP transformations that gets the least attention - and causes the most damage when ignored: Organizational Change...

    • Apple Podcasts

    Credit the people on this episode

  5. TechEd #6: Five Days to a Working AI Solution — Inside SAP's Forward Deployed Engineering Model

    Nov 11, 202623 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets to the heart of what the autonomous enterprise actually looks like when it's working. Host Yannick speaks with Sindhu Gangadharan,...

    • Apple Podcasts

    Credit the people on this episode