From the Project Archives
This project showcases earlier work using technologies from a previous era of SAP development. It is preserved here for historical reference and to illustrate the breadth of experience built up over the years.
Project Overview
In the gaming retail industry, articles — games, consoles, accessories — flow through a constant lifecycle: announced, pre-order, release, budget re-release, permanent price drop, discontinued. Each article requires master data across multiple SAP modules: material master, vendor info records, pricing conditions, and web-specific data for the online shop and store register software.
The standard SAP approach required navigating a dozen separate transactions and entering data in the correct sequence. For a busy purchasing department managing hundreds of articles per month, this was slow, error-prone and frustrating.
This custom ABAP transaction consolidates all article maintenance into a single tabbed cockpit. All data is entered once and saved in a single operation using BAPIs and batch input maps. Article creation that previously took 15 minutes now takes 30 seconds.
Features
- Single-screen cockpit replacing a dozen standard SAP transactions
- Article creation in ~30 seconds (vs. ~15 minutes standard process)
- Integrated with the web shop and store register software
- Tab-based layout covering all article data domains
- Full article maintenance history log
Tab Overview
| Tab | Content |
|---|---|
| Main Article | Standard SAP material master data |
| Info Records | Vendor records and pricing information |
| Conditions | Pricing conditions |
| Store Register | Store software data, temporary & permanent price actions |
| Web Tools | Web-specific material data (PEGI, categories, etc.) |
| Web Texts | Web-facing text fields and search keywords |
| Article Linking | Related article links for web shop cross-sell/upsell |
| History | Maintenance audit trail |
Technical Implementation
The transaction is built as an ABAP OO application using SAP GUI Controls (tree, grid, tab strip) for the cockpit UI. On save, all data is written via SAP BAPIs and batch input maps in the correct sequence. SAP Workflow is used for the article approval process before the data becomes active in the system.
Technologies Used
- ABAP OO
- SAP GUI Controls (TabStrip, Grid, Tree)
- SAP BAPIs
- SAP Batch Input Maps
- SAP Workflow
Project Gallery
Technologies Used
All showcased content, designs, and solutions remain the intellectual property of the respective clients. For any copyright inquiries, please contact us.