The dashboard layer that inherits every limit

The front end is only as fast as the system behind it. Live connections send every click back to the source, blending is off for live models, and even sending a report on a schedule is license arithmetic.

RuleModel once in a warehouse you own. Then any reporting tool works, and sending a report is not a licensing question.

Neverpromise the business scheduled distribution before reading the publication limits. The ration is documented, per hour and per license count.

◆ Live means round tripevery interaction goes back to the source, and waits.

A live connection stores nothing in the dashboard layer. Every filter click, drill, and page load becomes a query against the source system, so a story inherits the source’s performance, its load, and its limits. SAP’s own guidance is candid that story performance depends on the backing system.

The complaint threads are about exactly that: stories taking up to minutes per load against live sources, tuned at the source because there is nowhere else to tune them. The dashboard did not add the slowness. It just cannot subtract it.

◆ Blending and the publication rationthe documented walls, with the numbers.

Blending, combining two models in one visualization, is not available for every model type. SAP notes 2915065 and 3466290 document that blending is unavailable for S/4HANA and BW live models in the optimized story mode. The data has to meet somewhere, and with live models it has nowhere to meet.

Scheduled distribution is rationed by license count, and these numbers are vendor-documented in the product help:

Published limit	The number
Publications per hour	1 per 20 licenses, so 5 per hour at 100 licenses.
Recipients outside the product	3 per publication, maximum.
Creating any schedule at all	25 licenses minimum.
Burst mode	One license per recipient.

Read that as a distribution budget. A 40-license shop gets 2 publications per hour, 3 outside recipients each. The monthly pack for 200 suppliers is not a feature request; it is a license order.

◆ The owned answermodel once, then distribution is a loop, not a license.

Model the data once in your warehouse, fed by the extraction pattern, and the walls fall together. Any reporting tool queries the model, blending becomes an ordinary join, and a scheduled report is a small job that renders a PDF and mails the whole list. Distribution stops being license math because nothing meters it.

The layer underneath has the same lesson: the delivered analytics keep no history by design, and the managed warehouse sold as the fix has its own cost story. The model you own answers all three pages at once.

Use case

Problem

Dashboards on live connections inherit source performance, cannot blend live models, and ration scheduled publications by license count.

What we build

A modeled layer in your warehouse fed by the extraction pattern, with reporting and scheduled distribution built on top of it.

What you get

Stories that respond in seconds, joins that just work, and report distribution sized by your recipient list instead of your license count.

Is your report schedule a licensing question?

We build the owned model where distribution is a loop over a list.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
ERP: Enterprise resource planning, the system of record for operations and finance.
SAC: SAP Analytics Cloud, the vendor’s dashboard and planning product.
BW: Business Warehouse, SAP’s classic data warehouse product.
PDF: Portable document format, the file a scheduled publication delivers.
live connection: A dashboard link that queries the source system on every interaction.
blending: Combining two data models inside one visualization.
publication: A scheduled, rendered story sent to a recipient list.