> 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-ewm/configuration-guide/customising-the-screen-layout/detailed-screen-fields-customisation/defining-extra-screen-elements.md).

# Defining Extra Screen Elements

If any additional TCT screen plugins are enabled (e.g. image display and capture), the process to inserting them is a similar to adding standard screen fields.

In this node, custom additional elements can be linked and positioned on the screen:

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-c47bb7aa691087dd18b0c25e466276d4ed048108%2FEWM-Adding%20extra%20non-standard%20screen%20elements.png?alt=media" alt=""><figcaption><p>Adding extra non-standard screen elements</p></figcaption></figure>

* Element Name – User definable name to identify the element to be used.
* Element Type – Element as defined in the ‘Extra Element Types’ node.
* Row – Row to display the element in.
* Visual Length – Visible length by ratio of the element.
* Line Position – Column number of the element.
* Row Span – How many rows the element is displayed in across on the screen.

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

[Extra Element Types](/prebilt-ewm/configuration-guide/customising-the-screen-layout/detailed-screen-fields-customisation/extra-element-types.md) must be configured before defining extra screen elements.
{% endhint %}

### Parameters

Additional parameters related to the configuration of the additional elements are defined on this node. The available parameters will vary per element.

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-422787a49e75c54dc8bc9f5b5f361b44d83ab4ab%2Fimage%20(34).png?alt=media" alt=""><figcaption><p>Setting the parameters for an extra screen element</p></figcaption></figure>

### UOMS Screen Element and Parameters

{% embed url="<https://www.youtube.com/watch?index=17&list=PL74nuGSklShkPfMTELqxruD4Qhedw_f_E&v=biEsY73oeZE>" %}

When activating enhanced selection for a UoM input field in any logical transaction step (apart from setting the field type to UOMS) Extra Screen Elements must be defined with the exact field name of the UoM input. No screen positioning values are required for this element.

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-7c561354471ea9fe0b436877d35089133ca7129d%2FEWM-Extra%20Element%20for%20UOMS.png?alt=media" alt=""><figcaption><p>Extra Element for UOMS</p></figcaption></figure>

The Extra Element Parameters required for UOMS are:

| **Parameter**      | **Use**                                          | **Expected Value**          |
| ------------------ | ------------------------------------------------ | --------------------------- |
| CHANGE\_FCODE      | FCODE used after selection                       | ‘ENT’                       |
| DISP\_DIMENSIONS   | Display UoM dimensions                           | ‘X’ or blank                |
| DISP\_EAN          | Display UoM EAN                                  | ‘X’ or blank                |
| DISP\_VOLUME       | Display UoM volume                               | ‘X’ or blank                |
| DISP\_WEIGHT       | Display UoM weight                               | ‘X’ or blank                |
| PRODUCT\_FIELD     | Associated product field                         | Field name                  |
| UOM\_EXCLUDE       | List of UoMs to exclude                          | UoM keys separated by comma |
| UOM\_FROM\_QTY\_CL | Only consider UoMs from Qty Classification table | ‘X’ or blank                |

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-9768cf026e909b495e573ba1b6577b8e3a3d0a64%2FEWM-UOMS%20Extra%20Element%20Parameters.png?alt=media" alt=""><figcaption><p>UOMS Extra Element Parameters</p></figcaption></figure>

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

The Extra Element Type for UOMS and its available parameters must first be defined in transaction */TCTM/EWM\_CUST*.
{% endhint %}

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-281d7ecc4bd2464530d6fd84ade051d5d81804cb%2FEWM-Extra%20Element%20Type%20UOMS%20Definition.png?alt=media" alt=""><figcaption><p>Extra Element Type UOMS Definition</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-65d9336e71d3e137a05d59afc8623270cf67f8bd%2FEWM-Extra%20Element%20Type%20UOMS%20Parameters.png?alt=media" alt=""><figcaption><p>Extra Element Type UOMS Parameters</p></figcaption></figure>

### Scandit Screen Element and Parameters

As per the UOM, an additional Extra Element and parameters must be configured for Scandit. In this example, Scandit has been configured for step XSERNR (Serial Number Maintenance).

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-efdb377923ec22c1be3f60a7680d548764c5d723%2FEWM-Extra%20Element%20Type%20for%20Scandit.png?alt=media" alt=""><figcaption><p>Extra Element Type for Scandit</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-56df71ff7b6f8d500099303d5de276726d86e104%2FEWM-Extra%20Element%20Type%20Parameters%20for%20Scandit.png?alt=media" alt=""><figcaption><p>Extra Element Type Parameters for Scandit</p></figcaption></figure>

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

Under the parameter symbologies, the expected barcode formats are defined.

Barcode formats supported by Scandit can be found using the link below:

<https://docs.scandit.com/data-capture-sdk/capacitor/barcode-capture/api/symbology.html#enum-scandit.datacapture.barcode.Symbology>
{% endhint %}

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

The Extra Element Type for Scandit and its available parameters must first be defined in transaction */TCTM/EWM\_CUST*.
{% endhint %}

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-4cdedc3df48f9fd5907368da20b2d704c85e87f1%2FEWM-Extra%20Element%20Type%20Scandit%20Definition.png?alt=media" alt=""><figcaption><p>Extra Element Type Scandit Definition</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-9828f92722e1529f977eb3356be5918d9a3cc340%2FEWM-Extra%20Element%20Type%20Scandit%20Parameters.png?alt=media" alt=""><figcaption><p>Extra Element Type Scandit Parameters</p></figcaption></figure>

### KPI Screen Element and Parameters

An additional Extra Element and parameter must be configured to display embedded KPIs.

<table data-header-hidden><thead><tr><th width="160">Parameter</th><th>Use</th><th>Expected value</th></tr></thead><tbody><tr><td><strong>Parameter</strong></td><td><strong>Use</strong></td><td><strong>Expected value</strong></td></tr><tr><td>KPI Key</td><td>Mapping for KPI to display</td><td>KPI_KEY from table /TCTM/EAP_ANALY</td></tr></tbody></table>

This KPI Key maps to table `/TCTM/EAP_ANALY`, where entries can be maintained to link KPI tiles to EWM Measurement Services or CDS Analytics (SAP Smart Business Evaluation) as KPI types. These must be defined before being mapped in `/TCTM/EAP_ANALY`. After this, extra elements & parameters must be defined in PreBilt customising.

<table data-header-hidden><thead><tr><th width="157">KPI key</th><th>KPI type</th><th>EGF object</th><th>SSB object</th></tr></thead><tbody><tr><td><strong>KPI Key</strong></td><td><strong>KPI Type</strong></td><td><strong>EGF Object</strong></td><td><strong>SSB Object</strong></td></tr><tr><td>KPI Key</td><td>Select either EWM_MS or SSB_EVAL.</td><td>EGF Object value if applicable.</td><td>SAP Smart Business Evaluation Object value if applicable.</td></tr></tbody></table>

Extra elements with Extra Element Type KPI can then be created and positioned within the screen. For the example below, extra element “BLKQ” has been configured with KPI type BLKQ and is mapped to an EGF Object via KPI Key:

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-ee88077c1826d5b85422b59a498bea623406cf86%2FEWM-Extra%20Element%20Type%20KPI.png?alt=media" alt=""><figcaption><p>Extra Element Type KPI</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-ab8ad29273fdc3f37922bb8a73bf33cdecdc7163%2FEWM-Extra%20Element%20Type%20Parameters%20for%20KPI.png?alt=media" alt=""><figcaption><p>Extra Element Type Parameters for KPI</p></figcaption></figure>

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

The Extra Element Type for KPI and its available parameter must first be defined in transaction */TCTM/EWM\_CUST*.
{% endhint %}

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-377d25f0acdbd06e96d4b307abb8fccc727fdec7%2FEWM-Extra%20Element%20Type%20KPI%20Definition.png?alt=media" alt=""><figcaption><p>Extra Element Type KPI Definition</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-825b0d8d3855b179e340a82bc46caae25abd3cf8%2FEWM-Extra%20Element%20Type%20KPI%20Definition%20Parameter.png?alt=media" alt=""><figcaption><p>Extra Element Type KPI Definition Parameter</p></figcaption></figure>

### Image Display & Capture Screen Element and Parameters

Additional Extra Elements and parameters must be configured for Image Display (Extra Element Type “IMAGE) and Image Display & Capture (Extra Element Type “IMG\_DISCAP”).

The Extra Element Parameters required for Image Display are detailed below (note “UPLOAD\_TOAST” required for Image Display & Capture only, otherwise all possible parameters are shared):

<table data-header-hidden><thead><tr><th width="174"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Parameter</strong></td><td><strong>Use</strong></td><td><strong>Value Type &#x26; Expected Value</strong></td></tr><tr><td>FORCE_CAPTURE</td><td>Force Capture when screen is entered</td><td>X</td></tr><tr><td>FORCE_CAPT_TXT</td><td>Text to present before capture is forced</td><td>Translatable Text: ‘Please provide a product picture’.</td></tr><tr><td>HEIGHT</td><td>Image Display Width (in pixels)</td><td>Fixed: ‘150’ or other number or no entry (no entry is dynamic)</td></tr><tr><td>UPLOAD_TOAST</td><td>Text displayed to confirm image upload</td><td>Translatable Text: ‘Upload successful’</td></tr><tr><td>URL</td><td>URL for image repository</td><td>Fixed: URL path</td></tr><tr><td>URLKEY1</td><td>Mapping image to be displayed</td><td>Fixed: Value 1 to be mapped</td></tr><tr><td>URLKEY2</td><td>Mapping image to be displayed</td><td>Fixed: Value 2 to be mapped</td></tr><tr><td>URLKEY3</td><td>Mapping image to be displayed</td><td>Fixed: Value 3 to be mapped</td></tr><tr><td>URLKEY4</td><td>Mapping image to be displayed</td><td>Fixed: Value 4 to be mapped</td></tr><tr><td>URLVAL1</td><td>First parameter value</td><td>Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)</td></tr><tr><td>URLVAL2</td><td>Second parameter value (_ delimited from URLVAL1)</td><td>Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)</td></tr><tr><td>URLVAL3</td><td>Third parameter value (_ delimited from URLVAL2)</td><td>Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)</td></tr><tr><td>URLVAL4</td><td>Fourth parameter value (_ delimited from URLVAL3)</td><td>Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)</td></tr><tr><td>WIDTH</td><td>Image Display Width (in pixels)</td><td>Fixed: ‘150’ or other number or no entry: (no entry is dynamic)</td></tr></tbody></table>

In this example below, the filename of the image to be retrieved is “COMPONENT-EWM-02\_EA.png” which is determined by.

“COMPONENT-EWM-02” = the RF frontend value for /SCWM/S\_RF\_ORDIM\_CONFIRM-MATNR (Product)

“EA” = the RF frontend value for /SCWM/S\_RF\_ORDIM\_CONFIRM-ALTME (UoM)

With an underscore delimiter between each value.

In this example, the image displayed on screen is determined by the values also displayed on screen. The corresponding image is retrieved from the repository defined in “URL”.

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-071a3f5ec363362c92406ac8e9da8db5f1b20456%2FEWM-Extra%20Element%20Type%20Parameters%20for%20Image%20Display.png?alt=media" alt=""><figcaption><p>Extra Element Type Parameters for Image Display</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-9239fe3eec584a1c070ad0e5ca7e7de25065440d%2FEWM-Extra%20Element%20Type%20Image%20displayed%20on%20screen.png?alt=media" alt=""><figcaption><p>Extra Element Type Image displayed on screen</p></figcaption></figure>

This illustrates that the image could, for example, be different for a pallet, if there was a corresponding image with the filename “COMPONENT-EWM-01\_PAL.png” where ALTME (Unit of Measure) = “PAL”. URLKEY 3 & 4 together with URLVAL 3 & 4 allow displayed images to be determined based on additional variables.

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

Image Display, Image Capture & Display screen elements are not “plug and play” for deployment and will be specific to your PreBilt build. Additional requirements include, but are not limited to:

* Image repository – where images are stored and retrieved from (can be SAP server, can be elsewhere).
* Image capture device integration – where and how captured images are sent from mobile devices.
* Associated authentication & permission requirements for image display & capture.

Implementation should be discussed with your TCT consultant.

The framework for image display & capture has been designed with flexibility in mind and is largely parameter driven, which should reduce development requirements for implementation.
{% endhint %}

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

The Extra Element Type for Image Display / Image Display & Capture and its available parameters must first be defined in transaction */TCTM/EWM\_CUST*, as shown below.
{% endhint %}

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-a90217cd8fde7f5575a0acb649985339e61e6d25%2FEWM-Extra%20Element%20Type%20Definition%20IMAGE%20and%20IMGDISCAP.png?alt=media" alt=""><figcaption><p>Extra Element Type Definition: IMAGE and IMG_DISCAP</p></figcaption></figure>

<figure><img src="https://1016750988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7lFTpSLijn44pippdL6u%2Fuploads%2Fgit-blob-a4bbd1bfddeeaa1fef1db4843bfa79436ff4db01%2FEWM-Extra%20Element%20Type%20IMG_DISCAP%20Parameters.png?alt=media" alt=""><figcaption><p>Extra Element Type IMG_DISCAP Parameters</p></figcaption></figure>


---

# 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-ewm/configuration-guide/customising-the-screen-layout/detailed-screen-fields-customisation/defining-extra-screen-elements.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.