When
October 27–29, 2026
Three days of in-person learning, technical exploration and SAP community connection.
Past event · Gold Sponsor · Berlin · October 27–29, 2026
ArchiveHub at SAP TechEd Berlin 2026.
SAP TechEd Berlin brings the SAP technical community together for learning, workshops and technology sessions. ArchiveHub was a Gold Sponsor of the 2026 event.
The Berlin event has concluded. Continue the conversation about SAP S/4HANA, legacy-application retirement and governed access to business history.
Where
Messe Berlin
Messedamm 22, 14055 Berlin, Germany.
ArchiveHub
Gold Sponsor
Request a follow-up discussion about historical SAP data, application retirement, modern reporting and governed agent access.
Past event: SAP TechEd Berlin 2026 took place October 27–29 at Messe Berlin. This page retains the original dates and venue for reference. See SAP's official event information or explore upcoming ArchiveHub appearances.
Continue exploring
Bring one transformation question. Leave with a clearer decision path.
Use these resources to explore practical design choices that determine whether historical information remains useful after migration or shutdown.
S/4HANA historical-data decisions
Decide what information belongs in the operational target, what should be archived, what needs independent preservation and what may be eligible for defensible disposition.
Explore the strategy →Legacy SAP retirement
Replace “keep ECC for occasional lookup” with an evidence-based path covering data, documents, relationships, reporting, validation and accountable shutdown approval.
Review SAP decommissioning →Historical reporting and user experience
Give appropriately authorized users a business-oriented way to search, report, drill into relationships and retrieve supporting documents without reopening the retired source.
Explore historical reporting →Governed AI and agents
Explore how authorized historical context may support agent experiences while preserving identity, authorization, provenance, audit and human accountability.
Explore AI and agents →Explore a follow-up demonstration
Retire the application. Keep the business history usable.
A successful application-retirement program must do more than copy tables. It should define which business objects and documents remain required, preserve their meaning and relationships, validate historical user journeys, reconcile agreed control totals and assemble reviewable shutdown evidence.
Request a governed historical-data demonstration designed around those requirements. Demonstration scope depends on the scenario and configuration; a demonstration does not imply that every source, object or integration is available without discovery and design.
Useful questions to bring
- Which legacy SAP applications remain online only for historical access?
- Which ECC history should move to S/4HANA—and which should not?
- How will users retrieve transactions, reports, attachments and related documents after shutdown?
- What must finance, audit, security, records and business owners validate?
- What evidence is required before leadership authorizes shutdown?
AI and agents
Governed historical context for SAP Joule, A2A and MCP experiences.
Discuss SAP Joule, Agent2Agent interoperability and Model Context Protocol integrations with the ArchiveHub team. Confirm current availability and the supported integration scope for your architecture and customer environment.
Historical information should not be treated as unrestricted AI context: identity, authorization, provenance, audit, privacy and human-review controls remain part of the design.
Review ArchiveHub AI and agent principles →Prepare for the conversation
Choose a starting point for your follow-up.
Select one application
Choose an ECC system or another legacy application with a clear transformation, cost, risk or retirement driver.
Identify continuing users
List who still needs historical information, which questions they ask and what documents or exports they require.
Bring known constraints
Capture existing archives, custom data, document repositories, retention concerns, interfaces and unresolved ownership.
Book a focused discussion
Use the meeting request to tell us which scenario matters so the conversation can begin with your decision—not a generic presentation.
Frequently asked questions
Following up after SAP TechEd.
When and where did SAP TechEd Berlin 2026 take place?
The event took place October 27–29, 2026 at Messe Berlin, Messedamm 22, 14055 Berlin, Germany. It has concluded; this page is retained as a past-event reference.
Was ArchiveHub a sponsor of SAP TechEd 2026?
ArchiveHub was a Gold Sponsor of SAP TechEd Berlin 2026.
Can I request a follow-up after the event?
Yes. Use the TechEd follow-up request and describe the SAP transformation, historical-reporting or application-retirement question you want to discuss. ArchiveHub will follow up using the contact information you provide.
Can we discuss SAP Joule, A2A and MCP capabilities?
Yes. Ask the ArchiveHub team about governed agent scenarios involving SAP Joule, Agent2Agent interoperability and Model Context Protocol integrations. Confirm current release availability and the supported scope for your environment with the team.
Do I need a fully defined decommissioning project?
No. A useful conversation can begin with one candidate application, its continuing historical users and the dependencies that currently prevent retirement.
Continue after TechEd
Make your follow-up specific to your landscape.
Tell us which SAP system, historical-access requirement or retirement decision you want to explore.