Name: Showcasing Updates in SAP Ariba Central Procurement – PET 2026
Uploaded: 2026-6-3
Duration: 1202 s

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Personalize your learning.

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Activate your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

This browser is not supported

Show more

Ooops, something went wrong!

Oh no! Tell us how we can improve.

Great! We value your feedback

Thank you!

Browse by capability

Please wait

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn't find what you're looking for

To continue, please log in

Your session has timed out

Validate your skills and learning by completing the certification exam and gain a highly recognised accreditation.

Book your certification exam

Complete the assessment to validate your SAP PartnerEdge competency qualifications.

Ready to take your assessment?

Learn about the key features and essentials in the latest release to help you prepare for the Stay Certified assessment.

Prepare for assessment

Learn new skills you need at your own pace with our bite-sized lessons.

Prepare for certification

In your My Learning account you can view your certification and learn how to take your Stay Certified assessment.

Ready to take your Stay Certified assessment?

Get tailored answers, tune into podcasts, and dive deeper with interactive study guides, mind maps, FAQs and more.

Upskill faster with AI-powered assistance

Upgrade to AI-powered learning

Enroll to Google NotebookLM to flexibly interact with SAP Learning content. It's free and activates instantly.

You are all set. Google NotebookLM is now active. You will have access to AI powered learning for all our eligible courses.

Enrollment successful!

Get started with AI-powered learning

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Overview

Support Resource

Certification Exam

Theoretical Exam

Schedule

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Hands-on Practice for {title}

Quiz

Scenario Based Assessment

Course Assessment

Course

SAP Expert Lectures

Stay Certified

Subscription

System Based Assessment

Unit

Video

Video Playlist

Week

Want to remove this from your Learning List?

You have until July 30, 2026 to complete your Stay certified assessment.

Your SAP Certification extension is now active!

Your exclusive access to the SAP Learning Hub, Event Edition is ready. <link>Start learning now.</link>

Access activated

You can now register for free Live Sessions.

<div><div><div><div><div><div>SAP Business Suite Product Expert Training (PET) H1 2026 / Source to Pay / SAP Cloud ERP / SAP S/4HANA Cloud Public Edition / Sourcing and Procurement<br><br>This video features a collection of recent innovations from SAP S/4HANA Public Cloud release 2602 of SAP Ariba Central Procurement including the support of service level agreements in the central processing of demands or the account assignment facet in central purchase contracts. Additionally, the video includes a preview on the defaulting of distribution lines, which is scheduled to be released with the release 2608 of SAP S/4HANA Public Cloud.<br><br>Ask your questions in our <a target="_blank" rel="nofollow noopener noreferrer" href="https://community.sap.com/t5/enterprise-resource-planning-q-a/qa-p/erp-questions">community</a> using the PET_Enablement tag under “Question User Tags.” <br><br>Here is the <a target="_blank" rel="nofollow noopener noreferrer" href="https://d.dam.sap.com/a/KA35FxV/Showcasing_Updates_in_SAP_Ariba_Central_Procurement.pdf?rc=10&inline=true&doi=SAP1317717">slide deck</a>.<br><br>Please note that captions have not been edited.</div></div></div></div></div></div>

Showcasing Updates in SAP Ariba Central Procurement – PET 2026

Welcome, everybody, to a new session on our product expert training, this time showcasing updates in SAP Ariba central procurement. My name is Peter Paschat, I'm going to be your host in this presentation, and I'm product manager for central procurement as well as the S4 purchase requisition, and today I'm going to show you our five new features in central procurement in the source-to-pay process and if we look at the agenda the first four are basically features that we have just released with the 2602 release and the fifth one is an outlook a preview to the upcoming release 2608 so let us directly jump into the details so the first feature that we want to talk about our service level agreement categories in central processing of demands so what does that mean in central purchasing we have the central cockpit process purchase requisition centrally that you can see on the right hand side of the screen and we have now introduced a new field and a new column to the work list which depicts the sla status of a requisition of a demand so what challenges or pain points do we want to address with that so usually a processor central purchaser is missing certain priorities he might have a long list of requisitions to work on and he may not really know which are the urgent ones which prs have the highest priority to work on so with the sla categories we can indicate that to him so he can clearly distinguish the high priority items from the from the low important ones and we can also give a hint how much processing time would be usually assigned to such a category. So how much time is typically left for the purchaser to carry out his processing. So based on the SLA categories, whether this is a high, medium, or low priority item, you can configure different SLA times. So for example, I might assume the processor has about 48 hours time, and this is then indicated in his work list. So you can see how much time is left how many days or if a certain action a certain processing is already overdue so this way you can guide the processor of these different PR lines to the most important demands which are coming up so maybe an urgent maintenance repair item might be much more important than a low-level office materials supplies with a business add-in that we also provide the customer can then define for which of his demand lines a certain category is applicable so you can have your own custom logic maybe based on the material groups on the connected back and on the purchasing org what kind of category do you want to assign to a requisition when you extract it from the backend into the central cockpit and based on that the configuration kicks in and can then calculate what is the remaining processing time. So how does that look like in action? We have a small demo for that. So let's roll this one. So we are the ProcessPair Centrally app. You can see now the SLA status. Some items are completed, some still have some days left to work on and in this case we want to create a purchase order so we mark the requisition line item we continue with the creation of the purchase order so in that intermediate screen typically select the document type you can make some other adjustments in this case we just go straight ahead we create the PO in the connected backend system and confirm and when you go back into the list then either you have a delta run scheduled or you can just go to the details and refresh that demand line it will automatically update all the data from the connected system and in this case you see the PO has been created and going back to the work list you can also see the status has changed to completed so this way the purchaser can really navigate his workload and go step by step and take care of those items which have the highest priority for him. Now in the next example we take a look at the new feature called validation of overconsumption and this is true in the case of central purchase contracts. So what does that mean? Typically over the lifecycle of a central contract there might be changes that you want to do to that contract even though callers have already been made in the connected background. So if you take a look on the right hand side of the screen you can see that central contract is already consumed up to 80 % and the reason is you can see in the release documentation a purchase order has already called off a value of 480 euros. Now if I would not be using that specific validation that we have introduced you can just go ahead and any time make changes either to the local contract or even the central contract, which could lower the value of the anticipated or the connected contract in the backend system. So if I would now go ahead and edit the central contract and I would bring it lower to a value where I say the target value should only be 300, but I actually know 480 have been called off already, this would be a mismatch. And with this new validation, you can then actually decide if you want to just give a warning message or even an error message, not allowing that you can accidentally over consume the central contract by making later changes to it, which bring you lower than the already call of value. So this way you can enforce a very strict consumption tracking, which was not really in place before. The local contract itself does not really offer that kind of over -consumption check. And especially for the central contract being the central object in the multi-ERP landscape, we felt that flexibility should be given to the customers. so basically what it addresses is subsequent changes to a central contract cannot actually lead to an overconsumption so the central purchaser is always guided that he cannot mistakenly lower the value underneath the already called off values so this additional validation is now put into place and it can track the consumption across all the backends so let us take a quick look at a demo as well how this looks like in action so we are in the central contract and you see there is a new flag called consumption check and you can see we have a certain target value we want to flag that contract for this additional consumption check and you can see we have an even distribution so we now release the central contract and it's getting distributed to the connected systems so checking these back-end contracts that we have created so we can now pick one of those for example look at the distributed details and we create a call of a purchase order which is now consuming a certain amount of that distributed contract of course if if now the automatic jobs kick in and also the central contract is updated with these call-off amounts then you can centrally track how much consumption has actually been booked in the connected backend systems. So in this case we even create a second call-off now once everything is released and once the jobs for update have been triggered we can go back to the central contract. so now looking at the overall consumption we can see 65 percent of that whole contract has been consumed already if we go deeper to the distribution line level you can even see the consumption on the distribution level it's even 80 percent and for the second line item 50 now we can try switching into edit mode and keep in mind this consumption check is active so in the past there would have been no errors no warnings if you now go underneath the already consumed value if I now cut the distribution percentage and only have 35% for the first line then we get this error that this would actually violate the already consumed amount and now you can play around and test and you can always see how much percentage are you like over consuming so what kind of changes are still allowed if later on in the lifecycle of the sample contract you have to distribute different different levels here to your connected backends so this concludes the demo and we move on to the next feature put in line we have the account assignment facet that we have newly integrated into the central contract so in forward times purchases were not really able when they were creating the central contract to directly also store accounting information so you would always have to go to the connected backend after the initial distribution and then add on the different accounting information per backend system we have now included an accounting facet that's a reuse facet that we have in various other documents as well and now you can do the same way of single account assignment multi account assignment with split criteria as you know that from from the local contract from the purchase order the main benefit is you can directly do everything from one place it doesn't need to be distributed between the central contract creation and adding that information in the connected system also you have search apps for the different accounting objects and you can directly maintain everything in one go let's take a look at the demo as well so we already have a central contract available here we go to the line item details and here you can select what kind of account assignment category should be used so in this case we choose the cost center and when you go down to the distribution level so in this case we first create a distribution line then you will find the new account assigning facet map. Down here you can just add account assignment information as you see fit so it's just optional information you do not really have to maintain it in case you still want to stick to the backend process flow. In this case here we can now select the cost center for the search out we have the online search app into the backend for the GL account and we create that new line additionally this is now a single line on accounting you can also go back to line item level and choose to have a multi-accounting of course either based on the quantity or based on percentage and in this case we go back to the accounting test once more now we are able to add an additional line have a different cost center you give the split 50 items quantity here 50 there and again you can pull out the cost center search out and the GL account and store all that accounting information in one go while you create a central contract and you spare all that later maintenance in the connected backend system so once everything is now maintained we click on apply we can release the central contract and distribute it to the connected backend and now quickly double-checking this is the distributed contract the local contract number in the connected system and looking at the details we can verify that the account assignment has been stored okay over to the fourth feature that we want to display so again this has all been released with 2602 already so the public cloud these features are all available and central procurement next one is about header and item notes in central supplier confirmations so we have added this basically following on the heels of the local supplier confirmation which also supports notes in the meantime so these notes can typically come from the supplier side where the supplier might explain to you why he has chosen to reject a purchase order line item why he cannot confirm so he can give a reasoning that reasoning is not only stored in the central supplier confirmation but it's actually copied over into the purchase order as well and in the use case of central procurement it is even copied into the back-end purchase order so that any local buyers can also verify what are the reasons why has a certain line item not been confirmed by the supplier so suppliers cannot communicate directly with the purchaser by adding comments so supply rejections can have a certain reasoning we update the purchase order so this is all supported whether you manually create the supplier confirmation via the Fiori app on behalf of the supplier or it's also integrated into the electronic XML interface so if you receive XML confirmations so let's take a look at the demo in this case we will showcase the manual creation of these nodes so we give a reference purchase order that we want to confirm in this case we have two different line items so we have the line item 10 and 20 all the related information is pulled in from the purchase order and we can choose in this example to reject one of the line items and give a reasoning for the second line item which is confirmed so just some basic example text rejection comments demo that should be it the other line item we will confirm with a quantity and we then release the confirmation now upon release that information is also updating the purchase order so in this case we can take a look at the purchase order in the connected backend system pick up the line item that was rejected so you can see in the confirmation the rejection indicator set on the pure line item has been marked for deletion and under the text you can now see the line item text for the supplier comments second line item as expected will show a positive confirmation so last but not least we will now come to a preview of a feature that is currently in the making so this is for 2608 we want to introduce so -called distribution templates so that you can actually default all your distribution lines instead of manually creating each line after line very painfully you can just set up a template and say that central contract should be distributed to 10 backends in one go so how does that look like we have introduced a new action into the central purchase contract it's called use templates these templates you can define in your configuration so as a business process expert you can define those lines you can give a template ID and you can add as many distribution lines as you see fit here in this preview you will see kind of hierarchy display which distribution lines all belong to one template ID and yet the main comfort is the purchaser does not need to manually maintain all these lines he can just use the search help pick a template ID can even pick individual lines if he likes and then all distribution line items are automatically copied to the central contract so especially the more backend systems you have and to the more systems we want to distribute a central contract in one go the more comfortable and the less work you will actually have let us take a look at the early demo so first of all you get a quick preview of the configuration there is an SS CUI that the business process expert can actually use you can give a template ID and then you see the list of all the distribution lines and all the field values that you can put in so basically all the necessary fields maybe except the accounting facet that we just spoke about you will find here and then when you're in the Fiori app of managing the purchase contracts the purchaser can just go ahead and use these templates you can see this is this hierarchy fashion you can either pick the whole template ID you can just copy individual distribution lines if you like and everything is copied over with all the details distribution percentages all the org data so there's basically nothing else that you need to do and you can use the templates either on header level as you just saw or you can go to the item distributions and even add additional ones also through the template feature so for example for this line item or we even add item distribution lines here in addition then in the end you just release the central contract and it will be distributed into nearly up to ten different outline agreements as you just saw so this concludes today's session so hopefully you stay tuned so remember every Friday new videos are getting added so you can always keep yourself up to date there There is even a community where you can drop your questions or last but not least, if you have direct questions to our experts, there is an email address where you can just put in your question. It will be routed to the right expert and you will get your answers soon enough. So thanks again for your attention today and have a great day. Bye.