> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/concepts/sap-objects-support.md).

# SAP objects support

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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/concepts.md) — Concepts hub
* [Guides](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides.md) — onboarding and Fiori support
* [Upload FLPCA data](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/upload-flpca-data.md) — Fiori Launchpad catalog import (required for Fiori before `search_testrepo`)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/concepts/sap-objects-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.