Explaining the Prepare Phase

In the Prepare phase, there are a core set of activities that must take place at the start of the project, outlined below.

Watch the following video to learn about the Prepare phase.

Let's walk through and understand some of the tasks that are to be considered when focusing on SAP Build Work Zone.

HXM content should be enabled and usable:

• Destinations back to SAP SuccessFactors maintained.
• Demo home pages and workspaces with focus on HXM created.

The same is relevant for Content Federation.

• Backend systems (for example, SAP S/4HANA or SAP Integrated Business Planning) with business content connected to SAP BTP.
• Business content (for example, SAP SAP Fiori apps) exposed, set up, and consumed in launchpad component of SAP Build Work Zone.
• Optionally demo home pages and workspaces with business content created.

These steps help to prepare for and conduct the Fit-to-Standard Analysis during the next phase.

The additional (and SAP Build Work Zone independent) information about tasks and accelerators for Prepare Phase can be also found at SAP Activate Roadmap Viewer.

In contrast to other SAP BTP offerings, it's not enough just to create a subscription in SAP BTP subaccount. Both SAP Build Work Zone and SAP SuccessFactors Work Zone have a dedicated onboarding procedure to implement certain prerequisites and configuration steps before and after creating the subscription. The onboarding procedures for SAP Build Work Zone and SAP SuccessFactors Work Zone are documented on SAP Help Portal.

Note

It is not recommended to enable subscription for SAP Build Work Zone or SAP SuccessFactors Work Zone in SAP BTP subaccount manually. SAP strongly recommends following onboarding procedures to complete initial configuration.

The onboarding procedure for both SAP Build Work Zone and SAP SuccessFactors Work Zone consists of four steps.

The starting point, is to check and implement any listed prerequisites for SAP Build Work Zone. Besides the availability of an SAP BTP subaccount, it is necessary to set up at least the project-specific identity and access management. Note that the information available on the SAP Help Portal covers the standard scenario for this utilizing SAP Cloud Identity Services, Identity Authentication, as primary engine for user authentication in SAP Build Work Zone. It is possible to have more complicated security infrastructure with third party Corporate Identity Provider (IdP) (for example, Microsoft Azure or Ping Identity), but it should be designed and configured by security architects and consultants separately. In addition, it is necessary to migrate SAP Jam to ondemand.com domain if the scope of the project includes the migration from SAP Jam to SAP Build Work Zone or SAP SuccessFactors Work Zone.

Note

It is recommended to disable Default Identity Provider (sap.default) in SAP BTP subaccounts where SAP Build Work Zone is used. It cannot be used because SAP Build Work Zone requires additional IAS and IPS configuration. The required configuration cannot be done for Default Identity Provider (sap.default).

The next step in the onboarding procedure is running the so-called Booster for SAP Build Work Zone or SAP SuccessFactors Work Zone.

Note that they have different Boosters. It is executed from the SAP BTP global account and it is necessary to have respective authorizations. The booster helps scope and enable necessary subscriptions and services in the selected SAP BTP subaccount, generate destinations, create role collections, and so on. For instance, it is not required to enable SAP Business Application Studio in SAP BTP non-development subaccounts.

When the execution of the selected Booster is completed, it might still be required to perform some manual configuration activities (not covered by the Booster). These steps fall under the post-Booster section. It includes, but is not limited to:

• Provisioning Identity Provisioning service (IPS) bundle tenant mapped with Identity Authentication service (IAS) tenant, if the service is not yet available. The information about relevant IAS tenant is obtained from Trust Configuration from SAP BTP subaccount where SAP Build Work Zone subscription enabled.
• Upgrade IPS bundle tenant to include the SAP Build Work Zone bundle.

Note

When there is no SAP Build Work Zone bundle activated in IPS standalone tenant, it is not possible to set up SAP Build Work Zone as the Target System for user provisioning. Meanwhile, from March 15th, 2022, IPS tenants created on the infrastructure of SAP Cloud Identity Services come with all required bundles enabled.

The last step covers the execution of Work Zone Configurator. This wizard belongs to the SAP Build Work Zone subscription and is part of launchpad component. It helps to complete application-specific configuration steps, for example, setup user provisioning to Digital Workplace Service (DWS) component of SAP Build Work Zone with SAP Cloud Identity Services, Identity Provisioning service (IPS).

Keep in mind that user provisioning to DWS is driven by overall corporate security architecture. It is not mandatory to use SAP Cloud Identity Services, Identity Authentication service (IAS), as source system for user records. They can also be provisioned from SAP SuccessFactors or Microsoft Azure AD.

If everything is configured properly and users are provisioned with correct roles, administrators should be able to find menu item, Administration Console in their user menu, as shown in the graphic above.