Pre-built peoplesoft to oracle fusion data mapping for every production PS_ table. ChartField → COA segment, SetID → BU/Set, PeopleCode → Application Composer + AMX + OIC. Crosswalk store signed off by finance, HR, audit before any load runs.
The hard part isn't moving rows. It's translating two enterprise data models that evolved independently and never converge cleanly. ChartFields, SetIDs, PeopleCode and effective-dated history have no clean Fusion equivalent.
PeopleSoft 9.2 carries decades of customer-specific customization buried in ChartField design, SetID partitioning, PeopleCode events, App Engine jobs and Integration Broker service operations. Two PeopleSoft installations of the same module rarely look alike in the PS_ tables. The same Account values mean different things across SetIDs. The same Department codes carry different cost-center semantics across Business Units. Customer-specific PeopleCode events drive default values that never appear in the table schema.
Every peoplesoft to oracle fusion data mapping decision has to translate not just the value but the semantics — and the wrong choice produces a successful load that breaks downstream reporting six months later. Hand-built mapping spreadsheets and one-off SQR-to-FBDI conversions can do it, but every PS_ table becomes a multi-week negotiation between functional, technical, finance and compliance teams. Syntra ETL replaces that with a pre-built crosswalk store refined across dozens of PeopleSoft conversions.
The mapping engine handles three deployment scenarios: full PeopleSoft replacement where every PS_ table maps to a Fusion target, single-pillar migration where Finance maps to Fusion while HCM stays on PeopleSoft (with Integration Broker keeping them in sync), and Campus Solutions co-existence where Student Financials maps to Fusion AR while academic records remain in PeopleSoft.
What the Syntra mapping engine ships pre-built. No more multi-month bespoke mapping spreadsheet development.
PSTREEDEFN, PSTREESELECT06, PSTREELEAF walked to extract every active tree. Materiality analysis against nVision reports run in last 24 months. Proposed Fusion COA shape with full audit trail.
Every PeopleSoft SetID inventoried with its share scope (vendor, customer, asset, item). Re-modeled as Fusion BU assignments plus Set ID assignments on master entities. Routing preserved in DFF for audit.
200+ XLAT (translate) values per common PS field with customer-specific extensions, translated to Fusion Common Lookups with sample values shown. Conflicts surfaced for sign-off — not silently swallowed.
EFFDT/EFFSEQ history from PS_JOB, PS_POSITION_DATA, PS_PERSON converted to HDL HISTORY_DATA segments. Date-effective workflow preserved for Fusion HCM. Original audit columns preserved as DFFs.
Active PSPCMPROG objects classified by business purpose. Per-object Fusion replacement plan: Application Composer rule for validations, AMX for approvals, OIC for integration triggers, FBDI default for derivations.
Mapping versioned per PeopleSoft PUM + Fusion 26x release pair. Regression-tested against shipped sample data. Active projects pin to a version for stability and upgrade on their schedule.
A repeatable workflow that produces a signed crosswalk store before any load runs. Typical timeline: 3–5 weeks alongside discovery and design.
PSDBFIELD/PSRECDEFN/PSRECFIELD catalog walked. Every active PS_ table identified. Customization layer (PS_ table extensions, custom views, custom Component Interfaces) inventoried. Effective-dated history depth measured per master table.
PSTREEDEFN/SELECT06/LEAF analysis produces ChartField materiality report. nVision/SQR usage analysis identifies which ChartFields drive reporting splits. SetID share scope inventoried for vendor, customer, asset, item master.
Fusion target COA shape proposed (typically 6-segment: Company + Cost Center + Account + Sub-Account + Product + Future, customer-specific). Fusion Business Unit structure proposed. Required vs optional ChartField routing decided.
Pre-built crosswalks loaded for standard PS_ tables (PS_LEDGER, PS_JRNL, PS_VOUCHER, PS_VENDOR, PS_EMPLOYEES, PS_JOB). Customer-specific overrides applied. XLAT-to-Lookup translation populated. Effective-dated handling decisions captured.
Finance leads sign off GL/AP/AR mappings. HR leads sign off HCM mappings. Compliance leads sign off retention and audit mappings. Crosswalk store frozen with version tag. Becomes the single source of truth for all subsequent loads.
Regression testing against shipped sample data per PeopleSoft PUM and Fusion 26x release. Delta updates published with backwards-compatible versioning. Active projects pin to a version for stability.
What the mapping looks like for the most common PS_ tables. Customer-specific overrides apply in the actual crosswalk store.
BUSINESS_UNIT → Ledger + BU. LEDGER → Ledger Name. FISCAL_YEAR + ACCOUNTING_PERIOD → Period Name. ACCOUNT + DEPTID + FUND_CODE + PROGRAM_CODE + CLASS_FLD + PROJECT_ID → COA segment combination. POSTED_TOTAL_AMT → Period Activity. Loaded via FBDI GL Balance Import.
JOURNAL_ID + JOURNAL_DATE + LINE_NUM → Journal Header + Line. Same ChartField crosswalk as PS_LEDGER. MONETARY_AMOUNT → Entered Amount. CURRENCY_CD → Currency. RATE_MULT → Conversion Rate. Loaded via FBDI Journal Import. Original PS journal_id preserved as Source Reference.
VOUCHER_ID + BUSINESS_UNIT → Invoice Number + BU. VENDOR_ID + SETID → Supplier Number (via SetID re-model). INVOICE_DT → Invoice Date. GROSS_AMT + MERCHANDISE_AMT + SALETX_AMT → Header amounts. Voucher distribution lines from PS_VCHR_DST → Invoice Distribution. Loaded via FBDI Payables Invoice Import.
VENDOR_ID + SETID → Supplier Number with Supplier Set assignment. NAME1 + NAME2 → Supplier Name + Alternate. PS_VNDR_LOC rows → Supplier Sites per Procurement BU. PS_VNDR_ADDR rows → Supplier Addresses. PS_VNDR_BANK_ACCT → Bank Account assignments. Loaded via FBDI Supplier Import.
EMPLID → Person Number. PS_NAMES (current EFFDT) → PersonName. PS_ADDRESSES (current EFFDT) → PersonAddress. PS_PERSONAL_DATA → PersonNationalIdentifier + PersonEthnicity. PS_EMPLOYEES → Worker top-level. Loaded via HDL Worker.dat.
EMPLID + EMPL_RCD → Worker + Assignment. EFFDT + EFFSEQ → date-effective HISTORY_DATA segments. JOBCODE → Job. POSITION_NBR → Position. DEPTID → Department. LOCATION → Location. SAL_ADMIN_PLAN + GRADE → Grade. Loaded via HDL Assignment.dat with full effective-dated history.
PeopleSoft to oracle fusion data mapping is the field-level translation layer between PeopleSoft 9.2's PS_ tables and Oracle Fusion Cloud entities. Every PeopleSoft source column has to land somewhere in Fusion: PS_LEDGER.POSTED_TOTAL_AMT → Fusion GL Period Balance, PS_JRNL_LN.ACCOUNT + DEPTID + FUND_CODE → Fusion COA segment combination, PS_VOUCHER.VENDOR_ID + SETID → Fusion Supplier Number, PS_EMPLOYEES.EMPLID → Fusion Worker Person Number, PS_JOB.JOBCODE → Fusion Job. Syntra ETL's mapping engine ships a pre-built crosswalk for every production PS_ table with the most common Fusion target — refined across dozens of conversions — plus a governance UI for the inevitable customer-specific exceptions. Output is a signed crosswalk store consumed by the load engine and re-used for delta-replay during parallel run.
Because PeopleSoft's data model and Fusion's data model evolved independently and never converge cleanly. PeopleSoft uses ChartFields (Account + Department + Fund + Program + Class + Project + up to 7 more), partitioned by SetID; Fusion uses a 6-segment Chart of Accounts partitioned by Business Unit. PeopleSoft has 200+ XLAT (translate) values per common field with customer-specific extensions; Fusion uses Common Lookups with different code structures. PeopleSoft worker history is effective-dated with EFFDT/EFFSEQ; Fusion uses HDL HISTORY_DATA segments with date-effective workflow. Every peoplesoft to oracle fusion data mapping decision has to translate not just the value but the semantics — and the wrong choice produces a successful load that breaks downstream reporting.
ChartField to COA segment mapping is the heart of any peoplesoft to oracle fusion data mapping exercise. Syntra ETL's ChartField analyzer walks PSTREEDEFN, PSTREESELECT06 and PSTREELEAF to extract every active PeopleSoft tree, then runs a materiality analysis: which ChartFields drive reporting splits in nVision reports actually run in the last 24 months. The output proposes a target Fusion COA shape — typically Company + Cost Center + Account + Sub-Account + Product + Future, but customer-specific. Required ChartFields collapse into Fusion COA segments. Optional ChartFields route to Fusion segment qualifiers or descriptive flexfields (DFFs). Reporting-only ChartFields move to OTBI dimensions or to the long-term PeopleSoft archive. Every decision is captured in the crosswalk store with sign-off from finance, audit and reporting leads.
Worker-to-Worker mapping is straightforward at the high level but full of detail. PS_EMPLOYEES + PS_PERSON + PS_NAMES + PS_ADDRESSES + PS_PERSONAL_DATA → HDL Worker.dat with PersonName, PersonAddress, PersonNationalIdentifier, PersonEthnicity, PersonReligion segments. PS_JOB effective-dated history → HDL Assignment.dat with date-effective HISTORY_DATA segments. PS_POSITION_DATA → HDL Position.dat with cost-allocation and assignment-restriction segments. PS_DEPT_TBL → Fusion Department setup. PS_LOCATION_TBL → Fusion Location. PS_JOBCODE_TBL → Fusion Job. PS_SAL_GRADE_TBL → Fusion Salary Range. Plus PS_PAY_CHECK + PS_PAY_EARNINGS → HDL Element Entry for current FY payroll history; older payroll routes to long-term archive per IRS 4–7 year retention.
PeopleSoft SetIDs are the data-sharing partitions that govern which set of supplier, customer, asset or item master records each Business Unit sees. They have no direct Fusion equivalent — Fusion uses Business Unit boundaries plus Set ID assignments on specific master entities. Syntra ETL's peoplesoft to oracle fusion data mapping re-models SetIDs as a combination of: Fusion Business Unit assignments for vouchers, journals and transactions; Fusion Supplier Site Set assignments for PS_VENDOR sharing; Fusion Customer Account Set assignments for PS_CUSTOMER sharing; Fusion Asset Book assignments for PS_ASSET sharing. Each PS_ row gets routed to the correct Fusion target by SetID context, with the original SetID preserved in a DFF for audit traceability and downstream reconciliation.
PeopleCode SaveEdit, FieldChange and FieldDefault events drive a surprising amount of business logic — derivation rules that fill in cost centers from department codes, validation rules that block postings to suspended accounts, integration triggers that push to Integration Broker on save. None of that PeopleCode runs in Fusion. Syntra ETL's peoplesoft to oracle fusion data mapping inventories every active PeopleCode object using the PSPCMPROG catalog, classifies each by business purpose, and produces a Fusion-equivalent recommendation: native Fusion default-value rules (FBDI default-value processing or Application Composer rules) for derivations, Fusion AMX rules for approvals, OIC integration flows for outbound triggers. The mapping output includes which Fusion construct replaces which PeopleCode object — so nothing silently goes missing.
Yes — the crosswalk store is the single source of truth and every entry is reviewable, overridable and signed off before any FBDI or HDL load runs. The mapping UI shows source PS_ table column, sample source values, proposed Fusion target field, transformation rule (passthrough, XLAT lookup, ChartField crosswalk, derivation, etc.) and current sign-off status. Finance leads review GL/AP/AR mappings; HR leads review HCM mappings; compliance leads review retention and audit mappings. Overrides are versioned with timestamp and user. Once signed off, the same crosswalk drives every load — bulk migration, delta-replay during parallel run, post-cutover incremental — with byte-identical results.
PeopleTools 8.6x continues to ship quarterly PUM updates that occasionally introduce new PS_ table columns or alter existing semantics. Oracle Fusion ships quarterly 26x releases that occasionally add new FBDI columns or new HDL segments. Syntra ETL's peoplesoft to oracle fusion data mapping is versioned per release pair (e.g. PeopleSoft 9.2.045 → Fusion 26B) with automated regression testing of every active mapping against shipped sample data. When a new PeopleSoft PUM or Fusion 26x release lands, the mapping store is updated, regression-tested and republished. Customers in active parallel-run windows pin to a specific mapping version for stability and upgrade on their schedule. Migration projects pin to the current released pair at kickoff with a documented upgrade plan.
30-minute call. Walk through your PeopleSoft ChartField design, SetID share model and PeopleCode customization — leave with a concrete peoplesoft to oracle fusion data mapping plan and timeline.