Reference Data Models
A ready-to-deploy library of SAP S/4HANA reference data models for Finance, Supply Chain, Master Data, and Admin, in three forms: XS Classic and XS Advanced / HDI calculation views for SAP HANA, and ABAP CDS views for any S/4HANA edition, which SAP Datasphere can replicate into SAP Business Data Cloud. Every form emits the same columns, so the purchase-to-pay KPI catalog and Pinnova BDS work unchanged whichever you deploy. The KPI views that ship alongside run over the calculation views in SAP HANA. Available to Enterprise subscribers.
SAP S/4HANA models by domain, in three deployable forms
30 models over the standard S/4HANA tables, in the zpnv package across four domain packages. Each ships as an XS Classic calculation view for on-premise HANA and as an XS Advanced / HDI container for SAP HANA Cloud and Datasphere. The purchase-to-pay chain — seven of the supply chain models — also ships as ABAP CDS view entities that activate on any S/4HANA edition through abapGit and transports; that is the route into SAP Business Data Cloud. The download also includes a purchase-to-pay KPI catalog of 39 procurement KPIs; KPI views — 115 SAP HANA views across 16 purchase-to-pay analyses (duplicate invoices, three-way match, GR/IR, price variance, …), deployed on SAP HANA with tools/deploy.py views and read by any tool; the column contract every form honours; a starter configuration that registers the models as data entities in Pinnova BDS; a schema matrix of every view's deployed columns and data types; and a deployment guide for every form and the replication path.
ZCV_FI_ACCT_POSTINGS_ACDOCA (ACDOCA) and the current-versus-previous-year view ZCV_FI_ACCT_POSTINGS_CURR_PREV_YEAR.ZCV_PURCHASE_ORDER_EKPO, ZCV_PURCHASE_ORDER_DETAILS, ZCV_VENDOR_INVOICE_DETAILS, ZCV_VENDOR_SPEND_DETAILS, …) unioned end to end in ZCV_PURCHASE_TO_PAY — plus outline agreements and price lists, purchase order change logs, and inventory balance and movements. 17 views; the seven-view chain also as ABAP CDS.ZCV_MATERIAL_MASTER_MARA, ZCV_MATERIAL_MASTER_MARC), material group valuation, vendor (ZCV_VENDOR_MASTER_LFA1), and WBS masters. 9 views.ZCV_OBJECT_DEPENDENCIES).Download the models
Checking your account…
The reference data models are included with an Enterprise subscription. Sign in with your Enterprise account to download them.
Sign inNot on Enterprise yet? See plans or email quality@pinnova.com.
Signed in as — your Enterprise subscription includes the reference data models.
One zip of the latest pinnova/rdm release: the calculation views in XS Classic and XS Advanced / HDI form, the ABAP CDS views, the KPI catalog, the KPI views with the view layer they read (hana/, one guide per analysis under docs/kpi/), the column contract, the starter configuration for Pinnova BDS (bds-config/), and the deployment guide (docs/DEPLOYMENT_GUIDE.md).
From download to your first data product
-
1
Pick a form and deploy it
The deployment guide covers each form: import the
zpnvpackage into the HANA repository (XS Classic); build and deploy the HDI container (XS Advanced, HANA Cloud, Datasphere); or import the archive into an abapGit offline repository and transport it (ABAP CDS). To reach SAP Business Data Cloud, replicate the activated CDS views from Datasphere — nothing deploys into BDC itself. -
2
Create the KPI views and point Pinnova at them
Run
python tools/deploy.py viewsagainst SAP HANA: it renders the canonical view layer for your SAP client, finds the schema holding the SAP tables, reports whether the views on HANA are this release's, asks before creating anything, then creates the KPI views and the settings table their thresholds live in. Recreate them with--replaceafter each new release of the models. (tools/view_layer.pyrenders the layer's SQL to run by hand.) Any tool that reads a table reads the views. In Pinnova BDS, register the models and views you want as data entities on your HANA connection: import the starter configuration inbds-config/through the config editor, or register a view by hand from the schema and object names the guide lists for each form. -
3
Productize, profile, validate
Build data products on the governed views and run profiling and validation against them.