Sap Fiori Tree Table

by SAP69e2c50833f1No licenseListed Oct 8, 2026Updated Oct 8, 2026

Configure hierarchical tree table to SAP Fiori elements application for displaying parent-child recursive hierarchies. Supports CAP and ABAP RAP (OData V4).

Instructions onlySoftware Development
AI-generated overview

Configures hierarchical tree tables in SAP Fiori elements apps for CAP and ABAP RAP projects.

What it does
This skill guides an agent through adding a hierarchical tree table that displays parent-child recursive hierarchies in a SAP Fiori elements application. It covers both CAP (CDS managed association, @hierarchy annotation, manifest configuration, CSV test data) and ABAP RAP (CDS view with @OData.hierarchy.recursiveHierarchy, read-only or editable tree views, manifest configuration). It also collects required inputs such as entity name, ABAP package and transport need, and provides troubleshooting for common errors.
When to use it
Use it when a SAP Fiori elements app must show recursive parent-child data such as organizational hierarchies, category trees or nested structures. It fits CAP or ABAP RAP projects using OData V4 where a tree table is needed instead of a flat list.
Requirements
Requires an agent environment with the Fiori MCP Server and, for CAP, the CDS MCP Server; CAP work needs VS Code or SAP Business Application Studio, while ABAP RAP work needs VS Code with the ABAP Development Tools extension. CAP requires @sap/cds 9.6.0+ and OData V4. It ships no scripts, only reference documentation.

SAP Fiori Tree Table with Recursive Hierarchy

Purpose

Configure hierarchical tree table to display parent-child relationships in a recursive structure (organizational hierarchies, category trees, nested data).

Environment Requirements

CAP Projects:

  • ✅ VS Code or SAP Business Application Studio (BAS) - Both environments supported
  • ✅ Fiori MCP Server - Required for Fiori app generation and modification (VS Code only)
  • ✅ CDS MCP Server - Required for CDS model queries

ABAP RAP Projects:

  • ✅ VS Code only - ABAP Development Tools extension is VS Code-specific
  • ✅ Fiori MCP Server - Required for Fiori app generation and modification
  • ✅ ABAP Development Tools for VS Code extension - Required for backend development (includes ADT MCP server for RAP operations)

MANDATORY: Gather Required Inputs First

STOP and ASK the user for ALL of these inputs if ANY are missing from the prompt:

For ABAP RAP Projects:

  1. Package name - Where to create or find backend hierarchy objects ($TMP for local, or specific package like Z_MAINT)
  2. Transport Required: Depends on package type (No for local packages like $TMP, Yes for transportable packages)
  3. Entity name - The entity to make hierarchical (e.g., "Equipment", "Category", "FunctionalLocation")

For CAP Projects:

  1. Entity name - The entity to make hierarchical (e.g., "Travel", "Category", "ProductCategory")

DO NOT proceed with implementation until all inputs are confirmed.


CAP Implementation

📖 Complete CAP Implementation Guide

Quick Summary:

  • 6-step process: Check entity → Add association → Add @hierarchy → Configure manifest → Create data → Test
  • Supports UUID, String, and Integer keys (single key only)
  • Requires @sap/cds 9.6.0+ and OData V4
  • Use CDS MCP to search model before editing

ABAP RAP Implementation

📖 Complete RAP Implementation Guide

Quick Summary:

  • 4-step process: Check existing hierarchy → Implement backend → Configure manifest → Test
  • Decision required: Read-only (List Report only) vs. Editable (with Object Page)
  • For detailed backend implementation:
    • Read-Only Treeviews Guide
    • Editable Treeviews Guide

Quick Troubleshooting

CAP Common Issues

  • "@hierarchy not supported" → Use managed association (no on condition)
  • "table has no column" → Use parent_ID (with underscore) in CSV
  • "TreeTable not rendering" → Check type: "TreeTable" and hierarchyQualifier in manifest

ABAP RAP Common Issues

  • "Element must not be search enabled" → Remove @Search annotations from hierarchy projection view
  • "Primary keys do not match" → Child table needs composite key (child UUID + parent UUID)

📖 Full error reference in implementation guides


Key Differences

CAP:

  • Managed association in entity
  • @hierarchy annotation on service
  • CSV data with parent_ID column
  • Test with npm run watch

ABAP RAP:

  • CDS view with @OData.hierarchy.recursiveHierarchy
  • Qualifier in metadata
  • Test data in database tables
  • Test with npm start or npm run start-mock

Source and attribution

Source:SAP/open-ux-toolsinpackages/fiori-mcp-server/skills/sap-fiori-tree-tableat commit69e2c50

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal