on 2022 Jul 13 8:49 PM
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!
Request clarification before answering.
Dear customer,
As per SAP Note 904711 - SAPoffice: Where are documents physically stored?, section solution:
"It is not possible to determine the storage location for individual document types. It is also not possible to determine in which scenario the document was created. You can only determine whether SAPoffice documents are stored in the ' SOFFCONT1' database table using the KPRO or in an external system."
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You cannot directly identify the transaction that created each SOFFCONT1 record.
However, you can infer the business context by checking SRGBTBREL:
- TYPEID_A shows the business object (e.g. BUS2012, BKPF, DRAW)
- RELTYPE = ATTA indicates an attachment
For DMS documents, check table DMS_DOC2LOIO.
Also verify content repository configuration in OACT, because SOFFCONT1 is the default store but may be overridden.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, this is true but still you can get an idea of what type of business documents have attachments stored in there.
For most of them just look in SRGBTBREL table, the column TYPEID_A contains the business object type, and RELTYPE indicates ATTA when an attachment is effectively stored in the table SOFFCONT1.
For the particular case of DRAW (DIR - document info records) you can check table DMS_DOC2LOIO which contains also DIRs to which attachments have been added and which are also by default stored in SOFFCONT1
Of course you should always check the configuration of the content categories (OACT) as SOFFCONT1 is used by default but that can be changed to other content store such as content server, yac, opentext, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 8 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.