> 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/determining-allowed-fields-components.md).

# Determining allowed fields/components

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

Most of the screen configuration relies on referencing fields / components available within pre-defined structures that have been set up to work with each screen. Full details of which structures can be used as standard for a particular app/screen are provided in the configuration guide for the relevant app and can also be found using transaction */TCTM/WM\_AMD\_DTYPES*.

Pressing F4 while the cursor is in the field will show the fields that can be used for the structures relevant to the particular screen. However, the following prerequisites must have been performed in the system in order for data to be available to display:

* Table `/TCTM/WM_DU` needs to be populated with data for the particular app transaction and screen.
* This is achieved by someone having set their userid with PID `/TCTM/WM_SAVE_DU` and then running through the app transaction in PreBilt.
* The first time the app transaction is processed through the various screens by the user with the PID set, the data is written into the table `/TCTM/WM_DU`, and thus available for the F4 lookup.

The primary structure is the main structure that builds a table containing ancillary data from the secondary structures (structures with a prefix).  Fields should be used from the secondary structures as best practice, and those fields should be in the format \[prefix]-\[field].  Fields in AMD with a prefix should not require a class.

The available structures can be viewed via standard SAP transactions (e.g., *SE12*). Enter the structure in the ‘View’ field and select ‘Display’:

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2F3Iu67sS8dJN3w9xw6DfY%2Fimage.png?alt=media&amp;token=c93baf2c-47c2-4fee-ac40-de95f30814ae" alt=""><figcaption></figcaption></figure>

The available fields/components will then be displayed on the left. The structure and component can be used to add a field as needed into an app screen.

In the example below, if structure /TCTM/LQUA was available as a structure in a particular app screen and the field ‘Blocking Reason’ (SPGRU) needed to be added, either add SPGRU or LQUA-SPGRU into the app master data for that screen.

<figure><img src="https://3149936122-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CkvzIq48sLzTY4bfcWl%2Fuploads%2FNbBrl1h5po8ujixYnrO2%2Fimage.png?alt=media&amp;token=af078b52-a204-4266-b9f7-90ff4fb5a559" alt=""><figcaption></figcaption></figure>

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

The ‘Component Type’ is the value to use for the DDIC (Data Dictionary) definition in the app master data field ‘Label’, not the ‘Component’. For example, plant is denoted by field/component ‘WERKS’ but its label must be maintained with ‘DDIC-‘, followed by the Component Type, followed by a dash and a character to determine the SAP field description length to use:&#x20;

* S (short)
* M (medium)
* L (long)

In the example of Plant, the label will be maintained as `DDIC-WERKS_D-M` in order to display the medium label text for plant.
{% endhint %}


---

# 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/determining-allowed-fields-components.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.