Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. SAP Application Retirement
  9. Creating Retirement Archive Projects
  10. Retention Management
  11. External Attachments
  12. Data Archive Restore
  13. Data Discovery Portal
  14. Data Visualization
  15. Oracle E-Business Suite Retirement Reports
  16. JD Edwards Enterprise Retirement Reports
  17. Oracle PeopleSoft Applications Retirement Reports
  18. Smart Partitioning
  19. Smart Partitioning Data Classifications
  20. Smart Partitioning Segmentation Policies
  21. Smart Partitioning Access Policies
  22. Language Settings
  23. Data Vault Datatype Conversion
  24. Special Characters in Data Vault
  25. SAP Application Retirement Supported HR Clusters
  26. Glossary

Retention Management Example

Retention Management Example

You can use Data Archive to enforce different retention rules for different records.
For example, a large insurance organization acquires a small automobile insurance organization. The small organization uses custom ERP applications to monitor policies and claims. The large organization requires that the small organization retire the custom applications and use its ERP applications instead. After acquisition, records managers use Data Archive to create retirement projects for the custom applications.
The large organization must retain records from the small organization according to the following rules:
  • By default, the organization must retain records for five years after the insurance policy termination date.
  • If messages exist against the insurance policy, the organization must retain records for five years after the most recent message date in the policy, messages, or claims table.
  • If the organization made a bodily injury payment, it must retain records for 10 years after the policy termination date or the claim resolution date, whichever is greatest.
  • If a record contains a message and a bodily injury payment, the organization must retain the record according to the bodily injury rule.
The small organization stores policy information in the following tables in the AUTO_POLICIES entity:
POLICY Table
Column
Description
POLICY_NO
Automobile insurance policy number (primary key column)
TERM_DATE
Policy termination date
LAST_TRANS
Date of last message for the policy
...
MESSAGES Table
Column
Description
MSG_ID
Message ID (primary key column)
POLICY_NO
Policy number related to the message (foreign key column)
LAST_TRANS_DATE
Message date
...
CLAIMS Table
Column
Description
CLAIM_NO
Claim number (primary key column)
POLICY_NO
Policy number related to the claim (foreign key column)
LAST_DATE
Date of last message for the claim
RESOLVE_DATE
Claim resolution date
CLAIM_TYPE
Claim type: property (1) or bodily injury (2)
CLAIM_AMT
Claim damage amount
...
As a retention administrator for the merged organization, you must create and apply these rules. To create and apply the retention management rules, you complete multiple tasks.

0 COMMENTS

We’d like to hear from you!