Routing of Archive Files to Different Directories

This process describes how you can use archive routing to define rules and conditions that enable archive files to be automatically stored in specific directories in the file system during archiving. The way in which archive files are actually stored is also described here.

If you are not using a storage system that is connected using ArchiveLink, or you initally want to only store your data in the file system, you can specify logical file names in Archive Routing to define directories in which archive files can be stored automatically. If archive files are subsequently to be stored in content repositories, you can subsequently assign the correct content repository to the rules. The system observes this assignment in the storage location.

In Basis Customizing (transaction FILE), you have defined logical file names for use in Archive Routing and assigned them to the individual logical file names. For more information, see Defining Logical Path and File Names.

1. 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 directory is to be determined using archive routing.

   2. Rules

      You select an archiving object and enter one or more rules with the respective logical file names here.

   3. Conditions

      You select one of the rules and enter the condition(s) that the system can use to determine a directory that is suitable for the rule. Enter a selection here, such as carriier ID or booking date and the associated value or interval. (Note the following: You can only enter single values, such as carrier ID, and not intervals for selection values, 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.

2. Routing of Archive Files

   During the write phase of an archiving session, the system checks the rules and conditions that you have specified in the Customizing settings for specific archiving objects.

   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 directory 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 variant is found within the 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 to the respective directories during the write phase in the production mode, if all conditions described here are met and it was possible to uniquely determine a directory using the logical file name.

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

During the write phase, the system stored the archive files in the directory according to the rules and conditions that you specified.

Before archiving using SD_VBAK, define the routing rules as follows:

In words, these rules mean the following:

• Archive files for sales organization 0001 are created in the directory associated with the logical file name Z_MY_LOG_FILE1.

• Archive files for sales organization 0002 and a creation date during 1999 are created in the directory associated with the logical file name Z_MY_LOG_FILE2.

• Archive files for sales organization 0002 and a creation date during 2000 are created in the directory associated with the logical file name Z_MY_LOG_FILE3.

• Archive files for sales organization 0002 and a creation date during 2001 are created in the directory associated with the logical file name Z_MY_LOG_FILE4.

Archive files are not stored, since no content repository was specified. They remain in the file system. However, they are created in the directories for the corresponding logical file names. Once archives have been generated for both sales organizations, you decide to store the archive files. To do so, you extend the rules as follows:

Since the files have already been generated for the rules you defined previously and routed to the appropriate directories, you can easily store these here.

These examples show it can be necessary to change routing rules for sessions that have not yet been stored. This is often the case if a storage system is to be introduced at a subsequent stage.

Routing of Archive Files to Different Content Repositories