Loading a warehouse
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.
Overview
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.
Not covered: 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.
BW here is SAP BW/4HANASAP BW/4HANASAP's data warehouse product for on-premise and private-cloud landscapes, optimised for the HANA database and installed rather than subscribed — the 2023 release is current, with its own master and upgrade guides. Outside the atlas because there is no adoption decision to model: you have a BW system or you do not, and what is entered here is the tooling that reaches one. or a BW release on NetWeaver; the routine behaviour is read from the BW 7.5 documentation.
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. ERPLERPLA DuckDB extension that reads SAP ERP tables, CDS views and BW queries from SQL over RFC, BICS and ODP, and can mount an SAP system as a DuckDB catalog to join against other data.independent, abap pulls SAP ERP and BW data into DuckDB through ODP extraction, in full and delta.
Artifacts
Details
Coverage
For your agent
- Ref
capability:warehouse-loading- JSON
- /capabilities/warehouse-loading.json
- MCP
- Connecting an agent