Configuring the Environment in a Two-System S/4HANA Cloud Landscape

Objectives

After completing this lesson, you will be able to:

  • Describe the two-system S/4HANA Cloud landscape for SAP Business Network Supplier Portal, focusing on the integration and management of business processes for efficient deployment and operation

Two System Landscape: An Overview

In this lesson, we will delve into the configuration environment of a two-system S/4HANA Cloud landscape, specifically tailored for use with the SAP Business Network Supplier Portal.

Each component in this landscape is interconnected, highlighting the integrated nature of SAP systems and the seamless flow of data and processes across different platforms and services. Understanding this environment is crucial for implementing and managing SAP Business Network Supplier Portal effectively.

The picture shows a 2-system Public Cloud landscape with additional systems like the SAP Central Business Configuration, SAP Cloud ALM and Integration Suite, Managed Gateway as well as SAP Business Network.

The 2-System Landscape (2SL) in SAP S/4HANA Cloud Public Edition refers to a simplified environment structure that consists of a Quality system and a Production system. This setup is tailored for buyers who prefer a streamlined approach to their cloud solution deployment and management. Here’s a concise overview:

  • Quality System: This environment serves as the deployment and testing ground for new configurations, customizations, and updates before they are applied to the production system. It's where all the preliminary work is done to ensure that changes will not negatively affect the production environment.
  • Production System: This is the production environment where all the business processes occur. It is the system used by the end-users for day-to-day operations.

The 2SL model offers several advantages, including:

  • Simplicity: By reducing the number of systems, SAP aims to simplify the administration and maintenance of the cloud environment for buyers.
  • Efficiency: The 2SL allows for quicker implementation and testing cycles since there are fewer systems to manage and synchronize.
  • Cost-effectiveness: With one less system to operate compared to the traditional 3-System Landscape (development, quality, production), buyers can potentially reduce their operational costs.

In this setup, we use SAP Central Business Configuration to set up our integration solution and manage the transport of objects. SAP Cloud ALM steps in to assist with managing the project effectively.

Connecting to SAP Business Network

For effective system integration and to mirror the real-world application scenarios as closely as possible, the Quality system is connected to the test SAP Business Network buyer account. This setup allows for rigorous testing and quality assurance processes without impacting the live business operations. It provides a safe environment to identify and rectify issues, ensuring that only well-tested and validated changes are moved to the production system.

Conversely, the production system is connected to the production SAP Business Network buyer account, which is the live environment. This connection is vital for the actual business transactions and operations. It ensures that all data, transactions, and processes running in the production system reflect real operational activities and interact with the live SAP Business Network ecosystem.

As middleware, we employ the Integration Suite, managed Gateway, to ease the connection between the Buyer's Backend system and the SAP Business Network, also ensuring smooth conversion between different message formats.

S/4HANA Cloud Starter System

While the buyer starts the journey inside the S/4HANA Cloud starter system, this instance is not intended to be connected to SAP Business Network. SAP S/4HANA Cloud Starter System is a preconfigured system with the enterprise scope (all lines of business enabled) and business data. Consultants use the Starter system to deliver Fit-to-Standard workshops. The Starter System is decommissioned thirty days after the provisioning of the S/4HANA Cloud Production instance.

Log in to track your progress & complete quizzes