Backend installation

Prerequisite

This section assumes a certain familiarity with ABAP Development.

Transport, Package and Naming Conventions should be discussed and provided. See Checklist.

Create Package (optional)

This step is only required if the agreed upon package does not exist yet.

Create the agreed-upon SAP Package (e.g. ZTCTM_EWM) using transaction SE80 or ABAP in Eclipse.

Populate the agreed fields and click 'Continue'.

Assign the implementation to the transport provided.

Activate RF Flow BAdIs

Note

PreBilt EWM requires both RF PRE and POST Flow RF BAdIs to deliver important PreBilt functionality.

Any pre-existing implementation for those BAdIs 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 the existing custom implementation class can be reused).

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

In transaction SE19, create a new Implementation for Enhancement Spot /SCWM/ES_RF_FLOW

Create the implementation in accordance with the agreed-upon Naming Conventions.

Create the BAdI Implementations for /SCWM/EX_RF_FLOW_PRE and /SCWM/EX_RF_FLOW_POST with a Naming-Convention aligned implementation name and implementation class /TCTM/EWM_FLOW_BADIS

Activate the Enhancement Implementation to set its status to "Active"

The RF Flow BAdIs are now activated.

Activate the Performance Check BAdI

Similar to the previous chapter, create a new Enhancement Implementation for Enhancement Spot /SCWM/ES_RF_PERF_CHK in transaction SE19.

Create a BAdI implementation for /SCWM/EX_RF_PERF_BEFORE_SCR and provide class /TCTM/EWM_FLOW_BADIS as in the step above (the class implements multiple interfaces).

Activate the implementation to finish

Activate the TCT RF Manager BAdI

In transaction SE19, create an implementation for Enhancement Spot /TCTC/ES_EWM_RFUI .

Create the BAdI implementation for /TCTC/EX_EWM_RFUI_GET_MANAGER with implementation class /TCTM/EWM_MANAGER .

Activate the Enhancement Implementation and ensure it is set to "Active"

Create the ITS service

In transaction SE80, under the agreed-upon package, create a service implementation. Preferably named ZTCTM_EWM (so no ICF changes are required).

Note

If your naming conventions require a different name, ensure the ICF node in /tctm_ewm/its is copied and adjusted to the correct name.

In this case, the Front-End must be build in a manner that supports the changed ICF node (can be configured)

To do this, right click on the object and select 'Create' -> 'Other (1)' -> Internet Service.

In the pop-up screen, enter the details:

• Internet Service: ZTCTM_EWM

• Transaction Code: /SCWM/RFUI

Save the package and the transport.

Enter the description TCT Mobility ITS Mobile Intergration in the short text field and click 'Save'.

Activate SICF nodes

Note

Ensure that any services requiring activation are fully activated in all environments and clients throughout the project.

In transaction SICF, search for all TCTM nodes.

Activate all three of them (including sub-nodes) by right clicking the service and clicking 'Activate Service'. When prompted to confirm, use the 'Yes including subnodes' button.

Create the 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 , click 'New Entries' in the Define Application Parameters structure.

Create a new RF Application Parameter:

• Appl. Parameter Name: TCTM_UI_DATA

• Parameter Type: /TCTM/EWM_S_RF_UI_DATA

Click 'Save'.

Note

If you receive a namespace error, press Enter.

Assign the new entry to a transport.

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.

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.

Assign to a transport and click the green tick.

IMPORTANT

The next step is critical, and details should be completed exactly as provided.

Fill out the popup as displayed below, adjust the Destination Display Profile Name as required.

Note to use Function Group /TCTM/EWM_UI_TEMPL with screens 1000 and 1001 as shown on the image above. This function group assumes the standard height/width of 8x40.

Set the Pushb.Qty to the amount of push buttons visible in the bottom bar of the screen.

The SAP system will prompt that the function module already exists, but this can be ignored.

As an alternative to using the pre-delivered /TCTM/EWM_UI_TEMPL function group, a Z copy can be made and used instead.

Generate ITS templates

Note

In the below section, you will need to adjust the service names given in the instructions and screenshots if it has been changed, and use the display profile name created above.

In transaction /TCTM/EWMITSTEMPGEN, enter:

• Service: ZTCTM_EWM (or whatever chosen before)

• IAC theme: 99

• Display profile: Z1 (or whatever used in the step before)

• Generating Style: /TCTM/EWM TCT Mobility Templates for EWM

• Publish?: Checked

• Update Fields: Checked on the first run ONLY. After that, unchecked

From the next screen, select all the screens displayed and click 'Create Templates'.

Add the package name when prompted and click the green tick, before assigning to a transport.

The templates should have been activated as indicated by a green status light.