sap ariba upstream and downstream modules

There are two types of data that are critical in buying and invoicing, vendor master data and user master data. That’s because cleaning up things like duplicate entries and inactive suppliers/purchase organizations, commodity codes, or plant data can be a months- or years-long process by itself. Master DataĪs we discussed in previous articles in this series, most notably Supplier Management, having a clean, organized data source is crucial to avoid significant project delays. Our goal as consultants and Ariba partners is to prepare clients beforehand so they understand what’s required to keep the system running and aren’t surprised by its complexity down the road.īut before we get into that, let’s look at some pre-deployment tasks for Ariba Buying and Invoicing that will keep the project timeline on track. They aren’t ready to deal with the challenges of ongoing administration, and there are a LOT of challenges there.

I frequently hear from clients who are frustrated because they were under the impression that the system would practically run itself once it was installed. One that’s critical to preparing for downstream implementations, however, especially Ariba Buying and Invoicing, is understanding the challenges you’ll likely face in post-production. There are many similarities in how to prepare for each, including data cleansing and preparing key stakeholders across the organization.

Now we’ll look at the Ariba downstream modules related to Buying and Invoicing. In the previous articles in this pre-deployment readiness series, we’ve examined preparing for your deployment as it applies to SAP Ariba upstream modules.

Sap ariba upstream and downstream modules