SAP Certified Associate C_WZADM_2404 Book

Shadow users are users that are created in the SAP BTP subaccount to map the users from the connected identity provider. Shadow users are required for users to access SAP Build Work Zone. The following methods can be used to create shadow users:

Automatic creation upon login via connected identity provider: This is the recommended and default method for creating shadow users. When a user logs in to SAP Build Work Zone for the first time using an identity provider such as SAP Cloud Identity Services, a shadow user is automatically created and assigned to the role collections that are mapped to the groups attribute in the identity provider1.

Admin UI on the SAP BTP subaccount cockpit: This is a manual method for creating shadow users. An administrator can use the SAP BTP subaccount cockpit to create and manage shadow users and assign them to role collections2.

Authorization & Trust Management Service API: This is a programmatic method for creating shadow users. An administrator can use the Authorization & Trust Management Service API to create, read, update, and delete shadow users and assign them to role collections3.

The following methods cannot be used to create shadow users:

Import from SAP SuccessFactors Employee Central: This method can be used to import users from SAP SuccessFactors Employee Central to SAP Cloud Identity Services, but not to create shadow users in the SAP BTP subaccount.

CSV file upload in the SAP BTP subaccount cockpit: This method can be used to upload users and assign them to role collections in the SAP BTP subaccount, but not to create shadow users. Shadow users are created only when the users log in via the connected identity provider. References:

1: Explaining the Authentication Flow of SAP Build Work Zone

2: Assign SAP Build Work Zone Roles to Users

3: Authorization & Trust Management Service API

: Importing Users from SAP SuccessFactors Employee Central

: Uploading Users and Assigning Them to Role Collections

The SAP Build Work Zone mobile app passcode policy can be configured in the SAP BTP subaccount mobile service. This is the SAP Mobile Services instance that is used by the SAP Mobile Start app as an https endpoint for authentication and routing. It provides an Admin Cockpit that allows administrators to access logs and configure specific settings for the app, such as the passcode policy. The passcode policy determines the minimum length, complexity, and expiration time of the passcode that users mustcreate to access the app. By default, the passcode should have a minimum length of 8 digits/characters and it is possible to allow biometric authentication (for example, face ID, fingerprint) upon successful passcode creation. To access the SAP BTP subaccount mobile service, administrators need to have the MobileAdmin role assigned to them and construct the URL for the SAP Mobile Services Admin Cockpit. References:

Accessing SAP Mobile Services Settings

About the SAP Build Work Zone Advanced Mobile App

The Fit-to-Standard Analysis is a process of identifying the gaps between the customer’s business requirements and the standard SAP solutions, and determining the best way to close those gaps1. When pre-delivered content is planned to be used, such as the content packages provided by SAP Build Work Zone, some activities can help prepare the Fit-to-Standard Analysis, such as:

Expose business content: This means making the relevant business content (for example, SAP Fiori apps) available and accessible in the launchpad component of SAP Build Work Zone. This can be done by configuring the destinations, catalogs, and roles for the business content sources2. Exposing business content can help demonstrate the standard SAP solutions and evaluate their fit with the customer’s needs.

Maintain destination to SAP SuccessFactors: This means creating and configuring a destination to connect SAP Build Work Zone to SAP SuccessFactors, which is a cloud-based human resource management system. This can be done by using the SAP BTP cockpit or the SAP Cloud Connector3. Maintaining destination to SAP SuccessFactors can help leverage the pre-built content packages for SAP SuccessFactors that are available in SAP Build Work Zone, such as the Employee Onboarding package4.

The other options are incorrect because they are not related to the pre-delivered content for SAP Build Work Zone. SAP Cloud Transportation Management service and SAP IBP are different SAP solutions that are not part of the content packages for SAP Build Work Zone.

References:

Proven practices for fit-to-standard for your SAP Activate project, Section 1

Explaining the Prepare Phase, Section 2.2

Create and Configure Destinations, Section 2.1

SAP Build Work Zone Content Packages, Section 2.2

An administrative area is a designated space for subject matter experts to manage content and interact within their lines of business. Company administrators assign area administrators to administrative areas. Area administrators have a subset of company administrator capabilities to perform area-related tasks. The company area is created by default and it is the top level of the internal structure of the site. Information on the company level is visible to all users in the company. There can only be one company level. If you want to add multiple subsidiaries or business areas, you can create different administrative areas for them. References:

Administrative Areas

Area & Workspace Configuration