Migrating SOFFCONT1 Attachments to an External Content Server in SAP

Introduction

When planning an S/4HANA migration or optimizing your SAP system landscape, one of the hidden but critical tasks is dealing with the SOFFCONT1 table. This table stores SAP Office attachments (emails, workflows, GOS attachments), and it can grow rapidly—bloated databases, slow performance, and migration pain are often the result.

This blog walks you step-by-step through the concepts, customizing, and migration steps needed to offload SOFFCONT1 to an external content repository, ensuring your system stays lean and future-proof.

1. Understanding SOFFCONT1

The SOFFCONT1 table is where SAP saves SAP Office documents, including:

• Emails and faxes sent from SAP

• Attachments created with Generic Object Services (GOS)

• SAPscript or SmartForms outputs

• Workflow attachments

Over time, these unstructured objects (binary documents like PDFs, Excel files, ABAP lists) accumulate and consume large amounts of database space.

2. GOS & PPF – Why It Matters

• Generic Object Services (GOS): Allows linking SAP documents (POs, Sales Orders, etc.) to external files, notes, or URLs.

• Post Processing Framework (PPF): Successor to message control, it automates follow-up actions (e.g., trigger an email when a sales contract is near expiry).

 3. Customizing SOFFCONT1 for External Storage

The goal: redirect SOFFCONT1 storage from the database to an ArchiveLink Content Server.

Step 1: Define a Content Repository (OAC0)

Create a new repository (e.g., ZSOFTDB).

Step 2: Assign Category (OACT)

Copy SOFFDB → assign it to your new repository.

Step 3: Enable Category Maintenance (SE16 → SDOKPHCL)

Maintain PH_CLASS SOFFPHIO, set CAT_MAINT = X.

Step 4: Map in SKPR08

Assign new category (ZSOFTDB).

 4. Migrating Existing Documents

SAP delivers Report RSIRPIRL to move attachments from old SOFFDB to your new repository (ZSOFTDB).

• Test Run Mode → Simulates migration, lists documents.

• Productive Run → Copies documents, deletes from old repository.

5. Validating Migration

• Check documents in SE16 (BKPF Table) for company codes and document numbers.

• Use FB03 → Attachments → Attachment List to confirm successful migration.

Key Takeaways

• SOFFCONT1 holds unstructured attachments that grow fast.

• Redirecting storage to an ArchiveLink Content Server reduces DB size.

• Migration via RSIRPIRL ensures old documents are moved safely.

• Proper customizing (OAC0, OACT, SDOKPHCL, SKPR08) is crucial.

By following this approach, you ensure your S/4HANA migration is lighter, faster, and more compliant.