Device type
Last updated
Was this helpful?
Last updated
Was this helpful?
Where different device types are being used within the warehouse, it is possible to maintain different app master data for each device type, allowing, for example, to have different screen layouts by device type with, for example, the number of fields on each row of the screen increased or reduced, or the position of actions modified according the space available on the screen.
Different font sizes, types and colours can also be maintained as appropriate for the device screen size, or for visually impaired users.
To create a new device, enter a device type (there is a 4 character limit) and its description.
Once the device type is defined, return to the Configuration Fields for all of the transactions that require different layouts by Device Type and identify which configuration element needs to be copied with the new Device Type added to the key.
Typically, this may be SELECT, LIST or INPUT screens and/or the ACTIONS associated with each of those screen types.
See below for an example of where just the LIST_QUANT_WM screen for this particular transaction was updated to allow a different setting based for the TM (Truck Mounted) device type.
The settings for that particular screen can now be amended in the app master data, for that particular transaction, to allow differences between the generic devices (blank) and the specific TM devices.
Each user can control which device type they use by maintaining their user parameter /TCTM/WM_DEVICE_TYPE with the appropriate device type. This is done in transaction SU3:
When a particular screen in an app/transaction is called, the app will check the user’s parameters /TCTM/DEVICE_TYPE to see if they have a specific device type maintained. If so, the app will look for the matching configuration option to determine how to display the data.
If the app master data contains both configuration options SELECT_OPTS, Device Type = blank and SELECT_OPTS, Device Type = TM, and the user sets the device type parameter to TM, the app will prioritize and apply the settings from SELECT_OPTS, Device Type = TM.
If the user’s parameter value was blank or did not match / exist in the app master data, the app would use the first option SELECT_OPTS, Device Type = blank.
