Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Archive 6.4.4
  • All Products

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. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Oracle E-Business Suite Retirement Reports
  18. JD Edwards Enterprise Retirement Reports
  19. Oracle PeopleSoft Applications Retirement Reports
  20. Smart Partitioning
  21. Smart Partitioning Data Classifications
  22. Smart Partitioning Segmentation Policies
  23. Smart Partitioning Access Policies
  24. Language Settings
  25. Appendix A: Data Vault Datatype Conversion
  26. Appendix B: Special Characters in Data Vault
  27. Appendix C: SAP Application Retirement Supported HR Clusters
  28. Appendix D: Glossary

User Guide

User Guide

Back Next

Task 5. Change the Retention Policy for Specific Archived Records

Task 5. Change the Retention Policy for Specific Archived Records

The retirement archive job sets the expiration date for all records in the AUTO_POLICIES entity to five years after the insurance policy termination date. To implement the message and the bodily injury rules, you must change the retention policy for records that have messages or bodily injury payments.
  1. Select
    Data Discovery
    Manage Retention
    .
    The
    Manage Retention
     window appears.
  2. Click the
    Entities
     tab.
  3. Click
    Actions
     next to entity "AUTO_POLICIES."
    The
    Associate Retention Policy to Entity
     window appears.
  4. Click
    Modify Assigned Retention Policy
     next to retention policy "5-Year Policy."
    The
    Modify Assigned Retention Policy
     window appears. It displays the archive folder, existing retention policy, and entity name.
  5. To select records with messages, enter the following condition:
    MSG_ID Not Null
  6. In the
    New Retention Policy
     list, select new retention policy "5-Year Policy."
  7. In the
    Base Retention Period On
     area, click
    Add Row
     and add a row for each of the following columns:
    Entity Table
    Retention Column
    POLICY
    LAST_TRANS
    MESSAGES
    LAST_TRANS_DATE
    CLAIMS
    LAST_DATE
  8. In the
    Comments
     field, enter comments about the retention policy changes.
  9. To view the records affected by your changes, click
    View
    .
    A list of records that the retention policy changes affect appears. Data Archive lists the current expiration date for each record.
  10. To submit the changes, click
    Submit
    .
    The
    Schedule Job
     window appears.
  11. Schedule the Update Retention Policy job to run immediately.
  12. Click
    Schedule
    .
    Data Archive runs the Update Retention Policy job. For records with messages, it sets the expiration date to five years after the last transaction date across the POLICY, MESSAGES, and CLAIMS tables.
  13. Repeat steps 1 through 4 so that you can implement the bodily injury rule.
    The
    Modify Assigned Retention Policy
     window appears.
  14. To select records with bodily injury payments, click
    Add Row
     and add a row for each of the following conditions:
    • CLAIM_TYPE Equals 2 AND
    • CLAIM_AMT Greater Than 0
  15. In the
    New Retention Policy
     list, select new retention policy "10-Year Policy."
  16. In the
    Base Retention Period On
     area, click
    Add Row
     and add a row for each of the following columns:
    Entity Table
    Retention Column
    POLICY
    TERM_DATE
    CLAIMS
    RESOLVE_DATE
  17. Repeat steps 9 through 13 to update the expiration date for records with bodily injury payments.
    Data Archive sets the expiration date to 10 years after the policy termination date or the claim resolution date, whichever is greatest.
If a record has a message and a bodily injury payment, Data Archive sets the expiration date according to the bodily injury rule. It uses the bodily injury rule because you ran the Update Retention Policy job for this rule after you ran the Update Retention Policy job for the message rule.
0 COMMENTS
We’d like to hear from you!