Data Archiving

You can safely move transactional data from the online transactional database. However, SAP recommends that you do not move customer data, since this information is required in the transactional online database to ensure referential integrity. Customer data should be small compared to the amount of transactional data in the system. When archiving data from the online database, the data is no longer visible through the user interfaces.

Note: When moving transactional data, be aware for foreign-key constraints.
Choose a repository and move all information associated to a transaction, including the audit, history, and traceable request data:
  • MOB_TXNS
  • MOB-SUB_TXNS.ID_TXN->MOB_TXNS.ID_TXN
  • MOB_TXN_ATTRIBUTES.ID_TXN->MOB_TXNS.ID_TXN
  • MOB_FEES.ID_SUB_TXN->MOB_SUB_TXNS.ID_SUB_TXN
  • MOB HISTORY (tracks changes to individual columns in the database)
  • MOB_AUDIT_LOGS (tracks each remote service call)
  • MOB_TRACEABLE_REQUESTS (stores 24 hours of data for nonrepudiation and response dehydration)
If the transaction is an invoice payment, you must also move the invoice information:
  • MOB_INVOICES
  • MOB_INV_TXNS.ID_TXN->MOB_TXNS.ID_TXN
  • MOB_INV_TXNS.ID_INVOICE->MOB_INVOICES.ID_INVOICE
  • MOB_INV_ATTRIBUTES.ID_INVOICE->MOB_INVOICES.ID_INVOICE
Parent topic: Data Archiving, Retention and Deletion