SAP-certified via ArchiveLink
SAP-certified archiving using ArchiveLink patterns. Retrieval inside SAP transactions is native.
OpenText • Data management
OpenText Core Archive for SAP
Core Archive for SAP (Archive Server lineage) is the SAP-certified archive for SAP documents, data, and print lists. Merito runs the SAP archive program.
Merito sells OpenText Core Archive for SAP (Archive Server lineage) and delivers SAP-certified archiving for documents, data, and print lists with in-place retrieval inside SAP transactions.
- Best for
- SAP Basis leaders managing SAP database growth, SAP CoE leaders on ECC and S/4HANA, Compliance officers with SAP records retention requirements
- Hosting
- SaaS
- Time to value
- One SAP object archived in as little as one week. First SAP object archived in two to four months. Enterprise-wide SAP archival programs typically run twelve to twenty-four months across object types.
- Security posture
- ISO 27001, GDPR, SAP-certified integration
- Last reviewed
- 2026-04-26
What it is
OpenText Core Archive for SAP in the enterprise stack
OpenText Core Archive for SAP is the SAP-certified archive product carried from the Archive Server lineage. It archives SAP documents, data, and print lists using SAP ArchiveLink patterns, preserving long-term records outside the SAP database while keeping in-transaction retrieval available to SAP users.
The product is foundational for SAP programs with meaningful volumes. SAP databases grow quickly if documents, attachments, and print lists are not offloaded. Core Archive for SAP solves that by offloading content to an archive while SAP transactions continue to reference it seamlessly.
Implementation targets SAP object types first (financial documents, HCM files, material documents, print lists) and scales through SAP landscapes as volumes justify. Merito's engagements plan archiving waves around SAP performance, legal retention, and cost.
Ideal use cases
- SAP document archiving (financial documents, material documents, HCM files)
- SAP data archiving for older transactional data
- SAP print list archiving
- SAP performance optimization through database offload
- S/4HANA migration document preparation
What it is best at
Where OpenText Core Archive for SAP earns its seat
Database offload for SAP performance
Offloading SAP documents and data to the archive keeps SAP databases smaller, which keeps SAP performance predictable.
Works across ECC and S/4HANA
Customers migrating from ECC to S/4HANA preserve archive content; the transition does not require re-archiving.
Core capabilities
OpenText Core Archive for SAP capabilities, grouped by outcome
SAP archival patterns
Archiving patterns specific to SAP content and data.
ArchiveLink document archival
Documents attached to SAP objects archived through standard ArchiveLink.
SAP data archiving
Transactional data archiving for older fiscal periods and business objects.
Print list archiving
SAP print list archival for long-term output retention.
Retention and retrieval
Archive retention and in-transaction retrieval for SAP users.
SAP-compliant retention
Retention schedules aligned with SAP record-keeping and jurisdictional requirements.
In-transaction retrieval
SAP users retrieve archived content through standard SAP transactions.
Audit trail continuity
Archive events logged into the same audit trail as SAP transactions.
SAP landscape coverage and scale
SaaS archive tier tuned to SAP landscapes at scale.
Source SAP flexibility
Connects to ECC, S/4HANA, RISE with SAP, and customer-managed SAP wherever the source system runs.
Multi-system landscapes
Single SaaS archive spanning multiple SAP instances across business units and geographies.
Large-volume throughput
Designed for enterprise SAP archival volumes across financial close, procurement, HCM, and logistics.
Where it fits in the stack
How OpenText Core Archive for SAP connects to the rest of your landscape
SAP (native)
Native- SAP ECC, S/4HANASAP-certified ArchiveLink integration.
- SAP Data ArchivingIntegrated SAP data archiving for transactional objects.
OpenText Content catalog (certified)
Certified- OpenText Content Cloud for SAPLive SAP content bridge and archive work together.
- OpenText Vendor Invoice Management for SAP SolutionsVIM-generated invoice documents archived in Core Archive for SAP.
- OpenText Information ArchiveNon-SAP archival companion for general-purpose records.
Identity (custom)
Custom- SAP identityIdentity aligned with SAP authorization for archive access.
Deployment and implementation
How it rolls out
- Hosting
- SaaS (North America, EMEA, APJ)
- Implementation complexity
- High
- Typical time to value
- One SAP object archived in as little as one week. First SAP object archived in two to four months. Enterprise-wide SAP archival programs typically run twelve to twenty-four months across object types.
- Prerequisites
- SAP ECC or S/4HANA in scope
- SAP object types for archival identified
- SAP Basis partnership and retention agreement
- Target archive tier deployment shape decided
- What Merito usually handles
- Merito handles Core Archive for SAP deployment, SAP object archive configuration, retention schedule design, SAP Basis coordination, and ECC to S/4HANA archive continuity.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText Core Archive for SAP is subscription-licensed with packaging keyed to archive volume, SAP instance counts, and object type scope. Pricing depends on archive volume, SAP landscape size, and deployment shape. Merito sells Core Archive for SAP alongside SAP archive program design.
- Editions and modules
Core Archive for SAP standard
SAP-certified archive for documents, data, and print lists.
Best for: SAP-centric enterprises running ECC or S/4HANA at meaningful volume.
- Common expansion areas
- Additional SAP object types
- Larger archive volume tiers
- Content Cloud for SAP for live SAP content integration
- Managed Services for ongoing archive operations
- S/4HANA archive continuity planning
Merito services
How Merito helps you win with OpenText Core Archive for SAP
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
SAP Archive Program
SAP object archive configuration, retention design, and archive wave planning.
Explore service02SAP-Adjacent Delivery
Core Archive for SAP rolled out inside broader SAP ECC and S/4HANA programs.
Explore solution03Upgrade and Migration
ECC to S/4HANA archive continuity and legacy Archive Server transitions.
Explore service04Premium Support
Named engineer, priority SLAs, and release-time coverage for SAP archive operations.
Explore service05Managed Services
Long-term SAP archive run support including volume management and retention evolution.
Explore service06Training and Enablement
SAP Basis, archive administrator, and SAP user training.
Explore service07Staff Augmentation
Merito-placed SAP archive specialists.
Explore serviceCore Archive for SAP licensing
Archive SAP before S/4HANA. Shrink the footprint. Cut the migration cost.
Merito sells OpenText Core Archive for SAP and delivers the SAP object archive configuration, retention design, and archival waves that precede a lean S/4HANA migration.
Merito point of view
SAP database growth is the silent cost driver. Archive early, archive consistently.
Merito has seen customers run ECC for fifteen years without archival and hit database sizes that drive multi-million-dollar infrastructure cost and noticeable performance drag. Core Archive for SAP solves that at a fraction of the cost. The discipline is consistency and archive early, archive consistently, and the problem never becomes acute.
For S/4HANA migrations, archiving before migration could be the right call. The smaller the database going into HANA, the smaller the license footprint and the cheaper the migration. Merito typically builds archival waves into S/4HANA migration plans.
Core Archive for SAP and Information Archive are complementary, not alternatives. Core Archive for SAP handles the SAP landscape; Information Archive handles everything else. Most enterprise programs run both.
What buyers usually underestimate
- Running SAP without archiving and hitting database-growth cost walls.
- Skipping archival before S/4HANA migration and paying for a larger HANA footprint.
- Treating Core Archive for SAP as a storage problem rather than a records-retention program.
- Not coordinating with SAP Basis on archival timing.
- Running Information Archive without Core Archive for SAP where SAP is in scope.
Related from Merito
Continue exploring OpenText Core Archive for SAP on Merito
Related solutions
Related services
Related products
- OpenText Content Cloud for SAPLive SAP content integration companion.
- OpenText Vendor Invoice Management for SAP SolutionsVIM invoice archival into Core Archive for SAP.
- OpenText Information ArchiveNon-SAP archive companion for general-purpose records.
- OpenText Content AviatorGrounded AI over archived SAP content.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText Core Archive for SAP FAQs
Consultation request
Talk to Merito about OpenText Core Archive for SAP
Share your SAP footprint (ECC or S/4HANA), archive scope, and S/4HANA migration timeline if applicable. A Merito SAP archive specialist follows up within one business day.
SAP-certified
ArchiveLink-native retrieval
Archived SAP content retrieves inside standard SAP transactions. No separate access tooling.
Pre-S/4HANA leverage
Smaller database, cheaper migration
Archiving before S/4HANA reduces the HANA footprint and migration cost. Merito plans archival into migration scope.
Next step
Map the archive candidates. Plan the waves. Execute.
A Merito Core Archive for SAP engagement scopes the archival backlog with Basis, plans waves by object type, and executes toward a lean SAP footprint.