With this object, you can archive scenario sets. You can do this to reduce data volumes. Over time, scenario sets are finished or become obsolete, as the marketing contents are either completely executed and closed, or in some cases, the contents are never executed at all.
When a scenario set is archived, the system writes it to an archive file, together with information about all its scenarios and its planning scope. The system does not archive individual scenarios.
For the data to be archived, it must have the appropriate archiving status
Can Be Archived
. This status is set during the archivability check that you carry out during the check phase, and can only be set if the scenario set has the status
Finished
. You have to set this status manually in your scenario set.
The system does not archive the data until the residence time has elapsed. You define the residence time in the
SAP Implementation Guide
, under
When the system archives a scenario set, it writes it to an archive file with information about all the scenarios it contains and the scope. It is not possible to archive individual scenarios.
In addition, the system writes an entry in an index table (CRMD_MKTSC_ACIDX) that can be accessed by the scenario planning application. The index table makes it possible for the application to find and retrieve archived scenario sets.
Once a scenario set has been archived, you cannot un-archive it again. The system can only read it from the archive.
The archiving process for the marketing projects contained in the scenario set is completely independent from the archiving process of the scenario set. Consequently, when a scenario set is archived, the marketing projects are not archived along with it (and vice versa). For more information about the archiving of marketing projects, see Archiving Marketing Data .
Archiving of scenario sets follows the standard three-phase approach, in which the objects to be archived are first selected, archived, and finally deleted.
When a scenario set is archived, the following objects are archived:
Table Name |
Content |
---|---|
CRMD_MKTSC_WKS_H |
Scenario set headers |
CRMD_MKTSC_WKS_T |
Scenario set header texts |
CRMD_MKTSC_SCN_H |
Scenario headers |
CRMD_MKTSC_SCN_T |
Scenario header texts |
CRMD_MKTSC_SCO_I |
Scope items (links to marketing projects) |
CRMD_MKTSC_ACLOG* |
Action log (user actions) |
Note
Entries from CRMD_MKTSC_ACLOG are only deleted and not written to an archive file
The following archiving class and programs can be used for the archiving of scenario sets:
Program |
Function |
Remarks |
---|---|---|
CL_CRM_MKTSC_AC |
Archiving class |
Contains a number of static methods used by the archiving programs |
CRM_MKTSC_CHECK_AC |
Select archivable objects |
Selects a number of scenario sets in status "Finished" and switches their status to "Can be archived" |
CRM_MKTSC_WRITE_AC |
Write objects to archive |
Selects a number of Scenario Sets in status "Can be archived" and writes their data to archive files. The status is then set to "Archived" |
CRM_MKTSC_DELETE_AC |
Delete archived data from DB |
Enables you to select archive files and delete the original data of the objects in the archive file from the database |
Note
You can use the programs individually to select scenario sets for archiving.