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 67: Implementation of Central Procurement at OMV

May 11, 202224 minAudio
ShareXLinkedInFacebookWhatsAppEmail

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.

Hi, and Welcome to our podcast inside sap. As for Hannah, there's no customer success, without product success and project success in episode 43. We introduced Central procurement with sap as for Hannah tune in, if you want to know the concept and what you can expect from it, In theory. Now, in this episode, we switch perspectives and look at the reality. So please welcome David Walsh from OMB who talks about their Vision approach and ongoing projects to implement Central

procurement in their landscape. Clear. And unfiltered from customer to customers on my side. I brought the expert from last episode pita pocket from sap. Peter S you know we always start with an icebreaker. So I love do. Ox and how is your cray Hound Emma doing? Yeah, thanks. Katrina is he's doing very fine. So we just came back from a vacation to the Baltic Sea, and you need help. She's not a regular Greyhound. She's actually an Italian

greyhound and these can be very cheeky bastard. So yeah. She's proud and independent and very clever indeed. Correct. You have you again for this podcast, Peter and it's actually you who suggested to invite David to this podcast. So it's also warm. Welcome to David. Would you also tell us a bit about? You may be a fun Factor, not even your colleagues might know like Peter told us about his dog, sure. So, first of all, hello from my side, and thank you very much for having me on the podcast today.

My name is David Walsh. I'm originally from Ireland, but I've been based in Vienna for the last three years at, OMG, I'm responsible for the global procurement processes and I've been also leading the OM, V, S4 Hannah procurement stream. Mmmmm for the last two and a half years, a fun fact about me. I think I'm the only person in my team who can speak the Irish language. That sounds good and we can already hear your excellent. So let's let's get a get a bit into business. So David could you tell us who

is only only is a global energy and chemicals company. Headquartered here, in Vienna Austria where Australia's largest listed Industrial company with sales of over turkey? Billion and over 22,000 employees globally, important to understand. For today's discussion, is that omv comprises of multiple business units, with multiple SAP systems all under the umbrella of OMB? We have our exploration and production business, which covers central eastern Europe,

Middle East and Africa, the North Sea and Asia Pacific. Our Downstream business which includes multiple refineries in Europe and also a quite a large retail business. We also have petram, which is one of the largest companies in Romania and this became part of the omv group. We're back in 2005 and more recently, we've increased our steak and Borealis to 75% and Borealis or global leaders in the chemicals business and also, to Circular economy. Thanks, David. Let me directly jump in here.

So, can you tell us? Why did you actually decide to go for sap as, for him, out for Center procurement. So, what is what is the OMB is digital procurement Vision here? Yeah. So as a long time, sap customer our technology landscape has evolved through expansions Acquisitions. And so on over the past 20 years, it's quite a complex mix of integrated and not Integrated Systems across the group. And due to this, we decided over three years Years ago. Now, to begin our S4 Hannah Journey with the sole aim of simplifying and standardizing

our business processes and applications looking to procurement specifically, we do have a centralized procurement organization that is fully into and responsibility for the complete spend. So, starting from Calgary strategy, all the way to purchase order generation and purchase order, output, and therefore we needed a system where our users could work centrally without entering each and Back in system of which we currently have seven. So we have a mix of s for Hannah and DC Systems after working

better implementation partner and ACP directly. We concluded that the S4 Century procurements which was a good fit for our requirements and would help us to replace rsrm system which had been in place for over 25 years at OMB. Okay, it sounds like a quite typical setup for an SRM customer with such a long year history. So what were the main value drivers for this implementation? Then yes, more question. So our chief procurement officer always reminded us that, you know, omv procurement should be

a value-added organization. And therefore we try to mirror, this this attitude into RS for Hannah implementation. So I guess with that in mind, our major value drivers or success factors, whatever you may call them, were to build a robust standardized, and Global is for had a template and Template could be deployed into each and every S4 system. We wanted to create a central One, Stop Shop for a procurement Community to interact with all of our SAP systems by logging

into only one system. So, as you heard previously, we have seven. But we have a central procurement organization and we really want this team to have this One. Stop Shop concept for they can just log in once Central, we also wanted to retire our Legacy Applications and go for standard Solutions where possible and this as you can imagine over 20, 25 years of growth and expansion. We've got quite a spaghetti-like integration scenario. And, you know, underpinning

everything was to not only maintain or are quite High procurement automation race but it was two increases. Okay. And that was that was one of our major value drivers that we always checked back on Every design decision. Yeah, all valid points from my point of view of what also might be interesting for us is how you started the implementation. So, I mean, the renovation of a core Erp system is a big step, and I can imagine that change comes with some Taste of end user assistance and procurement

units. So two questions here. How did you start and how did you convince the people after 25 years for SRM? So let me start with the first part. Like any successful program of this size, we made the decision, very early on that too. We should view this as a business transformation powered by AC p-- rather than a purely. Technical it implementation So some of the things we did at the start, we had a program level decision around the S4 roadmap and that included, some key

design decisions. There was also a series of business process. Workshops that allowed us to map. What do we do currently in the organization and then map where we wanted to go? And that was really, then the basis for the technical steps, in the technical analysis that we did. Next. Once we had that in place, we started with our high level design workshops for. We really started to look at the system and in total and we took a deeper look at the technology and just checking in.

Where could it further? Support us. In that PPD business process design that we had done up front coming to the second part. You know, we were very conscious of the change impact from an early stage, especially considering that, that omv have been using sap and SRM, for nearly 25 years. And we actually have some users who have been using those systems since day one, so that that is quite a change for our organization.

To overcome any resistance to change. We first of all established, a very strong, key user Network, and that key user Network represented, the various procurement categories that we have in on the these key users war and very much still are fundamental in helping the project team to develop the Strategic direction of the landscape. So this key user Network would validate design. They would test the solution, prior to the go-live. And ultimately, they were our

sparring partners for any change discussions, Polska, life. We often call them the Guardians of the template. We also invested a lot of time in our communication strategy. So we ran a series of coffee talks. Maybe once every two, three weeks for the project team would keep the entire procurement Community up to date on the progress of the program. So what phase are we in? Are we in design? Build test Etc. We would do some solution demos. So before you 80, we would hold

a coffee too. Where we would demo that solution. We also listen to 20 concerns that the business may have had. Obviously, if you're changing something, which has been there for 25 years, there is that sense of the unknown. And this communication strategy we had in place allowed us to deal with this element of the unknown. And I suppose quell any, any kind of worries that typical Roman community may have had, and they were quite successful. We continue them to this day.

We still run these coffee talks because I think the community want them and it's also a really good tool in our Arsenal as well. So in the end the formula it sounds quite simple but investing in a strong key user Network and having a very open communication strategy and approach between the project and the business is really the key that we found two successful in user adoption, that's it.

You sound like a good approach. I mean we had sap have also something like a coffee talks. We call it Coffee corner where you can, yeah, also address your concerns to Executives and stuff like that. So that sounds sounds good and seems to be a valuable approach. Now, tell us a bit about the current situation. Where are you right now and what is the status of the implementation today compared to own these procurement vision? Sure. So we had the first is for Hannah, go live and Central

procurement. Go live on the fourth of January 2021. And that goal I was was based around our corporate headquarters here in Vienna. So all of our corporate processes with that, we created a global procurement template which I mentioned earlier and that template included Theory Bogota buying sweet. Something that we called PR 2 gr, which is basically the purchase requisition to Goods, receipt templates, all of your back-end, mmm processes. And also the first two modules

of S4 Central procurement. So, managing Central requisitioning and managing Central purchase orders. So that was the first go live in January 21. Very shortly afterwards in July of the same year. So July of 21, we went live further Downstream business. Are we implemented the above-mentioned global procurement templates? And also a new module of this for Central procurement called Central Contracting. So with this go live, we actually integrated all of our

connected SAP systems of which we had seven. Still have seven actually and ultimately retired the Legacy SRM system which had been in place for 25 years. We fast-forward again, six months later coming to the end of 2021 and we had another major go live in this time it was with the Upstream business at all in V. So here we replaced the Upstream ECC system with as for implement the global procurement team. This went live with the read the guide of buying as well as a connection to the fullest for

Central procurement. Sweet. So we're now in a phase of what we're calling solution optimization. We've done the core of our implementations now and it's really about extracting value. Looking at benefits, realization of what we have done and we're focusing a lot of our efforts internally with our Consulting partners and also with Peter and Frank from sap. Me to translate some of our ideas, and some of our Ambitions and wishes around central procurement into reality.

Thanks David. So keep us honest here. So, Katerina said, in the beginning, we should focus on the from customer to customers. So, what were the challenges during your implementation and then, yeah, keep us. Keep us. Informed, to be honest. What would you do if you could turn back time? What would you do differently? And at OMB Good question. There's two, major things. I think we would two major challenges. At least. I think the first challenge is and was unavoidable.

We delivered all of the above mentioned projects. So, three major is for Hannah and Central procurement implementations during covid. And, of course, this was a challenge. So, take an example, it was, it was the first time that any of us including our Consulting Partners head Had conducted full-day workshops remotely. So full high level design via Microsoft teams, and I think if we had, if we had the chance to gain, we probably would have spread that design or over a longer period and put more

emphasis on, on design Challenge and rice of challenge. That was certainly a takeaway in the end. The design was successful, but we did put ourselves under a lot of pressure to get that complete of. So, With the benefit of hindsight, we would have spread that out over a bit more time just to cater for some of the challenges that happened. Would it be in a remote? A remote project office? I think our biggest challenge then, in terms of the, the system was pretty much an

age-old challenge in sap Transformations. I don't think we're the first company in the history of sap. Go live to have a challenge with data migration and specifically. In our case it was it was the migration of few thousand contracts from our Legacy SRM system to the completely newest for Central Contracting system. So all I'm very Were one of the first companies in the world to go live with as for essential Contracting. And of course with that we had

the challenge of being one of the first customers in the world to do a data migration from a CRM to S4. So none of us had that experience in such a migration. And I think one of the major takeaways and if I was to give anybody advice, is really understand what your Source data structure looks like understand what? It should look like in your target system and take your time, don't make assumptions around how that process will

look like in reality do plenty of migration Cycles Mark Cycles up front and really rely on your keys or network in your business Network to validate that data. So that's definitely something we would do different. That was certainly a challenge and looking to the Future. We're gonna Really examine, how do we do this for future? Go live and, and take it from there. So, there were two major challenges Peter. So, Peter is turn it around.

I have a question for you. So as you know, Central procurement is, is a Strategic investment at all envy and it will very much continue to be. So what roadmap items are coming up in the next 12 months that could be interesting for the wider audience. Yeah, thanks. David and rest assured. It's also Strategic investment for us for sap. So Central procurement died, plays a very important role in our procurement strategy. And of course, we are going to invest more and more in the upcoming quarters. So for everybody, you can always

take a look at our sap road map Explorer, which is which is available online. You can see what is planned in the upcoming quarters and just to pick a few topics here just to mention. So lately, we have Introduce the central output of purchase orders from the central Hub system. And now in return, we also focusing on supporting Central supplier confirmation. So, if you send out the approaches or a centrally from The Hub system, we also want to give away to receive

confirmations from the supplier side. Centrally approve them and then update the purchase orders in the connected back-end systems. This is one of the new features that we're going to introduce. And the other one, you may know that we are integrating an item hierarchy into our local procurement processes. So the same is also true for the central contract, for example. So, we will also support a hierarchy of various levels with services and materials. And you can also distribute that Central contract with a service

hierarchy, then to a connected S4 back. End, one feature that many customers have already asked for especially in the service provider industry. Um, then, of course, we want to introduce more collaboration into into our tools, so David, as you have explained, you're using the process, PR centrally app, so that the central purchases cockpit quite a lot to, to process the incoming demands. And we also heard you that, that

you need more support for collaboration. How can purchases exchange ideas nodes, how can you assign? Appeared to somebody maybe have a queue handling. So this is very much in Focus. What we will also accomplish accomplish in the future, and maybe last but not least, looking at another Persona the Casual user. So you said, you're also integrating a Reaper Guided by we've seen the procurement and in here we we had the request

from several customers to also support the receiving features, so that a casual user can not only create this shop. Ben Cardin guided buying but also be able to confirm and receive his Goods in this one unique user interface. These are some of the topics that we are concentrating on. I would say the next four quarters Thanks Peter for outlining dad, and as we are already talking about roadmap David. If you if if we had Christmas

and you had one wish, what would you ask as AP for? Well that's a that's a great question, look. I mean, there's obviously always things that customers will want. I think one of the major, the major requirements are requests coming from Mauer. All Envy procurement Community is Keeping in mind that we have no mirrors the organization into a application, which is, as far as Central procurement, and

keeping in mind, this One, Stop Shop concept for we do everything within one application. We very often get to request to have visibility on payment status on purchase order. What I mean by that is In S4 Central procurement, we use the manage purchase orders, centrally app. And within this application you've got quite a nice feature which is the document flow and here we see original PR purchase order.

See your gr documents you see your invoice document and our buyers often added first. First point of contact to our suppliers. So what happens is the supplier might call up and say, hey dear, dear buyer. Can you tell us what's happening with the Such and such invoice. And the vision that we have is okay, well using this document flow or even the use of a status flag. Show me the payment status on that Pier. So, right now, it's a, it's a case of we ring accounts payable

they carry out various chips in their system and they come back and they give us that information. So the information is available of course, but our buyers would love to see that payment status Contained within manage po, Century app. So Father Christmas if we if we could have that in the future, that would be quite nice. Yeah, sounds valuable. Now Peter imagine you're Santa can we fulfill this wish okay, you have me being Center?

Yeah, that a little bit tricky. One because you may know we also have our Central invoice management solution which is basically You the, the brother next to Center procurement, and we separate this quite clearly between the Persona of the purchaser and the Persona of the accountant, s is David just mentioned. So in that Central invoice management solution, which is, which is very similar to Center procurement, it's a central system with connected back ends and you have all the visibility on the, on the invoicing

process. So they are, of course, we have this Central status. I can very well. Understand why the results of division need from the, from the Poetry decide to also see some status of the payment. So for us, we need to align internally a bit. How is our strategy with these two solutions? Then where are the boundaries? Where can work in the exist together? And I hear you very well David. I cannot promise it and how in this, in this podcast session here. But yeah, we will take a closer

look. We will see how we could Maybe improve that document flow and give some hint here. Shows some status what the payment is doing. Again, it's not so straightforward. We need to do some internal lyman's but yeah, thanks for the hint and for the feedback very valuable and we will certainly take a look at it. So, thanks for my side. Thanks guys, actually, we're already at the end of this podcast and I appreciate this honest dialogue and I think this

helps our audience, Has to start their Journey as well. Thank you, David for your unfiltered insights. And for adding this nice, Irish accent and Peter Pleasant to have you here once more again. And thank you for connecting us to David, and also, please give Emma a snack from me. Hey, everyone, feel free to drop us an email via inside. As for at sap.com/learnbi, which topics you are interested in for the next podcast episodes. June, in next time and be

inside. Sap as for Hannah.

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