> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-ewm/configuration-guide/configuring-prebilt-features/communication-hub/communication-hub-1.md). # BC Set Installation Steps Communication Hub {% hint style="danger" %} **NOTE:**\ Using BC Sets to configure features is only available for demonstration system setup by TCT Partners. It should not be used for full system configuration. {% endhint %} ## Applying the BC set {% hint style="warning" %} **Prerequisite** Ensure that a custom monitor is created beforehand, as it is required to associate with the BC Set activation. {% endhint %} {% hint style="info" %} If you have **NOT** been provided with a BC Set, please complete the installation manually by following the [Manual Installation Steps](/prebilt-ewm/configuration-guide/configuring-prebilt-features/communication-hub/communication-hub.md) {% endhint %} #### Activating the BC Set {% hint style="info" %} To download the Partner BC Sets, please use the following link: [BC Sets Download](https://portal.theconfigteam.co.uk/fs/288a1ec5993040c48cdaeb112935f3d0). If you have not been provided with a Password, please contact TCT. When activating BC Set ZTCTBCSETCH, input the values relevant to your setup. {% endhint %}

{% hint style="info" %} **NOTE:** After activating the BC Set, review the activation logs to confirm that the BC Set was activated successfully. {% endhint %}

#### Custom Monitor View The result should look something like the example below.

Define Messaging in Warehouse Monitor Tree

### Operator Groups - /TCTM/EWM\_OPGRP {% embed url="" %} {% hint style="info" %} **Note** Operator Groups must be configured in all environments and clients throughout the project. {% endhint %} Users to be grouped into Operator Groups for the purpose of sending messages. These could be shift groups or supervisor/manager groups. They can be used in the following contexts: * Assigned as a receiver when sending a message from the Warehouse Monitor. * Assigned as a receiver within a messaging type. This applies for operator to operator messages. Operator Groups are defined at the warehouse level

Members assigned are SAP users. For example:

{% hint style="info" %} **NOTE** It is necessary to apply filter conditions to BAdI implementation `ZTCTM_EWM_SRV_OM_NOTIF_MSTEAMS` to control when this implementation should be executed. Without this filter, the Operator Messaging process will not generate messages correctly, resulting in * No messages appear in the EWM Monitor * No notifications are being passed through to PreBilt for delivery Create the following Filter Value within Enhancement Implementation: `ZTCTM_EWM_SRV_OM_NOTIF_MSTEAMS`

{% endhint %} ### Operator Messaging Data - /TCTM/EWM\_OMCFG {% embed url="" %} {% hint style="info" %} **Note** Operator Messaging Data must be configured in all environments and clients throughout the project. {% endhint %} Messaging types define and control the content of messages sent from mobile devices. Below are examples of message types and their corresponding structure configurations:

Selected Messaging Type	Field Name	Sequence	Field Type	Field Description
Selected Messaging Type	Field Name	Sequence	Field Type	Field Description
ACCIDENT	COMMENTS	040	TEXTAREA	Additional comments
ACCIDENT	DESCRIPTION	030	TEXTAREA	Detailed Description
ACCIDENT	LOCATIONS	020	SELECT	Location
ACCIDENT	REPORT_STATUS	050	CHECKBOX	Send me status notifications
ACCIDENT	URGENCY	010	RADIOBUTTON	Urgency
BREAKREQ	COMMENT	010	TEXTAREA	Comment
CLEANINGRE	COMMENTS	002	TEXTAREA	Comments
CLEANINGRE	LOCATION	010	COMBOBOX	Location
OTHER	COMMENT	010	TEXTAREA	Details
RESOURCE_R	ACTIVITY	010	SELECT	Activity
RESOURCE_R	COMMENTS	050	TEXTAREA	Additional Comments
RESOURCE_R	EQUIPMENT	030	CHECKBOX	FLT Required
RESOURCE_R	EQUIPMENT2	035	CHECKBOX	Supervisor Required
RESOURCE_R	EQUIPMENT3	040	CHECKBOX	Workers Required
RESOURCE_R	LOCATION	020	RADIOBUTTON	Location

#### Parameters

Selected Messaging Type	Selected Field Name	Field Parameter Type	Param Seq	Field Parameter Value	Translatable Field Parameter Value
Selected Messaging Type	Selected Field Name	Field Parameter Type	Param Seq	Field Parameter Value	Translatable Field Parameter Value
ACCIDENT	LOCATIONS	SELECT_ITEM	001	AISLE01	Aisle 01
ACCIDENT	LOCATIONS	SELECT_ITEM	002	AISLE02	Aisle 02
ACCIDENT	LOCATIONS	SELECT_ITEM	003	AISLE03	Aisle 03
ACCIDENT	LOCATIONS	SELECT_ITEM	004	AISLE04	Aisle 04
ACCIDENT	URGENCY	RADIO_BTN_ITEM	001	CRITICAL	Critical
ACCIDENT	URGENCY	RADIO_BTN_ITEM	002	HIGH	High
ACCIDENT	URGENCY	RADIO_BTN_ITEM	003	NORMAL	Normal
ACCIDENT	URGENCY	RADIO_BTN_ITEM	004	LOW	Low
CLEANINGRE	LOCATION	COMBOBOX_ITEM	001	FREEZER	Freezer
CLEANINGRE	LOCATION	COMBOBOX_ITEM	002	PICKFACE_AMB	Pickface Ambient
CLEANINGRE	LOCATION	COMBOBOX_ITEM	003	DECON	Deconsolidation Area
CLEANINGRE	LOCATION	COMBOBOX_ITEM	004	TOILET	Toilets
RESOURCE_R	ACTIVITY	SELECT_ITEM	000	Picking	Picking
RESOURCE_R	ACTIVITY	SELECT_ITEM	001	Packing	Packing
RESOURCE_R	ACTIVITY	SELECT_ITEM	002	Replenishment	Replenishment
RESOURCE_R	ACTIVITY	SELECT_ITEM	003	Physical Inventory	Physical Inventory
RESOURCE_R	EQUIPMENT	SELECT_ITEM	000	HHT	Handheld Terminal
RESOURCE_R	EQUIPMENT	SELECT_ITEM	001	FLT	Forklift Truck
RESOURCE_R	EQUIPMENT	SELECT_ITEM	002	RT	Reach Truck
RESOURCE_R	EQUIPMENT2	SELECT_ITEM	000	HHT	Handheld Terminal
RESOURCE_R	EQUIPMENT2	SELECT_ITEM	001	FLT	Forklift Truck
RESOURCE_R	EQUIPMENT2	SELECT_ITEM	002	RT	Reach Truck
RESOURCE_R	EQUIPMENT3	SELECT_ITEM	000	HHT	Handheld Terminal
RESOURCE_R	EQUIPMENT3	SELECT_ITEM	001	FLT	Forklift Truck
RESOURCE_R	EQUIPMENT3	SELECT_ITEM	002	RT	Reach Truck
RESOURCE_R	LOCATION	RADIO_BTN_ITEM	020	Receiving	Receiving Area
RESOURCE_R	LOCATION	RADIO_BTN_ITEM	030	Dispatch	Dispatch Area
RESOURCE_R	LOCATION	RADIO_BTN_ITEM	040	Inspection	Inspection Area

The Message Type Description is displayed in the first drop down after selecting the message icon and **New Message** in PreBilt.

The ‘Importance’ selection influences the icon displayed when messages are viewed within PreBilt. In the example below, a message designated as ’Important’ will display with an orange “X” icon in PreBilt.

Full importance-icon determination is: | **Importance** | **App Icon** | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | General | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-04e6b6a210629ae4261dadb97627691d57b709b8%2Fgeneral%20info%20icon.png?alt=media) | | Warning | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-73e67757d0f9cc6f5aea10ca7a4d66bf4362b36a%2Fwarning%20icon.png?alt=media) | | Question | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-24fb54e3602b20375dabc97bac67b200f40dffd3%2Fquestion%20icon.png?alt=media) | | Information | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-04e6b6a210629ae4261dadb97627691d57b709b8%2Fgeneral%20info%20icon.png?alt=media) | | Important | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-d71dd1f5d76c19e7c5052239fa1cf9aa6f1345ce%2Fimportant%20icon.png?alt=media) | Receivers must be defined in the standalone dialog structure prior to their assignment to a messaging type. Receivers (Operator Messaging – Receiver) can either be SAP users or Operator Groups. If an Operator Group is added as a receiver, determination for the Operator Group will happen automatically and any messages will be received by all members of that Operator Group. * “Type” will be used for additional receiver types in a future release. * “… Receiver Data” is a description field.

Receivers defined in the standalone dialog structure can then be assigned to messaging types. This influences the distribution of operator to operator messaging. When sending messages from the warehouse monitor, the receivers must be assigned. If a message is not intended for operator to operator messaging, a non RF user should be specified.

In the Fields master data: * Field Name acts as the key field * Sequence is the sort order ascending as displayed in the app * Field Type is the field type / input type * Field Description is displayed as the field header in the app An example of the master data setup and corresponding app display is demonstrated below.

For Field Parameters: * The Field Parameter Type and Param Seq act as key fields. * The Param Sequence is the sort order ascending as displayed in the app. * The Translatable Field Parameter Value is displayed as the description in the app. The corresponding Field Parameter setup for the above app screenshot is displayed below as an example.

{% hint style="info" %} **Note** For checkboxes, no field parameters are required, each required Checkbox should have its own “Fields” entry. An app screenshot example is displayed below for the corresponding Field display setup at the top of this section. {% endhint %}

### Operator Messaging Execution - Warehouse Monitor {% embed url="" %} Operator Messaging within the Warehouse Monitor is accessed through its own node, “Messages”. Navigation & user experience is consistent with standard Warehouse Monitor features, with a selection screen, the ability to set selection and display variants etc.

For sending messages to operators from the Warehouse Monitor, the following features are worth highlighting: * The “Message Sender” will default to the user logged in but can be overridden with free text. * Message Importance influences the icon displayed next to the message on an operator's mobile device as in the below table: | **Importance** | **App Icon** | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | General | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-04e6b6a210629ae4261dadb97627691d57b709b8%2Fgeneral%20info%20icon.png?alt=media) | | Warning | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-73e67757d0f9cc6f5aea10ca7a4d66bf4362b36a%2Fwarning%20icon.png?alt=media) | | Question | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-24fb54e3602b20375dabc97bac67b200f40dffd3%2Fquestion%20icon.png?alt=media) | | Information | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-04e6b6a210629ae4261dadb97627691d57b709b8%2Fgeneral%20info%20icon.png?alt=media) | | Important | ![](https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-d71dd1f5d76c19e7c5052239fa1cf9aa6f1345ce%2Fimportant%20icon.png?alt=media) | * If a response required is checked, **Answer editable** (by mobile device user) and **Answers** become available as input options. * For receivers, SAP Users as well as Operator Groups defined in `/TCTM/EWM_OPGRP` can be specified. If an Operator Group is used, this will automatically be identified and the message will be sent to all associated members.

Send message dialog window – Warehouse Monitor

For sent messages, the **Recipients** button will display read receipt and response data (where applicable) by user.

Sent message recipient data – warehouse monitor

### Operator Messaging Execution - Mobile Devices {% embed url="" %} If a message is received from the Warehouse Monitor, a red notification icon will appear next to the message icon (highlighted below). Note, operator to operator messages will not trigger a notification to minimise disruption.

When the operator receives a message from a desktop user requiring a response, if there are two options, these will display as radio buttons. If more than two response options, these will display as a drop down list. The tick box icon highlighted below must be pressed to confirm the response.

When confirmed, the reply inputs will be grayed out. If the message from the monitor was sent with **Answer editable** checked, a pencil icon will appear where the operator can modify their response.

In app confirmed message response & edit icon

For operators to send messages, the Message Type option can be selected in New Messages. Details can then be input in accordance with the Operator Message Master Data setup (`/TCTM/EWM_OMCFG`). The receivers defined in the Master Data setup only influences the receipt of messages between operators. All message data is visible for desktop users in the Warehouse Monitor.

In the example above, when the operator presses submit a confirmation pop up appears on screen and sent messages are displayed in message history.