Requirements, prerequisites & assumptions

Note

Before you can start with your PreBilt for Public Cloud setup you must be registered on the system with a customer or partner account and be setup via email invitations as a PreBilt administrator.

Requirements

• SAP S/4HANA Public Cloud (active tenant).

• Configuration of the appropriate business processes for warehousing, inventory, etc. in SAP S/4HANA Cloud Public Edition with SAP Central Business Configuration.

• SAP Cloud Identity Services for authentication (if used).

• Access to maintain authorisation roles for API permissions.

• Access to maintain communication arrangements and CORS settings.

Prerequisites

WM Setup

In your WM setup you need to have defined the following:

• Suitable SAP warehouse structures.

• Defined queues in the warehouses.

• Maintained resource groups.

• Defined queue sequence.

• Assigned resources to resource groups.

SAP Authorisations

In order to use PreBilt, the users will need to have appropriate authorisations with appropriate business roles that give access to the Business Catalog IDs that provide access to the appropriate API’s and permissions needed to allow the users to communicate back and forth between PreBilt and SAP.

PreBilt communicates with SAP S/4HANA Cloud Public Edition through the use of API’s. Authentication is done using OAuth 2.0 details that are configured to grant Scope ID access. This access is granted at the Business Catalog / Business Catalog ID level. The Business Catalog is asssigned to a Business Role which in turn is assigned to the Business User.

• Business Catalog ID = collection of apps, API’s and permissions. Essentially a set of capabilities.

• Business Role = collection of catalogs + restrictions. Essentially representing a job (Warehouse Operator, Product Specialist).

• Business User = person accessing system via PreBilt.

Currently we use up to eight business catalogs to grant OAuth2.0 scope access to the API’s in the communication arrangements required to allow full PreBilt functionality.

Business Catalog	Business Catalog ID
Logistics Execution - Inbound Delivery API	SAP_LE_BC_ID_API_PC
Logistics General - API Packing Instruction	SAP_LO_BC_API_PACKGINSTRN_PC
Sales - Sales Order Processing	SAP_SD_BC_SO_PROC_MC
Master Data - Product Master	SAP_CMD_BC_PR_MAINT_PC
LO - API Handling Unit	SAP_LO_BC_API_HNDLGUNIT_PC
WM - External APIs	SAP_SCM_BC_EWM_API_PC
Materials Management - Material Document API	SAP_MM_BC_IM_MAT_DOC_API_PC
Materials Management - Purchase Orders	SAP_MM_BC_PO_MANAGE_PC

Note

SAP does allow the use of the following two business catalog IDs without the need to consume a "core" SAP license:

• SAP_SCM_BC_EWM_API_PC

• SAP_LO_BC_API_HNDLGUNIT_PC

Stock Enquiry transaction uses the business catalog ID SAP_CMD_BC_PR_MAINT_PC but that can be setup in the roles to be "read only" and as such will not require a "core" license.

However, if you are using any of the following transactions / processes, then these do use other business catalog IDs and as such will require a "core" SAP license:

• Inbound serial number capture

• Purchase order receiving

• Packing

Device requirements

• Android or iOS devices.

• Supported enterprise scanning hardware.

Assumptions

• Network/WiFi coverage is appropriate for warehouse usage.

• Certain elements remain the customer’s responsibility within SAP, such as roles, communication arrangements, and allowlists.

• SAP must allow the operational behaviour that PreBilt has been designed to perform.