Hierarchy

⤷

⤷

IMG Activity
ID | BC_ADK_ROUTING | Archive Routing |
Transaction Code | S_BCE_68002181 | (empty) |
Created on | 20041008 | |
Customizing Attributes | BC_ADK_OPTIONAL | Data Archiving - Optional Activity |
Customizing Activity | BC_ADK_ROUTING | Archive Routing |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BC_ADK_ROUTING |
Use
In this Customizing activity you can create rules and conditions for routing archive files to specific content repositories. A content repository can be determined on organizational unit level (for example, company code) or time-related criteria (for example, fiscal year).
Features
In this Customizing activity, you can enter rules to specify how the system should determine into which content repository to route archive files, using the selection criteria you enter in the write program during archiving. The rules are always entered for a specific archiving object. For each rule you enter conditions that are made up of a selection criterion and a corresponding value or interval. It is also possible to enter one or more rules with one or more conditions for an archiving object. The complexity of the rules depends on how specific the criteria for separating your archived data into different content repositories must be.
If you did not enter any rules, the system determines the content repository in the manner it did before Archive Routing.
The smallest unit for which a content repository can be determined using Archive Routing is an archiving session. This means that the individual files and all data objects (documents) of a session are routed to one and the same Content Repository. If you want to route data to different content repositories, you must execute a separate archiving session for each content repository.
Archiving Process
The rules are checked twice during the archiving process: Once during the write run and again during the archiving session. Note that Archive Routing does not use the actual contents of the archive files to determine the content repository, but rather the selection criteria you entered for the write session (the values you entered in the variant of the write program). Keep in mind that the data set covered by the selection criteria of the write variant does not need to match the data set determined by the routing rules exactly. Rather, the data set covered by the variant must fall inside the data set determined by the routing rules. If this is not the case, the archiving session is terminated. If this is the case, the archiving session is executed and the archive files are routed to the corresponding content repository during the storage phase.
More information:
For more information, see the application help, which you can reach from the Customizing activity by choosing Help -> Application Help.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
ARCH_ROUTING | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20050114 |
SAP Release Created in | 700 |