Consumer-side access to archived B1 data — small-business owners, accountants, tax advisors, IRS/HMRC examiners, statutory auditors, customer service. No B1 licence, no HANA, no SQL Server. SQL + REST + BI tools + pre-built reports.
The CIO sees 'archive access' as a single requirement. The reality is five different user populations with five different access patterns — and a one-size-fits-all approach fails three of them.
After a SAP Business One decommissioning or successful migration to Oracle Fusion, the question 'who needs access to the archived B1 data?' has more than one answer. There's the SMB principal who wants to look up the contact details of a customer from three years ago. There's the bookkeeper who needs to reproduce a year-end trial balance for a tax return amendment. There's the external CPA preparing the SMB's annual filing and reconciling against prior-year B1 numbers. There's the IRS examiner who has just opened an income-tax examination covering FY2019–2022. There's the customer-service rep dealing with a vendor who claims a 2020 invoice was paid twice.
Each of these users wants different things. The SMB principal wants a search box. The bookkeeper wants Excel via ODBC. The CPA wants a clean, well-documented set of pre-built reports plus ad-hoc SQL. The tax examiner wants a time-scoped, audit-logged, jurisdictionally-formatted evidence package. The customer-service rep wants a customer-360 lookup that returns in under a second. A single 'go log into the archived BI tool' answer fails everyone except the bookkeeper.
Syntra ETL's legacy data access layer supports all five user populations natively — with appropriate access scoping, appropriate interfaces, appropriate pre-built artifacts. The data underneath is the same B1 archive (OCRD, OITM, OJDT/JDT1, OINV/INV1, OPCH/PCH1 in their original shape) — but each user population gets the access pattern that actually works for their job.
Different users need different access paths. The Syntra layer supports all of them against the same underlying archive.
Web-based query interface for SMB principals and customer-service reps. Customer/vendor search box, invoice lookup, period summaries. No SQL knowledge required. Mobile-friendly for owner-on-the-go scenarios.
Standard ODBC connection for accountants and bookkeepers using Excel. Named ranges pull period-end snapshots, refresh-on-open updates working papers automatically. Works with Smart View if customer prefers.
Direct JDBC/ODBC connection from BI tools for analyst-style users. Pre-built data models for trial balance, AR/AP aging, sales analysis. Refresh schedules supported for ongoing dashboards.
Direct SQL access for SQL-fluent users (CPAs comfortable with SQL, auditors with SQL skills, programmatic consumers). Same OINV/OPCH/OJDT/OCRD table shapes as live B1 — queries from the B1 era work unmodified.
Programmatic access for customer portals, partner integrations, downstream systems that need to look up historical B1 data. JSON responses, OAuth2 auth, rate-limited per consumer.
Standard SMB reporting outputs: trial balance, GL detail, AR/AP aging snapshots, inventory valuation, sales by customer/product, VAT/sales-tax extracts. Export to PDF, Excel, CSV.
The setup overhead per new user is minutes, not days — because the underlying archive is already built.
Who is requesting access? What population (SMB principal, accountant, tax advisor, tax authority, external auditor, customer-service rep)? What's the scope (which fiscal years, which data domains, which companies if multi-company)? What's the duration (permanent for internal users, time-scoped for external auditors and tax authorities)?
Pick the user-population access template (each population has a pre-configured role with appropriate scoping, PII masking defaults, and interface availability). Configure user-specific scope (fiscal years, data domains, companies, duration). Auto-apply jurisdiction-specific evidence package access if tax authority.
Account provisioned with appropriate authentication (SSO for internal users, federated SAML for external auditors with SOC2-compliant identity providers, time-limited tokens for tax authorities). Interface URL, REST API token, ODBC connection string emailed to user.
User runs sample query (built-in onboarding flow: 'show me OINV for FY2023'). Access logged. Confirmation that the user can see what they expect to see. Common issues (BI tool driver setup, ODBC PATH config) handled by short troubleshooting guide.
Time-scoped accounts auto-revoke at end of configured window (tax-authority access ends at audit close). Permanent accounts continue. Revocation evidence logged. All historical query log retained for archive audit purposes per retention policy.
The standard tasks users repeatedly perform against archived B1 data — pre-built so users don't have to invent the SQL.
Single-screen customer view: contact details from OCRD/OCPR, complete invoice history from OINV, deliveries from ODLN, payments from ORCT, credit memos from ORIN, returns from ORDN. Sub-second response. Used by customer service for dispute resolution.
Vendor view mirroring customer 360: contact from OCRD (CardType=S), AP invoices from OPCH, payments from OVPM, credit memos from ORPC, purchase order history from OPOR. Used by AP teams and procurement for vendor relationship lookups.
Trial balance + GL detail + AR aging + AP aging + inventory valuation, all as of a specified period-end date, in a single downloadable pack. Used by accountants producing year-end statements that span B1 and post-B1 periods.
Jurisdiction-specific VAT (UK, EU) or sales-tax (US states) extracts for a specified period. UK MTD-format VAT return inputs, German UStVA, French TVA, Italian LIPE, US state-specific sales-tax detail. Used by tax advisors and tax authorities.
Historical multi-currency journal lookup showing Doc, Local, and System currency values at the original transaction rate. Used by treasury for FX-impact analysis spanning B1 and post-B1 periods.
Free-text search across all archived OJDT, OINV, OPCH, ORCT, OVPM with regex support on memo/remarks fields. Used by internal/external auditors investigating specific transactions or suspicious patterns.
SAP Business One legacy data access is the ability for consumers — small-business owners, accountants, bookkeepers, tax advisors, external auditors, IRS/HMRC examiners, customer-service reps researching old disputes — to query a SAP Business One archive after the live B1 system has been decommissioned or after migration to a successor ERP like Oracle Fusion. The 'legacy data' in question is historical OCRD business partners, OITM items, OJDT/JDT1 journals, OINV AR invoices, OPCH AP invoices, OINM inventory postings, plus all UDF and UDO extensions specific to the original B1 deployment. Syntra ETL's legacy data access layer exposes this data through SQL (JDBC/ODBC), REST API, BI tools (Power BI, Tableau, Excel via ODBC), and pre-built reports — all without needing an active B1 licence or running B1 infrastructure.
Five distinct user populations. (1) Small-business owners — the SMB principal who occasionally needs to look up a historical customer, vendor, or invoice to settle a question. (2) Accountants and bookkeepers — internal finance staff or external accounting firms maintaining the books, producing year-end statements that reference prior-year B1 data. (3) Tax advisors — CPAs, chartered accountants, fiscalists preparing tax returns and amendments that span B1 and post-B1 periods. (4) Tax authorities — IRS, HMRC, German Finanzamt, Italian Agenzia delle Entrate, French DGFiP examiners conducting audits that look back 6–10 years. (5) External auditors — statutory auditors, IPO due-diligence teams, M&A diligence teams who need historical financial detail at transaction level.
No — that's the point. The Syntra archive runs entirely independently of SAP Business One. Once the archive is built (during a B1 decommissioning project or as ongoing parallel archive alongside live B1), legacy data access operates against the archive directly. No B1 licence, no SAP HANA Runtime Edition, no SQL Server licence, no Service Layer, no DI API, no Crystal Reports runtime, no B1 client install on any user's machine. Users access archived data through their existing tools — Power BI, Tableau, Excel via ODBC, browser-based query interface, REST API. This is what makes the TCO math work: legacy access without legacy infrastructure.
Tax authorities (IRS in the US, HMRC in the UK, German Finanzamt, French DGFiP, Italian Agenzia delle Entrate) have legal 'right of inspection' powers that compel SMBs to provide access to historical financial records during examinations. Syntra ETL's legacy access layer supports tax-authority access patterns directly: a time-scoped read-only account is provisioned for the duration of the examination (typically 30–180 days), scoped to specific fiscal years and data domains relevant to the audit (e.g. VAT/sales-tax audit gets AR/AP only; payroll audit gets payroll only; full income-tax audit gets full GL). Every query is logged with user/timestamp/query/rows-returned. Jurisdiction-specific evidence packs (GoBD for Germany, SDI for Italy, US IRS-format extracts) are pre-built and accessible directly.
Yes. External accounting firms regularly need access to former-client B1 data for year-end work, tax filings, regulatory submissions, and historical lookups. With Syntra's legacy access layer, the SMB's accountant gets a scoped read-only account against the archive — no SAP user licence required, no SAP partner involvement needed. The accountant uses their preferred tool (Excel via ODBC is by far the most common for SMB accountants, followed by Power BI and increasingly cloud-based accounting software with JDBC import) to pull whatever historical data the engagement requires. This is particularly useful where the original SAP Partner Edge partner relationship has ended or where the SMB doesn't want partner involvement in tax/audit work.
Customer-service reps researching old customer disputes (a question about a 2019 invoice, a 2020 delivery discrepancy, a 2021 return) need fast access to historical OINV/INV1, ODLN/DLN1, ORDN/RDN1 data with full customer context from OCRD/OCPR. Syntra's legacy access includes a pre-built customer-360 lookup view: search by customer (CardCode or CardName), see all historical invoices, deliveries, payments, returns, credit memos in chronological order, drill into any one for transaction line detail. Sub-second response times because the archive is partitioned by customer/branch/fiscal year. This was previously a 'log into B1, navigate to BP master, click around' workflow that took 5–10 minutes; legacy access reduces it to seconds.
The archive retention window is configurable per data domain and per jurisdiction — typically 6 years for HMRC, 7 years for IRS, 10 years for German GoBD and Italian SDI, and indefinite for cases where the SMB has chosen extended retention as a business policy. Within that retention window, legacy data access works exactly the same in year 1 as in year 10: same SQL endpoints, same REST API, same BI tool connectivity, same pre-built reports. Storage cost scales with data volume (Parquet on cloud object storage at pennies per GB-month), and query infrastructure scales with concurrent reporter count — both economically minimal compared to keeping a live B1 instance. Beyond the retention window, data is securely destroyed per the configured policy with a destruction evidence log.
Each B1 company database is archived separately, with its own complete copy of OACT/OJDT/OCRD/OITM (because B1 stores each company in its own database, whether HANA-based or SQL Server-based). Legacy access lets users query a single company, a subset, or all companies depending on access permissions and use case. For consolidated cross-company reporting (common in M&A roll-ups where each acquired SMB had its own B1 instance), virtual consolidation views are built on top of the per-company archives — with appropriate currency translation and intercompany elimination logic that mirrors the consolidation rules used in the original B1 setup. Per-company audit access can also be scoped independently — useful when one acquired entity is under examination but others aren't.
30-minute call. Walk through your post-migration user populations, their access needs, and any active tax-authority or audit engagements — leave with a configured access plan that goes live the same week.