Move closed-period OJDT, OINV, OPCH, OINM history to queryable cloud archive. IRS 7-yr, HMRC 6-yr, German GoBD 10-yr, French CGI, Italian SDI compliant. SQL/REST query interface. 60–90% lower TCO than keeping B1 alive on HANA or SQL Server.
A B1 instance running 'just for audit access' is one of the most expensive line items on a CFO's IT budget — and most SMBs don't realise the scale of the spend.
SMBs that migrate from SAP Business One to Oracle Fusion (or to any successor ERP) often leave the source B1 system running 'in case audit asks'. Three years later, that 'just in case' system is still consuming $40K–$200K per year in SAP licence maintenance, HANA Runtime Edition or SQL Server licensing, infrastructure (app + DB + Service Layer + dev/test), SAP partner support retainer fees, and part-time admin attention. The auditor queries it twice a year. The TCO math doesn't work — but most CFOs have never quantified it because the costs are spread across multiple budget lines.
SAP Business One data archival flips the economics. The complete operational dataset — every OCRD business partner, every OITM item, every OJDT/JDT1 journal, every OINV/OPCH invoice, every OINM inventory posting — moves to cloud object storage in Parquet, partitioned by fiscal year and branch, with a SQL/REST query interface auditors find faster than the original B1 system. Production B1 can be fully decommissioned: licence returned to SAP, infrastructure shut down, partner support retainer ended. Retention requirements stay satisfied for the full IRS/HMRC/GoBD window.
For SMBs still on B1, archival also works as ongoing database hygiene. Closed-period OJDT/JDT1 older than two fiscal years migrates to archive on a continuous schedule, keeping the live B1 OJDT manageable, accelerating month-end close, and shrinking HANA memory or SQL Server backup footprint — letting you stay on a smaller (cheaper) HANA tier.
Not just data — everything an auditor, tax authority, or regulator might ever ask about your decommissioned B1 system.
OJDT (journal entry headers), JDT1 (journal entry lines), OINV/INV1 (AR invoices), OPCH/PCH1 (AP invoices), ORCT/RCT1-4 (incoming payments), OVPM/VPM1-4 (outgoing payments), OINM (inventory postings). Full closed-period detail with original branch and currency context.
OCRD (customers + vendors + leads), OCPR (contacts), CRD1/CRD2/CRD3 (addresses, groups, extensions), OCRG (BP groups), OPYM (payment methods), OCRC (currencies). PII masking applied per GDPR/CCPA defaults.
OITM (items), OITB (item groups), OITW (item-warehouse), OBTN (batches), OSRN (serials), OPLN (price lists), ITT1 (BOM components), OWHS (warehouses). Costing history preserved per warehouse.
CUFD (UDF metadata + UDF_xxxx columns on every base table), OUDO (UDO metadata + UDO data tables), SBO-COMMON catalog, registered SDK and Service Layer add-on inventory. Customer-specific extensions fully preserved.
Crystal Report templates (.rpt), B1 Studio dashboard definitions, PLD (Print Layout Designer) templates, Formatted Search SQL. Indexed by report name, last-used date, business owner — preserved as audit artifacts.
B1 user roster, permission templates, branch-level access rules, OADM company configuration, financial-period structure (OFPR), document numbering series. The evidence layer auditors need to validate access controls and configuration during the retention window.
Whether you're archiving for Fusion migration prep, ongoing B1 hygiene, or full B1 decommission, the workflow is the same.
Inventory B1 modules in use, classify data domains (Financials, AR/AP, Sales, Purchasing, Inventory, BP master), map each domain to applicable retention regime (IRS, HMRC, GoBD, CGI, SDI, GDPR). Output: a per-domain retention policy signed by compliance, finance, and operations leads.
Pre-built B1 extractors pull every in-scope table via Service Layer or direct HANA/SQL Server JDBC — full history, not just open transactions. Output staged to cloud object storage as Parquet, partitioned by fiscal year, period, branch. Hash-signed at row level with manifest.
Discovery engine crawls CUFD, OUDO, SBO-COMMON catalog, Crystal Report library, B1 Studio dashboards, Formatted Search definitions, PLD layouts. Catalog stored alongside data with same retention policy. Add-on registration inventory preserved.
SQL (JDBC/ODBC) and REST endpoints provisioned. Role-based access configured per domain. Pre-built auditor extracts (GL detail, AP aging, AR aging, inventory valuation snapshot) materialized. Sensitive-field masking and GDPR right-to-erasure tagging applied.
Sample auditor queries run against archive vs live B1 to validate parity. Sign-off pack issued to compliance and audit. B1 moves to read-only, then full decommission (licence returned, infrastructure shut down, partner support ended). Archive is now system of record for retention.
The TCO math of SAP Business One data archival vs running a 'compliance-only' B1 instance.
B1 named-user licences carry $95–$135/user/year maintenance on perpetual purchases. A 50-user compliance-only B1 instance still costs $5K–$7K/year just for SAP maintenance — and SAP discourages reducing user counts after migration. Archive: zero SAP licence cost.
B1-bundled HANA Runtime Edition or SQL Server Standard Edition licensing. Typical $10K–$40K/year depending on edition and capacity. Archive runs on cloud object storage at pennies per GB-month — no DB licence.
App tier (B1 server), DB tier (HANA or SQL Server), Service Layer node, web tier, dev/test environments — typically $15K–$60K/year in cloud hosting or amortised on-prem. Archive uses cloud object storage and a small query-engine tier.
SAP Partner Edge partners typically charge SMBs $1K–$5K/month ($12K–$60K/year) for B1 support contracts that include patch application, UDF maintenance, Crystal Report tweaks. Archive has no partner-support requirement.
B1 PatchLevel (PL) upgrades typically come quarterly and require partner involvement — 1–3 person-weeks per year of effort, plus testing of all UDFs/add-ons. Archive has no patch cycle, no version risk, no add-on breakage.
A live B1 instance is an attack surface (Service Layer endpoint exposed), a compliance dependency, and a hostage to partner availability. Archive removes all three risks while preserving every byte of data and full audit evidence.
SAP Business One data archival is the process of moving closed-period transactional data (OJDT/JDT1 journal entries, OINV/OPCH invoice history, ORCT/OVPM payment history, OINM inventory postings) and inactive master data (terminated business partners, discontinued items) out of the live B1 database — whether running on SAP HANA or Microsoft SQL Server — into a queryable long-term cloud archive. SMBs archive B1 data for three reasons: regulatory retention (IRS 7-yr in the US, HMRC 6-yr in the UK, German GoBD 10-yr digital record retention, French CGI fiscal retention, Italian SDI e-invoicing), database-size control (B1 HANA licence cost scales with memory footprint), and migration preparation (a smaller B1 footprint is faster and cheaper to migrate to Oracle Fusion). Syntra ETL routes cold data to Parquet on cloud object storage with a SQL/REST query interface for auditors and tax authorities.
Retention varies by jurisdiction and data domain. In the US: IRS requires 7 years for income tax records, state sales-tax authorities often require 4–6 years, payroll records 7 years. In the UK: HMRC requires 6 years for VAT and corporation tax records. In Germany: GoBD (digital records under HGB §257) requires 10 years for accounting records and tax-relevant documents. In France: CGI requires 6 years for fiscal records, 10 years for accounting books. In Italy: SDI e-invoicing requires 10 years for B2B invoices. EU GDPR adds a layer requiring personal data to be deleted when no longer needed for the original purpose — meaning customer/vendor contact data in OCRD/CRD1 needs explicit retention rationale. Syntra archive policies are configurable per domain and jurisdiction so each data class meets its own rule without over-retention.
Yes. The B1 archival path preserves the source table schema — column names, datatypes, the original OCRD/OITM/OJDT/OINV structure — in the archive. Archived data lives as Parquet with embedded schema, plus a JSON Schema sidecar for tooling. UDF columns are preserved with their CUFD-defined metadata, so an auditor querying an archived OINV record sees the same UDF_TAX_REGION or UDF_PROJECT_REF field they would have seen in live B1. The archive query interface lets auditors run familiar SELECT statements against OJDT, JDT1, OINV, INV1, OPCH, PCH1, OITM, OCRD and return results identical in shape to what live B1 would have returned — same ChartField context, same multi-currency context, same multi-branch context.
The reports themselves are preserved as artifacts in the archive alongside the data. Crystal Report templates (.rpt files), B1 Studio dashboard definitions, Formatted Search SQL definitions, and PLD (Print Layout Designer) templates are inventoried, copied into the archive, and indexed with metadata: report name, last-used date, data sources, business owner. This serves audit and compliance needs — a future regulator or tax inspector can see exactly what the Q3 2018 sales report or the 2021 year-end financial statement looked like when it was originally produced. For active use, the archive query interface lets auditors run equivalent SQL against archived data; they don't need a live Crystal Reports runtime to retrieve historical numbers.
Yes, for SMBs that have completed migration to Oracle Fusion or otherwise retired their B1 deployment. The Syntra archive holds the complete data (every OCRD, OITM, OJDT, OINV, OPCH row), the customisation catalog (every UDF, UDO, SDK add-on, Crystal Report), the security model snapshot (B1 user/role configuration at decommission), and the company-master configuration. Everything an auditor, tax authority, or regulator would otherwise demand a live B1 instance for. SMBs typically save $40K–$200K per year on B1 licence fees (per-user annual maintenance), Oracle Database or HANA support, infrastructure hosting, and SAP partner support retainer fees. The archive satisfies IRS, HMRC, GoBD, CGI, and SDI retention requirements through the full retention window.
Access is role-based with mandatory audit logging. Every query against the B1 archive is logged with user, timestamp, query text, rows returned, and data classification. Archive data is encrypted at rest with KMS-managed keys (AES-256) and in transit with TLS 1.3. Sensitive fields (bank account numbers in OCRD/CRD8, customer credit-card tokens, employee social numbers if stored as UDFs) are masked by default and require explicit role permission to unmask. For GDPR-covered EU data, right-to-erasure requests can be processed by tagging individual OCRD rows for soft-delete in the archive while preserving aggregate financial integrity (the related OINV/OPCH rows stay; the personal-data fields are nulled with a deletion-evidence log).
A live B1 instance kept running for occasional auditor queries typically costs $40K–$200K per year for a small instance and $200K–$800K for a multi-company partner-supported instance. Breakdown: B1 named-user licences ($95/user/year maintenance on perpetual licence, plus annual SAP fees), SAP HANA Runtime Edition for B1 or SQL Server licensing, infrastructure (app server + DB server + Service Layer node, dev/test environments), SAP Partner Edge partner support retainer ($1K–$5K/month for most SMBs), DBA/admin time. Syntra archive runs on cloud object storage (Parquet) at pennies per GB-month plus a flat query-interface subscription — typically $8K–$30K per year for the same data footprint. TCO reduction: 60–90% in year one, compounding.
Yes. The Syntra archive exposes a standard SQL interface (JDBC/ODBC), so any BI or audit tool that connects to a relational database — Power BI, Tableau, Excel, Smart View, Alteryx, ACL, IDEA, ARBUTUS — works without modification. The schema looks like B1: SELECT * FROM OINV WHERE DocDate BETWEEN ... returns AR invoice history in B1-native shape. There's also a REST API for programmatic access, and underlying Parquet files queryable directly from Athena, BigQuery, Snowflake, Databricks, or Spark. Standard auditor extracts (GL detail by period, AP voucher detail with vendor, inventory valuation snapshot) ship as pre-built saved queries — just point the BI tool at the JDBC endpoint and the queries return in seconds.
30-minute discovery call. Walk through your B1 backend (HANA or SQL Server), modules in use, retention obligations, and decommission timeline — leave with a quantified year-one TCO reduction and a 6-week archival plan.