The Config Team Ltd
Contact usDemo App
PreBiltâ„¢ for EWM
PreBiltâ„¢ for EWM
  • PreBilt for EWM
    • Overview
    • Functionality
    • Frequently asked questions
    • Release notes
      • v4.13 release notes
      • v4.12 release notes
  • Installation
    • Minimum requirements
    • Prerequisites and assumptions
    • Backend installation
    • Frontend installation
    • UI deployment
  • Configuration Guide
    • EWM RFUI requirements
    • Initial generation of EWM ITS screen templates
    • Overview screen of technical information
    • BC sets
    • Customising the screen layout
      • Logical Transactions and Step Header
      • Detailed screen fields customisation
        • Replacement field labels
        • Field type
        • Toggling a drop-down list
        • Hiding field borders
        • Hiding a field from display
        • Hiding a field from display when empty
        • Making a field read-only
        • Setting the display row for a parameter
        • Setting the visual length of a parameter
        • Setting the position of a parameter on the row
        • Maintaining table types for step-loop table functionality
        • Assigning field roles for table types
        • Maintaining a hint text
        • Defaulting a parameter value
        • Setting a parameter label's font style, size and colour
        • Setting a field value font style, size and colour
        • Adding a new screen field
        • Enhanced UoM selection
        • Defining Extra Screen Elements
        • Function code overrides
        • Menu extras
        • Function code extras
        • Exception code extras
        • Extra element types
        • Voice Fields
    • Translations
      • Downloading translations
      • Transforming the data
      • Uploading translations
    • Configuring PreBilt features
      • Communication Hub
      • Gamification
        • Competitions
        • Challenges
        • Game Monitoring
      • Voice
        • EWM RFUI requirements for Voice
        • Functional scope
        • Initial generation of ITS templates and customising for voice
        • Overview screen of technical information
        • Customising the voice flow for a screen
          • Maintain basic configuration
          • Maintain TCT mobility basic customising
          • Logical transaction and step header
          • Detailed screen field customisation
        • Master data
      • Analytics
        • Installation
        • Embedding Analytics into PreBilt
      • Unified Search Configuration
        • Installation
      • Image Capture
  • Using PreBilt
    • Screen elements
    • Process steps
    • Validation messages and troubleshooting
    • Operator messaging
    • Gamification
    • Troubleshooting
Powered by GitBook

Help

  • Can't find what you're looking for? E-mail us.

© The Config Team 1994 - Present Day

On this page
  • Embedding a KPI tile in to a transaction
  • Identify the transaction
  • Create "Extra Elements"
  • Create "Parameters"
  • Creating a KPI dashboard

Was this helpful?

  1. Configuration Guide
  2. Configuring PreBilt features
  3. Analytics

Embedding Analytics into PreBilt

PreviousInstallationNextUnified Search Configuration

Last updated 5 months ago

Was this helpful?

KPIs can be embedded either within the newly created logical transaction as a dashboard or within any logical transaction step.

Note

When embedding KPI tiles into standard logical transactions, ensure there is enough screen space available to maintain a positive user experience.

Embedding a KPI tile in to a transaction

1

Identify the transaction

Identify the logical transaction where you would like to embed your KPI tile by selecting the information icon in the top right of the PreBilt UI.

Prerequisite

The SET/GET Parameter ID /SCWM/RF_TECH_TITLE must be maintained in SU3 with the parameter value set to "X".

2

Create "Extra Elements"

Access the transaction /TCTM/EWM_CFG and navigate to the appropriate logical transaction and step. Once there, select the Extra Elements node.

Enter and maintain the following element details:

  • Element Name: Specify the name of your Analytics Tile.

  • Element Type: Select "KPI" as the type of tile.

  • Row: Indicate the row where the tile should be placed.

  • Visual Length: Define the visual length of the KPI tile.

  • Line Position: If the tile shares a row with other objects, determine its display order.

  • Row Span: Specify the number of rows the KPI tile will span.

Select the entry and then choose the Parameters sub-node.

3

Create "Parameters"

Save the changes to a customising request.

Update the KPI Key field in the maintenance table /TCTM/EAP_ANALY with the value from the Extra Element Parameter Value shown in the screenshot above.

  • If the KPI is based on standard measurement services, the KPI type should be set to EWM_MS (EWM Measurement Service) and an EGF object must be maintained.

  • If the KPI tile is a Fiori KPI, the KPI type should be set to SSB_EVAL (Smart Business Evaluation) and your Fiori CDS view ID would need to be maintained against the Unique Identifier Field.

After saving, the KPI tile will be embedded in the logical transaction and visible on screen.

Creating a KPI dashboard

The YTANLY logical transaction allows multiple tiles to be created in to a KPI dashboard.

This process is similar to embedding within a specific logical transaction as above. Instead of selecting the specific logical transaction in transaction /TCTM/EWM_CFG, select logical transaction YTANLY and follow the steps as normal.

Embedded within the Analytics logical transaction
Embedded within a standard logical transaction