Case Solutions
Here we showcase real‑world success stories, highlighting the technologies we used and the high‑level approach we took to solve each challenge.
RAP List Report with Excel Upload
RAP (RESTful ABAP Programming) list reports let you display large datasets as pageable, filterable tables built on CDS views and OData services. By adding an Excel‑upload feature, users can import bulk data directly into the underlying table via a predefined template. The UI (Fiori Elements) presents an “Upload” button, parses the Excel file and sends it to the backend (ABAP) for further processing. Errors are reported per row, allowing correction before the data is saved, streamlining mass‑maintenance while preserving RAP’s transactional consistency and authorization checks.
Custom flexible Workflow
A custom flexible workflow for EHS chemical changes captures any modification to chemical master data and triggers automated email notifications. Administrators define trigger fields (e.g., hazard class, regulatory status) in the app; when those fields are updated, the workflow starts. It evaluates the change, selects recipients based on role, user, or custom rules, and sends a templated email containing the altered values, justification, and links to the record. Users can configure additional approvers or escalation paths, ensuring compliance tracking and timely communication while leveraging SAP Business Workflow’s extensibility and notification services.
APIs OData V2 and V4
Standard OData V2/V4 APIs expose SAP business objects via REST. Enhancing them involves extending generated service metadata, adding custom fields, actions, or filters while preserving backward compatibility. When the system supports RAP, you create a custom RAP‑based OData service (V2 or V4 depending on the release) that implements the same entity sets but leverages RAP’s CDS‑driven modeling, transactional handling, and draft support. Additionally, RAP can encapsulate BOPF (Business Object Processing Framework) objects, exposing their methods through the OData service while keeping BOPF’s lifecycle, validation, and authorization logic intact, thus unifying classic BOPF and modern RAP paradigms.
UI5 custom libraries
Custom UI5 libraries bundle reusable components, models, and utilities into a modular package that can be shared across multiple applications. Developers create a library project (e.g., my.company.lib) with its own namespace, defining controls (XML/JS), formatter functions, and data‑binding helpers. The library’s manifest.json declares dependencies, version, and exported modules. Apps then add the library as a dependency in their manifest.json, import its controls, and inherit consistent styling and behavior. This approach reduces duplication, eases maintenance, and ensures uniform UX across related SAP UI5 apps.
Enhancing Standard Apps
Enhancing classic SAP GUI transactions can be done traditionally with BADIs, screen exits, or enhancements to insert custom logic and UI elements. Modern approaches replace or complement these by adding custom fields via the Fiori “Custom Fields and Logic” app, creating CDS view extensions to enrich data models, and implementing UI5 extensions (view‑or‑controller or component‑based) to overlay new controls on existing SAP Fiori screens. Together, these techniques cover all enhancement paths: legacy ABAP hooks for deep backend changes, and contemporary SAP UI5/CDS/Fiori methods for flexible, UI‑centric extensions that preserve upgrade compatibility and deliver a consistent user experience.
