Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A SAPUI5 table is connected to data through a binding. A filter must reach the intended OData V2 request or supported client processing before the displayed rows can change correctly.

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 OData V2 filtering: Check the binding and request before the table
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.

SAPUI5 OData V2 list filtering using historical 1.38 guide/API references; confirm corresponding APIs and operation/count-mode behavior in the deployed runtime.

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

Verify the plant purchasing filter reaches the service

Did the filter reach the data request?

Search input: Customer A. Table binding: Relevant Orders binding. Outgoing request: Inspect applied filter. Returned rows: Compare with request scope
What to notice: Entering text on a screen is not proof that the intended service filter was applied.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Search input
Customer A
Table binding
Relevant Orders binding
Outgoing request
Inspect applied filter
Returned rows
Compare with request scope

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.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Filter input → Binding and request → Returned rows. Conceptual diagram for SAPUI5 OData V2 filtering: Check the binding and request before the table.
Apply the idea: A manufacturer's worklist appears filtered on screen, but its developer needs to confirm the selected business predicates reached the OData request.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. Verify the plant purchasing filter reaches the service

    A manufacturer's worklist appears filtered on screen, but its developer needs to confirm the selected business predicates reached the OData request.

  2. Prove where the filter runs and what it returns

    For a SAPUI5 OData V2 table, inspect the list binding that supplies the rows, its operation mode and the actual request or client result.

  3. Identify the model, binding and deployed UI5 version

    This example targets sap.ui.model.odata.v2.ODataModel and an Orders list binding.

  4. Worked fixture: two predicates and three expected orders

    Use an authorized test service with the illustrative rows below.

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.