Self-Service Product Change Reporting for a Global Medical Device Manufacturer
From support-driven report generation to self-service access to product change history.
Quick Info
Solution
This reporting functionality was developed as part of a broader product management solution built on top of SAP Commerce to simplify day-to-day operations for business users. Within that larger environment, one of the client’s goals was to improve visibility into product changes and employee activity based on modification data already stored in SAP Commerce.
Starting with a practical reporting foundation
SAP Commerce recorded product changes in its saved values data, which created a solid basis for reporting. To address the immediate need, the reporting functionality was initially built around a Groovy script running as a cron job. This approach was chosen deliberately over standard SAP Commerce reporting tools such as Jasper Reports, as it better matched the support team’s existing skill set and allowed the client to operate the feature without extensive additional training.
While this approach covered the core reporting need, it still depended on support teams to run the script, define parameters, and deliver the output to stakeholders. As reporting requests became part of ongoing business operations, this process created unnecessary dependency and slowed access to change history.
Evolving into self-service reporting
To make reporting more accessible, the reporting logic was extended through APIs and connected to the product management interface. Business users could now generate reports directly by entering parameters such as region, date, and employee name, with the system automatically processing the request and sending the results by email. The original Groovy-based core remained in place, while API-based parameter handling made the feature more flexible and user-facing.
As usage expanded, the reporting capability continued to evolve. The reports were incrementally refined to make the output more readable and practical for everyday use, while keeping the focus on clear access to historical change data rather than adding analytical or predictive logic.
Results
