- Rapid loading and deployment of data from SAP S/4 HANA to Snowflake
- Completely automated, no-code solution uses Change Data Capture to sync data
- Data is immediately available on Snowflake for Reporting and Analytics in near real-time
- Data is delivered with business logic intact, no need to recreate it on target
Weber Inc. is an American manufacturer of charcoal, gas, and electric outdoor grills and related accessories. It also owns restaurants and publishes cookbooks. The company offers traditional charcoal, gas, wood pellet, portable, and electric grills, as well as carts, covers, fuel, cleaning, and cookware products. Weber has operations on a global scale and is present in multiple countries.
Weber uses its SAP technology platform to handle a a lot of operational tasks. This includes sales and operations planning, inventory management and scheduling and also cross functional applications that support finance and IT. SAP is an integral part of Weber’s IT infrastructure. In an effort to further modernize the platform, Weber transformed and upgraded its SAP instance to S/4 HANA internationally. To achieve economies of scale, cost-effectiveness and benefit from the various capabilities of the Cloud, the company decided to move data from the SAP S/4 HANA applications to Snowflake. The challenge for Weber was to extract their data from SAP S/4 HANA in near real-time to Snowflake for reporting and analytics. SAP HANA to Snowflake with BryteFlow
BryteFlow was deployed to extract data from the SAP application layer and automate the loading on Snowflake. BryteFlow automated every process on Snowflake, including data extraction, data mapping, schema, table creation, data merges and upserts including SCD type 2. A big advantage was that BryteFlow delivered the data with application logic intact. Learn about the BryteFlow SAP Data lake Builder
Weber now has an extremely scalable data implementation on Snowflake that meets its requirements of real-time reporting and analytics. The solution was deployed in just weeks and there was no coding required at any point in the implementation.