Tuesday, December 2, 2008

Stundent Admin - tables that can/cannot be purged!

Motive : Sharing something I found on Customer Connect - helped me while moving PeopleSoft Campus Solutions from Sql Server to Oracle.

PROBLEM:  Which tables can or cannot be purged in Campus Solution : Student Admin Module

Ultimately, the customer is responsible for their own data when archiving records, and unless the purge process is delivered, this is not  a supported function.  We do have information on some tables that we can share, however, as long as the customer realizes that testing and maintenance of this will not be supported.  Any table not appearing in this solution should be regarded as un-purgeable.

The following table, which is NOT all inclusive, outlines some of the tables which should never be purged without serious analysis and testing.  This table was compiled as a result of a direct request regarding these specific tables, and you should not take this to mean that these are the only tables that need to remain intact.

ITEM_SF
ITEM_LINE_SF
ITEM_XREF
ITEM_DUE_SF
ACCOUNT_SF
TUIT_CALC_TBL
FEE_CLASS_PRICE
BI_BILLING_LINE
STDNT_CAR_TERM
STDNT_ENRL  (except through the delivered process)
STDNT_SESSION

The following tables may be purged through delivered processes:

STDNT_ENRL - (Manage Student Records, Manage Academic Records, Process, Drop Purge) will purge all of the classes in a drop status from PS_STDNT_ENRL.  The process is documented in Peoplebooks.

PS_SA_REPORT_RSLT

The following tables can be purged as indicated:

PS_STDNT_CARTRM_PD after Consolidated Statistics has been run

BI_EMPLID_TEMP - After any billing run
BI_ACCT_TEMP - After any billing run
BI_ACCT_ITM_TMP - After any billing run
CREDIT_HISTORY of all but the most current effective dated rows for each student
ITEM_SF_GL_HIST - if the following table is purged
SF_ACCTG_LN - after journals are processed and data no longer needed for historical purposes

COMM_SCTN _DATA  in conjunction with the following table
COMM_SCTN_HDR. (see res 200732040)

PS_SF_ACCTG_LN_OLD after upgrade has been completed

No comments: