Networked EXtraction & Unified Selection

One report definition.
Many systems.
The same shape.

NEXUS lets an SAP team build a report once — its fields, its joins, its outputs — and then run it across the live database, the archive, and remote SAP systems over RFC. Every row carries a Source badge, the result is identical in shape no matter the origin, and an inbuilt comparison surfaces differences at a glance.

The problem

The same question, coded three different times.

In any long-running SAP estate, the same business question — "give me all materials with this profile, anywhere we have data on them" — has to be answered out of three places: the live database, the archive, and a handful of sister systems reachable only over RFC.

So three separate reports get written. Each one with its own SELECT, its own selection screen, its own ALV. None of them know about the others. Comparing the results is a copy-paste-into-Excel exercise. And when a field changes, all three reports drift apart.

How it works

One configuration. Three jobs.

NEXUS lives in three layers — you set up a report once, then anyone can run it across whichever sources matter for that particular question.

1

Configure

A tree-based builder for the report definition: fields, joins, archive mapping, outputs.

  • Data source — fields with DDIC references
  • View — visual join builder or raw Open SQL
  • Archive — connect an archiving object & map fields
  • Outputs — ALV, Excel by email, local file
2

Execute

Pick a report, get an auto-generated selection screen, choose which sources to hit, and see the unified result.

  • Auto-built selection screen from configured fields
  • Per-run choice of Live, Archive, and named RFC systems
  • Result grid with a Source column on every row
  • Same shape regardless of source
3

Compare

Pull the same report from multiple systems in one run and surface differences across them.

  • Side-by-side cross-source diff
  • Filter by source category (DB / Archive / RFC)
  • Drill into a row to see its origin record
  • Export the compared dataset just like any other output
Benefits

Less duplication. Faster answers. A single shape end-to-end.

One definition, many sources

Define a report once. Run it against live, archive, and any number of RFC-connected systems without rewriting the logic.

Consistent result shape

Every row comes back with the same fields, regardless of origin. The Source badge tells you where it lives.

Comparison built in

Cross-system comparison is part of the framework — no separate report, no copy-paste-to-Excel ritual.

Constructor & Pro modes

Point-and-click join builder for the common case. Raw Open SQL when you need something the constructor can't express.

📤

Three outputs in one run

ALV grid for interactive use, .xlsx by email for stakeholders, flat file on the app server for downstream jobs.

🔒

Authorisable & transportable

Reports are objects in your namespace. Standard SAP transport, standard SAP authorisations.

Who it's for

Anyone who has to answer the same question out of more than one SAP system.

Reporting team

Stop maintaining three versions of the same report.

One definition feeds every consumer — no more drift between the live and archived versions of "the same" report.

SAP basis & archiving

Make the archive useful again.

Archived records become first-class data, not a dead corner. Anyone running a report sees archived rows alongside live ones.

Reconciliation & audit

One run = one cross-system answer.

Pull the same dataset from DEV / QAS / PRD in a single execution; compare differences side-by-side without staging.

Functional consultants

Build reports without ABAP, when you can.

The Constructor view covers the common joins; Pro mode is there when you need it. No development ticket for every new report.

Take it for a spin.

The clickable mockup walks you through both apps — the Configuration tree-builder and the Execution runtime, with the RFC system picker and the unified result.