EWM RFUI requirements

Maintain Display Profile Settings

To generate a display profile, please refer to the backend installation. Once created, the Display Profile can be configured to your needs.

• Screen size – use 8x40 (standard display profile) as a starting point. This does not affect or limit the actual screen size used in PreBilt for EWM. Screen field lengths and positioning can be changed as required in the PreBilt customising toolkit.

• Push button quantity – this will define the maximum number of buttons displayed on each screen. PreBilt for EWM adheres to this setting to display push buttons at the bottom of the screen. Push buttons are only displayed if assigned to the Function Code Group Sequence 01 in the standard RF customising. All buttons exceeding this number can be accessed from the three-dot menu on the bottom left of any screen, which displays all available functions.

• Template location – use TCT template function group /TCTM/EWM_UI_TEMPL with screens 1000 and 1001. These screens contain the required PBO/PAI routine calls for PreBilt for EWM.

• Function group for sub-screens – do not not create sub-screens and/or step-screens (if this is an option in your EWM release).

Display Profile settings

The Display Profile Setting Node in transaction /TCTM/EWM_CUST enables the default setting of text style, sizes and colours for labels and values. These will apply where no field specific setting is applied in /TCTM/EWM_CFG, any field specific setting applied in /TCTM/EWM_CFG will override the display profile level setting.

The Frontend Data I/O Class and Generator Class references are used for Voice integrations.

For a given Display Profile level, it is possible to define additional CSS Styles which can then be defined in transaction /TCTM/EWM_CFG, providing additional flexibility to the screen design beyond the default options (Some CSS experience is required). As examples, additional font styles can be used other than bold or italic, or CSS references can be used for colours instead of hex codes. To do this, in the CSS Style sub node, create a ”CSS Style” (the CSS Style is free text which can then be referenced in both the default Display Profile Settings in transaction /TCTM/EWM_CUST and the /TCTM/EWM_CFG field level customizing).

Then under the Definitions sub node, the actual CSS Style is applied.

Create EWM RF application parameter

This step should already be completed as part of the PreBilt installation.

In transaction SPRO under the EWM customising node SCM Extended Warehouse Management > Extended Warehouse Management > Mobile Data Entry > Radio Frequency (RF) Framework > Define Steps in Logical Transactions, ensure RF Application Parameter TCTM_UI_DATA is created with Parameter Type = /TCTM/EWM_S_RF_UI_DATA.

Presentation Device

A Presentation Device for each device type must be created in transaction /SCWM/PRDVC, such as ZV01 or ZV02, then assigned to the relevant Display Profile.

Automatic assignment of Presentation Device

If automatic logon is not set up for a user in transaction /SCWM/USER, the standard RF resource logon screen is displayed upon signing in.

This screen requires the selection of the warehouse (if not defaulted in /SCWM/USER), the resource (if not defaulted in /SCWM/USER) and the Presentation Device (if not defaulted in /SCWM/RSRC).

However, if the same resource in a warehouse uses different types of devices (e.g. handheld, vehicle-mounted, voice) and is constantly switching between them, the Presentation Device must be manually selected in this logon screen each time. Entering an incorrect and unexpected presentation device for the type of device being used may result in runtime errors or an undesirable user experience. To help prevent this, the Presentation Device can be defaulted in the PreBilt app when deploying to a particular device. Please refer to the PreBilt technical deployment guide for the relevant platform for further details.

The Presentation Device assignment is supported in all of these scenarios:

• During app build time (e.g. Capacitor, Mendix, Movilizer, Neptune, Fiori)

• As part of Launchpad/Mobile Client header (Platform: Neptune)

Presentation Device determination

The Presentation Device Node in transaction /TCTM/EWM_SETTINGS enables Display Profile determination for a given Presentation Device. Below is an example of a PreBilt override only (/SCWM/PRDVC entries still required) which is useful if:

• There is a need to test or run a more typical ITS service in parallel.

• Multiple Device Nodes are required, such as combining screen and voice. This is set via the “TCT Mode” option (selection help available).

Extended Presentation Device determination

The Extended Presentation Device Determination Node in transaction /TCTM/EWM_SETTINGS enables further determination, so a Personalisation Profile and main menu Logical Transaction can be assigned based on one or more of the following:

• SAP User

• Warehouse

• Resource Group

• TCT Mode

For example:

Toggling display of the Function Key quantity

Depending on the device being used, the Function Key number associated with a displayed function code can be hidden on the main screen. It can be removed with the Standard configuration in Presentation Device setup.

Set Qty = ‘ ‘ (blank) to remove the function codes from the push buttons in the screen.

The function codes assigned with a push button in the first (01) function code group of the step are displayed.

Device sounds

Device sounds are used in the RFUI to provide audible feedback to warehouse workers during various processes. This can enhance user experience and increase efficiency, especially in environments where visual attention may be limited.

This helps to notify users about specific events or actions such as confirmations, errors and important messages. Common triggers for device sounds include information alerts, errors & warnings.

Device sounds settings can be found in transaction code /SCWM/PRDVC

Changing the “ErrorSound” values will call a different error message sound.