> 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/configuring-prebilt-features/analytics/embedding-analytics-into-prebilt.md).
# Embedding Analytics into PreBilt
KPIs can be embedded either within the newly created logical transaction as a dashboard or within any logical transaction step.
Embedded within the Analytics logical transaction
Embedded within a standard logical transaction
{% hint style="info" %}
**Note**
When embedding KPI tiles into standard logical transactions, ensure there is enough screen space available to maintain a positive user experience.
{% endhint %}
### Embedding a KPI tile in to a transaction
{% stepper %}
{% step %}
#### 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.
{% hint style="info" %}
**Prerequisite**
The SET/GET Parameter ID /SCWM/RF\_TECH\_TITLE must be maintained in SU3 with the parameter value set to "X".
{% endhint %}
{% endstep %}
{% step %}
#### Create "Extra Elements"
{% hint style="info" %}
**Prerequisite**
KPI Screen Element and Parameters must be configured in the 'Defining Extra Screen Elements' section beforehand
{% endhint %}
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.
{% endstep %}
{% step %}
#### 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.
{% endstep %}
{% endstepper %}
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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)