Spend Environment Backup and Recovery 
The spend fact tables, two per context, have names that begin with FCI_SA_FACT. The fact tables are populated using Oracle's direct load method. This method does not produce a change log. The dimension tables, one set per enterprise, have names that begin with FCI_SA_DIM. Changes to the dimension tables are logged.
It is strongly recommended that you do a backup of your enterprise's spend database objects, tables, and indexes after each spend fact import action, which appends data to the fact table. A minor variation on this is to back up the tables only and re-create the indexes after a restoration of the tables.
An alternative backup procedure is to back up your enterprise's spend database objects less frequently. However, you should be prepared to recover data added by subsequent conversions of master data to dimension data (which update tables) and spend fact import actions. Changes to the dimension tables are logged, so a normal roll-forward can be done from their most recent backup. The spend fact table, however, must be updated by reprocessing all the spend fact import actions since the most recent backup. This requires that the imported spend fact tables be backed up, which is recommended in any case.
To perform this alternative backup procedure for an enterprise, follow these high-level steps:
Restore the spend fact table to the most recent backup.
Restore the dimension tables to the most recent backup data.
Roll forward the logged changes to the dimension tables.
Recreate the indices for the dimension tables, if they were not included in the backup.
Recreate the indices for the spend fact tables, if they were not included in the backup.
Repeat each spend fact import action since the most recent backup, in the same order that they were originally performed.
To use Online Help Contents, Index, and Search, choose the Panel icon in the toolbar.Import and Export Tools.