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:
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.
Parameters
Additional parameters related to the configuration of the additional elements are defined on this node. The available parameters will vary per element.
UOMS Screen Element and Parameters
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.
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
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).
KPI Screen Element and Parameters
An additional Extra Element and parameter must be configured to display embedded KPIs.
Parameter
Use
Expected value
KPI Key
Mapping for KPI to display
KPI_KEY from table /TCTM/EAP_ANALY
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.
KPI Key
KPI Type
EGF Object
SSB Object
KPI Key
Select either EWM_MS or SSB_EVAL.
EGF Object value if applicable.
SAP Smart Business Evaluation Object value if applicable.
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:
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):
Parameter
Use
Value Type & Expected Value
FORCE_CAPTURE
Force Capture when screen is entered
X
FORCE_CAPT_TXT
Text to present before capture is forced
Translatable Text: ‘Please provide a product picture’.
HEIGHT
Image Display Width (in pixels)
Fixed: ‘150’ or other number or no entry (no entry is dynamic)
UPLOAD_TOAST
Text displayed to confirm image upload
Translatable Text: ‘Upload successful’
URL
URL for image repository
Fixed: URL path
URLKEY1
Mapping image to be displayed
Fixed: Value 1 to be mapped
URLKEY2
Mapping image to be displayed
Fixed: Value 2 to be mapped
URLKEY3
Mapping image to be displayed
Fixed: Value 3 to be mapped
URLKEY4
Mapping image to be displayed
Fixed: Value 4 to be mapped
URLVAL1
First parameter value
Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)
URLVAL2
Second parameter value (_ delimited from URLVAL1)
Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)
URLVAL3
Third parameter value (_ delimited from URLVAL2)
Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)
URLVAL4
Fourth parameter value (_ delimited from URLVAL3)
Fixed/RF Structure Field from Frontend/RF Structure Field from backend: (see example below)
WIDTH
Image Display Width (in pixels)
Fixed: ‘150’ or other number or no entry: (no entry is dynamic)
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”.
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.
Last updated
Was this helpful?