SOOD table — SOOD - SAPoffice Document Header Table

Each row in SOOD represents one SAPoffice document object header: an internal mail sent through Business Workplace, a workflow deadline or notification document, an ABAP list saved to a folder, or an outbound fax, telex or email item picked up by SAPconnect. The row carries the subject line, the object's creation date and time, the owning user, and the object type that tells the system what kind of document it is (raw text, external file attachment, folder, distribution list entry, and so on). SOOD does not hold the payload itself. The three-part key formed by object type, object year and object number identifies the document uniquely and is the join point used everywhere else the object is referenced: folder membership, content storage, distribution, and workflow linkage.

SOOD is client-dependent and grows continuously as long as workflow, Business Workplace and SAPconnect stay active, so client and a date range on CREDATE are the first two restrictions before running any selection. OBJTP is highly selective and should be added whenever the investigation concerns one category of document, such as external fax attachments versus internal mail. Selecting by OWNSAP narrows to one user's mailbox activity. Never select on OBJNO alone; it repeats across OBJYR and across OBJTP, so a bare object number match across years produces false positives that look like duplicate documents.

To confirm whether a specific workflow notification or fax was actually generated, search SOOD by OBJDES using the known subject text pattern together with a CREDATE range around the reported time and, if known, OWNSAP. A matching row proves the document object was created; absence of a row proves the generating step (workflow step, background job, or SAPconnect send) never fired, which redirects the investigation upstream to the job or workflow log rather than to SAPoffice itself.

SOOD is unchanged structurally on S/4HANA and continues to be populated by internal Business Workplace mail, workflow notifications and SAPconnect-based outbound communication. There is no known compatibility view replacing it; it remains a classic transparent table under the same technical name. Newer communication channels built on more current messaging frameworks bypass SOOD entirely, so on systems that have moved notification-heavy processes off classic SAPoffice, the table's growth rate can look much flatter than on an older ECC system doing the same business volume.

First point of contact is Basis, since SOOD sits under SAPoffice and SAPconnect administration alongside job scheduling and outbound communication configuration. Functional teams get pulled in when the question is about a specific workflow's notification text or a specific business object's attachment, since they own the template or the triggering step; Basis owns the table's size, growth rate and reorganisation schedule.

SOFM carries folder membership for the same object key. SOFFCONT1, and SOC3 on older releases, hold the actual document content. The send request monitor behind SOST surfaces outbound status for documents originating here. Business Workplace (transaction SBWP) and the classic inbox transactions are the main writers of new SOOD rows through everyday mail and workflow activity, alongside background jobs that generate automated notifications.