{"ref":"capability:warehouse-loading","page":"/capabilities/warehouse-loading","json":"/capabilities/warehouse-loading.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"warehouse-loading","name":"Loading a warehouse","domain":"data-and-persistence","ecosystems":["btp","abap"],"universal":false,"description":"Getting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from [replication](capability:replication), which is an application reading data that lives elsewhere as if it were local rather than a warehouse being filled.","short":"Getting data into an analytical store and keeping it current","core_coverage":{"state":"core-and-community","assessed_at":"2026-09-10","relationship":"unassessed","what_core_does":"The product owns the pipeline and the roles around it: in Datasphere, a space administrator or integrator creates connections to source systems and databases and schedules and monitors data replication and other data integration tasks, alongside importing business content and controlling access to the space.","where_it_stops":"At the tenant's own scheduler and monitor. What ran, what failed and what has to be re-run is visible in the product, and getting that into whatever else watches your landscape is nobody's job by default.","note":"SAP's answer here is a product rather than a service you bind, and the products are now entries — Datasphere, Analytics Cloud, Business Data Cloud and HANA Cloud as BTP services, BW/4HANA as an external because it is installed rather than subscribed. Both sides of this assessment are artifacts.","sources":[{"url":"https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0/8f98d3d3d4914fbf9c0e0a41c2fee6cc.html","title":"Integrating Data and Managing Spaces in SAP Datasphere — SAP Help Portal","checked":"2026-09-10","quote":"can schedule and monitor data replication and other data integration tasks"}],"community_adds":"Tools that reach the loading surface from outside the product: BW's Push API and request monitor, SAC's import-job lifecycle, Datasphere's ETL extraction, and SAP's [dbt-sap-hana-cloud](artifact:sap-samples-dbt-sap-hana-cloud) adapter, which loads dbt models into SAP HANA Cloud."},"history":[{"date":"2026-09-10","field":"entry","from":null,"to":"created","reason":"Named alongside analytic-modelling and data-cataloguing so the data and analytics artifacts have concerns to answer rather than only a protocol to be."},{"date":"2026-09-10","field":"core_coverage.note","from":"The core's answer here is an SAP product rather than a service you bind, and none of those products — Datasphere, Analytics Cloud, Business Data Cloud, BW/4HANA — is an entry in the atlas yet. So the community side of this reading is artifacts and the core side is prose with a citation. That asymmetry is a gap in our coverage, not a statement about the ecosystem.","to":"SAP's answer here is a product rather than a service you bind, and the products are now entries — Datasphere, Analytics Cloud, Business Data Cloud and HANA Cloud as BTP services, BW/4HANA as an external because it is installed rather than subscribed. Both sides of this reading are artifacts.","reason":"The note said the core side of this reading was prose with a citation because SAP's products were not entries. They are now, so the admission is retired rather than left standing as a stale caveat."},{"date":"2026-09-14","field":"ecosystems","from":"btp","to":"btp, abap, hana","reason":"pawelwiejkut's bw_remove_characters and bw_trfn_pocketknife answer the concern inside SAP BW transformation routines on ABAP, and SAP-samples' dbt-sap-hana-cloud answers it on HANA Cloud with a dbt adapter that transforms and loads data there."},{"date":"2026-10-17","field":"description","from":"Getting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from [replication](capability:replication), which is a CAP service reading data that lives elsewhere as if it were local rather than a warehouse being filled.","to":"Getting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from [replication](capability:replication), which is an application reading data that lives elsewhere as if it were local rather than a warehouse being filled.","reason":"Keep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit."},{"date":"2026-10-26","field":"core_coverage.community_adds","from":"Tools that reach the loading surface from outside the product — BW's Push API and request monitor, SAC's import-job lifecycle, and Datasphere's ETL extraction.","to":"Tools that reach the loading surface from outside the product: BW's Push API and request monitor, SAC's import-job lifecycle, Datasphere's ETL extraction, and SAP's dbt-sap-hana-cloud adapter, which loads dbt models into SAP HANA Cloud.","reason":"Reassessed against the graph (check:capabilities): the dbt adapter for SAP HANA Cloud is a provider the text never named. State unchanged."},{"date":"2026-10-26","field":"coverage_by_ecosystem.abap.community_adds","from":"Reusable ABAP classes for those routines: one strips characters ... a class to a transformation's start routine from the transformation's ID ...","to":"Same text, plus: ERPL pulls SAP ERP and BW data into DuckDB through ODP extraction, in full and delta.","reason":"Reassessed against the graph (check:capabilities): ERPL is a provider the text never named, and it loads from ABAP systems outside BW routines. State unchanged."}],"coverage_by_ecosystem":{"abap":{"state":"core-and-community","assessed_at":"2026-09-14","relationship":"unassessed","what_core_does":"SAP BW transformations carry ABAP routines for rules the mapping cannot express: a start routine runs on each data package before the rules, an end routine post-processes each package after them, and an expert routine covers cases the other functions cannot.","where_it_stops":"At the hook. Each routine is generated into its own transformation's program, so a check every flat-file load needs, such as removing characters an InfoObject rejects, still has to be written into or called from every transformation that runs it.","note":"BW here is [SAP BW/4HANA](external:sap-bw4hana) or a BW release on NetWeaver; the routine behaviour is read from the BW 7.5 documentation.","sources":[{"url":"https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/4a/489a4b826114d1e10000000a42189c/content.htm","title":"ABAP Routines in Transformations — SAP Help Portal (BW 7.5)","checked":"2026-09-14","quote":"The start routine is run for each data package at the start of the transformation."}],"community_adds":"Reusable ABAP classes for those routines: one strips characters an InfoObject would reject at activation from an end routine, another attaches a class to a transformation's start routine from the transformation's ID so each one is not edited by hand. [ERPL](artifact:datazoode-erpl) pulls SAP ERP and BW data into DuckDB through ODP extraction, in full and delta."}},"framing_by_ecosystem":{"abap":{"description":"On ABAP this is loading SAP BW, where each transformation from a source into a DataStore object may carry ABAP start and end routines, and those routines are where custom cleansing and checks run."},"btp":{"description":"Getting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from [replication](capability:replication), which is a CAP service reading data that lives elsewhere as if it were local rather than a warehouse being filled."}},"drafted_with_ai":true},"sap_delivery":{"door":"btp","all":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:sap-samples-dbt-sap-hana-cloud","name":"dbt-sap-hana-cloud","json":"/artifacts/sap-samples-dbt-sap-hana-cloud.json"},{"ref":"artifact:btp-analytics-cloud","name":"SAP Analytics Cloud","json":"/artifacts/btp-analytics-cloud.json"},{"ref":"artifact:btp-datasphere","name":"SAP Datasphere","json":"/artifacts/btp-datasphere.json"}]},"by_flavor":{}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:mariodefelipe-sap-datasphere-mcp","name":"@mariodefe/sap-datasphere-mcp","json":"/artifacts/mariodefelipe-sap-datasphere-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:dnic-dev-bw-modeling-mcp","name":"bw-modeling-mcp","json":"/artifacts/dnic-dev-bw-modeling-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:sap-samples-dbt-sap-hana-cloud","name":"dbt-sap-hana-cloud","json":"/artifacts/sap-samples-dbt-sap-hana-cloud.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:datazoode-erpl","name":"ERPL","json":"/artifacts/datazoode-erpl.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:pawelwiejkut-bw-remove-characters","name":"pawelwiejkut/bw_remove_characters","json":"/artifacts/pawelwiejkut-bw-remove-characters.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:pawelwiejkut-bw-trfn-pocketknife","name":"pawelwiejkut/bw_trfn_pocketknife","json":"/artifacts/pawelwiejkut-bw-trfn-pocketknife.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:btp-analytics-cloud","name":"SAP Analytics Cloud","json":"/artifacts/btp-analytics-cloud.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:btp-datasphere","name":"SAP Datasphere","json":"/artifacts/btp-datasphere.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:jumenengels-sac-mcp","name":"sap_analytics_cloud_mcp","json":"/artifacts/jumenengels-sac-mcp.json","ecosystem":"btp","origin_ring":"independent"}],"samples":[{"ref":"artifact:sap-samples-sap-bdc-explore-hyperscaler-data","name":"SAP-samples/sap-bdc-explore-hyperscaler-data","json":"/artifacts/sap-samples-sap-bdc-explore-hyperscaler-data.json"},{"ref":"artifact:sap-samples-teched2025-da260","name":"SAP-samples/teched2025-DA260","json":"/artifacts/sap-samples-teched2025-da260.json"}],"explained_by":[{"ref":"content:devtoberfest-2026-dat-13-bw-modernization-bdc","name":"Strategy and Tool Updates on BW Modernization with SAP Business Data Cloud","json":"/content/devtoberfest-2026-dat-13-bw-modernization-bdc.json"},{"ref":"content:sap-datasphere-integration-patterns-lessons-learned-from-two-years-of-implementa","name":"SAP Datasphere Integration Patterns: Lessons Learned from Two Years of Implementations","json":"/content/sap-datasphere-integration-patterns-lessons-learned-from-two-years-of-implementa.json"},{"ref":"content:ac-explore-your-hyperscaler-data-with-sap-business-data-cloud","name":"Explore your Hyperscaler data with SAP Business Data Cloud","json":"/content/ac-explore-your-hyperscaler-data-with-sap-business-data-cloud.json"},{"ref":"content:ac-medallion-reference-architecture-for-big-data-processing-in-sap-hana-cloud","name":"Medallion Reference Architecture for Big Data Processing in SAP HANA Cloud","json":"/content/ac-medallion-reference-architecture-for-big-data-processing-in-sap-hana-cloud.json"}],"normative_context":[]}}