> 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-for-im-wm-strm/configuration-guide/device-type.md).

# Device type

{% embed url="<https://www.youtube.com/watch?index=7&list=PL74nuGSklShmOsKDpgus4wrEML55aCSkW&v=QdVwxw-5Dqs>" %}

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.&#x20;

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FMKiQlvojBv5Q49uBINUE%2Fimage.png?alt=media&amp;token=9cfd361f-bef6-42ee-8469-18c4eef618e0" alt=""><figcaption></figcaption></figure>

To create a new device, enter a device type (there is a 4 character limit) and its description.

## Add device type into configuration fields

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.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FvCnN4tKYlVFiHkAjbNPd%2Fimage.png?alt=media&amp;token=551e0fa5-24ce-4724-9a35-9ba867827433" alt=""><figcaption></figcaption></figure>

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.

{% hint style="info" %}
**Note**

The AMD settings for the new device type are not automatically populated. You will need to copy the settings in place from the non-device type screen or actions to the new device type element and then amend as required for the new layout.
{% endhint %}

## Activating a device type

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:

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FISEttIjm6zAv5lCCnrVR%2Fimage.png?alt=media&amp;token=3485f87d-ecb2-4853-b32c-a7e2d74aaf32" alt=""><figcaption></figcaption></figure>

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`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.theconfigteam.com/prebilt-for-im-wm-strm/configuration-guide/device-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.