Routing of Archive Files to Different Content-Repositories

Purpose

This process describes how you set up rules and conditions for automatically routing archive files to specific content repositories during archiving, and how this storage process is then performed. This entire process is called Archive Routing.

Process Flow

       1.      Setting up the rules and conditions for Archive Routing

The rules and conditions are set up in Archiving-Object-Specific Customizing available in Archive Administration (transaction SARA), under Archive Routing.

                            a.      Archiving Object

First you must enter for which archiving objects the content repository is to be determined using Archive Routing. If an entry has been made here, the system ignores the entry for content repository made in the technical settings.

However, without further information the system cannot determine a content repository and archiving will not be possible.

                            b.      Rules

Here you select an archiving object and for this object enter one or more rules, each with one content repository.

                            c.      Conditions

Here you select one of the rules and enter one or more conditions, based on which the system can determine the corresponding content repository for this rule. You enter a selection value, such as Carrier ID or Booking Date and the corresponding value or interval. (Note: for selection values such as Carrier ID, you can only enter single values, no intervals. The single value, such as LH, is entered in the From field). The input help (F4) can assist you in choosing a selection value.

       2.      The routing of the archive files

During an archiving session the system checks the rules and conditions you created twice: once during the write phase and again during the storage phase.

As described under Archive Routing, it is important to point out that the system uses the selection values entered in the variant of the write program, to determine into which content repository the archive files of an archiving session should be stored. Therefore, you must ensure that the data covered by the selection values of the variant falls within the data set determined by the rules. If this is not the case, the archiving session is terminated during the first check, meaning even before data is even written.

The actual routing of the archive files does not take place until the storage phase, if all conditions have been fulfilled and an appropriate content repository could be determined.

Only one content repository can be targeted during an archiving session. This means that if you want to use more than one content repository for one archiving object, you must start a different session for each content repository.

After the data has been stored: Changing the routing rules does not affect the archive files that have already been stored. When an archiving file is created, the system saves the content repository information in Archive Administration. This information is then always read from there, which ensures that the system can find an archive file even if it would be stored in a different content repository according t the new routing rules.

Note particularly that the storage space is not reorganized if you change the routing rules. Files that have already been stored remain in their original place.

Result

The archive files have been routed to the appropriate content repository during the storage phase, based on the rules and conditions you set up in Archive Routing.

Example

The following examples show different scenarios in Archive Routing.

You created the following routing rules in Archive Routing:

Sales Org.

Creation Date

Content Repository

Logical File Name

0001

any

A1 (rule 1)

0002

1.1.2000 to 12.31.2002

A2 (rule 2)

0003

1.1.2003 to 12.31.9999

A3 (rule 3)

In words these rules can be expressed as follows:

·        Documents of sales organization 0001 are stored in content repository A1.

·        Documents of sales organization 0002 that were created between 2000 and 2002 are stored in content repository A2.

·        Documents of sales organization 0002 that were created starting in and including 2003, are stored in content repository A3.

The creation date refers to the “Created On” selection field and not to 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

An archive file that is created using this variant is stored in content repository A2. The sales organization is exactly the sales organization from rule 2, and the time interval falls exactly within the time interval of rule 2.

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

01.31.2000

or

from

01.01.2001

to

01.31.2001

without

from

01.06.2001

to

This variant means that you want to archive sales documents whose document number falls between 1 and 100,000, that belong to sales organization 0002 and that were created in January 2000 or January 2001, except those from Jan. 6, 2001.

Based on these selection values, the system would choose content repository A2. The line of the sales document is ignored, because this selection criterion does not appear in the rules. The last line is also ignored, because this selection already falls within the “from 01.01.2001 to 21.01.2001” interval. This means that in terms of Archive Routing the following is relevant:

Selection variant

Sales organization

from

0002

to

Created on

from

01.01.2000

to

01.31.2000

from

01.01.2001

to

01.31.2001

Based on these criteria, the program would choose rule 2.

Example 3:

Selection variant

Sales organization

from

0002

to

Created on

Larger than or equal to

01.01.2003

to

In this case the system would not be able to determine a content repository. On first glance, it seems as though the third rule would be the corresponding rule, and that content repository A3 would be determined. However, this is not the case, because the system does not know whether all data that is larger than or equal to 01.01.2003, automatically falls into the “from 01.01.2003 to 12.31.9999” interval.

See also:

If the standard Archive Routing does not sufficiently meet your requirements, you can implement a Business Add-In (BAdI) ARCH_ROUTING_EXTERN. For more information see Business Add-In: Archive Routing.