BUSINESS REQUIREMENTS

MAPPING
For: PA Dept Public Welfare
Optim Archiving
COMPASS Archiving Solution

Author:

Pritesh Shah

Creation Date:

February 19, 2008

Last Updated:

January 30, 2015

Version:

version 1.0

Business Requirements Mapping

Document Control
Change Record
4

Date

Author

Version

Change Reference

02/19/08
03/20/08

Pritesh Shah
Pritesh Shah

1.0
1.1

Initial draft
Changed based on input

Reviewers

Name

Position

Distribution

Copy No.

Name

Location

1
2
3
4

Library Master

Project Library

Note To Holders:
If you receive an electronic copy of this document and print it out, please write your
name on the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.

File Ref: 262334334.doc

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

Business Requirements Mapping

Contents

Document Control.......................................................................................... ii
Mapping Source - COMPASS...........................................................................4
Current Solution.......................................................................................4
Practices....................................................................................................... 4
Policies......................................................................................................... 4
Procedures.................................................................................................... 4

Mapping Solution......................................................................................4
Practices....................................................................................................... 4
Policies......................................................................................................... 5
Procedures.................................................................................................... 5
Tables used in COMPASS Archive.................................................................... 6
Selection criteria used for COMPASS Archive.....................................................8
Solution/Design............................................................................................. 8
User Access to Archive files............................................................................. 9

Open and Closed Issues................................................................................10

Open Issues........................................................................................... 10
Closed Issues......................................................................................... 10

File Ref: 262334334.doc

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

Mapping Source - COMPASS

PA Dept PW
Process: - Archiving

Business Area:

Control Number:

Mapping Team:

COMPASS

<Control Number>

PA Dept PW / IBM
H
<Priority (H,M,L)>

Librarian:

Priority (H, M, L):

<Librarian>

Source Type:
<module name> Production Data

Author:
Mac Doraiswamy and Julia Pavia, Deloite

Date:

02/19/08
Process Owner:

<Process Owner>
Core? (Y/N) N

<Core? (Y/N)>

Ref. Doc.:

BRS Reference #: 001

Current Solution

Practices
COMPASS does not currently maintain any archiving practices. All data that
COMPASS retains is maintained in the database. There is a purge process in place
for detailed application level data. This process is run through a nightly batch
process which removes specific application details from the database 180 days after
the application was submitted or closed. For more detailed information regarding the
purge process, please refer to the Information Lifecycle Management and Archival
Approach document.
Policies
COMPASS data sets are archived according to the time frames listed in the Archive
After column of the Information Lifecycle Management and Archival Approach
document. Retrieval time and purge time frames for archived data sets are also
specified in this document.
Procedures
The COMPASS process owner will arrange for scheduling of the COMPASS archives
by submitting a Database Service Request with the DPW Database Management
Section.

Mapping Solution
Practices
The proposed practice for Archiving COMPASS data are as follows:

File Ref: 262334334.doc

Archive COMPASS data as per given selection where T_APPLN is the

driving table.

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

COMAPSS data will be removed from the Production database to Archive

files, validated then deleted from the Production database.

Archive files will reside on \\pwishbgopt10\E:\Archive (SAN). They may later

be moved to another device, based on needs.

<define data to be retained> will be retained in Production database.

Policies
The proposed policies for Archiving COMPASS data are as follows:

Archive process is initiated by <Name of Access Definition>.

Archive data is validated by verifying record count before and after delete.

Archive is deleted from the Production database by <Delete Request

Name>.

Procedures
The proposed Procedures for archiving COMPASS data are as follows:

Optim Directory
Name of the Optim Directory: ILMREP
Development and SAT environments both are on same server
(pwishbgopt10).
ILMREP is created in Oracle Database and keeping in UTF8 format.its
shared directory which has dbalias for Oracle and SQL Server.

DBAlias
For Oracle: CMPD , which is in ACSII format.

Access Definition
For Oracle: COMPASS_DEVL (for Development)
COMPASS_SAT (For SAT)

Parameters to be used for Archive COMPASS

FROM_DATE: Date of Submission from
TO_DATE

: Date of Submission To

Validate Archive data

Delete Archive data for Production database

T_APPLN_INDIV is child of T_APPLN and T_INDIV.
T_APPLN_INDIV may have some new application with cde_staus_appln <>
6 with old individuals.While Deleteing we need to care for NOT to Deleting
such individuals with New application.i.e CDE_status_appln <> 6.

File Ref: 262334334.doc

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

STEPS:
1) Create table T_INDIV_PURGE as staging table.
2) Create T_APPLN_ARCH_HEADER and T_APPLN_ARCH_DETAIL to
strore ARCH_GUID and application number.
3) Call customized package
COMPASS_APP_PKG.PKG_ILM_ARC_PURGE.USP_ILM_PROCES
S_STAGING to insert record in T_INDIV_PURGE in Start of extract
process archive action phase.
4) T_INDIV_PURGE is truncated before inserting any records while running
new archive process.
5) Remove the Oracle RI between T_APPLN_INDIV and T_INDIV
6) Create PST relationship between T_APPLN_INDIV and
T_INDIV_PURGE
7) Create PST relationship between T_INDIV_PURGE and T_INDIV
Steps to improve delete Process performance:
1) Call customized package ilmrep.pkg_constraint.fk_constraint to
disable/enable RI constraints in Before Delete of first row from table
and After delete of last row from table. Its local archive action to
T_APPLN and T_INDIV table.
2) Select max connection in Delete tab of archive request so that delete
runs in multi thread. We need to disable the customized trigger to run
delete process in max connection parameter.
3) Call customized package
ilmrep.pkg_constraint.SCHEMA_TRIGGER in Start of Delete
Process and End of Delete Process to disable/enable the customized
triggers.

Tables used in COMPASS Archive

Start Table: T_APPLN
Archive Tables:
ILMAPPLREP.COMPASS.T_APPLN_PROFILE
ILMAPPLREP.COMPASS. T_APPLN_SERV
ILMAPPLREP.COMPASS. T_APPLN_SCRNG_FU
ILMAPPLREP.COMPASS. T_APPLN_PREV_HH_INFO
ILMAPPLREP.COMPASS. T_APPLN_OTHER_HH_EXP
ILMAPPLREP.COMPASS. T_APPLN_SCRNG_FU_INDIV
ILMAPPLREP.COMPASS.T_APPLN_INDIV
ILMAPPLREP.COMPASS.T_INDIV_PURGE
File Ref: 262334334.doc

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

ILMAPPLREP.COMPASS.T_INDIV
ILMAPPLREP.COMPASS.T_INDIV_PROFILE
ILMAPPLREP.COMPASS.T_INDIV_HIST
ILMAPPLREP.COMPASS.T_APPLN_HIST
ILMAPPLREP.COMPASS.T_APPLN_ESGNR_VERIF_HIST
ILMAPPLREP.COMPASS.T_APPLN_SSERV_RTG_STATUS_HIST
ILMAPPLREP.COMPASS.T_APPLN_INDIV_HIST
ILMAPPLREP.COMPASS.T_APPLN_STATUS_HIST
ILMAPPLREP.COMPASS.T_APPLN_ESGNR_VERIF
ILMAPPLREP.COMPASS.T_APPLN_SSERV_RTG_STATUS
ILMAPPLREP.COMPASS.T_APPLN_CPV
ILMAPPLREP.COMPASS.T_APPLN_INTFC_STATUS
ILMAPPLREP.COMPASS.T_REFL_APPLN
ILMAPPLREP.COMPASS.T_APPLN_XML
ILMAPPLREP.COMPASS.T_APPLN_VEH_INS
ILMAPPLREP.COMPASS.T_APPLN_VEH
ILMAPPLREP.COMPASS.T_APPLN_UTIL_COMPY
ILMAPPLREP.COMPASS.T_APPLN_SURVEY
ILMAPPLREP.COMPASS.T_APPLN_SOLD_PROP
ILMAPPLREP.COMPASS.T_APPLN_SHARED_EXP
ILMAPPLREP.COMPASS.T_APPLN_RESRC
ILMAPPLREP.COMPASS.T_APPLN_REAL_PROP
ILMAPPLREP.COMPASS.T_APPLN_PW_DRIVER
ILMAPPLREP.COMPASS.T_APPLN_OTHER_PROG
ILMAPPLREP.COMPASS.T_APPLN_NSLP_RTG_STATUS
ILMAPPLREP.COMPASS.T_APPLN_MBLHM
ILMAPPLREP.COMPASS.T_APPLN_MAIL_ADR
ILMAPPLREP.COMPASS.T_APPLN_LIFE_INS_POLICY
ILMAPPLREP.COMPASS.T_APPLN_HH_EXP_PAID_OTSD
ILMAPPLREP.COMPASS.T_APPLN_HEALTH_PROVIDER
ILMAPPLREP.COMPASS.T_APPLN_HEALTH_INS
ILMAPPLREP.COMPASS.T_APPLN_HEALTH_CARE_LEARN
ILMAPPLREP.COMPASS.T_APPLN_FS_REP
ILMAPPLREP.COMPASS.T_APPLN_EXPTD_RESRC
ILMAPPLREP.COMPASS.T_APPLN_ESGNR
ILMAPPLREP.COMPASS.T_APPLN_CS_EXP
ILMAPPLREP.COMPASS.T_APPLN_CLOSED_DPLT_ACCT
ILMAPPLREP.COMPASS.T_APPLN_CC_EXP
ILMAPPLREP.COMPASS.T_APPLN_BURIAL_PROP
ILMAPPLREP.COMPASS.T_APPLN_BURIAL_AGRMT
ILMAPPLREP.COMPASS.T_APPLN_APAR
ILMAPPLREP.COMPASS.T_MOTOR_VEH_OWNER
ILMAPPLREP.COMPASS.T_RESRC_OWNER
ILMAPPLREP.COMPASS.T_REFL_INDIV
ILMAPPLREP.COMPASS.T_PROP_OWNER
ILMAPPLREP.COMPASS.T_MBLHM_OWNER
ILMAPPLREP.COMPASS.T_LIFE_INS_POLICY_OWNER
ILMAPPLREP.COMPASS.T_INDIV_TRNG
ILMAPPLREP.COMPASS.T_INDIV_TRANSP_EXP
ILMAPPLREP.COMPASS.T_INDIV_STEP_PARENT_CHILD_REL
ILMAPPLREP.COMPASS.T_INDIV_SSI
ILMAPPLREP.COMPASS.T_INDIV_SERV
ILMAPPLREP.COMPASS.T_INDIV_SCRNG_RESULT
ILMAPPLREP.COMPASS.T_INDIV_SCHOOL_INFO
ILMAPPLREP.COMPASS.T_INDIV_RLTV_VET
ILMAPPLREP.COMPASS.T_INDIV_REL
ILMAPPLREP.COMPASS.T_INDIV_PRGNT
ILMAPPLREP.COMPASS.T_INDIV_PNDG_BNFT
File Ref: 262334334.doc

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

ILMAPPLREP.COMPASS.T_INDIV_OTHER_TYPE_INCOME
ILMAPPLREP.COMPASS.T_INDIV_OPT_DMGRPHCS
ILMAPPLREP.COMPASS.T_INDIV_NON_CIT
ILMAPPLREP.COMPASS.T_INDIV_IDNTY_VERIF
ILMAPPLREP.COMPASS.T_INDIV_EMPLMT_INCOME
ILMAPPLREP.COMPASS.T_INDIV_EMPLMT_HEALTH_INS
ILMAPPLREP.COMPASS.T_INDIV_DSBLTY
ILMAPPLREP.COMPASS.T_INDIV_CNTC
ILMAPPLREP.COMPASS.T_INDIV_CITSHP_VERIF
ILMAPPLREP.COMPASS.T_INDIV_CHECKS_SENT
ILMAPPLREP.COMPASS.T_INDIV_CC_EXP
ILMAPPLREP.COMPASS.T_HH_MEMBR_CVRD_LIFE_INS_POL
ILMAPPLREP.COMPASS.T_BURIAL_PLOT_OWNER
ILMAPPLREP.COMPASS.T_BURIAL_AGRMNT_OWNER
ILMAPPLREP.COMPASS.T_NSLP_SCHOOL
ILMAPPLREP.COMPASS.T_INDIV_CNTC_ROLE
ILMAPPLREP.COMPASS.T_REAL_PROP_RETURN
ILMAPPLREP.COMPASS.T_APPLN_TYPE_PROFL
ILMAPPLREP.COMPASS.T_APPLN_INTFC_STATUS_HIST
ILMAPPLREP.COMPASS.T_APPLN_INDIV_HEALTH_CVGE
ILMAPPLREP.COMPASS.T_APPLN_HEALTH_INS_TYPE
ILMAPPLREP.COMPASS.T_APPLN_HEALTH_INS_BNFT
ILMAPPLREP.COMPASS.T_CLOSED_DPLT_ACCT_OWNER
ILMAPPLREP.COMPASS.T_APPLN_INDIV_APAR
ILMAPPLREP.COMPASS.T_APPLN_AREL_RACE
ILMAPPLREP.COMPASS.T_APPLN_AREL_PROP
ILMAPPLREP.COMPASS.T_APPLN_NSLP_RTG_STATUS_HIST
ILMAPPLREP.COMPASS.T_APPLN_SERV_HIST
ILMAPPLREP.COMPASS.T_INDIV_SERV_HIST
ILMAPPLREP.COMPASS.T_TRANS_AUDIT_HIST
REFERENCE TABLES:
ILMAPPLREP.COMPASS_FRAME.T_RE_TABLE_VALUE
ILMAPPLREP.COMPASS_FRAME.T_RE_TABLE
ILMAPPLREP.COMPASS_FRAME.T_ADDNL_RE_TABLE_VALUE
ILMAPPLREP.COMPASS_FRAME.T_ADDNL_RE_TABLE_ATTRIB

Selection criteria used for COMPASS Archive

Select * from t_appln where cde_status_appln='6' and DTE_SUBMIT_APPLN
between to_date(:FROM_DATE,'yyyymmddhh24miss') and
to_date(:TO_DATE,'yyyymmddhh24miss')

Solution/Design
The COMPASS Archive solution is as follows:

Use an Optim Access Definition COMPASS_UAT to establish the tables

from which data is to be archived, the table relationships and the selection
criteria. This was based on the above tables selected by the client.

The current solution involves running the Archive, and Delete Requests from
Optim:
o

File Ref: 262334334.doc

Archive <archive request name> is specified and Archive run is

initiated

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

Archive data is Validated

Archive data is deleted from the Production database

User Access to Archive files

The COMPASS Archive files will be accessed as follows:

File Ref: 262334334.doc

Create datasource ILMREP on ODM server which is pointing to Arvhive file

collection.
ArchiveCollection name is ILMREP.COMPASSCOL

Company Confidential - For internal use only

Open and Closed Issues

10 of 6

Open and Closed Issues

Open Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

Resolution

Responsibility

Target Date

Impact Date

Closed Issues

ID

Issue

File Ref: 262334334.doc

Company Confidential - For internal use only

Open and Closed Issues

10 of 6