Sap ecc legacy data access for the six populations that need ECC history after decommission — tax authorities, external auditors, internal audit, finance retro queries, M&A diligence, forensic investigation. Self-serve, country-format-ready, fed by your existing IdP.
Once ECC is decommissioned, six different consumer populations need access to ECC history through six different access patterns. A working legacy-data-access strategy solves for all of them.
The historical archive is necessary but not sufficient. Having ECC data sitting in WORM-locked Parquet on cloud object storage is the foundation — but that foundation only delivers business value when consumers can actually use it. And the consumers are wildly different. A German Finanzamt tax auditor needs a GoBD-compliant invoice extract pack covering company code DE01 for FY2019, deliverable within four weeks of the §147 AO notice. An external SOX auditor needs to pick a sample of 60 BKPF document numbers from FY2022 and see the full doc + line items + GL impact for each, ideally through a familiar browse-and-drill UI. An M&A diligence team needs 5-year customer-vendor concentration trends as an aggregated dashboard. A forensic investigator needs to query the full BSEG history with SQL looking for anomalous payment patterns.
Each population has different ergonomic expectations, different tooling preferences, different security scopes, different output formats. Solving for one (say, BI dashboards for finance) leaves the other five frustrated. Solving with custom one-off IT effort per request burns the TCO advantage of decommissioning ECC. Sap ecc legacy data access is the discipline of making the archive truly self-serve across all six populations.
The Syntra ETL approach: a lookup app for browse-and-drill (tax authorities, external auditors, internal audit), standard SQL access via Snowflake/Databricks/BigQuery/Athena (forensic investigation, M&A diligence, finance retro analysis), pre-built BI dashboards (finance, executive reporting), and country pack generators (regulator-format demands). All federated to your enterprise IdP, all logged to your SIEM, all governed by role-based access mapped from the original SAP authorisations.
Six populations, six tuned access patterns, all running off the same WORM-locked Parquet archive.
Tax lead opens country pack generator, parameterises by company code and period, generates GoBD/SDI/SPED/KSeF/CFDI/MTD pack. Regulator deadline met. No IT ticket. No ECC running.
Auditor logs into lookup app via SAML SSO. Browses customer KNA1, drills to open AR (BSAD), drills to BKPF doc, sees BSEG lines + Z-* fields + attachment. SOX-evidence-ready, fully logged.
Internal auditor uses SQL or BI tool to select stratified sample from BKPF/BSEG for SOX walkthrough. Each tested record reproduces fully. Workpapers document with audit-log evidence.
Controller opens parameterised Power BI report on the archive. Reviews 5-year vendor concentration. Drills into specific BSEG lines for any concerning patterns. Saved as scheduled report if recurring.
Acquirer team gets restricted-scope access via federated IdP. Pulls multi-year customer concentration, revenue trends, asset positions. Diligence pack delivered in days, not weeks.
Forensic team given temporary elevated SQL scope. Runs deep cross-period queries against full BSEG history. Read-access log itself WORM-locked — chain-of-custody defensible.
Typical timeline: 8–12 weeks from archive populated to legacy data access in production for all six populations.
Catalogue the six populations against your enterprise: which tax authorities are active, which external audit firms, which internal audit teams, which finance retro patterns recurring, which M&A patterns expected, which forensic-readiness needs. Sign-off from each population's leadership.
Per population, choose access channel: lookup app, SQL via warehouse, BI tool, country pack generator. Role-based access scopes mapped from original SAP authorisations. IdP federation configured. SIEM integration verified.
Lookup app deployed with transaction-style navigation paths per module. BI dashboards built for the top finance retro patterns. Country pack generator templates configured for active jurisdictions.
Tailored training per population: external auditors trained on lookup app browse-and-drill, finance trained on BI dashboard parameterisation, tax leads trained on pack generators, forensic team briefed on scoped SQL access.
Each population runs a representative real workload against the archive: external audit runs a SOX sample test, tax lead generates a sample GoBD pack, finance reproduces a historical TB, M&A team pulls a sample diligence aggregation. Issues caught and resolved.
Legacy data access declared production. Ongoing operation: scheduled archive integrity check, annual audit dry-run, quarterly pack-generator refresh as regulatory formats evolve. Run rate typically 8–12% of pre-decommission ECC TCO.
What this looks like in steady state, three years after the ECC system was switched off and the migration is just memory.
Typical mid-market sees 200–600 archive queries/month across all six populations. External audit spike at FY close. Tax inquiries through the year. Finance retro queries monthly. M&A activity sporadic.
$40K-$120K/year for the full archive + access stack. Object storage tier-optimised. Query compute pay-per-use. Lookup app on small managed compute. SIEM integration via existing enterprise stack.
Annual external-audit dry-run verifies WORM integrity, schema preservation, access-log completeness. Pass-rate 100% across customer base — the architecture is built for it.
Country pack formats evolve (Polish KSeF schema updates, Italian SDI version bumps, IRS format changes). Generators updated quarterly. Customer impact: zero — pack generator updates are runtime.
Three years post-decommission, the consumer populations are well-known. External audit firm and internal audit team have established workflows. Tax pack patterns repeat. New M&A diligence pulls are the main variable.
Per WORM policy, partitions become unlock-eligible as retention windows expire. Year-10 HGB partitions move out of lock. Year-7 SOX partitions move out. Storage gradually de-classifies and eventually deletes — no permanent cost growth.
Sap ecc legacy data access is the user-facing capability that lets external consumers — tax authorities, external auditors, internal audit, finance retro queries, M&A diligence teams, regulators, forensic investigators — retrieve, browse and report against SAP ECC historical data after the ECC system has been decommissioned. It is the consumer-side equivalent of historical reporting: where historical reporting focuses on the report-build capability, legacy data access focuses on how those consumers actually get the answer they need without involving IT for every request. The Syntra ETL approach combines a SAP-style browse-and-drill lookup app, standard BI tool federation, country-format export pack generators, and self-serve SQL access — each tuned for a different consumer population.
Six distinct consumer populations. (1) External auditors testing SOX or country statutory controls across the 7–10yr SOX/HGB retention window. (2) Tax authorities — German Finanzamt issuing §147 AO inquiries, IRS field auditors, HMRC VAT inquiries, Italian Agenzia delle Entrate SDI checks. (3) Internal audit running SOX walkthroughs and controls testing. (4) Finance teams doing retro analysis (vendor concentration, customer payment behaviour, historical TB reproduction, prior-period restatement support). (5) M&A and diligence teams pulling historical customer/vendor concentration, multi-year revenue trends, asset positions. (6) Forensic investigators (regulatory enforcement actions, suspected fraud, insider-trading inquiries). Each gets self-serve access through the appropriate channel.
Cost and ergonomics. Running ECC for read-only lookup costs $400K-$1.5M/year (SAP licence, DB licence, Basis team, hardware) for a mid-market deployment — there is no reduced rate for not posting transactions. Sap ecc legacy data access through the Syntra ETL archive costs $40K-$120K/year fully loaded — 8–12% of the run-ECC alternative for equivalent user accessibility. Ergonomically, the lookup app provides the same SAP-GUI-style browse-and-drill auditors expect (KNA1 → open AR → BKPF doc → BSEG lines → attachment) while also offering SQL access through Snowflake/Databricks/BigQuery for power users and country-format pack generators for regulator demands — three access patterns from a single archive, none of which are available from a vanilla read-only ECC.
Country-specific. German Finanzamt §147 AO requests get answered via the GoBD pack generator — parameterised by company code and period, generates a GoBD-compliant CSV plus invoice-image bundle, filed within the statutory deadline (usually 1 month for §147 inquiries). IRS field audits get the IRS field-audit data pack format. HMRC inquiries get the MTD-compatible pack. Italian Agenzia delle Entrate SDI checks get the SDI XML retention pack matching the timbro fiscale format. Brazilian Receita Federal SPED inquiries get the SPED Contábil and SPED Fiscal formats. Each pack generator runs against the WORM-locked archive partition for the requested period and produces regulator-ready output in seconds — no ECC system required, no Basis team needed.
Yes, for the common cases. Historical GL trial balance (F.01 / FAGLB03 equivalent) reproduces from BKPF + BSEG aggregation matching the original ECC output to the cent across all parallel currencies and all ledgers. Customer aging at historical date (FBL5N / FBL5H equivalent) reproduces from BSAD/BSID with the same aging-bucket logic. Vendor aging (FBL1N) reproduces from BSAK/BSIK. Asset register (AR01 equivalent) reproduces from ANLA/ANLC at any historical date. Sales order display (VA03) and billing display (VF03) reproduce from VBAK/VBAP/VBRK/VBRP. Document display (FB03) reproduces from BKPF + BSEG. These are the workhorses of auditor and tax inquiry — covered by saved parameterised reports in the lookup app and BI tool dashboards on the archive.
Internal audit runs SOX walkthroughs and controls testing directly against the archive. SOX sample selection is performed via SQL against BKPF/BSEG (or via the lookup app for transaction-style sampling) — pulling random or risk-stratified samples across the period under test. For each sampled record, the auditor sees full doc header + line items + GL impact + Z-* fields + supporting attachment (where archived). The workpaper documents the test result. Every read is logged for the SOX evidence trail. Compared to running tests against live ECC (which required scheduling around ECC change windows and obtaining IT-mediated sample selection), the archive-based approach is faster, more reproducible, and substantially cheaper to operate. External audit follows the same pattern with their own user accounts and role-based scope.
Yes. SAP ECC tenants in Germany, France, Italy, Spain, Portugal, Brazil, Mexico, Japan, China, Korea, Taiwan and elsewhere carry text data in local languages (customer/vendor names, material descriptions, document text, address fields) and often multi-byte character sets. The archive preserves every text field as UTF-8, with original code-page metadata captured at extraction time so reconstruction to the original SAP code page is possible if needed. The lookup app displays content in the user's session language matching the SAP GUI experience. SQL queries can filter and display in any language captured. Country-specific extension fields (German VAT MWST codes, Italian SDI XML segments, Brazilian SPED J-class fields, French Chorus Pro tags) display natively.
Through standard enterprise identity federation. The lookup app and BI tooling all federate to your IdP via SAML 2.0, OIDC or Azure AD — single sign-on, multi-factor authentication, conditional access policies all apply. Role-based access is mapped from the original SAP authorisations: the user who had display-only access to company code DE01 in ECC gets the same scope in the archive. Sensitive data classes (employee PII, payroll detail, M&A documents) are tagged at extraction time and gated by additional role membership. Every read logged to SIEM with user identity. SOC 2 Type II evidence built in. No archive-specific identity provisioning required — your existing IdP and SIEM stack do the work.
30-minute discovery call. We'll scope your six consumer populations (tax, audit, finance, M&A, regulator, forensic), the access channels each needs, your IdP and SIEM integration, and produce a legacy-data-access timeline aligned to your ECC decommission.