Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A growing table loads additional rows as needed rather than showing the entire dataset at once. The visible or loaded rows therefore may be only part of the available business data.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Fiori is SAP’s design approach for business applications. SAPUI5 is a user-interface toolkit, and Fiori elements uses metadata to generate common application patterns.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAPUI5 growing tables: Loaded rows are not the complete business dataset
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

Read-only sap.m.Table/ListBase growing with OData collections; historical 1.38 control references and 1.120 performance guidance require deployed-version checks. sap.ui.table.Table has different APIs.

Primary documentation reviewed on 14 November 2026 using official indexed excerpts. Documentation review only; authored examples were not compiled or executed in an SAP system.

A MANUFACTURING EXAMPLE

Avoid treating loaded orders as the whole plant backlog

Visible rows versus available data

Available orders: 250. Initially loaded rows: 20. Growing behavior: More rows on demand. Current table count: Not necessarily total dataset
What to notice: Do not use the number currently loaded into the table as the complete business-record count.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Available orders
250
Initially loaded rows
20
Growing behavior
More rows on demand
Current table count
Not necessarily total dataset

A REAL SCREEN TO RECOGNIZE

SAP’s Fiori elements feature showcase. The filter bar, table columns and row actions are distinct UI regions. Compare the region discussed in this guide with the corresponding service and metadata.

SAP’s Fiori elements feature showcase. The filter bar, table columns and row actions are distinct UI regions. Compare the region discussed in this guide with the corresponding service and metadata.

View the original SAP example ↗ · License

© 2021 SAP SE or an SAP affiliate company and project contributors. Apache-2.0. Reproduced unchanged for educational commentary. This is a source example, not a capture of your system.
Words you’ll meet in this guide
Binding
A connection between a screen control and data.
Metadata
Information describing data or how it should be used.
Service
A software interface that provides data or operations.
Backend
The system or service that provides business processing behind the interface.
OData
A standard for reading and updating data through a web API.
API
A defined interface through which programs exchange data or request actions.
XML
A format that organizes data into named, nested elements.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Business dataset → Loaded page → Additional rows. Conceptual diagram for SAPUI5 growing tables: Loaded rows are not the complete business dataset.
Apply the idea: A manufacturing worklist initially loads only part of an order collection, while a manager asks for the complete affected population.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Avoid treating loaded orders as the whole plant backlog

    A manufacturing worklist initially loads only part of an order collection, while a manager asks for the complete affected population.

  2. A growing table contains a changing subset of the query

    A growing sap.m.Table requests additional items as needed.

  3. Scope the control and model before changing a threshold

    The example is a read-only sap.m.Table with an OData list binding.

  4. Worked fixture: 20 loaded orders out of 250

    Create 250 authorized orders O001 through O250, each with an amount of 10 EUR.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.