SAP Solution Manager

4.5.1 DSVASRESULTS*: Service Sessions in SAP Solution Manager

The content of the service session performed on your solution manager, e.g. Early Watch Alert, Going Live Check, etc. is stored in tables like DSVASRESULTSGEN, DSVASRESULTSATTR , DSVASRESULTSSEL and some more. (see SAP Notes 1300107 (ST 400))

4.5.1.1 Avoidance

An Early Watch Alert (EWA) session is automatically created for all systems in all solution landscapes. By ensuring, that a system is only assigned to one solution landscape instead of assigning it to many different solution landscapes, you can ensure, that an Early Watch Alert session is only executed once per system.

4.5.1.2 Summarization

Cannot be used

4.5.1.3 Deletion

Old sessions can be deleted via standard report RDSMOPREDUCEDATA. In case a service session was not attached to a solution report RDSVAS_REDUCE_DATA has to be used alternatively. (see SAP Note

1799531).

See also SAP Notes:

638785 (ST 310 – 400): SAP Solution Manager - reduce data volumes

1799531 (ST 400 – 710): Deletion of old service sessions not attached to a solution

4.5.1.4 Archiving

Sessions can be archived by moving the data to an external content repository.

See also SAP Notes:

546685 (ST 320 - 400): Archiving in Solution Manager (operation)

4.5.2 SACONT01, SASACONT1: Document Management in Solution Manager

In the Solution Manager, you can manage the documents which arise in the various project phases. Each Solution Manager system has an internal SAP Knowledge Warehouse for storing documents created in a project, solution or roadmap. The system puts the documents in the context in the Knowledge Warehouse, which you specified when you created the project, solution or roadmap.

Documents in projects, solutions or project documentation in a roadmap with project link belong to document area IWBSOLAR.

Roadmap documents (topics, accelerators) belong to document area IWBASAP.

The Solution Manager system has its own Knowledge Warehouse to store documents, but you can also connect an external SAP Knowledge Warehouse.

A project can generate a lot of data because the Solution Manager saves every version of a document by default. You can relieve the database by moving the contents of documents which you have created in a project, into another data repository. You can also delete old versions of documents which you no longer need.

Table SACONT01 basically contains document content belonging to SAP Solution Manager and stored using Knowledge Warehouse. Its content resumes to documents in area IWBSOLAR.

These documents are created and managed in the implementation area (SOLAR01, SOLAR02) and depending on the usage of projects; this table can grow very big. As long the documents are being created and managed, every version of these documents is stored (you may access older versions through

document’s history of changes), that is the main reason for the table growth.

Also, even if you don’t use projects and have never created a project, this table will grow as long as you keep implement Solution Manager Implementation Content (ST-ICO) packages. This package delivers content for the implementation area, and one example is the BPR (Business Process Repository) content. This includes many previously built business scenarios and documents for usage in projects.

Regarding table SASACONT1, it is very similar to SACONT01 but it is specifically for roadmap content. It handles the content created for roadmaps and content delivered by ST-ICO.

See SAP Notes:

966400 (Solution Manager ST 400): Solution Manager and Knowledge Warehouse

4.5.2.1 Avoidance

Not possible

4.5.2.2 Summarization

Not possible

4.5.2.3 Deletion

Report SOLMAN_DOCU_VERSION_DEL deletes older versions of documents in all data repositories. But only table SACONT01 is concerned. Please check SAP note 1360436 for futher information regarding this report.

If you are authorized, this program also deletes the contents of documents which you have moved into another data repository or archive, with the program SOLMAN_DOCU_VERSION_ARCHIVE. Report SOLMAN_UNUSED_DOCUMENTS search for unused documents. A document is considered

unused when it is not assigned to any project but it still exists physically. The report searches for all

documents created by a user and checks whether they are used. The system issues documents for which it cannot find a record of use in a list. The listed documents can be selected individually and deleted if required. For further instructions on how to use this report, please check note 923203.

Please be aware of the fact that only table SACONT01 will be touched by these reports.

See SAP Notes:

1360436 (Solution Manager ST 400): Error in the program SOLMAN_DOCU_VERSION_DEL 923203 (Solution Manager ST 320 - 400): Deleting unused documents from the Solution Manager

4.5.2.4 Archiving

For archiving of table SACONT01, please check use of report SOLMAN_DOCU_VERSION_ARCHIVE. This report moves the contents of documents or older versions of documents, into another data repository, e.g. into an archive. The document header data and attributes are retained in the Solution Manager. The program SOLMAN_DOCU_VERSION_ARCHIVE moves all document versions of the selected status values that were changed last by a person other than "SAP", except for the most recent version in each language.

See SAP Notes:

1360988 (Solution Manager ST 400): Error in the program SOLMAN_DOCU_VERSION_ARCHIVE 1773780 (Solution Manager ST 700 – 720): How to check if a document was successfully archived by SOLMAN_DOCU_VERSION_ARCHIVE

As far as table SASACONT1 is concerned, the size of the table is either determined by use of large number of own roadmaps or by the roadmap documents contained in ST-ICO.

Unfortunately if you would delete unused roadmaps this would not delete the corresponding documents. There will be a deletion report in future.

However it is planned to reduce the size of future support packages of ST-ICO by deleting unused or outdated roadmap documents. This would be a solution if there is not an acute problem with table space but only concerns of further growing.

The usual way to reduce the size of this table is move the content to an external content server.

In transaction OAC0, you can change the customizing of a content repository and assign an external content server instead of the currently maintained DB table. This is explained in note 546685 and the detailed steps are contained in note 710711.

See SAP Notes:

546685 (Solution Manager ST 320 - 400): Archiving in Solution Manager (operation) 710711 (Solution Manager ST 310 - 400): Solution Manager: Using a Content Server