Archiving Trade Repository Objects with TRTM_TARO
You use this archiving object to archive trade repository objects (TAROs) in the Transaction Manager
(TRM).
This archiving object is used to archive the following groups of trade repository objects:
Trade repository objects for financial transactions in the Transaction Manager
with the action type 30
Valuation
and 35
Security
Trade repository objects for external transactions
It is only possible to archive trade repository objects that have acquired one of the following statuses:
06
Rejection Accepted
07
Accepted
08
Obsolete
09
Reconciled
10
Reconciliation Failed
20
Invalid
The period of time that has elapsed between the time of the last change made to the TARO and the start date of the archiving run must be equal to or greater than the retention period.
Trade repository objects for financial transactions of the Transaction Manager
are generally archived together with financial transactions with the archiving object TRTM_FTR
. However, you can archive from this set of trade repository objects just those with the action types 30
Valuation
and 35
Security
, using the archiving object TRTM_TARO
and independently of the financial transaction.
Maximum size in MB: 500
The archiving object TRTM_TARO
is used to archive data from various tables.
ILM Object: TRTM_TARO
In transaction ILMARA
, assign the audit area Archiving
to the ILM object TRTM_TARO
.
Enter a residence rule for the trade repository objects.
Call transaction IRMPOL
.
In the Policy Category
field, select the residence rule
.
In the Object Category
field, select the entry SAP Business Suite
.
In the Audit Area
field, select the entry Archiving
.
In the ILM Object
field, select the entry TRTM_TARO
.
If you have not yet created a set of rules for the ILM object, you need to create one and set it for productive use.
Enter a residence rule or rules for the trade repository objects. You can specify the residence period specific to the trade repository.
For more information, see the documentation on Information Lifecycle Management
(ILM) in SAP ERP Library on the SAP Help Portal under SAP NetWeaver Information Lifecycle Management. Here you find additional information on the connection between data archiving and ILM. Note that, compared to data archiving for ILM Retention Management, you need a product license and you need to have activated the business function Information Lifecycle Management(ILM
).
Authorization Object: S_ARCHIVE
Program | Function |
|---|---|
| Write |
| Delete |
| Reload |
Creating Archive Files
You are in the Archive Administration: Initial Screen
(transaction SARA
), and the name of the archiving object TRTM_TARO
is entered in the Archiving Object
field.
Choose Write
.
A screen appears on which you can schedule the write program to be run in the background.
If archiving has already been performed for an archiving object and there are still archive files from that archiving run that have not yet been processed by the relevant deletion program, the system informs you of this in a separate window.
The same applies for interrupted archiving runs.
Caution
Archiving data more than once can lead to various problems. Hence some archiving objects require that data is not replicated in the archive, because this can lead to incorrect results (such as using archived data to produce totals). Ensure the following:
The new write job that needs to be scheduled does not select the same data that is contained in archive files that have not yet been processed by the deletion program
No variants with overlapping selection values are used in parallel.
Note
If the variant that you have selected is already being used in other jobs, you can choose the Jobs with Selected Variant
pushbutton to display the variant and delete it if necessary.
Use the input help to select a variant. If no variant is available, choose Maintain
and create the variant that you require.
Enter the start date
and the spool parameters
.
Note
With the Archive Directory
pushbutton, you can determine how much storage space is free in the current object-specific archive directory before you start to archive.
Now you have entered all of the data required for the background job. To run the job, choose Execute
.
Note
After all archive files of a session have been written completely, the system event SAP_ARCHIVING_WRITE_FINISHED
is triggered by the ADK. In reaction to this event, processes that occur downstream from archiving (such as automated file storage) can be triggered by external tools.
Furthermore, you can navigate to the following menu options:
Customizing
Job Overview: Here you find an overview of all archiving jobs as well as functions for processing them.
Administration
Database Tables
Information System
Note
You can display the logs documenting processing by choosing Logs
from the Archive Administration initial screen.
Deleting Archived Data from the Database
You can display the archived data as follows:
In the Archive Information System
(transaction SARI
), you can display the data archived when you have activated archive information structures for the archiving object.
In exceptional cases when archiving runs contain errors, you can use the "Reload" function to reload the archive. For more information, see Reloading the Archive
Archiving is performed using the Archive Development Kit (ADK)
. See also: The documentation on Data Archiving
in SAP NetWeaver Library, in particular the section relating to archiving using the Archive Development Kit (ADK)
.