cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hello everyone,

Currently we have execute a project which we migrate all documents from the SOFFCONT1 table to a ContentServer repository. We are migrating this documents with the report RSIRPIRL.

Our question is about the type of document storage on SOFFCONT1, it is possible to know which transaction or type of document is currently saving documents on this table? This is because we need to perform testing with the migrated document, but we need to know who storage documents to ask to the final users test this new content server.

Thanks and best regards!


------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.
0 Likes
View Entire Topic
JuveriaK
Active Participant
0 Likes

The SAP Note is correct  SAP does not store “document type” metadata directly in SOFFCONT1.

However, from a diagnostic and migration-planning perspective, you can still infer which business objects are contributing to SOFFCONT1 growth, even if you cannot determine the original transaction code.

Practical approaches used in ECC → S/4HANA assessments:

 SRGBTBREL

  • RELTYPE = 'ATTA' indicates GOS attachments

  • TYPEID_A identifies the BOR object (BUS2012, BKPF, DRAW, etc.)

 SOFFPHIO

  • Provides metadata consistency checks for attachments

  • Useful for identifying orphaned or unreachable content

 DMS scenarios

  • For DIR objects (DRAW), tables like DMS_DOC2LOIO help correlate document usage

 OACT configuration

  • Determines whether content is stored in SOFFCONT1 or external repositories

  • Often inconsistently maintained over long system lifetimes

In practice, content risk assessment focuses on relationship integrity and volume distribution, not individual creation transactions.

This distinction becomes critical during S/4HANA migrations, where SOFFCONT1 size and broken GOS links are common cutover blockers and HANA cost drivers.