Minimum baseline setup

Note

Before you can access the portal your customer account must have been setup (which will need to include a valid license) and you must have been sent an invitation via email to join your team on the portal.

To access the portal go to https://admin.prebilt.cloud

Minimum required setup

The initial setup for using PreBilt requires both setup in the Admin Portal as well as some setup in your SAP system for communications, as detailed below.

You will need to do the following steps at a minimum:

• Check you have a valid license defined.

• Define an SAP environment and link it to the required API URL.

• Setup the SAP communications as supported using the wizard on the Admin Portal.

• Define the device you will use to log into the PreBilt mobile solution.

Check license

Select the "License Management" page from the left-hand navigation column and check you have an "active" license. You will not be able to create or edit you license, however you can update your company logo, if required.

Before you can use the PreBilt Mobile Solution you will need your license, as updated by a PreBilt administrator, to be active. You can continue with the portal setup without a license but you will not be able to access the mobile solution.

Define an environment

Note

You will eventually create an environment in the Admin Portal for each of SAP instances that you have, but initially you only need to set up for the environment you are starting out with, typically your "Starter" or "Development" system.

Create an environment to connect to your SAP system. Click on the “New Environment” button.

Enter the following in the popup and click on the “Create Environment” button to save:

• Name – this can be anything you want and you can change it after creation if required.

• ID – this must be unique within your customer space. It cannot be changed after creation.

• SAP System Identifier – this is to complete the API URL.

• Toggle to activate the environment that is linked to your SAP "production" environment.

Note

If you do not have the SAP System Identifier to hand, you can edit and add it to the environment at a later date. Likewise, you can activate the "Production environment" later.

Setup communications

Before you can activate PreBilt for Public Cloud you need to prepare your SAP system(s) to allow PreBilt to communicate with it.

From the Admin Portal, for a particular environment, you can follow the communications "Setup Guide" that can be accessed from the SAP System page (in the SAP Communication User section), which provides links to the relevant SAP transactions, or alternatively you can maintain each of the steps, as described here.

1

Create a communication user

Open Maintain Communication Users and create a new user.

Enter the user name and description as shown:

Set a secure password using "Propose Password" or enter your own.

Note

Copy this password — you will need it later to paste into the Admin Portal to make the connection.

2

Create a communication system

Open Communication Systems and create a new entry.

Enter the system ID and system name as shown:

Tick the Inbound Only checkbox.

In the Users for Inbound Communication tab, add the communication user you created in step 1 (PREBILT_ADMIN).

Leave all other fields at their defaults and save.

3

Create a communication arrangement

Open Communication Arrangements and create a new arrangement.

Select the scenario "SAP_COM_0A48" and enter an arrangement name by suffixing the communication name on the end, as shown below.

Select the already created Communication System from step 2, and this will also copy in the Inbound Communication User into the appropriate fields.

Check that the Authentication Method is set to "User ID and password" and save.

This links the scenario Communication Management Integration to your system and user. It's the minimum scope PreBilt's onboarding wizard needs to start. The wizard self-elevates with SAP_COM_0889 afterwards.

4

Configure CORS allowlist

The PreBilt mobile and admin apps call your SAP tenant directly from the browser. Add the PreBilt-hosted origins to the Cross-Origin Resource Sharing allowlist so the browser doesn't block them.

Open Maintain Protection Allowlists (Fiori app F3195), switch to the Cross-Origin Resource Sharing tab, and click + to add the allowed/trusted host names.

Complete the following and then select "Add".

Note

The list of trusted host names must be entered as a single string separated by commas.

For Production: enter the following domains (as a minimum) as the trusted host names into the Trusted Host Name field:

• prebilt.cloud,prerelease.prebilt.cloud

For non-production SAP systems: enter the following complete list in the Trusted Host Name field to support testing and developments:

• prebilt.cloud,prerelease.prebilt.cloud,test.prebilt.cloud,*.theconfigteam.workers.dev,localhost,127.0.0.1

• Enter the trusted host names (as shown above) as a string into Trusted Host Name field.

• Enter the following into HTTP Service Path field:

  • /sap/

• Tick all nine boxes of the Allowed Methods (GET, POST, HEAD, PUT, PATCH, DELETE, TRACE, OPTIONS, CONNECT).

• Paste the following into the Allowed Headers field:

  • origin,Authorization,x-requested-with,content-type,content-length,accept,x-csrf-token,allow-failure,if-match,odata-maxversion,odata-version

• Paste the following into the Exposed Headers field:

  • x-csrf-token,etag,odata-version,sap-authenticated,sap-server,strict-transport-security,x-content-type-options,x-xss-protection

• Tick Allow Credentials and Allow Private Network Access.

• Leave Maximum Age blank.

5

Save the communications password in the portal

In the Admin Portal, go to the SAP Communication User and save the password created in step 1.

Once the password is saved, you can then test the connection with the "Test Connection" button that will appear.

6

Run the SAP automated onboarding script

Once you have a successful connection you can run the onboarding script which will check and activate all the relevant resources to allow communication between PreBilt and SAP.

Click "Run automated setup" to let PreBilt create everything you require for communication.

Define a device

All devices which will be used to access the PreBilt for Public application, including desktop computers or laptops, will need to be defined in the portal.

Note

Currently there is no mass upload facility. This will be developed in the future.

Make sure you have selected the appropriate environment and then go to the “Devices” page.

Click on the “New Device” button to create. In the popup enter a unique Device Name and click on “Create Device”.

Note

The Device Name cannot be changed after creation.

After creating the device you can select it for login by clicking on the ellipsis menu for the particular device.

Select the “Login” option.

From there you can access the QR code or the Magic Link for the login process.

Once logged on the user of the device will be presented with the supplied baseline transactions with the baseline configuration.

If more than one WM warehouse is defined in the SAP system then the user will be forced to select one before proceeding to the baseline menu.

Note

Doing only the above basic setup (which does not include the transactions and menus setup) means that the menu and the transactions are taken from the "demo" application and so some of the default configuration may be missing or not compatible with what you have in your SAP system – for example queue names - and you cannot make any transaction configuration updates. To make configuration changes, load the out-of-the-box transactions and the out-of-the-box menu in the required environment as detailed in the Admin Portal operational setup page.