> 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/applications/user-maintenance/configuration.md).

# Configuration

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

This configuration guide refers to PreBilt transactions beginning '*PB2\_*' and details the standard process without additional features or enhancements. You should [copy these transactions](/prebilt-for-im-wm-strm/configuration-guide/transaction-codes.md#create-a-transaction) with a different prefix to maintain a backup and protect the originals.

The guide displays the standard PreBilt screens and gives details of the structures in which the on screen fields can be found. Fields within these structures can be used to customise and enhance the screen. For instructions on how to use structures to find fields, please see [Available data structures](/prebilt-for-im-wm-strm/app-master-data/screen-framework/features/available-data-structures.md). For instructions on how to maintain the configuration elements in AMD, please see [General configuration elements](/prebilt-for-im-wm-strm/app-master-data/general-configuration-elements.md).

This covers the user profile maintenance that covers RF queues, default printers and any parameter ID updates for app transactions *PB2\_USER\_MAINT\_ALL, PB2\_USER\_MAINT\_PRINT* and *PB2\_USER\_MAINT\_RF*.
{% endhint %}

## User profile updates

All the supplied app transactions behave in the same way and are just different flavours with the same logic and structures.

### User defaults

{% tabs %}
{% tab title="PB2\_USER\_MAINT\_ALL" %}

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FsQsNYaseQBkDGwm3l0F0%2Fimage.png?alt=media&amp;token=51c0284a-3081-46ec-b156-03032ab4a80c" alt="" width="236"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="PB2\_USER\_MAINT\_PRINT" %}

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2Fg0ZpuBMZ1UHGnNpmJhsM%2Fimage.png?alt=media&amp;token=fa3c06cf-4541-48c2-8526-634c9b932ba0" alt="" width="236"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="PB2\_USER\_MAINT\_RF" %}

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2Fs8dYAfaLAQ2K8t9cOh2M%2Fimage.png?alt=media&amp;token=226d0b62-2367-4b11-9413-cf09863ec2de" alt="" width="236"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

<table><thead><tr><th width="242">Configuration element</th><th width="502">Available structures/fields</th></tr></thead><tbody><tr><td>INPUT_MAIN</td><td><p>LRF_WKQU-QUEUE - queue assigned to the user</p><p>USR01-SPLD - printer assigned to user</p><p>USR05-&#x3C;parameter ID> - PID from user profile</p><p></p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>To add the input fields for changing a value, use the above field names suffixed with "_IN".</p></div></td></tr><tr><td>INPUT_MAIN_ACTIONS</td><td><p>BACK - back to previous screen.</p><p>SAVE – save updates.</p></td></tr></tbody></table>

{% hint style="warning" %}
**Warning**

For any parameter IDs that have a "/" (such as, for example, the TCT created ID for device types "/TCTM/WM\_DEVICE\_TYPE"), you will need to replace the "/" with a "." in the field column (since the frontend code cannot process "/"). Therefore the value to be added into the "Field" column in the AMD should be "USR05-.TCTM.WM\_DEVICE\_TYPE". In the "Initial Value Source" column in the AMD however you still use the PID as normal, e.g. "PID:/TCTM/WM\_DEVICE\_TYPE". See picture below for example.
{% endhint %}

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FsBrRtinhokMc27QWqe0f%2Fimage.png?alt=media&amp;token=738e8c3f-b91d-4cd8-a3dc-73234ebe60ee" alt=""><figcaption></figcaption></figure>

### General configuration elements

<table><thead><tr><th width="242">Configuration element</th><th width="502">Description</th></tr></thead><tbody><tr><td>FE_APP</td><td>Frontend class to use in running the transaction.<br><br>Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.</td></tr><tr><td>QUEUES_FILTER</td><td>Enables filtering of queues assigned to the warehouse, allowing the user to include or exclude specific values in the list view.</td></tr><tr><td>PRINTERS_FILTER</td><td>Enables filtering of printers assigned to the warehouse, allowing the user to include or exclude specific values in the list view.</td></tr><tr><td>SLOC_LIST</td><td>Allows a static list to be maintained for choosing a storage location.<br><br>If the user is required to select from a list of storage locations, the allowed values can be set here.<br><br>The value and description of the storage locations are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP. </td></tr><tr><td>APP_TEXTS</td><td>Defines standard app text to be used in screen headers, buttons etc.</td></tr><tr><td>TRANS_INFO</td><td>Information about the transaction.</td></tr></tbody></table>