Savings Breakdown for ABAP (SAP)

Last updated 16 hours ago

Was this helpful?

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."
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.

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. These lines are expandable to show unique impacted tests.
Transport Name Indication: For each executable, the Transport name will be displayed next to the Executable / Context name. This is particularly helpful when a build wasn't fully tested, as impacted tests from prior, untried builds will roll up to the current view, and the transport name helps identify their origin. A help icon will appear next to the transport name (on both the timeline card and the Impacted Tests table) to display the transport 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.

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."
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.

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. These lines are expandable to show unique impacted tests.
Transport Name Indication: For each executable, the Transport name will be displayed next to the Executable / Context name. This is particularly helpful when a build wasn't fully tested, as impacted tests from prior, untried builds will roll up to the current view, and the transport name helps identify their origin. A help icon will appear next to the transport name (on both the timeline card and the Impacted Tests table) to display the transport 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.