Routing of Archive Files to Different Content Repositories

Use

This process describes how you can use archive routing to define rules and conditions that enable archive files to be stored in specific content repositories automatically during archiving. The actual storage process is also described here.

Process

Define Rules and Conditions for Archive Routing

You define the rules and conditions in the Customizing settings for specific archiving objects in archive administration (transaction SARA) under Archive Routing.
1. Archiving Object
  
  You first specify here the archiving objects for which the content repository is to be determined using archive routing. By specifying a content repository here, you can override the content repository entered in the technical settings.
  
  The system requires this information so that it can assign a content repository. Archiving is not possible without this.
2. Rules
  
  You select an archiving object and enter one or more rules with the respective content repository here.
3. Conditions
  
  You select one of the rules and enter the condition(s) that the system can use to determine a content repository that is suitable for the rule. Enter a selection here, such as airline or posting date and the associated value or interval. (Note the following: You can only enter single values and not ranges for selection values such as airline. The single value, such as the ID LH, is entered in the From field.) You can use the possible entries (F4) to select the selection values.
Routing of Archive Files

During an archiving session, the system checks the rules and conditions you have specified twice: Once during the write phase and then again during the storage phase.

As described under Archive Routing, it is essential that the system uses the selection values or the content of the write program variants to determine the content repository in which the archive files in an archiving session are to be stored. You should therefore ensure that the data quantity covered by the selection values in the write variant is found within the data quantity defined by the rules. If this is not the case, the system terminates the archiving session during the first check before the write phase.

Archive files are first routed during the storage phase if all conditions described here are met and it was possible to uniquely determine a content repository.

You can only define one content repository for each archiving session. If you want to use more than one content repository for the same archiving object, you must start a separate archiving session for each content repository.

Note
Following storage: Changes to the routing rules do not usually affect archive files that have already been stored. When an archive file is created, the system transfers the content repository to archive administration and then always reads it from there. This means that the system also finds an archive file even if the new routing rules would mean that it would be stored in a different content repository.

The storage is not reorganized even if the routing rules are changed. This means that archive files that have already been stored are not moved.

Result

During the storage phase, the system stored the archive files in the content repository according to the rules that you specified.

Example

The following examples show various archive routing scenarios.

You have created the following routing rules in archive routing:

Sales Organization	Creation Date	Content Repository	Logical File Name
0001	Any	A1 (rule 1)
0002	01.01.2000 to 12.31.2002	A2 (rule 2)
0003	01.01.2003 to 12.31.9999	A3 (rule 3)

In words, these rules mean the following:

Archive files for sales organization 0001 are stored in content repository A1.
Archive files for sales organization 0002 and a creation date between 2000 and 2002 are stored in content repository A2.
Archive files for sales organization 0002 and a creation date up to and including 2003 are stored in content repository A3.

Note
The creation date refers to the selection field "Created On" in the write variant and not the date on which the archive was written.

Example 1:

You start an archiving session with the following variant:

Selection variant

Sales organization	From	0002	to
Created On	From	01.01.2000	to	31.01.2000

Archive files that are to be generated using this variant should be stored in content repository A2. The sales organization is the sales organization in the second rule and the date range is found in the date range for the same rule.

Example 2:

You start an archiving session with the following variant:

Selection variant

Sales document	From	1	to	100.000
Sales Organization	From	0002	to
Created On	From	01.01.2000	to	31.01.2000
Or	From	01.01.2001	to	31.01.2001
Without	From	06.01.2001	to

This variant means that sales documents are to be archived if their document number is found between 1 and 100,000, which belong to sales organization 0002 and were created in January 2000 or January 2001 but not on 6.1.2001.

The system would determine content repository A2 for these selection values. The system ignores the line in the sales document, since this selection criterion does not appear in the rules. The system ignores the last line, since this selection is already found in the range between 01.01.2001 to 01.21.2001 This leaves the following for archive routing:

Selection Variant

Sales Organization	From	0002	to
Created on	From	01.01.2000	to	31.01.2000
	From	01.01.2001	to	31.01.2001

This is suitable for the requirements in rule 2.

Example 3:

Selection Variant

Sales Organization	From	0002	to
Created On	Greater or equal to	01.01.2003	to

The system was unable to determine any content repository here. It initially appears that the third rule should apply and the system would use content repository A3. This is not however the case, since the system does not know here that all data that is equal or later to 1.1.2003 is automatically suitable for the range "From 1.1.2003 to 12.31.9999".