Archiving Content Packages of Rapid Content Delivery
You use the archiving object CSU to archive data that belongs to content deliveries downloaded or imported in the rapid content delivery application.
When you archive data, the system writes the data to be archived into one or more archive files. To archive only data that is no longer needed in current business processes, this data must meet certain conditions. To ensure the data to be archived meets these conditions, the write program considers the following parameters and performs several checks.
The write program archives rapid content delivery content packages, taking into account the following parameters and checks:
Delivery Version
Status
Content Name
Content Registered Version
SP Level
The write program archives all the delivery versions of the content that are downloaded or imported, except for the highest delivery version of each of the contents. Archiving happens every three months.
Example
In the example below, the write program did not archive the highest downloaded and highest imported delivery version of the content.
Content Name | Delivery Version | Status | Content Registered Version | SP Level | Archived |
|---|---|---|---|---|---|
MAI | 3 | Downloaded | 1 | 12 | Yes |
MAI | 6 | Imported | 1 | 12 | Yes |
MAI | 9 | Downloaded | 1 | 12 | No |
MAI | 10 | Imported | 1 | 12 | No |
GP | 1 | Downloaded | 1 | 12 | Yes |
GP | 2 | Imported | 1 | 12 | No |
GP | 15 | Downloaded | 1 | 12 | No |
CUP | 1 | Downloaded | 1 | SP independent content | No |
CUP | 3 | Imported | 1 | SP independent content | No |
Tables
Archiving object CSU archives data from the RCSU_STAGING
table.
Programs
The following programs are delivered for the archiving object CSU:
Program | Function |
|---|---|
| Write |
| Delete |
| Reload |
The delete program contains the standard variants SAP∏(production mode) and SAP&TEST; (test mode).