Preface
Introduction
- Data Archive Overview
  - Features
  - Benefits
- Data Archive Use Cases
Accessing Data Archive
- Data Archive URL
- Log In and Out of Data Archive
- Update User Profile
Working with Data Archive
- Data Archive Editions
- Organization of Menus
- Predefined List of Values (LOVs)
- Online Help
Scheduling Jobs
- Scheduling Jobs Overview
- Standalone Jobs
- Scheduling Jobs
- Job Logs
  - Delete From Source Step Log
- Monitoring Jobs
- Pausing Jobs
  - Delete From Source Step
- Searching Jobs
  - Quick Search
  - Advanced Search
- Troubleshooting Jobs
Viewing the Dashboard
- Viewing the Dashboard Overview
- Scheduling a Job for DGA_DATA_COLLECTION
Creating Data Archive Projects
- Setting Up Data Archive Projects
- Viewing and Editing Data Archive Projects
- Running the Data Vault Loader Job
  - Run the Data Vault Loader Job
  - Troubleshooting Data Vault Loader
- Troubleshooting Data Archive Projects
Salesforce Archiving
- Salesforce Archiving Overview
  - Salesforce Archiving Process
- Step 1. Install the Salesforce Accelerator
- Step 2. Configure Salesforce Permissions
- Step 3. Import Salesforce Metadata and Configure Entities
- Step 4. Create a Salesforce Source Connection
- Step 5. Create the Salesforce Archive Project
- Refresh Schema for Salesforce Standalone Job
- Salesforce Limitations
SAP Application Retirement
- SAP Application Retirement Overview
- SAP Application Retirement Process
- SAP Smart Retirement
  - Running the SAP Smart Retirement Standalone Job
- Retirement Job
- Attachment Retirement
  - Attachment Storage
  - Attachment Viewing
- Data Visualization Reports
- Troubleshooting SAP Application Retirement
  - Message Format
  - Frequently Asked Questions
Creating Retirement Archive Projects
- Creating Retirement Archive Projects Overview
- Identifying Retirement Application
- Defining a Source Connection
- Defining a Target Repository
  - Adding Entities
  - Defining Retention and Access
  - Review and Approve
  - Confirming Retirement Run
  - Copying a Retirement Project
- Application Migration
- Application Migration Process
- Source (Pre-Production) Environment Tasks
  - Step 1. Add the Migration Administrator Role
  - Step 2. Run the Export Informatica Data Vault Metadata Job
  - Step 3. Create a Target Connection
  - Step 4. Run the Migrate Data Archive Metadata Job
- Target (Production) Environment Tasks
  - Prerequisites
  - Step 1. Add the Migration Administrator Role
  - Step 2. Update the Data Vault Connection
  - Step 3. Move the .Tar and SCT Data Files
  - Step 4. Update the ssa.ini File
  - Step 5. Run the Import Informatica Data Vault Metadata Job
  - Step 6. Recreate Indexes
- Report Migration
- Migrating Published Resources
- Step 1. Download the Reports and Catalog from the Source
- Step 2. Edit the Catalog Connection Details
- Step 3. Edit the Catalog Table Section
- Step 4. Edit the Schema Name in Imported SQLs
- Step 5. Rename the Existing Catalog
- Step 6. Create a Report Folder and Publish
- Step 7. Run a Migrated Report from Data Archive
- Migrating Real Path Resources
- Step 1. Download the Reports and Catalog
- Step 2. Edit the Catalog Connection Details
- Step 3. Create a Report Folder and Publish
- Step 4. Create a Report Folder in the Target File System
- Step 5. Copy the Reports and Catalog from the Source to Target Systems
- Step 6. Map the Folder to the Target File System
- Step 7. Select the Migrated Target Connection in the Patient Archives
- Troubleshooting Retirement Archive Projects
Integrated Validation for Archive and Retirement Projects
- Integrated Validation Overview
- Integrated Validation Process
- Row Checksum
- Column Checksum
- Validation Review
  - Validation Review User Interface
  - Validation Report Elements
- Enabling Integrated Validation for a Retirement Project
- Enabling Integrated Validation for an Archive Project
- Reviewing the Validation
- Running the Validation Report
- Integrated Validation Standalone Job
  - Running the Integrated Validation Standalone Job
Retention Management
- Retention Management Overview
- Retention Management Process
- Retention Management Example
- Retention Policies
- Retention Policy Changes
- Purge Expired Records Job
  - Purge Expired Records Job Parameters
  - Running the Purge Expired Records Job
- Retention Management Reports
- Retention Management when Archiving to EMC Centera
External Attachments
- External Attachments Overview
- Archive External Attachments to a Database
- Archive or Retire External Attachments to the Data Vault
Data Archive Restore
- Data Archive Restore Overview
- Restore Methods
- Data Vault Restore
- Data Vault Restore to an Empty Database or Database Archive
  - Restoring to an Empty Database or Database Archive
- Data Vault Restore to an Existing Production Database
- Database Archive Restore
- External Attachments Restore
  - External Attachments from the Data Vault
  - External Attachments from a Database Archive
Data Discovery Portal
- Data Discovery Portal Overview
- Search Data Vault
  - Examples of Search Queries
  - Searching Across Applications in Data Vault
- Search Within an Entity in Data Vault
- Browse Data
- Legal Hold
- Tags
- Troubleshooting the Data Discovery Portal
Data Visualization
- Data Visualization Overview
- Data Visualization User Interface
- Data Visualization Process
- Report Creation
- Report Permissions
- Assigning a User or Access Role to a Report
- Editing Report Permissions for a User or Access Role
- Deleting a User or Access Role From a Report
- Assigning Permissions for Multiple Reports
- Deleting Permissions for Multiple Reports
- Running and Exporting a Report
- Deleting a Report
- Copying Reports
  - Copying SAP Application Retirement Reports
- Troubleshooting
- Designer Application
Data Privacy
- Data Privacy Overview
- Data Privacy Process
- Column Indexing for Data Privacy Searches
  - Indexing Columns for Search
  - Indexing a Large Number of Columns for Search
- Data Privacy User and Access Roles
- Searching with Data Privacy
  - Supported Search Operators
- Using Data Privacy Purge
  - Scheduling the Purge Job Immediately
  - Adding the Purge Job to a Batch
- Using Data Privacy Export
  - Scheduling the Export Job Immediately
  - Adding the Export Job to a Batch
- Using Data Privacy Export and Purge
  - Scheduling the Export and Purge Job Immediately
  - Adding the Export and Purge Job to a Batch
- Manage Data Privacy
- Data Privacy Audit Logs
- Parallel Jobs
- Data Privacy FAQ
Oracle E-Business Suite Retirement Reports
- Retirement Reports Overview
- Prerequisites
- Accounts Receivable Reports
- Accounts Payable Reports
- Purchasing Reports
  - Purchase Order Details Report
    - Report Parameters
    - Report Tables and Views
- General Ledger Reports
  - Chart of Accounts - Detail Listing Report
    - Report Parameters
    - Report Tables and Views
  - Journal Batch Summary Report
    - Report Parameters
    - Report Tables and Views
- Saving the Reports to the Archive Folder
- Running a Report
JD Edwards Enterprise Retirement Reports
- Retirement Reports Overview
- Prerequisites
- Accounts Payable Reports
- Procurement Management Reports
- General Accounting Reports
- Accounts Receivable Reports
- Sales Order Management Reports
- Inventory Reports
  - Item Master Directory Report
    - Report Parameters
    - Report Tables
- Address Book Reports
  - One Line Per Address Report
    - Report Parameters
    - Report Tables
- Saving the Reports to the Archive Folder
- Running a Report
Oracle PeopleSoft Applications Retirement Reports
- Retirement Reports Overview
- Prerequisites
- Accounts Payable Reports
- Purchase Order Reports
- Accounts Receivable Reports
- General Ledger Reports
- Saving the Reports to the Archive Folder
- Running a Report
Language Settings
- Language Settings Overview
- Changing Browser Language Settings
Appendix A: Data Vault Datatype Conversion
- Data Vault Datatype Conversion Overview
- Data Vault
- Datatype Conversion Errors
  - Converting Datatypes for Unsupported Datatype Errors
  - Converting Datatypes for Conversion Errors
Appendix B: Special Characters in Data Vault
- Special Characters in Data Vault
  - Supported Special Characters
Appendix C: SAP Application Retirement Supported HR Clusters
- SAP Application Retirement Supported HR Clusters Overview
- PCL1 Cluster IDs
- PCL2 Cluster IDs
- PCL3 Cluster IDs
- PCL4 Cluster IDs
- PCL5 Cluster IDs
Appendix D: Glossary
- access policy
- administrator
- application
- application module
- application version
- archive
- archive action
- archive (Database)
- archive definition
- archive engine
- archive (File)
- archive project
- business rule
- business table
- column level retention
- custom object
- dashboard
- Data Archive
- Data Archive metadata
- data classification
- data destination
- Data Model Metadata
- Data Privacy
- data source
- Data Subset
- data target
- Data Vault access role
- de-referencing
- entity
- ERP application
- expiration date
- expression-based retention
- formula
- general retention
- history database
- home database
- interim
- job
- metadata
- production database
- restore (Cycle)
- restore (Full)
- restore (Transaction)
- retention management
- retention policy
- security group
- staging schema
- standard object
- system-defined role
- system profile
- transaction data
- translation column
- user
- user profile

User Guide

6.5.1
- 6.5 HotFix 1
- 6.5
- 6.4.4
- 6.4.3 HotFix 1
- 6.4.3

Back Next

Retirement Job

The retirement job uses a combination of methods to access data from SAP applications. The job accesses data directly from the SAP database for normal physical tables. The job uses the SAP Java Connector to log in to the SAP application to access data in transparent HR and STXL tables, ADK files, and attachments.

When you run a retirement job, the job uses the source connection configured in the retirement project to connect to the source database and to log in to the SAP system. The job extracts data for the following objects:

Physical Tables: Physical tables store data in a readable format from the database layer. The retirement job extracts data directly from the database and creates BCP files. The job does not log in to the SAP application.
Transparent HR and STXL tables: Transparent HR PCL1-PCL5 and STXL tables store data that is only readable in the SAP application layer. The retirement job logs in to the SAP system. The job cannot read the data from the database because the data is encoded in an SAP format.

The job uses the source connection properties to connect to and log in to the SAP application. The job uses an ABAP import command to read the SAP encoded data. The job transforms the SAP encoded data into XML format and creates BCP files. The XML transformation is required to read the data after the data is retired. The XML transforms occurs during the data extraction.
ADK Files: ADK files store archived SAP data. The data is only readable in the SAP application layer. The retirement job uses the source connection properties to connect to and log in to the SAP application. The job calls a function module from the Archive Development Kit. The function module reads and extracts the archived ADK data and moves the data to the BCP staging area as compressed BCP files.
Attachments: Attachments store data that is only readable in the SAP application layer. The retirement job uses the SAP Java Connector to log in to the SAP application and to call a function module. The function module reads, decodes, and extracts the attachments that are stored in the database. The job moves the attachments to the attachment staging area that you specify in the source connection. Depending on your configuration, the job may also move attachments that are stored in an external file system.

When the retirement job creates BCP files, the job compresses and moves the files to a BCP staging area. For physical tables, the job stores the BCP files in the staging directory that is configured in the Data Vault target connection. For transparent HR and STXL tables, ADK files, and attachments, the job uses an SAP function module to generate the BCP files. The SAP function module stores the BCP files in the staging directory that is configured in the source connection.

The job uses the BCP file separator properties in the

conf.properties

file to determine the row and column separators. The job uses the Data Vault target connection to determine the maximum amount of rows that the job inserts into the BCP files. After the job creates the BCP files, the Data Vault Loader moves the files from the BCP staging area to the Data Vault.

Rename Saved Search

Table of Contents

User Guide

User Guide

Retirement Job

Retirement Job