/Logo%202023%20final%20dunkelgrau.png?width=221&height=97&name=Logo%202023%20final%20dunkelgrau.png)
NextTables sits in its own dedicated namespace alongside your objects, and runs on the hardware your Basis team looks after. Your users open it in their browser.
- Everyone signs in with their own SAP user, and sees exactly the apps, tables and rows their SAP authorizations allow.
- Configuration travels by transport request, so your release process stays your release process.
- Installation, the first tables, the authorization design and the transport route are part of the work we do on a project.
Out of the box
Your Basis team imports the transports the same way it imports everything else.
Built for business teams
Inline edits, multi-row changes, paste straight from Excel, and imports that come back with a row-by-row validation report. Search help resolves the right value against your SAP BW master data.
Validated, authorized, auditable
Every entry is validated before it is written. Access is your SAP analysis authorizations, inherited unchanged, down to the row. And every change is accountable, through the ADSO change log or locked "last changed" fields we set up by configuration.
Ready for what comes next
When you modernize onto SAP Business Data Cloud or SAP Datasphere, the same maintenance capability is there in the cloud edition. Both editions are current products, and we implement both.
Edit SAP BW data like a spreadsheet
Your team changes a mapping, a classification or a figure that needs correcting, one cell or a thousand rows at a time. Multi-row edits, clipboard paste from Excel, and validation running field by field as people work.
- The business maintains its own data.
- On your analysis authorizations, down to the row.
Land on the right value, every time
Search help reads your SAP BW master data as your team types. Fuzzy search finds near matches on SAP HANA even with a typo, and a column can be set to require a valid value before the row saves.
- The right code, found by name.
- Values that already exist in your master data.
Bring in a spreadsheet, checked as it lands
Drop an Excel or CSV file into the grid and every row is checked against your rules before anything is written. Currency symbols stripped, formats normalized, duplicate keys flagged. Rows that still fail stay out of SAP BW.
- Bulk changes at spreadsheet speed.
- Every row validated before it reaches SAP BW.
Maintain the data from inside the dashboard
The grid embeds as a web object in any BI tool that supports them, so someone fixes a number in the report where they spotted it. URL parameters open the embedded grid filtered to the record in view.
- Maintenance happens where the decision happens.
- The same validation, embedded or standalone.
Real-time presence. A row locks while a colleague edits it, and you can see who.
The import monitor. Paste or drag a file in, and watch every row as it lands.
Most tables are ready to maintain in minutes, through configuration alone: add a table, an ADSO or an InfoObject through the wizard, set the column rules, and it is live. Your ABAP team keeps its backlog for the work that needs them.
- Bring in a DDIC table, a DataStore object or an InfoObject through the wizard.
- Set per-column rules, value help, locks and required fields as settings.
- Group tables into applications a department recognizes.
- Ship it the way you ship everything else, by transport request.
Set up by wizard
The common case is a configuration job, and it travels by transport like the rest of your SAP changes.
Validation as far as ABAP goes
Any rule you can express, from a required field to a cross-system lookup, before the row is written.
Shape the read, write and metadata
Derive a field on save, or go as far as a fully virtual table your own logic composes and writes back.
Custom buttons and process chains
When you modernize onto SAP Business Data Trigger an SAP BW process chain the moment data lands, so the next load starts itself.
NextTables was built inside our own SAP practice, and although it is an independent company today, our consultants wrote it. That shows up in the two things hardest to buy in: knowing which tables are worth onboarding first, and knowing what the product does when a table is awkward.
Most of the time the alternative is a custom write-back build. We have delivered plenty of those, and we know what they cost after go-live. The form is the easy part. Validation that holds against your master data, row-level access that survives an authorization review, and a change record somebody can read in two years are what take the budget, and they get rebuilt from scratch on the next project. Configuring NextTables gives you all three once, and again on the project after that.
20+ customers
Across 30-plus releases and counting.
Tell us which tables are costing your team the most time. We will tell you what an implementation looks like on your landscape.
Running on SAP S/4HANA?
Business teams maintain custom tables directly, in a validated grid, with access decided by the SAP authorizations you already run.
- Any custom table, your own Z tables included.
- The data in your embedded SAP BW, the same way.
- The same add-on, the same licence, the same transport route.
Or the cloud edition
Both editions are current products and the maintenance capability is the same on each. Start where your data is.
- SAP BW: inside your SAP system, your SAP users.
- Cloud: on your data platform, enterprise SSO.
More on NextTables from our blog
How to Fix the Gaps in SAP Datasphere's Standard Time Dimension
SAP Seamless Planning: Three Ways to Integrate External Data
See it on your own SAP BW
Every month it waits is another month of exports, failed loads and handovers. We will walk your landscape with you, name the tables worth starting with, and tell you plainly what an implementation involves and what it does not.
