Keep nVision, SQR, Crystal, PSQuery, and tree-based reporting working long after PeopleSoft is decommissioned. Trees and ChartFields preserved. SQL/REST/Parquet access. BI tool compatible. Auditor-grade evidence on demand.
The data has to keep working, the report definitions have to keep working, and the access paths have to keep working — for years.
Most migration programmes treat reporting as an afterthought: 'we'll figure out historical reporting after go-live'. That decision costs in two ways. First, the team that knows nVision, SQR, and PSQuery scatters to other projects within weeks of go-live; the institutional memory for legacy reports disappears. Second, the first time audit or finance asks for a comparative report against pre-migration data, the answer 'we'd need to spin up a PeopleSoft instance for that' creates an expensive scramble.
Syntra ETL solves PeopleSoft historical reporting properly at migration time. The archive preserves not just the transactional data, but the supporting metadata — trees, ChartField value sets, query definitions, report templates — so legacy reports keep returning the right numbers. The query interface mirrors the PeopleSoft schema, so analysts familiar with PS_LEDGER queries don't need to learn a new model. And modern BI tools (Tableau, Power BI, OTBI) connect through standard JDBC/ODBC so the post-migration reporting story is unified.
For ongoing operational reporting on Fusion-era data, the archive integrates with Fusion BI Publisher and OTBI so a single dashboard can show pre-migration PeopleSoft data alongside post-migration Fusion data — without copy-paste between systems.
Each pattern reflects a real auditor, finance, or HR query our customers receive years after PeopleSoft decommission.
Pull trial balance by ledger, business unit, period — with any ChartField filter applied. Sub-second response. Standard auditor request, served from archive without PeopleSoft instance.
PS_VOUCHER + PS_DISTRIB_LINE + PS_VENDOR joined and filtered by vendor, period range, payment status. The 'show me what we paid Acme Corp in FY23' request, answered in 2 seconds.
Effective-dated PS_JOB + PS_PERS_DATA_EFFDT chain returned per employee, full from-hire-to-current. Standard HR audit query for benefit eligibility, tenure verification, regulatory filings.
PS_PAY_CHECK + PS_PAY_EARNINGS + PS_PAY_DEDUCTION + PS_PAY_TAX assembled into the original payroll register PDF. Same format auditors saw in production.
Department hierarchy rolled up via PSTREENODE — 'show me all expense by Sales department including sub-departments'. Tree traversal handled natively.
Campus Solutions: PS_STDNT_ENRL + PS_ACAD_PROG + PS_STDNT_FA_TERM joined per student, with FERPA-grade access control. Standard registrar query for transcript reproduction.
Done right at migration time, historical reporting is a non-event for years afterward.
Crawl nVision macro library, SQR Process Scheduler catalog, Crystal Reports library, PSQuery definitions, BI Publisher templates. Classify each by business criticality and usage frequency. Output: a complete report inventory with retire/keep recommendations.
50–70% of legacy reports are duplicates, low-value, or already replaced by ad-hoc Excel work — retire outright. Critical reports get a preserve/rebuild plan.
For reports that need to keep running against historical data: extract data + metadata + report layouts to archive, set up SQL/REST query interface, validate report output matches PeopleSoft baseline to the penny.
For reports that need to keep running on go-forward Fusion data: rebuild in BI Publisher, OTBI, FRS, or Smart View. Validate against PeopleSoft baseline during parallel-run.
Analyst training on archive query interface, BI tool connection setup, pre-built auditor extracts. Documentation: 'how to answer the 25 most common historical reporting questions without a PeopleSoft instance'.
Auditors, finance, HR, and BI analysts all need different access patterns. The archive serves all of them.
Pre-built saved queries for GL detail, AP voucher detail, payroll register, asset register. SQL access for ad-hoc queries. Read-log on every query for evidence-of-access.
Tableau / Power BI / Cognos connectivity. Familiar PS_* schema mirrors PeopleSoft so existing analyst skill transfers. Comparatives across pre- and post-migration data unified.
Effective-dated employee history queries, payroll register regeneration, W-2/T4 PDF on demand. Sensitive fields masked by default with role-based unmask.
Campus Solutions queries with FERPA role partitioning. Transcript reproduction, financial aid history, billing detail — all preserved per institutional retention policy.
Standard regulator extract formats: IRS, state tax, HMRC, Inland Revenue, education department, healthcare. Signed, timestamped, deliverable on demand.
Thin portal facade for ex-employee historical W-2 / T4 retrieval. IdP-authenticated; common requirement to retain 5–10 years post-decommission.
PeopleSoft reporting is built on tightly coupled tools — nVision (Excel macros against PeopleSoft trees and queries), SQR (procedural SQL with embedded report layout), Crystal Reports (RDB-bound report files), PSQuery (metadata-driven query layer), and BI Publisher templates pointed at PeopleSoft datasources. None of these tools survive a Fusion migration intact: nVision macros break the moment the underlying ChartFields collapse to Fusion COA segments; SQR runs against the PeopleSoft Process Scheduler that no longer exists; Crystal Reports references PSPNLDEFN-style table names that aren't present in Fusion. PeopleSoft historical reporting after migration therefore requires either (a) keeping the old reports running against a frozen PeopleSoft snapshot, (b) rebuilding every critical report natively in Fusion BI Publisher and OTBI, or (c) routing historical data to a reporting archive that preserves the source data shape so the legacy reports can keep working. Syntra ETL supports all three patterns.
Yes — with caveats. nVision is Excel + a PeopleSoft client connector that reads PeopleSoft trees, queries, and tables directly. To keep nVision running post-decommission, you need the underlying PeopleSoft data structure preserved in queryable form, plus the nVision layout files. Syntra ETL's PeopleSoft archive preserves PS_LEDGER, PS_BU_LED_GRP_TBL, and the supporting tree and query metadata so a frozen nVision layout will still return the same numbers it did in production. For ongoing operational reporting on Fusion-era data, however, customers typically rebuild critical nVision reports in Fusion Smart View or Financial Reporting Studio — both better-supported than nVision in the Cloud era.
Operationally, 1–2 fiscal years is usually enough — long enough for year-end audit on the final pre-migration close and for prior-year comparatives in the first post-migration year. After that, ad-hoc requests are rare and can be served from the archive. For compliance retention, however, the data behind the reports must be retained 7+ years (SOX, IRS) or longer (HIPAA 6+, FERPA indefinite). Syntra ETL's approach: keep full nVision/SQR/Crystal report-runtime capability for 24 months post-migration, then transition to data-only retention in the cloud archive with on-demand report regeneration via BI Publisher templates.
PeopleSoft Trees (PSTREEDEFN, PSTREENODE, PSTREELEAF) are hierarchical structures that drive reporting rollups — department hierarchies, account hierarchies, organizational structure. These trees don't carry over to Fusion natively (Fusion uses account hierarchies and HCM organization trees, but with different model). Syntra ETL extracts the full tree structure as part of the archive, preserves it in a queryable form (parent-child table with effective dates), and exposes it through both SQL and a tree-traversal REST API. nVision reports, OBIEE reports, and ad-hoc auditor queries that depend on the tree hierarchy continue to work.
PSQuery definitions (stored in PSQRYDEFN, PSQRYRECORD, PSQRYFIELD, PSQRYCRITERIA) are extracted and preserved as part of the customization catalog. The query metadata is human-readable so an analyst can see exactly what each query did. For the queries that need to keep running post-migration, Syntra ETL provides a query-translation tool that converts PSQuery definitions into BI Publisher data models or OTBI subject area queries against Fusion data — preserving the business logic without requiring manual rebuild. Pure historical queries (against pre-migration archive data) continue to run against the archive directly via the SQL interface.
Yes. The Syntra archive preserves the full ChartField context on every PS_LEDGER and PS_JRNL_LN row — Account, Department, Fund, Program, Class, Project, Operating Unit, and every user-defined ChartField. Auditors can pull GL detail filtered by any ChartField combination, exactly as they did in PeopleSoft, with sub-second response. The archive also preserves the ChartField value tables (PS_DEPT_TBL, PS_GL_ACCOUNT_TBL, PS_PROJECT) and tree hierarchies, so descriptions and parent-child rollups are available for the entire retention window.
The archive exposes JDBC/ODBC for SQL access (Tableau, Power BI, Cognos, Looker), a REST API for programmatic access, and direct Parquet file access for warehouse engines (Snowflake external tables, BigQuery external tables, Athena, Spark, Trino). The underlying schema mirrors PeopleSoft so analysts familiar with PS_LEDGER, PS_JRNL_LN, PS_VOUCHER don't need to relearn anything. For Fusion-era reporting, BI Publisher and OTBI cover most needs; Syntra integrates with both so a single dashboard can show pre-migration PeopleSoft data and post-migration Fusion data side by side.
Yes. The Syntra archive preserves PS_PAY_CHECK, PS_PAY_EARNINGS, PS_PAY_DEDUCTION, PS_PAY_TAX, PS_W2_BOX, and PS_W2_AMOUNTS for the full IRS 7-year retention window (longer if your policy requires). Pre-built reports regenerate Payroll Register, Check Register, and individual W-2/T4 forms in PDF format on demand. For employee self-service access to historical W-2s (a common requirement post-decommission), the archive ships with a thin employee-portal facade that authenticates against your IdP and returns the requested historical tax forms.
30-minute call. Walk through your reporting inventory, retention requirements, and access patterns — leave with a concrete plan that handles year-7 audit as easily as year-1.