Non-production landscapes are the part of the SAP estate where the licensing posture is least visible and most often misread. Sandbox, quality, test, training and pre-production environments each carry an entitlement read against the contract language and the production licence. The buyer's job is to know what the entitlement actually covers.
A typical SAP estate runs across five landscape categories. Production is the live system carrying the business workload. Quality (also QA or pre-production) replicates production for final acceptance testing. Test (development integration test) sits one step earlier. Development is the back-end where ABAP code is authored. Sandbox is the disposable copy used for experimentation and training. Each category sits under a different licensing read.
The publisher's default contractual position is that the production licence covers a limited number of non-production landscapes for the purpose of supporting production. The exact count and the exact landscape categories that fall inside the covered set vary by contract vintage, by region and by the specific entitlement document on file.
The buyer-side question is what the contract actually says. The reconciliation runs against the original Order Form, the Software Schedule, and any amendments that adjusted the non-production grant. The wider context on the system measurement and what the publisher counts sits in SAP system measurement.
Sandbox and training environments sit at the most permissive end of the non-production spectrum, in part because they typically run for short windows, with a restricted user population and without writing to production. The publisher's posture on sandboxes is typically that they fall inside the production grant, provided the use is limited and the data is non-productive.
The buyer-side risk is sandbox sprawl. An enterprise running a dozen long-lived sandboxes with full production data refresh, full integration to other landscapes and a wide user population is materially outside the implicit publisher grant. The audit triggers on user count, on data classification and on landscape persistence.
The Admodum methodology runs a landscape census at the start of the renewal cycle, classifies each sandbox by purpose, user population, data type and lifespan, and reconciles the census against the contract language. The detailed reading on the developer-side use of sandboxes sits in SAP developer licences.
Quality and pre-production landscapes are the closest mirror to production. They typically carry production-grade data, the full user-access model, the full integration footprint and the live transport pipeline. The licensing read is more careful: the publisher's grant is more limited and the audit posture more aggressive.
The buyer-side question is the user population on quality and pre-production. Where the same user accesses production and quality (which is the normal pattern for an acceptance-testing population), the licensing read collapses across the two landscapes. Where the user accesses only quality (an unusual case), the licensing read may require a separate seat.
The detailed reading on Named User counting across landscapes sits in Named User recategorisation, and the FUE-side reconciliation in FUE conversion arithmetic.
Under RISE with SAP, the non-production landscape posture changes shape. The bundled subscription typically includes a defined non-production footprint (one quality landscape and one development landscape, sized as a fraction of production), and additional non-production environments are priced as add-on subscriptions. The buyer's job is to read the bundle composition.
The full reading on the RISE bundle composition sits in Anatomy of the RISE bundle. The parallel reading on the on-premise alternative sits in RISE versus on-premise, and the on-premise non-production posture often differs materially from the RISE-bundled position.
The procurement-side question is whether the RISE non-production footprint is sized correctly for the planned development and quality cycle. The default position from the publisher is often a single quality landscape at half production capacity, which may underwrite the buyer's planned cycle.
The publisher's system measurement scans every landscape inside the licensed estate. A landscape that is outside the contracted non-production grant raises a compliance flag in the measurement output. The buyer's audit-defence posture starts with a clean landscape census and reconciles the census against the entitlement document.
The Admodum audit-defence methodology runs a parallel measurement before the publisher's window opens, reconciles the landscape inventory against the Software Schedule, and presents a clean count. Active SAP audits route directly to the Audit Defence programme.
The renewal preparation runs in mirror. The buyer assembles a clean landscape inventory, reads the inventory against the entitlement document, identifies the gaps and goes into the renewal with the gap-evidence in hand. The renewal-cycle frame sits in the SAP renewal cycle.
Six checks for the buyer reading the SAP non-production estate: classify each landscape by category and lifespan. Reconcile the landscape inventory against the contract entitlement. Audit the user-population across non-production landscapes. Price the RISE non-production composition against the planned development cycle. Run a buyer-side system measurement before the publisher's audit window. Consolidate the non-production read into the renewal package.
For the wider SAP reading, return to the SAP pillar, visit the SAP knowledge hub, or open a private conversation with a senior Admodum SAP advisor through /contact/.
A senior Admodum SAP advisor will run the methodology through with your CIO, CFO, procurement team or audit response team on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active SAP audits route directly to the Audit Defence programme.