Self-serve historical lookups against archived OJDT, OINV, OPCH, OITM data — for controllers, accountants, auditors, tax authorities. No active B1 licence needed. SQL + REST + BI-tool access. Sub-second query response on billion-row archives.
Audit doesn't end at go-live. Tax authorities don't care that you moved to Fusion. Old customer disputes don't go away. Prior-year comparisons drive current-year decisions.
SMBs that migrate from SAP Business One to Oracle Fusion or otherwise retire their B1 deployment quickly discover that historical reporting access is a hard requirement, not an optional convenience. The IRS sends an examination letter referencing FY2019 AP transactions. The German tax authority demands GoBD-format evidence for FY2017–2022 under the 10-year HGB §257 rule. A customer disputes a 2020 invoice. The board wants a 5-year trend chart that includes B1-era data. The controller wants to know what the period-end inventory valuation was on 31 March 2018. Every one of those questions used to be answered by 'just log into B1 and run the report'.
Without live B1, those answers have to come from somewhere. The wrong answer is to keep B1 running indefinitely at $40K–$200K/year just for the occasional query. The right answer is purpose-built historical reporting against the B1 archive — same data shape (OJDT, JDT1, OINV, INV1, OPCH, PCH1, OITM, OCRD), same multi-branch and multi-currency context, same UDF fields, but exposed through modern SQL/REST/BI access patterns at a fraction of the cost.
Syntra ETL's historical reporting layer sits on top of the SAP Business One data archive. It surfaces archived B1 data through three access patterns: pre-built reports for the 90% of standard questions (trial balance, AP/AR aging, inventory valuation, sales history), SQL/JDBC for the 9% that need ad-hoc analysis, and REST API for the 1% that drive programmatic downstream consumers. All three patterns return data that looks exactly like B1 — because it is B1 data.
The 90% of historical questions answered out of the box. SQL/REST handles the rest.
Trial balance by period, branch, and ledger from OJDT/JDT1 archive. Drillable to journal entry, journal line, and originating document (OINV/OPCH/ORCT/OVPM). Multi-currency view supported.
Journal entry detail by account, period, branch, project. Full transaction-line context with sub-ledger source, currency triplets (Doc, Local, System), and UDF fields preserved from CUFD.
Open AR aging at any historical date from OINV/INV1/ORCT/RCT1. Bucketed (current, 30, 60, 90, 120+). By customer, by salesperson, by branch. Useful for auditor 'as-of' aging requests.
Open AP aging at any historical date from OPCH/PCH1/OVPM/VPM1. Same bucketing and pivot dimensions as AR. Critical for AP audit evidence and vendor dispute resolution.
Warehouse-by-warehouse inventory valuation at any historical date from OITM/OITW/OINM. Moving Average, FIFO, or Standard cost basis (matching B1 configuration). Drillable to individual stock movements.
Customer purchase history from OINV/INV1, product sales by period/region/salesperson, top-customer rankings. Drillable to invoice line, item, salesperson, branch.
From archived B1 data to self-serve historical reporting in 3–5 weeks.
Confirm B1 archive (from SAP Business One data archival project) covers required modules and fiscal-year range. Validate UDF/UDO preservation. Confirm jurisdiction-specific compliance (GoBD evidence package, SDI XML retention, etc.). Identify reporting user community.
Define reporting roles: internal finance, internal audit, sales/customer service, ops/supply chain, external auditor (time-scoped). Configure data-domain access scoping per role. Apply PII masking defaults. Set up auditor time-bounded access provisioning workflow.
Deploy pre-built finance reports (trial balance, GL detail, AR/AP aging, inventory valuation), sales reports (customer history, top customers), audit reports (VAT/sales-tax, GoBD evidence pack, SDI XML retrieval). Validate against last live-B1 numbers for sample periods.
Provision SQL/JDBC endpoints for BI tools (Power BI, Tableau, Excel via ODBC, Smart View). REST API tokens for programmatic consumers. User training session for finance and audit teams (1 hour — the data shapes are unchanged from B1, only the access layer is new). Go-live.
The corner cases that broke prior reporting strategies — and how the Syntra layer handles them cleanly.
Doc_Cur, LcAmt, FCAmt, SYSAmt fully preserved on every archived transaction. Reports pivot by any currency dimension. Currency conversions at the original transaction rate preserved — no retroactive re-translation.
B1's BPLId branch model preserved across all transactional tables (OJDT, OINV, OPCH, ORCT, OVPM). Branch-consolidated and branch-filtered reports both supported. Branch hierarchies preserved from OBPL.
Every UDF_xxxx column on every base table (preserved from CUFD enumeration during archival) is queryable in historical reports. No special treatment — UDFs show up as ordinary columns in BI tools and SQL queries.
B1 period status (from OFPR) treated as metadata, not as a query filter. Reports against 'unclosed' periods return the data as it actually existed at extract — useful evidence for partner-abandoned or under-managed instances.
PII fields on OCRD/OCPR null-able on request while preserving aggregate financial integrity. Erasure evidence log auditable. Tax-authority extracts continue to show legally-required detail.
Time-scoped external auditor accounts (valid for audit duration only), scoped to specific fiscal years and data domains. Every query logged. Sensitive PII masked beyond audit scope. Self-service revocation post-audit.
SAP Business One historical reporting is the ability for SMB users — controllers, accountants, sales managers, auditors, tax accountants — to run queries and produce reports against years of closed-period B1 data without needing the live B1 application running. After migration to Oracle Fusion or decommission of B1, the historical reporting capability must continue: tax audits go back 6–10 years depending on jurisdiction, prior-year comparisons inform current-year planning, customer disputes about old invoices need resolution, and IRS/HMRC examinations require pulling specific OINV/OPCH detail on demand. Syntra ETL's historical reporting layer sits on top of the B1 archive and exposes B1-shaped data (OJDT, INV1, PCH1, OITM, OCRD) through SQL, REST, BI tools, and pre-built finance/sales/audit reports — without keeping an active B1 licence.
For end users, the experience is nearly identical: same B1 table shapes (OINV, OPCH, OJDT, etc.), same column names, same UDF columns from CUFD, same multi-branch and multi-currency context. The differences: query performance is often faster because data is stored as columnar Parquet partitioned by fiscal year and branch (sub-second on typical period queries against billion-row archives); concurrent user count is unlimited (B1's named-user licensing doesn't apply); no Crystal Reports runtime is needed (queries return relational data that any modern BI tool can render); and audit logging is more granular (every query logged with user, timestamp, query text, rows returned). The data is the same — the access layer is modernised.
Pre-built reports cover the standard SMB use cases. Finance: trial balance by period and branch (from OJDT/JDT1), GL detail by account, journal entry detail with sub-ledger source, AR aging snapshot at any historical date (from OINV/RCT1), AP aging snapshot, period-end financial statements per OACT hierarchy. Sales/Customer: customer purchase history (from OINV/INV1), product sales by period, customer credit history, top-customer rankings. Inventory: warehouse valuation snapshot at any historical date (from OITM/OITW/OINM), item movement history, slow-moving items. Audit/Compliance: VAT/sales-tax report per jurisdiction, IRS-format payroll extract, German GoBD evidence package, Italian SDI invoice retrieval. Custom queries via SQL/REST cover anything pre-built reports don't.
Yes. The historical reporting layer supports external auditor access with tightly scoped roles. A typical setup: an external tax inspector or IRS/HMRC auditor gets a time-limited account (e.g. valid for the duration of the audit) with read-only access scoped to specific fiscal years and specific data domains (e.g. AP/AR for a sales-tax audit, payroll for a payroll-tax audit, GL for a general financial-statement audit). Every query is logged. Sensitive PII fields beyond audit scope are masked. The auditor uses their preferred tool — Excel via ODBC, Power BI, or a SQL client — to query archived B1 data directly. This satisfies the regulatory 'right of inspection' requirement (German GoBD, Italian SDI, French CGI all have similar provisions) without needing to spin up a B1 sandbox.
Full preservation. B1's currency model — local currency, system currency, and document/foreign currency for each transaction stored as Doc_Cur, LcAmt, FCAmt, SYSAmt columns on OJDT/JDT1/INV1/PCH1 — is preserved in the archive exactly as in B1. Reports can pivot by any of the three currency dimensions. Similarly, B1's multi-branch (BPLId on OJDT and dependent tables) and multi-segment account configuration are preserved. A consolidated trial balance across all branches in local currency works the same way it did in B1; a single-branch report in foreign currency works the same way. For SMBs running multi-company B1 (separate companies for separate legal entities), each company's archive can be queried independently or consolidated.
Yes — that's actually a common reason for archival. Many SMB B1 instances have years of 'not officially closed' periods because partner support has lapsed or the controller never ran the period-close procedure properly. The Syntra archive treats fiscal period status (from OFPR) as metadata, not as a query constraint. Historical reports can query any period regardless of B1's official close status. For audit purposes, this is useful evidence: the report shows the data as it actually existed at extract time, with a timestamp, regardless of whether the period was nominally open or closed. Customers commonly use this capability to produce 'as-of' snapshots for prior years that were never finalised in the live B1 system.
Yes. GDPR (and similar regimes like California CCPA, Brazilian LGPD) requires that personal data be deletable on request even from archives, while financial integrity must be preserved. Syntra's approach: the OCRD business-partner record stays for financial integrity (so the associated OINV/OPCH rows still tie to a row), but the PII fields (CardName if it's a person's name, contact name, contact email, contact phone, bank account, tax ID) are nulled and a deletion evidence record is written to a separate erasure log. The aggregate financial reporting (trial balance, AR aging) is unaffected. Tax-authority extracts continue to show legally-required transactional detail. The erasure log is auditable evidence that the GDPR request was processed correctly.
Dramatically lower. A live B1 instance kept for historical reporting access costs $40K–$200K/year for a small SMB and $200K–$800K for multi-company partner-supported instances (B1 licence maintenance + HANA/SQL Server + infrastructure + partner support + admin time). Syntra historical reporting is priced as a flat annual subscription based on archive data volume and concurrent named users for active reporting — typically $8K–$30K/year for the same data footprint. The pricing model matters: B1 licence costs scale with named users (and SAP discourages user-count reductions post-migration), while archive reporting pricing scales with active reporters — usually a much smaller population than the full historical B1 user base.
30-minute call. Walk through your B1 reporting workload, retention obligations, and reporting user community — leave with a 3–5 week historical reporting deployment plan and a quantified saving vs keeping B1 alive.