Next Generation Cloud Delivery FAQ
Next Generation Cloud Delivery FAQ
public
Q: Will the move require a change to existing contracts requiring SAP Ariba to notify all customers?
SAP Ariba cloud services agreements are data center agnostic and we reserve the right to choose a data center
provider. At SAP Ariba, we provide the list of vendors who have access to our data centers in the subprocessor
listing. We add the respective public cloud providers and notify customers of the change as the production data
center is operated by a public cloud vendor.
Q: Other SAP cloud businesses are leveraging Microsoft Azure and other providers already, is the vision that
SAP Ariba, SAP Concur, and SAP Fieldglass will be deployed on a common cloud provider within a region?
Each cloud line of business will select the provider that best suits their business and technology needs. In some
situations the lines of business may utilize the same provider and in others each may not.
Q: Will SAP Ariba APIs, services, and applications be available in next generation cloud delivery?
Yes, the objective is to have all services be available via the public cloud. New products will only be deployed in
one of the cloud provider platforms.
Q: Will SAP Ariba keep the same Ariba Network front doors/access points?
Ariba Network’s framework, where all Ariba Network traffic is channeled through the US data center, is not
changing in the immediate future so there are no plans today to change any front doors/access points. Customers
will need to update IP Allow lists based on information provided for the specific data center in the Technical
Addendum area of this page on SAP Ariba Connect.
Q: Will the move to next generation cloud delivery have a significant impact on the integrations customers have
established between internal systems and the current SAP Ariba systems?
This transition will have no impact on integrations. The underlying data center does not change application
behavior, but customers should check any IP address blocking that may have been implemented by their IT
departments to further insure seamless access to systems. Further details on IP address information may be
found in the specific data center entry in the Technical Addendum area of this page on SAP Ariba Connect.
Q: Can our SAP Ariba application hosting remain at the current SAP Ariba data center? Can I opt out of the
migration to one of the selected cloud providers?
Unfortunately, no. There is no technical solution available to opt out of the migration of applications to a
designated cloud system provider.
Q: May customers request which provider their environments are hosted in?
SAP Ariba determines the appropriate public cloud vendor to be utilized in a geographic region.
Q: How can customers get SAP Ariba applications deployed on public cloud in their own countries?
SAP Ariba determines the regions where the data centers are deployed.
Q: Will the public cloud meet FedRAMP, ITAR, and/or HIPAA secure infrastructure compliance?
Compliance framework is not tied to this effort. Please check with your SAP Ariba account team on timelines for
these regulatory controls. In addition, hyperscalers provide certain levels of compliance for their data center
hosting; applications hosted within these public clouds need to comply with these policies.
Q: What is our Recovery Time Objective / Recovery Point Objective and are we changing any operating policies?
All SAP Ariba data centers follow the same operating standards and certifications. Those same standards apply to
the data centers deployed on a public cloud. For additional details, please reference SAP Ariba’s Disaster
Recovery documentation.
Q: How does this move change or impact our support interaction model?
Environments deployed on public cloud will follow the same customer support process that is used for
environments deployed in legacy data centers. Contact SAP Ariba Customer Support to have issues
reported/addressed.
Q: Will customers deploying on public cloud need to sign an SAP Cloud Contract for the SAP Ariba services, and
in addition have a separate contract with the public cloud provider?
No additional contracts need to be signed for the public cloud providers. We have updated our list of sub-
processors to include our public cloud providers.
For customers integrated to an impacted environment, on the specific migration weekend they will be encouraged
to slow or stop transaction feeds in to the specified environment during the planned downtime. Once the system
goes offline for the migration downtime period, transactions will be queued from CIG customers and any Ariba
Procurement sites that may be online when others are offline, and will be processed during the post-migration
period shortly after the site comes back online.
For customers integrated to an impacted environment by a means other than through a legacy Ariba Procurement
system or Cloud Integration Gateway (CIG), so an integration from SAP ECC for example, they also will be
encouraged to slow or stop their data feeds to the environment during the schedule downtime, as their
transactions will fail and will need to be re-tried by the customer following the outage timeframe.