Archiving of Problems (CRM-MD-SDB)
Use
You can use archiving object CRM_SDBPBL to archive problems that are no longer needed in the Solution Database . You archive problems using archive administration (transaction SARA). The process is as follows:
You select the data using a selection variant.
The preprocessing program checks the data for archivability and flags it for archiving.
The write program writes the data to the archive.
The delete program deletes the data from the Solution Database.
Structure
Programs and Function Modules |
Name |
|---|---|
Preprocessing program |
CRM_ARC_SDBPBL_CHECK |
Write program |
CRM_ARC_SDBPBL_SAVE |
Delete program |
CRM_ARC_SDBPBL_DELETE |
Read program |
CRM_ARC_SDBPBL_READ |
Archiving-Object-Specific Characteristics
Archiving object CRM_SDBPBL archives entries from various database tables, which you can display via
Tables and Archiving Objects
(transaction DB15). In addition to these database table entries, the archiving object archives data via archiving classes (see following table).
Archiving Class |
Archived Data |
|---|---|
STATUS |
Status objects |
TEXT |
SAPscript texts |
SOBL |
Object links |
LOIO |
Logical info objects |
Integration
If you schedule a delete job in archive administration to delete archived problems from the Solution Database, the archived problems are no longer returned in searches of the Solution Database after:
The delete job is carried out.
You recompile the knowledge base using the Indexes application, usually via a delta compilation.
If you archive and subsequently delete a problem from the Solution Database, but do not archive its linked solution, the solution is no longer linked to the archived problem, and vice versa.
Problems cannot be archived if:
You have added them in Solution Database maintenance to
My Problems
, for example, for quick referenceYou have added them in Internet Customer Self Service to
My Solutions
They are used in an interaction record, which has not yet been archived
See Also: