YENRA PEOPLESOFT-TO-EBS MIGRATION DISCOVERY
Guide: https://yenra.com/peoplesoft-oracle-e-business-suite-conversion/
Use to organize a specific proposal, not as executable migration steps.
Obtain current version, support and commercial terms for the actual project.
The historical 2003 statement does not establish a current free entitlement.

Project owner/reviewer/date:
Business problem and alternatives considered:
PeopleSoft application, PeopleTools versions and modules:
Oracle E-Business Suite target release and modules:
Entities/processes in scope:
Written support/licensing assumptions and evidence location:

DISCOVERY
Process owners and target demonstrations:
Customizations/reports: retain / replace / retire and reason:
Master data, open transactions and historical data scope:
Source read-only retention and approved access:
Integration owners, schedules and failure handling:
Roles/approval limits and allowed/denied tests:
Operations, recovery objectives and support ownership:

OBJECT MAPPING (repeat per object)
Source business key / target key / crosswalk:
Dependencies and load sequence:
Field mapping, transformations, dates, units and currencies:
Supported target interface, version and prerequisites:
Validation/rejection/retry behavior:
Representative target record and business-action checks:

TRIAL ACCEPTANCE
Source population and cutoff:
Expected unique keys, counts and grouped totals:
Accepted records and totals:
Rejected/unresolved records and totals:
Duplicate/missing-key checks:
Owner approving reconciliation and remaining exceptions:

Fictional single-currency example: 100 source invoices total 250000 units;
98 accepted total 247500; 2 rejected total 2500. Counts and amounts reconcile
but acceptance is still pending until the 2 exceptions are resolved.
Do not combine currencies without a defined conversion method.

CUTOVER REHEARSAL
Source freeze/final delta and transaction-entry rules:
Measured extraction/load/reconciliation durations:
Data/access/integration/operations acceptance evidence:
Go/no-go time and decision owner:
Communication and escalation route:
Recovery procedure, including transactions created in the target:
Rehearsal result and remaining gaps:

Decision and next action/owner/date:
Recheck scope, interfaces, supported versions and written terms after changes.