SAP Integration Suite, managed gateway for spend management and SAP Business Network (ISMG)

Migration from SAP BTP NEO to SAP BTP Cloud Foundry (CF)

What is Happening?

SAP Business Technology Platform (BTP) has announced the end-of-life for SAP BTP NEO.  As such, applications such as Integration Suite, managed gateway for spend management and SAP Business Network (ISMG) must migrate to SAP BTP Cloud Foundry (CF).

We encourage you to check-in on this site until the migration is completed to stay up-to-date!

We have organized all necessary technical details by instance of SAP Integration Suite, managed gateway for spend management and SAP Business Network:

• China (completed)
• United Arab Emirates (UAE)
• North America (NA)
• European Union (EU) (completed)

Customer Webcast Sessions!

We are happy to offer some webcasts for you to attend and learn more about this effort. Please review and and attend a session by clicking the date/time you prefer (save the link to your personal calendar). Please note, we will add links for each date/time, so check back!

Completed

• • Customer webcast PowerPoint deck (click to view)
  • 12 Feb 2026 1:00pm UTC (click for webcast recording)
  • 12 Feb 2026 10:00pm UTC (click for webcast recording)
  • 26 Feb 2026 12:00pm UTC (UAE specific) (click for webcast recording)
  • 12 Mar 2026, 26 Mar 2026, 23 Apr 2026, 7 May 2026 (no recording available)
  • 16 April 2026 1:00pm UTC session (no recording available)
  • 16 April 2026 10:00pm UTC session (click for webcast recording)
  • 21 May 2026 10:00pm UTC session (click for webcast recording)
  • 11 June 2026 10:00pm UTC session(click for webcast recording)
  • 9 July 2026 10:00pm UTC session(click for webcast recording)
• Upcoming
  • More webinars coming soon!

We have assembled Frequently Asked Questions and a Steps/Checklist for you as well!

Many common questions are already answered in the FAQ below. We recommend checking it first to find a quicker solution.

For assistance, contact SAP Support using the Support Hotline. We recommend opening a support ticket with the component BNS-ARI-CI-PLT-CON.

What do Customers have to do?

• Buyers
  • Step 1 — Check your connection type in ISMG under My Configuration → Connection tab. If Transport shows ADDON or CLOUDCONNECTOR, you are using SAP Cloud Connector and must complete Step 2. If not, skip to Step 3.
  • Step 2 — SAP Cloud Connector users: Register new BTP Cloud Foundry subaccounts for your region as soon as possible — do not wait until your migration date.
    • See the How to Setup Cloud Connector demo for instructions
    • Do NOT delete any existing subaccounts. They MUST be retained until migration is complete and transactions have been successfully verified
  • Step 3 — IP Allow Listing (if applicable): Only required if your organization currently maintains an IP allow list. If unsure, check with your IT or infrastructure team.
    • Add the new BTP Cloud Foundry IP addresses for your region before your migration date. Please see more details in this article. 
    • Do NOT remove any current IPs. They MUST be retained until migration is complete and transactions have been successfully verified
• Suppliers
  • IP Allow Listing (if applicable): Only required if you currently whitelist SBN or Procurement IP ranges. If unsure, check with your IT team or service provider.
    • Add the new BTP Cloud Foundry IP addresses for your region before your migration date. IP details are published in this article.
    • Updates must be made within your internal systems — no changes are needed to your Managed Gateway for Spend & Network configuration
      • Do NOT remove any current IPs until migration is complete and transactions have been successfully verified

IMPORTANT: All necessary changes must be completed in advance of your scheduled migration date. You do not need to wait until your migration date to accommodate these changes. Please make these changes as soon as possible to avoid unnecessary disruption. 

We also recommend the adoption of new domain URLs.

What is changing?

• SAP Cloud Connector (SCC) configuration (if you are using SCC)
• IP allowlisting / IP filtering updates (if your network policies require it)

What is not changing during this migration?

• Integration URLs
• Certificates or authentication mechanism
• Functionality/UIs
• All customer data, including transactional and configuration data

Schedule

Customers will start noticing the actual impact or changes only when the SBN, SSP, and S4 updates are done.

Note: During this time customers will not face any issues with transaction flow. Only accessing Integration Suite Managed Gateway may have a small interruption of less than 5 minutes due to a restart. Apart from this, there will be no impact to customers.

ISMG Data Center - European Union (EU)

Region: cf.eu10.hana.ondemand.com

SAP Cloud Connector Subaccount Updates

If you use SAP Cloud Connector, you must add the following Subaccounts. Please do NOT delete any existing subaccounts or IPs. They MUST be retained until the migration is complete and transactions have been successfully verified.

For general instructions on Configuring SAP Cloud Connector, please see this.  While leveraging these instructions, please be sure to use the Region, Subaccount, and One-time Passcode URL details provided just above on this page.  Please remember to use the same Location ID that you are using today for the current Integration Suite, managed gateway for spend management and SAP Business Network.  Please maintain "Cloud to On-Premises" settings for the newly added sub accounts to match those of the current settings in SAP Cloud Connector.

When can we make these changes?

What happens if we fail to make these changes by the date above?

Your transactions will fail to be received by your ERP.

IP AllowList Updating

If you are leveraging IP AllowLists, you must update your AllowList to include the new regional endpoints for your region (cf-eu10, cf-eu10-002, cf-eu10-003, cf-eu10-004, cf-eu10-005).  The necessary IP details are published in the Regions and API Endpoints for SAP Cloud Foundry Environment resource. Please add new Cloud Foundry IPs before migration, but keep existing Neo IPs until migration is fully completed.

When can we make these changes?

You can add the new/future IPs to your AllowList effective immediately, but do not remove the current IPs until the migration is completed for your scheduled change date.

What happens if we fail to make these changes by the date above?

Your transactions will fail to be sent to SAP by your ERP.

ISMG Data Center - North America (NA)

Region: cf.us10.hana.ondemand.com

SAP Cloud Connector Subaccount Updates

If you use SAP Cloud Connector, you must add the following Subaccounts. Please do NOT delete any existing subaccounts or IPs. They MUST be retained until the migration is complete and transactions have been successfully verified.

For general instructions on Configuring SAP Cloud Connector, please see this.  While leveraging these instructions, please be sure to use the Region, Subaccount, and One-time Passcode URL details provided just above on this page.  Please remember to use the same Location ID that you are using today for the current Integration Suite, managed gateway for spend management and SAP Business Network.  Please maintain "Cloud to On-Premises" settings for the newly added sub accounts to match those of the current settings in SAP Cloud Connector.

When can we make these changes?

What happens if we fail to make these changes by the date above?

Your transactions will fail to be received by your ERP.

IP AllowList Updating

If you are leveraging IP AllowLists, you must update your AllowList to include the new regional endpoints for your region (cf-us10, cf-us10-001, cf-us10-002).  The necessary IP details are published in the Regions and API Endpoints for SAP Cloud Foundry Environment resource. Please add new Cloud Foundry IPs before migration, but keep existing Neo IPs until migration is fully completed.

When can we make these changes?

You can add the new/future IPs to your AllowList effective immediately, but do not remove the current IPs until the migration is completed for your scheduled change date.

What happens if we fail to make these changes by the date above?

Your transactions will fail to be sent to SAP by your ERP.

ISMG Data Center - United Arab Emirates (UAE)

Region: mtls.ae01-l-c.uc-live.shoot.live.k8s-hana.ondemand.com

SAP Cloud Connector Subaccount Updates

If you use SAP Cloud Connector, you must add the following Subaccounts. Please do NOT delete any existing subaccounts or IPs. They MUST be retained until the migration is complete and transactions have been successfully verified.

For general instructions on Configuring SAP Cloud Connector, please see this.  While leveraging these instructions, please be sure to use the Region, Subaccount, and One-time Passcode URL details provided just above on this page.  Please remember to use the same Location ID that you are using today for the current Integration Suite, managed gateway for spend management and SAP Business Network.  Please maintain "Cloud to On-Premises" settings for the newly added sub accounts to match those of the current settings in SAP Cloud Connector.

When can we make these changes?

What happens if we fail to make these changes by the date above?

Your transactions will fail to be received by your ERP.

IP AllowList Updating

If you are leveraging IP AllowLists, you must update your AllowList to include the new regional endpoints for your region (ae01).  The necessary IP details are published in the Regions and API Endpoints for SAP Cloud Foundry Environment resource. Please add new Cloud Foundry IPs before migration, but keep existing Neo IPs until migration is fully completed.

When can we make these changes?

You can add the new/future IPs to your AllowList effective immediately, but do not remove the current IPs until the migration is completed for your scheduled change date.

What happens if we fail to make these changes by the date above?

Your transactions will fail to be sent to SAP by your ERP.

ISMG Data Center - China

Region: cf.cn40.platform.sapcloud.cn

SAP Cloud Connector Subaccount Updates

If you use SAP Cloud Connector, you must add the following Subaccounts. Please do NOT delete any existing subaccounts or IPs. They MUST be retained until the migration is complete and transactions have been successfully verified.

For general instructions on Configuring SAP Cloud Connector, please see this.  While leveraging these instructions, please be sure to use the Region, Subaccount, and One-time Passcode URL details provided just above on this page.  Please remember to use the same Location ID that you are using today for the current Integration Suite, managed gateway for spend management and SAP Business Network.   Please maintain "Cloud to On-Premises" settings for the newly added sub accounts to match those of the current settings in SAP Cloud Connector.

When can we make these changes?

What happens if we fail to make these changes by the date above?

Your transactions will fail to be received by your ERP.

IP AllowList Updating

If you are leveraging IP AllowLists, you must update your AllowList to include the new regional endpoints for your region (cn40).  The necessary IP details are published in the Regions and API Endpoints for SAP Cloud Foundry Environment resource. Please add new Cloud Foundry IPs before migration, but keep existing Neo IPs until migration is fully completed.

When can we make these changes?

You can add the new/future IPs to your AllowList effective immediately, but do not remove the current IPs until the migration is completed for your scheduled change date.

What happens if we fail to make these changes by the date above?

Your transactions will fail to be sent to SAP by your ERP.

Steps to follow (Checklist)

• Determine your ISMG Data Center
• Confirm if you use SAP Cloud Connector
• Add new SAP BTP Cloud Foundry Subaccounts
  • Use correct Region (E.g. eu10, us10, ae01)
  • Use provided Subaccount ID and One-time Passcode (OTP)
  • Maintain same Location ID
  • Maintain Cloud-to-On-Premise settings
  • Configure for both TEST and PROD
  • Note: Do not remove existing/current IP addresses or subaccounts until the scheduled migration is fully completed.
• Confirm if you leverage IP Allow Listing and update accordingly

Steps to add cloud foundry subaccounts of Managed Gateway for Spend & Network

For SAP RISE customers only - How to contact your HEC/ECS/RISE hosting partner and IP Allowlisting for Cloud Integration

Region Codes for SAP BTP Neo and SAP BTP Cloud Foundry

To identify what Data Center applies to your organization, please log in to SAP Business Network or your SAP Ariba Procurement/Sourcing system (prior to accessing ISMG). You will find the applicable Data Center information displayed accordingly:

SAP Business Network	SAP Ariba Solutions

Frequently Asked Questions

General / Getting Started 

How can customers determine their Data Center? 

Please note that Region might be different from your company location. When you access ISMG, you can user the URL showing up in your browser to determine your Data Center:

• UAE: integration-uae.ariba.com
• NA: integration-us.ariba.com
• EU: integration.ariba.com

How can we check if we're using SAP Cloud Connector? / How can I tell if I'm applicable to make changes?

In ISMG, go to the My Configuration > Connection tab. If Transport has ADDON or CLOUDCONNECTOR, that means you are using SAP Cloud Connector:

What if I don't use SAP Cloud Connector (SCC)? 

If you do not see “Cloud Connector” /"AddOn" in your ISMG portal, that indicates you are not using SCC, so there is no SCC-related action required. You should still confirm with your IT team whether you use IP filtering / allowlisting and update it if needed.

What if I use CPI instead of a direct Cloud Connector connection?

This migration is specific to ISMG. Standalone CPI is not impacted. Where CPI is part of the integration landscape, customers should still review IP allowlisting from their side if applicable.

Is it mandatory to switch to the new BTP Cloud Foundry domains during this migration?

It is recommended, but not mandatory to adopt the new domain URLs.

Schedule & Timeline 

What is the migration timeline on the day of the event? 

The tentative maintenance windows are listed in the Schedule table above. Please note these windows are tentative — our migration can only begin after dependent solutions (SBN, SSP, and S4) have completed their own changes. The actual start time may shift within the window depending on when those upstream steps are finished.

We do not recommend customers remain on standby during the window. There is no action required from customers at the time of migration. Instead, we recommend checking your integration status the next business day to confirm transactions are flowing as expected.Yes. To reduce risk during migration, we strongly advise against making any changes to your ISMG portal configurations — including projects, connections, or user settings — in the days leading up to your scheduled migration date. Last-minute changes increase the risk of errors that may be difficult to diagnose during the maintenance window. Please complete all preparation steps well in advance.

Are there any restrictions on changes I make before the migration date?

Yes. To reduce risk during migration, we strongly advise against making any changes to your ISMG portal configurations — including projects, connections, or user settings — in the days leading up to your scheduled migration date. Last-minute changes increase the risk of errors that may be difficult to diagnose during the maintenance window. Please complete all preparation steps well in advance.

When can I make the Cloud Connector and IP Allowlist changes?

All preparation steps — adding new Cloud Foundry subaccounts and updating IP Allow Lists — can and should be completed as soon as possible. Do not wait until your migration date. Your current (NEO) configuration will remain active and fully functional until the migration cutover occurs. Making changes early reduces risk and gives you time to troubleshoot.

SAP Cloud Connector

If we are already using a Cloud Foundry environment with SAP Cloud Connector, do we still need to add the new CF subaccounts in SAP CC?

Yes, even if your current SAP Cloud Connector is connected to a Cloud Foundry subaccount, it is still necessary to add the new Cloud Foundry subaccounts. This requirement arises due to the migration of SAP Integration Suite (Managed Gateway for Spend Management) and SAP Business Network from NEO to SAP BTP Cloud Foundry (CF). It is independent of the customer’s existing Cloud Connector setup.

I used my P-user and P-user password to configure the subaccount. Is that OK?

No. You must use the One-Time Passcode (OTP) instead of the P-user password.

What should I do if I configured the subaccount using a P-user instead of the One-Time Passcode?

Delete the subaccount configuration and recreate it from scratch using the One-Time Passcode (OTP).

Why can't the P-user be used? Why must the One-Time Passcode be used? What's the difference?

• The OTP is part of SAP’s security design for onboarding Cloud Foundry subaccounts to the Cloud Connector.
• It is short‑lived, single‑use, and designed to minimize credential exposure during the trust setup.
• While it may sometimes be possible to onboard using a P‑user password, it is unsupported, increases security risks, and does not comply with SAP’s recommended security practices.
  SAP officially recommends using the OTP method only.

How do I get a One-Time Passcode (OTP)?

Follow the Steps to add cloud foundry subaccounts of Managed Gateway for Spend & Network

I see the identifier $SAP-CP-SSO-PASSCODE$ in the "Initiated By" field when using SAP Cloud Connector. Is this expected?

Yes. This is expected behavior in older Cloud Connector versions where the technical SSO passcode identifier cannot be replaced with a P-user.

What should customers do to resolve this? 

Customers are strongly advised to upgrade to the latest SAP Cloud Connector version. The upgrade provides:

• Accurate representation of initiating users (where supported)
• Improved transparency in audit and monitoring logs
• Alignment with SAP's latest security and compliance standards
• Enhanced logging, auditing, and user identification capabilities

After upgrading, customers may still need to configure users again, but the Cloud Connector will no longer reflect the passcode instead of the P-user.

My environment uses a Web Dispatcher, Load Balancer, or Gateway between the SAP Cloud Connector (SCC) and the backend SAP ERP or S/4HANA system. Are there any additional configuration steps?

We recommend consulting with the team responsible for managing your Web Dispatcher, Load Balancer, or Gateway to confirm which host value in the HTTP request header should be transmitted to the target server from the SCC. Based on this confirmation, configure the Host in Request Header field accordingly in SAP Cloud Connector > Cloud To On-Premises > System Mapping for each of the Cloud Foundry (CF) subaccounts.

When selecting Use Internal Host, the actual hostname will be used in the request header. When selecting Use Virtual Host, the virtual hostname will be used instead. In the latter case, the virtual host value is additionally forwarded via the X-Forwarded-Host header. More info refer SCC configuration guide here,  point 10.

Where can customers go to update their P-user password and when do they need to do it?

Customers can update their P‑user password by navigating to My Configurations → Authorization tab and clicking Change Password. They should only perform this action when they no longer remember their current P‑user password or must reset it for security reasons.

Important note: Changing the P‑user password in the portal should be considered a last resort. This action can disrupt production and test transactions originating from SAP ERP or SAP S/4HANA systems. To avoid integration failures or account lockouts, ensure that the new password is updated simultaneously across all connected interfaces and end systems where the P‑user is used. Alternatively, temporarily pause message transmission during the password update window.

For related configuration steps, customers can also refer to Steps to add cloud foundry subaccounts of Managed Gateway for Spend & Network. 

IP Allow Listing

How can I check if I need to update IP Allow Lists? Do I need to update IP Allow Lists? How do I know if this applies to me? 

IP allow listing updates are only required if your organization currently maintains an IP allow list. If you are unsure, check with your IT or infrastructure team before taking any action. 

Please add new Cloud Foundry IPs before migration, but keep existing Neo IPs until migration is fully completed.

Buyers

If you use SAP Cloud Connector, refer to the SCC subaccount steps for your region above. In addition, if your environment enforces IP allow listing, you must also add the new BTP Cloud Foundry IP ranges for your region. This applies whether your integration uses Cloud Connector or HTTPS-based connections (e.g., SAP PI, SAP CPI/Integration Suite, or any destination URL connecting directly to ISMG endpoints). The necessary IP details are published in the Regions and API Endpoints for SAP Cloud Foundry Environment resource.

Suppliers

If you are a supplier using SAP Integration Suite, Managed Gateway to exchange transactions with SAP Business Network, and you currently whitelist SBN or Procurement IP ranges, you must update those ranges to include the new Cloud Foundry IPs.

• Review your internal tools, applications, or servers used to send transactions to the network
• Contact your service provider if they manage your IP filtering on your behalf
• Update the IP ranges within your internal systems — no changes are needed to your Managed Gateway for Spend & Network configuration itself

Important: SAP cannot estimate all activities required within your internal organization. Please treat this guidance as a starting point and work with your IT team to confirm what is needed.

What happens if no action is taken?

Your internal systems will no longer recognize the new IP ranges and may stop accepting or transmitting data after migration. SAP Business Network will continue sending transactions as normal — but your environment will reject them if it is still relying on the old IP ranges for security checks.

Please do NOT remove any existing IPs until the migration is complete and transactions have been successfully verified.

For additional guidance: Supplier IP Allowlisting Reference | Buyer IP Allowlisting Reference | Regions and API Endpoints for SAP Cloud Foundry Environment

If you are unsure whether this applies to your setup, check with your IT/Basis team or open a case under BNS-ARI-CI-PLT-CON with your ANID and connection details.

If I use SAP S/4HANA Public Cloud. do I need to do anything regarding IP Allow Listing?

If you previously maintained an IP allowlist, ensure that the new subaccount IP ranges are included. SAP will update the KBA section on IP Allowlist Updating to help identify correct IPs per region.

If I use SAP S/4HANA Private Cloud hosted by SAP, do I need SAP to update IP Allow Listing?

Private Cloud Edition customers can restrict IPs. SAP recommends raising a PCO-OPS support ticket to confirm whether additional IPs need to be allow listed.

Should we Allow List all IPs for our region?

Yes. All entries should be included as ISMG may use additional domains in the future.

When configuring firewall rules, is the NAT IP used for inbound (ISMG to S/4) and load balancer IP for outbound (S/4 to ISMG)?

Yes. Details are available in the BTP help guide.

We already allow traffic from *.ariba.com. Is that sufficient? 

Not necessarily. Hostnames and IPs for the ISMG subaccounts are based on BTP and are different from ariba.com, so customers should review the exact IP details in the referenced migration article and validate them with their infrastructure team where needed.

What happens if I remove the old IPs before migration is complete?

Removing existing IP allow list entries before migration completion may lead to transaction failures or disruptions in communication with the Ariba Business Network.

Verification & Testing 

Is there a way to test whether the subaccount configuration is correct before the migration?

No pre-migration end-to-end testing is not available for the new ISMG subaccounts. However, you can confirm your preparation is complete by verifying:

• SAP Cloud Connector: A green "Connected" status in the Cloud Connector administration UI for each new subaccount confirms the trust relationship is established. If you keep the same Location ID and can perform a successful ping test from SCC to your backend system, the configuration is considered complete.
• IP Allow Lists: Confirm with your network/firewall team that the new Cloud Foundry IP ranges have been added and are active. Do not rely on a connectivity test to ISMG before migration — the new endpoints will not be live until the cutover.

A successful Cloud Connector connection to the new subaccounts is sufficient preparation. You do not need to wait for a transaction to confirm readiness.

I believe I have completed all required changes. How do I verify?

Use this checklist to confirm your preparation is complete:

SAP Cloud Connector (if applicable):

•  New CF subaccounts added for your region (both TEST and PROD)
•  Each subaccount shows "Connected" status in SCC admin UI
•  Correct Region used (eu10 / us10 / ae01 / cn40)
•  Same Location ID used as your current NEO configuration
•  "Cloud to On-Premises" settings replicated from existing subaccounts
•  Old subaccounts not deleted (retain until post-migration verification)

IP Allow Listing (if applicable):

•  New Cloud Foundry IP ranges added for your region (see Regions and API Endpoints resource)
•  IP allow listing updated at all relevant layers: perimeter firewall, Web Dispatcher, Load Balancer, or Gateway (if applicable)
•  Confirmed with your network team that the new IPs are active
•  Old (NEO) IPs not removed until after migration is validated

No action needed for: Integration URLs, certificates, authentication mechanisms, or functionality — none of these change.

If you have completed all items above and want SAP to confirm your readiness, open a case under BNS-ARI-CI-PLT-CON and provide your ANID, realm, or project details.

How will I know the system is back up after the migration downtime?

SAP will communicate the maintenance window start and end times via the EVB notice for your region. After the migration cutover, systems are expected to be operational after the announced window. Once the window closes, attempt a test transaction via your ERP system and monitor your integration logs for successful document exchange. If transactions are not flowing within a reasonable time after the window, log a P1 case under BNS-ARI-CI-PLT-CON.

How do I confirm success before go-live? 

A successful Cloud Connector connection to the new ISMG subaccounts is sufficient for migration preparation. Customers should also ensure that the same Location ID is retained and that Cloud to On-Premises settings are maintained.

Is there any practical check I can do?

If you keep the same LOCATION ID and can perform a ping test from Cloud Connector to your backend system, the configuration is considered done and good to go.

Post-Migration 

When can I delete my old subaccounts? 

After connecting to the new subaccounts, customers should keep the old ones until after the migration date and until they have confirmed that the transactions are flowing as expected via the new subaccounts.

When can I remove old (Neo) IPs? 

Once migration has is completed and validated, you can then safely delete the old (Neo) IP allow listing entries.

How do I confirm success after migration?

After the migration cutover, systems are expected to be operational after the announced window. Once the window closes, attempt a test transaction via your ERP system and monitor your integration logs for successful document exchange. If transactions are not flowing within a reasonable time after the window, log a P1 case under BNS-ARI-CI-PLT-CON.

Troubleshooting

“SCC handshake failed: 401 — Unauthorized” 

Create a support case under BNS-ARI-CI-PLT-CON and include the error details. This error can be associated with authorization issues when setting up or activating required subaccounts.

I used my P-user / P-account password when adding the new subaccounts. Is that OK? 

No. If you used the P-user / P-account credentials directly instead of the required one-time passcode, the setup must be redone using the one-time passcode. The P-user credentials are used to obtain the one-time passcode, which is then used to configure the subaccounts.

Do I need to install a new certificate as part of the migration? 

No. No certificate changes are required as part of this BTP Neo to Cloud Foundry migration.

We already allow traffic from *.ariba.com. Is that sufficient? 

Not necessarily. Hostnames and IPs for the ISMG subaccounts are based on BTP and are different from ariba.com, so customers should review the exact IP details in the referenced migration article and validate them with their infrastructure team where needed. 

Support (How to get help) 

Where to open a case

Open a support case under component BNS-ARI-CI-PLT-CON.

When to use high priority / P1 ticket

If an issue occurs after the migration, log a P1 case under BNS-ARI-CI-PLT-CON so Support can engage quickly.

If you want SAP to confirm your situation

To confirm whether action is required for your specific setup, open a case under BNS-ARI-CI-PLT-CON and request confirmation. When setup verification is needed, provide ANID, realm, or project details in the support case.

Additional Information

Questions?

• For assistance, contact SAP Support using the Support Hotline. We recommend opening a support ticket with the component BNS-ARI-CI-PLT-CON.

Additional Resources:

• Frequently Asked Questions
• Demos
  • How to Setup Cloud Connector
  • How to Identify my Email and Password
  • How and When to Change Password