PRESENTACIÓN

Table SOC3 contains the contents of documents (excluding object types FOL and DLI), such as application mails, URLs, work item notes, PC documents, etc., which are created and sent in SAP Business Workplace

(previously known as SAPoffice), and of documents that were created by Generic Object Services (GOS). Therefore, the size of this table depends heavily on whether and how frequently these types of documents are sent within a system. The documents are stored in folders that can be accessed either from the user interface or only through the system (the latter are called “dark folders”).

The corresponding management data is stored in table SOOD, the folder management data in table SOFM and the information of the send process in tables SOOS (send procedure) and SOST (send history). The size of these tables, however, should generally be no cause for concern.

Note: Further developments of the current SAPoffice functionality were stopped with SAP

Web AS 6.30. Maintenance on SAPoffice continues until the end of maintenance of SAP R/3 Enterprise (March 31, 2009). Therefore SAP recommends that you use SAPoffice only for the storage of temporary documents and that you store documents that have to be kept for the long term in storage systems using an appropriate technology such as ArchiveLink. No archiving functions are currently planned for SAPoffice.

If you are currently using SAPoffice as an internal communications platform, SAP recommends that you switch to an alternative mail system early enough.

For more information, see the Development News “Use of SAPoffice as an Office Application“ for SAP Web AS 6.30 (2003).

4.1.18.1 Prevention

The system saves the office attachments in table SOFFCONT1, if no external storage system is being used. If used, this table can grow very large. To prevent this table from growing too large, SAP recommends that you use an external storage system.

Subsequently moving attachments from table SOFFCONT1 to an external storage system is only possible through a modification. For more information see SAP Note 389366 (SAP R/3 4.6B – SAP Web AS 6.10) and 445057 (SAP R/3 4.6B – SAP Web AS 6.10).

4.1.18.2 Aggregation

Cannot be used.

4.1.18.3 Deletion

If a user deletes documents or mails from a folder (with or without attachments), only the references between the folder and the documents are deleted at first. The content of the document remains in the database, including the header data and the send logs. This data can be physically deleted from the database (tables SOC3, SOST, SOOS, SOOD, SOFM, SOFFCONT1) using program RSBCS_REORG (replaces the program RSSORE00 used up to SAP Web AS 6.20, see SAP Note 966854).

Because archiving of Business Workplace objects is not possible, it is very important for users to regularly delete their old documents manually.

If you want to delete business workplace objects, we recommend that you use the delete programs and follow the procedure named below:

1. Deleting the folder references (table SOFM) Use the following programs:

Program

What does it delete? Note

RSSOTRCL Data in the general wastebasket Ask your users to regularly delete the documents they no longer need. Then you can empty the general trash can using report RSSOTRCL. RSSO_DELETE_PRIVATE User folders: Inbox, outbox,

express mails, etc.

This program can be used to delete all the objects of a specific user, for example when he or she leaves the company. See also SAP Notes 63912, 862985, and 922671.

can also use

RSSO_DELETE_PRIVATE. See also SAP Note 431801. RSSODLWF

RSSOREDF¹

Workflow mails This program deletes documents from the dark folder. See also SAP Notes 131031 and 569123. RSSORESN Successful send processes Dark folders

¹ With version 14 of SAP Note 567975 report RSSODFRE was a completely revised. As of that date, you do not need any other programs besides RSSODFRE to reorganize the dark folders. The reports RSSODLWF (SAP Note 131031), RSSORESN (433457) and RSSOREDF (516110) are obsolete as of then and should no longer be used. The corresponding SAP Notes were also marked as obsolete.

2. Completely deleting an object using RSBCS_REORG.

SAP recommends that you schedule this program regularly as a background job. If you execute the program once a lot of data has accumulated, you can expect its runtime to be accordingly long.

If you want to delete objects that were created using the Generic Object Service (GOS), SAP recommends the following procedure:

1. Delete the object references using program RSGOSRE01

2. Delete successful send orders using program RSBCSRE03 (only for SAP R/3 Enterprise; for SAP NetWeaver 7.0 this program was replaced by RSBCS_REORG; see SAP Note 966854)

You should use this program before the general reorganization program RSBCS_REORG. 3. Completely delete a document using RSBCS_REORG.

See also SAP Notes:

966854 (as of SAP Web AS 6.20): SAP Note 966854 – Reorganization - New Report 881594 (as of SAP R/3 4.6C): Default expiry date for office document of workflow 988057 (SAP Web AS 6.20 – 7.00): Reorganization - information

4.1.18.4 Archiving

It is possible to move the document contents (document types RAW and SCR) from table SOC3 to an archive using transaction SOY8 or program RSSOAPUT. All other SAPoffice tables are not affected by this operation, meaning that the reference data is not archived at the same time. The program RSSOAPUT is designed to archive mass data.

It is not possible to archive SOFFCONT1 data records—it is only possible to delete them and reorganize the mailbox.

4.1.18.4.1 Table Analysis

If you want to run a table analysis (transaction TAANA) before data archiving (see Chapter 2), the following analysis variants are offered for the corresponding tables:

Table Analysis Variant

SOC3 STANDARD SOFM STANDARD SOST STANDARD