PreBilt Standalone Edition installation

This section will explain how to install PreBilt for EWM on the PreBilt Standalone Edition (PSE) platform.

The architecture consists of three main layers.

1 - SAP EWM RF Framework

The standard SAP EWM RF framework provides the underlying applications and logic for performing the Warehouse tasks. This can include both SAP provided transactions and customer developed RF transactions.

2 - PreBilt EWM Base Framework

The PreBilt EWM Base Framework consists of a number of components.

• ICF Data Service – The main data service returns the JSON formatted templates

• Template Generation – The ABAP Dynpro screens are converted to JSON format templates using the PreBilt template generation transaction.

• Configuration Framework

  • UI adjustments – The UI configuration layer can be used to arrange fields on the screen, hide fields, change labels and more.

  • Message Overrides – Message texts and be changed in the configuration layer to be more human friendly

  • Function Code Overrides – Descriptions and sequence of Function Codes can be modified

• Additional Services

  • Additional services are provided for Gamification, Analytics, Operator Messaging.

3 - User Interface Layer

The UI layer is developed in SAPUI5. The screens are rendered at runtime by parsing the JSON returned from the main data service. This framework has been developed in a flexible way which includes an plugin layer for any custom UI requirements. The User Interface is deployed to the SAP Application server for access via a web browser. The framework includes a configuration for Capacitor to provide an Android APK for deployment to devices.

App Deployment

The front-end app data is installed locally onto the SAP server as a BSP Application under ZTCTM_FIORI. This is a custom BSP application that acts as the interface for the PreBilt application.

Once the PreBilt core EWM transport is imported into the customer backend system, the PreBilt application is ready for use by end users via mobile devices within the customer network if all relevant ICF services have been activated.

• Default Host > sap > bc > apc > tctm> ewm_push_channel (Generated APC WebSocket protocol service). Only relevant for PreBilt Operator Messaging.

• Default Host > sap > bc > bsp > sap > ztctm_fiori (TCT Mobility: EWM Fiori App)

• Default Host > tctm_ewm (TCT Mobility for EWM)

The data flows from the backend system through the ICF and BSP services to the mobile app, where transactional processing takes place, and the end user interacts with the application.

Device Deployment

Either deployed/delivered to the customer as an APK file (Android) or a PWA (Progressive Web Application- compatible on iOS devices). We can also deploy PreBilt EWM via IPA (iOS applications) but these require the customer to procure the relevant certificates.

Licenses

In the SAP system, license management is conducted at the client level, while the creation and distribution of the licenses originate from technical resources within TCT.