Configuration of the Outboard DataTiering ERP is logically divided into configuration steps required on the Outboard service side and Archiving Client side.
...
| Parameter | Value | Description |
|---|---|---|
| Server Path | /default_host/dvd_crp_http | Host URL of the ICF service. This path is part of the host script identification in the Content Repository definition. |
| Logon Group | <optional> | The logon group delimits applications application servers that are used to execute incoming HTTP requests from an archiving client. |
| Service User | <mandatory> | Service user which executes incoming HTTP requests from an archiving client. |
| Handler | /DVD/CRP_HAL_CL_REQ_HANDLER | Request handler class of the OutboardTM DataTiering solution. |
| SSL | Not required – running within an internal network | Requirement to use secured communication |
Authentication | Standard SAP User | Only SAP users may request service |
...
Follow setup of a Storage ID as described in the chapter Storage Management.
| Info |
|---|
If you want to use data validation functionality, please turn on the hash calculation for the created storage ID. |
...
Transaction code: /DVD/CRP_SRC
→ Changes are written to the workbench transport request
...
Transaction code: /DVD/CRP_SRC_SM
→ Changes are written to the workbench transport request
Each individual Source must be mapped to a target Storage ID which identifies the storage connector and its corresponding customizing. This enables the distribution of different data categories into dedicated storage locations – different storages or just different containers (folders). Mapping of the Source D1 to a Storage ID is shown in the table below:
| Property | Description | Value Example |
|---|---|---|
| Source ID | Unique source identifier. Defined in the Outboard DataTiering’s Source customizing. | E1_D1 |
Storage ID | Unique storage identifier. It is defined in the Storage Management customizing. | ARCH_STOR |
Storage Type | Type of storage connector. | <storage type> |
Binary Container ID | Prefix for a container name. The container is equivalent to a folder in file-system-like storage. | E1-d1- |
| Note |
|---|
The Binary Container ID (container name prefix) must conform to naming rules of the Binary Storage platform. |
...
| Info |
|---|
Please note that retention management can be currently used only for archiving files created and stored using transaction SARA. |
Prerequisites
Datavard DataFridge transports imported the system. License for product Datavard DataFridge and Datavard Glue is required.
Extended cockpit
If you chose to use our service also with Retention management and you imported all relevant transports to the system your product cockpit will be automatically extended with Retention management setup steps.
...
Retention date field needs to contain date information (at least year is required) otherwise registration of file could fail with parsing error.
How to fill
...
customizing
Transaction: /DVD/CRP_RM_SETUP
If you already identified the retention date and legal entity field, you can now fill in the customizing using the mentioned /DVD/CRP_RM_SETUP transaction.
...
You can choose based on your use case preferences. However we recommend to have having a second option, so you have multiple sources mapped to one logical system.
...
Before you create a logical system you need to know for which archiving object/s it will be used. The setup report will generate so-called business objects (for each Archiving object) and assign it to a logical system.
Report parameters
| Parameter | Description |
|---|---|
| Source System ID | Source System ID and Source sys. The client is used for the creation of a new logical system name. New name will be created as follows: <Source System ID>_<Source sys. Client> Created logical system will be automatically used for registration of archiving files from sources that have set identical System ID and Client on Source definition (transaction /DVD/CRP_SRC). Kindly find more information below in the section How to pair the logical system to the source. Note that System ID doesn't need to be the ID of a real system and also apply |
to Client, it is possible to choose it freely. | |
| Source sys. Client | |
| Archiving Object | List of archiving object that will be assigned as business objects to the system. |
| Storage ID for gen. objects | Transparent storage ID where required tables will be generated. Storage ID created for the primary database is used in most cases. |
| Package for generated objects | Name of development package where generated tables will be created. You can use also the local package $TMP. |
How to pair a logical system to source
...
Another required step is to set a retention definition. There are two options on how to set retention for the archive file:
...
Specific retention for archiving object objects and legal entity entities can be set in the transaction.
...
- No retention rules are defined for a specific legal entity
- Archiving file contains more than one legal entity value
You can set default retention by following the step list:
- Open transaction /DVD/RMX_EXPERT
- Double click on tree node /DVD/RMX_OBJDIR: Object directory
- node location in tree: /OutBoard DataFridge/Metadata Management/General/Business Object Maintenance/
- Fill Object Identifier with the name of <logical system>.<archiving object> and execute
- example DV_111.BC_SBAL
- Click on the Edit entry button
- Fill desired Retention period and Retention period unit and execute
...
If your use case requires a definition of specific retention for legal entity value, firstly you need to make sure that archiving files in fact sessions fulfill the following prerequisite.
- All records in the archive file have the same legal entity value
Therefore you need to consider this before you start with the creation of archive variants in the SARA transaction.
Retention than then can be set using the following step list:
- Open transaction /DVD/CRP
- Double click on the Retention definition tree node
- Click on the New entry button
- Fill in the following details
- Object Identifier - <logical system>.<archiving object>
- Legal entity - legal entity value relevant for arching object
- Retention and Retention Period
- Execute
Automatic reg. document parameters
Registration of stored documents is a necessary step to be able to use retention management. This can be done manually or automatically when the document is successfully stored in the storage. Here you can find how to activate automatic registration.
...
- Open transaction /DVD/CRP
- Double click on Manual registration of the document
Report parameters
| Parameter name | Description | |||||
|---|---|---|---|---|---|---|
| Source ID | Source ID where documents are stored | |||||
| Register only new documents | Register that was added after the last execution of this report with this option If you want to check the last execution timestamp please follow:
| |||||
Re/Register selected documents | Register documents from source ID defined by select option Document ID | |||||
| Document ID | Fill document IDs that should be registered, this is valid only for option Re/Register selected documents |
Logs
For each execution of the report, an application log is created. This applies to manual as well as automatic registration. You can find detailed information about the registered documents.