Backend installation

Importing transports

TCT will provide you a PreBilt for EWM transport as a zip file. Please coordinate with your SAP Basis team to get the transport imported before any subsequent installation/customisation steps can be performed.

Because every SAP landscape is setup differently, specific import procedures will have to be discussed with your SAP Basis team and no detailed procedure can be given here.

TCT has SAP Basis specialists that can help you in case of questions or concerns.

Basis post-import activities

Prerequisite

This section assumes a certain familiarity with ABAP Development.

1

Activate flow BAdIs in SE18

Create BAdI implementation for /SCWM/EX_RF_FLOW_POST and /SCWM/EX_RF_FLOW_PRE with class /TCTM/EWM_FLOW_BADIS.

You should use the same Enhancement Implementation for this.

Any pre-existing customer implementation should be moved in to a new BAdI implementation for BAdI /TCTM/EX_EWM_RF_FLOW_POST (same interface as the SAP standard one, so existing customer class can be reused).

2

Activate TCTC RFUI BAdI for TCTM

Create a BAdI Implementation for /TCTC/EX_EWM_RFUI_GET_MANAGER using implementation class /TCTM/EWM_MANAGER.

3

Activate SICF nodes

In transaction SICF, search for all TCTM nodes.

Activate all them, including sub-nodes.

When prompted to confirm, use the Yes including subnodes button.

4

SSO RZ11 configuration

To use the ITS mobile login across other services, the system’s configuration must have the following two RZ11 parameters set:

• login/accept_sso2_ticket = 1

• login/create_sso2_ticket=2

5

Add Template Generators for PreBilt ITS templates

In transaction SM30, maintain table W3GENSTYLES.

Add an entry such as this:

To create this entry, you can copy and paste:

ZITSTCTM /TCTM/EWM_GENERATE_HTML TCT Mobility Templates for EWM

Create a display profile

To use PreBilt for EWM and customise screen appearances, you first need to create a new Display Profile in the standard RF framework. It's recommended to have separate Display Profiles for devices with differing screen sizes or layouts (e.g., handheld, vehicle-mounted, tablet) to allow when configuring the appearance of screens using the PreBilt customising toolkit.

1

Create a display profile

Create one display profile per device type which will use PreBilt for EWM.

In transaction SPRO under the EWM customizing node Mobile Data Entry > Radio Frequency (RF) Framework > RF Screen Manager:

Copy the standard ** display profile.

The subsequent popup requires input which depends on the concrete installation.

Value	Description
DstDispProfile	New display profile name. Ensure it follows customer naming conventions.
Screen Height / Width	Use the standard layout to avoid resizing subscreens.
Pushb. Length	Define the length of button texts on the final UI.
Menu Item Length	Define the length of menu item texts on the final UI.
Pushbutton Quantity	Set the number of visible buttons; extra buttons appear in the kebab menu.
Function Groups for Template Location	Coordinate name and package with the customer.
Function Group for Sub-Screens	Avoid creating sub-screens/step-screens if allowed by your EWM release

For futher information on configuring the display profile, check out the configuration guide.

2

Adjust Display Template function group

After the display profile template function group has been generated, create the following PBO/PAI routines in this new function group.

MODULE tctm_pbo OUTPUT.

* Call TCTM Get Data For Service
  /tctm/ewm_manager=>get_tctm_instance( )->get_enhanced_ui_data( )->push_additional_ui_data( /scwm/s_rf_screlm ).

ENDMODULE.

MODULE tctm_pai INPUT.

* Call TCTM Set Data Service
  /tctm/ewm_manager=>get_tctm_instance( )->get_ui_response_handler( )->process_incoming_data( CHANGING cv_okcode = ok_code ).

ENDMODULE.

Ensure all template screens (e.g. 1000 and 1001) call the PBO/PAI routines.

3

Create EWM RF application parameter

In transaction SPRO under the EWM customizing node SCM Extended Warehouse Management > Extended Warehouse Management > Mobile Data Entry > Radio Frequency (RF) Framework > Define Steps in Logical Transactions:

Create a new RF Application Parameter as such:

To define the application parameter above, you can copy and paste:

TCTM_UI_DATA /TCTM/EWM_S_RF_UI_DATA

4

Set-up RF presentation device

In transaction /SCWM/PRDVC, create a new default presentation device to be used for PreBilt for EWM.

Note

The FKeyQty should align with the number of physical F-Keys on the device.

5

Set-up PreBilt settings

In the event of a connection drop, the number of attempts to regain connection can be configured via transaction /TCTM/EWM_SETTINGS, node Frontend Settings. The timeout value is defined in milliseconds.

Example

There will be up to 10 re-connection attempts every 7 seconds. User specific entries can be added in addition to the default if desired.

6

Generate ITS templates

Create ITS service ZTCTM_EWM in transaction SE80.

Note

If customer naming conventions require a different name, ensure the ICF node in /tctm_ewm/its is adjusted to the new name.

Use transaction /TCTM/EWMITSTEMPGEN to generate HTML templates for all screens.

You can now move on to installing the frontend!