SAP Knowledge Base Article - Public

3012238 - FAQ: SAP S/4HANA / Marketing Cloud Converged Cloud Migration

Symptom

You have questions related to the SAP S/4HANA Converged Cloud Migration,

  1. Why is the SAP S/4HANA/Marketing Cloud system moving within/to CCloud?
  2. Are the Converged Cloud Datacenters Security Compliant?
  3. Is re-scheduling of the migration allowed?
  4. Will there be any downtime associated with the migration?
  5. Are there any actions required by the customer to support the migration?
  6. Does the migration impact transports?
  7. Would the SAP S/4HANA/Marketing Cloud Tenant URL change?
  8. Is there an impact on any Integrations such as Co-Pilot, IAS/IDP, SDI, JAM, etc.?
  9. Would there be an impact on my current explicitly allowed IPs configuration?
  10. Is there anything else changing with this migration?
  11. Who do I contact for any questions related to the Converged Cloud Migration?

Environment

  • SAP S/4HANA Cloud Public Edition
  • Migration within Converge cloud 

Resolution

1) Why is the SAP S/4HANA/Marketing Cloud system moving within/to CCloud?

To Leverage infrastructure resources

2) Are the Converged Cloud Datacenters Security Compliant?

Yes, Converged Cloud Datacenters are Security Certified (IS27001 and SOC) and all the certifications are available in SAP Trust Center portal link.

3) Is re-scheduling of the migration allowed?

Re-scheduling should be avoided as we expect no business impact on account of this activity. Since we are migrating your S/4HANA / Marketing Tenant during the Week-End Maintenance Window.

4) Will there be any downtime associated with the migration?

Downtime is expected to be completed in Week-End Maintenance Window.

5) Are there any actions required by the customer to support the migration?

In case you have configured any allowed IP list on your side for the S/4 HANA /Marketing Cloud URL connectivity, please also add the network range to the allowed list.

In case you do not configured any allowed IP list previously for the S4/HANA Cloud systems no action is required from your side

Location

Subnet IP

European Union

130.214.228.128/26, 130.214.193.0/27,
130.214.193.128/27, 157.133.160.192/26,
155.56.128.192/28, 157.133.170.128/26,
130.214.193.232/29, 130.214.145.32/29, 130.214.162.40/29, 130.214.145.40/29

US (S4)

130.214.242.128/26, 157.133.166.128/26, 130.214.243.232/29, 130.214.243.224/29

US (HMC)

130.214.243.192/27, 130.214.242.128/26, 157.133.166.128/26

American Samoa, Australia, Cook Islands, Fiji, Micronesia, Guam, Kiribati, Marshall Islands, North Mariana Islands, New Caledonia, Nauru, Niue, New Zealand, French Polynesia, Papua New Guinea, Palau, Solomon Islands, Tokelau Islands, Timor, Tonga, Tuvalu, Vanuatu, Wallis and Futuna Islands, Samoa

157.133.168.192/28, 157.133.168.224/27, 130.214.240.192/29

Nepal, Philippines, Pakistan, Singapore, Thailand, Tajikistan, Taiwan, Vietnam, South Korea, Laos, Sri Lanka, Myanmar, Mongolia, Macao, Maldives, Malaysia, Bhutan, Indonesia, India, Japan, Kyrgyzstan, Cambodia, North Korea, Afghanistan, Bangladesh, Brunei Darussalam

157.133.182.128/26, 130.214.244.128/26, 130.214.246.128/26, 130.214.245.104/29

China

157.133.186.128/26, 121.91.104.96/29, 121.91.104.112/28

Canada

130.214.238.128/26, 130.214.238.8/29
Saudi Arabia 130.214.222.128/26
UAE 130.214.250.128/26, 130.214.251.168/29

6) Does the migration impact transports?

There is no impact on transports.

7) Would the SAP S/4HANA/Marketing Cloud Tenant URL change?

No, the URL would remain the same after Migration.

8) Is there an impact on any Integrations such as Co-Pilot, IAS/IDP, SDI, JAM, etc.?

Integration scenarios which are not connecting through SAP Managed Middleware (ex. – Hosted on SCP{Co-pilot,IAS/IDP, etc.},Digital Interconnect, etc.), please update allowed IP list with below IP ranges on target system/network. Target system defined as a system/network which is outbound for S/4 HANA /Marketing Cloud system.

Location

Subnet IP

European Union

130.214.228.32/27, 157.133.160.32/27,
130.214.226.32/27, 157.133.170.32/27,
130.214.230.32/27

US (S4)

130.214.242.32/27, 157.133.166.32/27, 130.214.234.32/27

US (HMC)

130.214.242.32/27, 157.133.166.32/27, 130.214.234.32/27

American Samoa, Australia, Cook Islands, Fiji, Micronesia, Guam, Kiribati, Marshall Islands, North Mariana Islands, New Caledonia, Nauru, Niue, New Zealand, French Polynesia, Papua New Guinea, Palau, Solomon Islands, Tokelau Islands, Timor, Tonga, Tuvalu, Vanuatu, Wallis and Futuna Islands, Samoa

157.133.168.32/27, 130.214.240.32/27

Nepal, Philippines, Pakistan, Singapore, Thailand, Tajikistan, Taiwan, Vietnam, South Korea, Laos, Sri Lanka, Myanmar, Mongolia, Macao, Maldives, Malaysia, Bhutan, Indonesia, India, Japan, Kyrgyzstan, Cambodia, North Korea, Afghanistan, Bangladesh, Brunei Darussalam

157.133.182.32/27, 130.214.244.32/27, 157.133.184.32/27, 130.214.246.32/27

China

157.133.186.32/27, 130.214.218.32/27
Canada 157.133.176.32/27, 130.214.238.32/27
Saudi Arabia 130.214.222.32/27
UAE 130.214.250.32/27

9) Would there be an impact on my current explicitly allowed IPs configuration?

No impact for the allowed IP list that is implemented at SAP side, however the customers who have allowed the S/4HANA /Marketing Cloud Instance Public IP on their side, would have to adapt to new public IP.

Location

Subnet IP

European Union

130.214.228.128/26, 130.214.193.0/27, 130.214.193.128/27, 157.133.160.192/26, 155.56.128.192/28, 157.133.170.128/26, 130.214.193.232/29, 130.214.145.32/29, 130.214.162.40/29, 130.214.145.40/29

US (S4)

130.214.242.128/26, 157.133.166.128/26, 130.214.243.232/29, 130.214.243.224/29

US (HMC)

130.214.243.192/27, 130.214.242.128/26, 157.133.166.128/26

American Samoa, Australia, Cook Islands, Fiji, Micronesia, Guam, Kiribati, Marshall Islands, North Mariana Islands, New Caledonia, Nauru, Niue, New Zealand, French Polynesia, Papua New Guinea, Palau, Solomon Islands, Tokelau Islands, Timor, Tonga, Tuvalu, Vanuatu, Wallis and Futuna Islands, Samoa

157.133.168.192/28, 157.133.168.224/27, 130.214.240.192/29

Nepal, Philippines, Pakistan, Singapore, Thailand, Tajikistan, Taiwan, Vietnam, South Korea, Laos, Sri Lanka, Myanmar, Mongolia, Macao, Maldives, Malaysia, Bhutan, Indonesia, India, Japan, Kyrgyzstan, Cambodia, North Korea, Afghanistan, Bangladesh, Brunei Darussalam

157.133.182.128/26, 130.214.244.128/26, 130.214.246.128/26, 130.214.245.104/29

China

157.133.186.128/26, 121.91.104.96/29, 121.91.104.112/28
Canada 130.214.238.128/26, 130.214.238.8/29
Saudi Arabia 130.214.222.128/26
UAE 130.214.250.128/26, 130.214.251.168/29

10) Is there anything else changing with this migration?

No. Other attributes like SLAs, Contractual Clauses, Support Services, Service Catalogues, SLM (Hotfix & Release Upgrades) process etc. remains same.

11) Who do I contact for any questions related to the Converged Cloud Migration?

If you have any further questions, please create a ticket into XX-S4C-OPR-INC component.

Keywords

configured any allowed IP list , KBA , XX-S4C-OPR-INC , S/4HANA Cloud Availability, Performance and Administration , How To

Product

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions