> 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/app-master-data/screen-framework/selection-screens.md).

# Selection screens

{% embed url="<https://www.youtube.com/watch?index=4&list=PL74nuGSklShnLgW4UxtzhL9a1rK5DXrdp&v=qaJq5Dk86gM>" %}

Selection screens comprise the following configuration options:

* The screen itself, which is always setup in configuration with data type ‘D - Detail Screen Config’ allowing all the fields and their controls to be set up. See the section on [Detail Screen Configuration](/prebilt-for-im-wm-strm/app-master-data/screen-configuration/detail-screen-configuration.md)<mark style="color:yellow;">.</mark>
* ACTIONS option which is always setup with data type ‘H - Screen Action Config’. See the section on [Action Configuration](/prebilt-for-im-wm-strm/app-master-data/screen-configuration/action-configuration.md).

## Selection screen example

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FV4RLUCaE0sX4U8Yaitku%2Fimage.png?alt=media&amp;token=7708aa42-98b0-4ed8-9b64-d1ec546aee8f" alt=""><figcaption></figcaption></figure>

A selection screen is usually the first screen in the app when a selection of appropriate data is required before processing can begin, such as the selection of stock in the warehouse via stock enquiry by material.

### Selection screen fields and features

Each app generally has a selection screen. The fields and options available on the selection screen will be determined by the allowed options of each specific app.

All configuration relating to a selection screen will be captured under configuration option SELECT\_OPTS.

Some fields on the selection screen will have standard behaviour across all apps.

### Material

If the configuration option EXACT is not maintained for the field, entering a partial entry will return all matching materials, i.e. if TCT is entered, an input help screen will be displayed listing all matching materials; TCTFG001, TCTFG002 etc for the user to select the correct material.

The objects (and sequence of objects) that will be searched for in this process are determined at a global level, but also with an app specific search that will override the global option. This allows customers the flexibility to change the search per app, but also give them one place to maintain the search for consistency. The search options available are:

* M = Material (MARA-MATNR)
* E = Material EAN (MEAN-EAN11)
* D = Material Description (MAKT-MAKTX)
* B = Fixed Bin (MARD-LGPBE) – this is only used in certain apps such as Stock Enquiry.

If the app screen has been developed to work with wildcard entries containing an \*, all materials containing the string will be passed as part of the selection (see the individual app specifications for more detail).

The configuration option to determine what can be searched for in this field, e.g. Material Number, EAN, Material Description, is controlled by the configuration option MATERIAL\_SEARCH\_SEQ.

### Vendor

If the configuration option EXACT is not maintained for the field, entering a partial entry will return all matching vendors.

Both the vendor number and the vendor description are searched for a match.

### Wildcards

The possibility of wildcard searching will be defined at the app level.

For example, storage bin is set up to allow wildcard searching in the stock enquiry app:

* Entering 01\* will find all bins starting 01
* Entering \*01\* will find all bins containing 01 anywhere in the string
* Entering \*01 will find all bins ending in 01

Deactivating this functionality in the app is possible by making the field an exact match only with configuration field EXACT.


---

# 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/app-master-data/screen-framework/selection-screens.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.
