SAP objects support

SAP object types that ABAP Agent 2.0 uses for coverage, business context, and test impact analysis.

ABAP Agent 2.0 works with several SAP object types. They fall into different roles: some contribute code coverage, some represent the business context a user or service actually runs, and some matter for test impact even though they have no line-level coverage of their own.

This page is the customer-facing support matrix. Use it when you need to know why an object appears (or does not appear) in coverage, contexts, or impacted-test results.

Why object types matter

Role	What it means for you
Code (coverage)	Objects that SCMON can attribute execution to. These are the main items in coverage reports.
Context / executable	Entry points business users or integrations run (transactions, UI5/Fiori apps, OData services). The agent maps changed code to these contexts for impact and test matching.
Non-code	Objects that do not produce SCMON coverage themselves but can still influence test impact when they change (for example tables and enhancements).

Support matrix

Bucket	Type	Typical meaning	Coverage (SCMON)	Context / TIA role
Code (coverage)	INCL	Include	Yes	Covered code unit
Code (coverage)	PROG	Program / report	Yes	Covered code unit
Code (coverage)	METH	Class method	Yes	Covered code unit
Code (coverage)	FUNC	Function module	Yes	Covered code unit
Context / executable	TCOD	Transaction code (GUI)	No (as itself)	Primary GUI business context
Context / executable	WAPA	BSP / UI5 web application	No (as itself)	UI5 / Fiori-related application context
Context / executable	IWSV	OData V2 service	No (as itself)	Supported OData service context
Non-code	TABL	Table / structure (DDIC)	No	Can affect test impact when changed
Non-code	ENHO	Enhancement implementation	No	Can affect test impact when changed

Related reading

• Concepts — Concepts hub
• Guides — onboarding and Fiori support
• Upload FLPCA data — Fiori Launchpad catalog import (required for Fiori before search_testrepo)