# Savings Breakdown for ABAP (SAP)

SeaLights **Savings Breakdown page** has been specifically tailored to enhance the user experience for SAP applications. This ensures the data presented is intuitive and aligns with SAP's unique terminology and concepts.

## **Key Changes and Terminology Adjustments**

For SAP applications, you'll notice the following important changes on the Build Breakdown page:

* **`SAP App` Tag:** An **'SAP App' tag** will now appear next to the application name, clearly indicating that you are viewing an SAP application.
* **Transport-Centric View:**
  * The **"Build Range"** title is changed to **"Transport Range."**
  * The switch button will be changed from **"Build View" to "Transports."**<br>

    <figure><img src="/files/rUPvRBDzbxSOyka4RPAJ" alt=""><figcaption></figcaption></figure>
  * This change reflects that in SAP, a **Transport** represents a set of code changes, similar to a "Build" or "Commit" in other environments. SeaLights uses this terminology for SAP apps to ease the understanding of the data.
  * While an import may contain several transports, SeaLights processes and registers each transport as a distinct build.
* **Enhanced Impacted Tests Table:** The "Impacted Tests" table within the Build Breakdown page includes several critical improvements:
  * **Displaying Context / Executable:** Instead of "File" or "Path," you'll now see the **Context / Executable** (e.g., \[Transaction], \[Fiori App], \[ODATA Service], \[Program], \[Function]) which provides relevant business context for your code changes. The lines are expandable to show code relationship to tests in the given context. The same code can have impact from different tests in different contexts.
  * **Transport Name Indication:** For each executable, the **Transport name** will be displayed next to the Executable / Context name. This is particularly helpful as the table aggregates impacted tests from all transports imported since the last test stage run. The transport name, therefore, assists in identifying the origin of each change. Additionally, a help icon will appear next to the transport name (on both the timeline card and the Impacted Tests table) to display the transport's description on hover.
  * **Displaying No-Code Changes:** SeaLights now includes **non-code changes** (e.g., **\[TABC]** for table types) at the same level as code changes, along with their number of impacted tests. This provides a more complete view of all changes that might trigger testing.
  * **Code Type Display:** Next to each code or non-code change, its **type** (e.g., **\[FUNC]**, **\[PROG]**, **\[METH]**, **\[CLAS]**, **\[ENHO]**, **\[INCL]**, **\[SSFO]**) will be displayed in bold text inside square brackets. This makes it easier to scan and understand the specific type of object that was changed.

<figure><img src="/files/9SDFdMny7C4FZXznU6u4" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/savings-breakdown-for-abap-sap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.