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

Confirming Retirement Run

Confirming Retirement Run

The last step in an Retirement project is to confirm a retirement run. Internally, during a retirement, data is not directly retired from data source to data target. Instead a staging schema and interim (temporary) tables are used to ensure that retirement data and associated table structures are sufficiently validated during the application retirement.
The following steps are involved in the process:
  1. Generate Candidates. Generates Interim tables based on Entities and constraints specified in the previous step.
  2. Validate Destination. Validates table structure and Data in the Target repository to generate DML for modifying Table structure and/or adding Rows of data.
  3. Copy to Destination. Copies data to Data Destination.
  4. Purge Staging. Deletes Interim tables from staging schema.
After the retirement project completes successfully, you cannot edit or re-run the project.

0 COMMENTS

We’d like to hear from you!