AETHERSPEND™ / TECHNICAL EVALUATION
Clear about the architecture.
Specific about the fit.
Evaluate a working manufacturing purchasing showcase against your own SAP landscape. Start with the documented baseline, then agree the deployment and acceptance work.
THE REFERENCE LANDSCAPE
Start with the demonstrated baseline.
Product screens and engineering evidence describe the reference implementation. Target-system compatibility and production readiness are evaluated separately.
| Area | Current evidence | What to establish for your organization |
|---|---|---|
| Documented showcase | SAP S/4HANA 2022 · ABAP 7.57 | The reference baseline for a fit discussion. |
| Modern experience | RAP · OData V4 · Fiori Elements / Flexible Programming Model | Check capability level, service publication and Launchpad setup in your target landscape. |
| Classic experience | SAP GUI with the shared ABAP application engine | A classic screen does not establish ECC compatibility. |
| Other S/4HANA releases | Assessment required | Review APIs, native artifacts, authorizations and acceptance scenarios. |
| ECC or S/4HANA Cloud Public Edition | Compatibility is not established | Discuss your landscape; a supported delivery cannot be assumed from the showcase. |
ONE ENGINE, TWO EXPERIENCES
Preserve the business rules.
Classic SAP GUI and the modern RAP/Fiori surface reuse the ABAP calculation boundary. Compact decision adapters map engine results; PO evidence uses the secured CDS/service path for filtering and paging.
Monetary results stay in their document currencies. The browser presents the result rather than inventing a converted enterprise total.
Examine the engineering evidenceSupplier ranking, concentration and governed decisions.
Scoped supplier aggregation with native currencies kept separate.
ACCESS, DATA & FOLLOW-UP
Agree the operating boundaries.
Purchasing scope
Purchasing reads use the signed-in SAP user's secured context, including display checks for document type, purchasing group, purchasing organization and plant.
Confirm restricted-user behavior against your actual roles and test data.
Saved decisions
The Watchlist is creator-owned. It preserves decision-at-creation fields, with notes and lifecycle actions governed by the backend.
ETags protect against silent concurrent overwrites. Shared team assignment requires a separate design.
Deployment
Agree packages, namespace, transport route, service publication and Launchpad configuration. Some SAP-native artifacts require transport or reconstruction.
This public website is a marketing and evaluation surface; it does not connect to your SAP data.
PREPARE YOUR DISCUSSION
Four areas to bring into focus.
Landscape
- SAP product, release and ABAP capability level.
- Fiori, OData V4 and RAP availability for the intended modern experience.
- Relevant purchasing data, organizations, currencies and a representative review scope.
Access and ownership
- Named development, Basis, security and purchasing owners.
- Display-authorization scope for document type, purchasing group, purchasing organization and plant.
- Agreement on creator-owned Watchlist access, note editing, retention and review responsibilities.
Delivery
- Approved package, namespace, transport and service-publication approach.
- Required SAP-native artifacts and target-system reconstruction steps.
- Launchpad configuration, roles and a support/handover arrangement.
Acceptance
- Representative GUI, service and Fiori result comparisons by currency.
- Restricted-user tests, stale-update checks and lifecycle checks.
- Realistic data volumes, performance measurements and a controlled target-system installation rehearsal.
Restricted-user checks, realistic-volume performance tests and a controlled target-system installation are part of acceptance planning. A clean-system zero-touch installation is not certified.
A PRACTICAL NEXT STEP
Review the evidence at your pace.
The resources are available without sign-in or an enquiry form.