Customizing is an integral part of every SAP landscape. In on-premise systems, SM30-based table maintenance is usually generated using the Table Maintenance Generator, which can be easily maintained via the SAP GUI. With the introduction of ABAP Cloud – for example, in the SAP BTP ABAP Environment, S/4HANA Cloud, or BW Bridge – the SAP GUI is no longer supported. Instead, table maintenance is performed using a Fiori-based approach. It is not mandatory in on-premise systems such as S/4HANA or BW/4HANA, but it can also be used there.The technical basis for this is the ABAP RESTful Application Programming Model (ABAP RAP). In this blog post, we show how such a solution can be implemented – and then also present NextTables, a simple and fully ABAP Cloud-compatible alternative that does not require complex RAP implementation.
Fiori-based customizing with ABAP RAP and Custom Business Configurations (CUBCO)
ABAP RAP is the central development framework in S/4HANA for creating transactional Fiori applications and web APIs. It is based on a multi-layer model that clearly separates the data model, behavior, and service provision. The data model is defined using CDS views, while behavior is described using behavior definitions. A service definition is then used to release the desired scope, and a service binding connects the whole thing to the OData V4 protocol. The OData service created in this way is consumed by Fiori Elements without any additional SAPUI5 code, as the layout and behavior of the application are controlled solely by CDS annotations and behavior definitions. The resulting applications are typically Fiori Elements list reports.
Image source: see here
The key point is that the SAP standard app Custom Business Configurations (CUBCO) ensures that the maintenance apps for the customizing tables do not have to be operated as isolated Fiori apps. “Business Configuration Maintenance Objects” are registered in CUBCO and then appear as selections in the app. This means that all customizing maintenance is carried out via a central interface instead of using lots of individual apps.
RAP objects with just a click: The ABAP Repository Wizard
To support the development process, SAP provides a wizard (ABAP Repository Objects Wizard) that generates the required RAP objects. Based on a DDIC table, this wizard creates all the development objects that are required to maintain the contents of this table. These include:
- Additional DDIC tables for draft handling and transport
- CDS views with root entity views as well as composite and projection views
- Data Control Language (DCL) objects for authorization management
- Behavior definition and implementation (ABAP class) as a managed scenario
- Service definition and binding to ODATA V4
This wizard greatly reduces the development effort that would be required if all these objects had to be created manually. After generation, a few minor follow-up tasks still need to be performed, particularly for authorization management. A highly recommended step-by-step tutorial on creating such an application can be found at SAP Developers.
Is SAP BW Bridge a smart transition or rather a detour?
Download the Whitepaper here!
Example: From a customizing table to a Fiori app
The following example shows how the wizard can be used to quickly transform a simple customizing table into a Fiori-based maintenance application. The starting point is a simple Z table for managing functions and active statuses, which we created on the BW Bridge of our SAP Datasphere demo system. The wizard automatically generates all the necessary RAP objects based on this table.
Once generation is complete, the necessary authorization settings have been made, and the OData service has been activated, the created application can be accessed directly via the SAP standard app Custom Business Configurations (CUBCO). There, your own table appears as an entry in the overview and can be opened and edited directly in the maintenance view.
NextTables – the smarter alternative
With NextTables, we have a product on the market that is designed for the specific requirements of modern self-service data maintenance and offers a significantly simpler and more flexible alternative to the approach described above.
NextTables is fully ABAP Cloud-compliant and can therefore be operated in S/4HANA systems as well as on the SAP BTP ABAP Environment, for example in the BW Bridge. The solution is much more than just table maintenance. It enables self-service data management in almost all scenarios: from classic customizing tables to master data and data maintenance to simple planning and rule tables in BW or Embedded BW systems.
In this section, we will show you how the customizing table from the example above can be integrated into NextTables and edited directly in just a few simple steps.
As you can see, creating a maintenance view in NextTables is done in no time at all. In the central configuration view, you can configure all settings for each table to tailor the maintenance interface exactly to your requirements—both in terms of layout and available functions. No additional objects are generated in the background. All adjustments are made directly via the interface, and changes can be made immediately in the configuration at any time.
For special requirements, such as the implementation of individual business logic or validation rules when creating or changing data records, NextTables offers a simple BAdI concept. This allows company-specific checking or processing steps to be integrated in a targeted manner.
RAP vs. NextTables – which one performs better in practice?
SAP has established a modern standard for table maintenance in ABAP Cloud based on ABAP RAP, which quickly delivers initial results thanks to the wizard provided. However, as soon as special business logic or modifications to the process are required, the technical complexity increases significantly.
The wizard generates a large number of objects, and a deep understanding of the underlying technologies is required in order to make targeted modifications. These include, in particular, CDS entity views for describing the RAP business model (with root entity, composite, and projection views), the use of annotations (e.g., for UI and layout), and behavior definitions as a separate declarative syntax for describing the behavior of a business entity and its implementation with ABAP Cloud. Equally important is a basic understanding of OData and Fiori Elements. In addition, there are certain prerequisites that must already be met at the table level in order for the wizard to be used at all. These are not always given and often require prior adjustment of the tables in practice.
With NextTables, all settings and functions can be made directly in the tool via the central configuration view. Numerous functions are available as standard, without any additional development. Only for special requirements, such as the implementation of individual business logic, is the implementation of a BAdI in ABAP necessary.
What the NextTables standard offers:
- Support for all relevant table types (SAP DDIC tables, BW providers, InfoObjects)
- Intuitive search help and data maintenance functions (create, edit, copy, delete)
- Easy table customization – sorting, column order, show/hide, automatic column width, key/text display
- Advanced functions such as export, pivot service, and more
- Collaboration with templates (saved views) – including direct URL sharing via email
- Excel-like inline editing
- Multiple editing: change, delete, or copy multiple records at once
- Import functions for clipboard as well as large CSV and Excel files
- Individual documentation for tables and fields
- Comprehensive design customization of the user interface
- Detailed authorization control for table access
Our Conclusion: A Comparison between table maintenance with ABAP RAP and NextTables
Category |
ABAP RAP / CUBCO |
NextTables |
Setup effort |
⚠️ Medium Many generated objects, rework required |
✅ Very low Setup directly via interface |
Technical know-how required |
❌ High Knowledge of RAP, CDS, OData, ABAP Cloud required for modifications |
✅ Low No technical knowledge required, only ABAP knowledge for BAdI requirements |
Functionality |
⚠️ Basic funcstions Basic functions (maintenance, copy, transport, draft) |
✅ Advanced Filters, pivot, export, templates, multi-edit, Excel import, and much more |
Business logic can be extended |
⚠️ Medium Via behavior implementation in ABAP |
✅ Easy Via supplied BAdI |
Supported table types |
⚠️ DDIC tables |
✅ DDIC tables, BW-Provider, InfoObjects |
Maintenance & changes |
❌ Complex |
✅ Simple Changes can be made at any time via the UI |
Authorization control |
✅ SAP standard Combination of DCL and authorization objects. Enables granular, role-based access control |
✅ Integrated Own authorization object. Supports differentiation between read, write, config admin, content admin, and super admin |
ABAP Cloud conformance |
✅ Yes |
✅ Yes |
Get more information about how NextTables is making data editing easier by visiting our page.
Do you have questions on this or another topic? Simply get in touch with us - we look forward to exchanging ideas with you!
Do not miss out on our upcoming webinar: "Bridging Business and Analytics: The Plug-and-Play Future of Data Platforms".
FAQ - ABAP RAP vs NextTables
Here are some of the most frequently asked questions about SAP Fiori table maintenance.
A central maintenance hub: registered Maintenance Objects appear as entries and are edited there.
The complete ABAP RAP object structure for table maintenance, including draft tables, CDS views (root/composite/projection), DCL, behavior (definition+implementation), service definition/binding (OData V4).
Kickoff is fast with the wizard; tailoring (annotations, behavior, CDS/OData) raises complexity significantly.
RAP, if you want Fiori table maintenance in SAP Standard – with full access to CDS, Behavior, and OData, but with higher development costs. NextTables, if you are looking for a ready-to-use solution for table maintenance and data management with a wide range of functions.
