Explaining the Planning Landscape for SAP Build Work Zone

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Identify the key considerations for the design of IT landscape for SAP Build Work Zone
  • Identify how various content can be transported across IT landscape with SAP Build Work Zone

Key Considerations for the Design of IT Landscape for SAP Build Work Zone

Watch the following video to learn about the key considerations for the design of IT landscape for SAP Build Work Zone.

Note

Since SAP Build Work Zone and SAP SuccessFactors Work Zone are both SAP BTP services, they follow all design principles, guidelines, and best practices for SAP BTP. In regards IT landscape, it’s recommended to read Account Models with Subaccounts at SAP Help Portal: it explains different design patterns how subaccounts can be organized.

Let’s stop on the last question. SAP Build Work Zone has two components allowing to work with business applications and information: Digital Workplace Service (DWS) and launchpad. :

Transport of Content

Watch the following video to learn about SAP Cloud Transport management service.

Nowadays companies have a lot of different on-premise and cloud solutions with various recommended deployment models. As a result, there might be situations of a so-called uneven IT landscape. Below is an example of such an uneven IT landscape:

  • 4-tier landscape for SAP S/4HANA system.
  • 2-tier landscape for SAP IBP system.

The obvious question is how many tenants (SAP BTP subaccounts) does one need for SAP Build Work Zone — two or four? The rule of thumb is to align IT landscape for SAP Build Work Zone with core business system: if SAP S/4HANA system is primary business system in landscape, then SAP Build Work Zone needs 4-tier landscape. The same rule works for SAP SuccessFactors Work Zone (but with focus on SAP SuccessFactors system as primary one).

Save progress to your learning plan by logging in or creating an account