Update the data behind your reports, and know it fits your master data before you save
Your team edits in a familiar grid that writes straight to your data platform. Every value is checked while they are still in the field, and your reports show the change at once.

On this page
Guided entry with search against your master data
Compound keys, shown in full
SAP master data often needs several values to name one object. Once the controller has chosen controlling area EU01, typing “export” in the form lists the export cost centers of every company in EU01, each with its full key: controlling area, cost center and company code.
Values come live from your platform
Results come straight from the master data table or view in your platform at the moment of entry. A cost center created this morning is available this morning, and every app reads the same list.
Unknown keys find no match
A key that is not in your master data finds no match, so a typo stays out of your reports. Typing the subsidiary key BN4320 instead of BN4230 shows “No item found” before anything is entered.
A familiar grid: filter, sort, copy, paste and import
Upload a file to update the table
An Excel or CSV file maps to the table's fields, and the preview shows what will happen before anything is written: here three new rows, one update and two rows that fail a check, each marked at the cell with its reason. Duplicates inside the file are flagged the same way.
Export with texts
A download to CSV or Excel carries the master data texts next to the keys and follows the filters and sort order on screen, so the file matches what the person sees.
Business names for tables and fields
Every table and field carries a business name your team reads, while the technical name stays with your platform team and its integrations.
Intelligent forms that adapt as people fill them in
Designed by your key usersEnterprise
The form designer sets when a field is visible, read-only or required, what its default is and when it resets, each as a condition on other fields. Here the note becomes required as soon as a mapping starts during the year instead of on January 1.
The form designer is part of the Enterprise edition; the pricing page lists what each edition includes.
Defaults and helper text
Fields can start with a default or a computed value and carry a short hint below the label, so a first-time user knows what belongs there.
A form is also JSON
Every form can be written, copied and uploaded as JSON, so a form with many rules moves from one table to the next in a single step.
Hierarchies, restructured where your reports read them
Drag a node to its new parent
Dragging a node onto its new parent moves the whole branch with it. Several hierarchies, such as 2026 and 2027, sit side by side in one directory, every node carries its validity period, and a reference date shows the structure valid on that day.
Illustration from our hierarchy video. Watch the hierarchy video on YouTube.
Embedded in SAP Analytics Cloud, Power BI and Tableau

The dashboard's context filters the rows
The dashboard hands its current selection, such as a company code or a cost center, to the embedded app as a filter. The same validation and authorization apply whichever BI tool hosts the app.
One app across platforms





Validate here, write there
HR reference data in SAP Business Data Cloud serves as the validation source for classifications written to Databricks. One interface for the team, one set of rules across the boundary.
Native on each platform
SAP Business Data Cloud, Databricks and PostgreSQL are generally available. Snowflake and Microsoft Fabric are on the roadmap. The platform pages carry the architecture: SAP Business Data Cloud, Databricks.
One sign-in, through your identity provider
People sign in through your identity provider. The platform connection runs on one technical user, so maintenance-only users stay outside the platform's user management and licensing.
From data entry to the BI report, built by your own team
Create the table
A key user defines fields, types and which master data backs them. The table is created on the platform, in the schema your administrator scoped.
Maintain it in the grid or a form
Editors work in the grid, in the form or by upload. Validation and value help come with the field definitions, so each rule is built once.
See it in the report
The maintained table is available to your models and dashboards at once. The full cycle stays with the people who own the process.
Frequently asked questions
The grid works like the spreadsheet they know: filtering, sorting, copy and paste, bulk updates, file import. Value help and validation guide the entry itself, so people learn the rules of a table while they use it.
SAP Analytics Cloud, Power BI, Tableau, and any tool that supports web objects. The embedded mode shows the grid alone, and the dashboard's context filters the rows.
Yes. Excel stays an input: edit offline, upload through NextTables, and every row is validated before it is written. Keys match existing records and duplicates are flagged.
They sign in to NextTables through your identity provider. The platform connection runs on one technical user, so maintenance-only users stay outside platform user management.
Key users in the business team, in configuration rather than code: fields, master data, rules, roles. Where a rule needs logic, the built-in expression layer carries it.
NextTables is licensed as a subscription, sized by users and tables. The details are on the pricing page.
See it with your own tables
Take the deck to the team first, or spend half an hour with us on your data, in your BI tool.












