Difficulty Querying Replicated SQL Tables Outside SAP Commerce – Guidance or Alternatives for Business-Ready Data Export

[gpolito]

Hi SAP team,

Thanks for providing this tool — it’s been helpful for setting up data replication from SAP Commerce.

We’ve encountered a challenge: the tool replicates the raw SQL tables from SAP Commerce, which are tightly coupled to the platform’s internal data model. When trying to query this data outside of SAP Commerce (e.g., in a data lake or data warehouse in AWS), we run into difficulties because: • The structure is not optimized for direct SQL querying. • Many values rely on FlexibleSearch resolution — such as localized attributes, type hierarchies, relations, and other abstractions.

This makes it quite complex to extract meaningful, business-friendly data from the replicated tables without rebuilding a lot of internal SAP Commerce logic externally.

We’re considering alternative approaches, such as building custom export jobs using FlexibleSearch queries or using Integration APIs to expose denormalized views of orders, customers, products, etc.

Would you be able to advise on any of the following? 1. Are there any recommended tools, patterns, or extensions for exporting business-level SAP Commerce data to external systems? 2. Is there any internal roadmap or known community solution that addresses this gap — especially for analytics or integration scenarios? 3. Would it be feasible to extend this project in a way that includes a mode to export business-oriented datasets (e.g., via pre-defined views or queries)?

Appreciate your input and thanks again for the work on this project!