Triaging PeopleCode, Application Engine and the PeopleTools estate

Inventory and triage the twelve customisation surfaces the source package identifies — from PeopleCode rated very high effort down to the configurable PeopleTools surfaces — using business capability rather than technology as the organising principle.

What you will be able to do

Introduction

The customisation estate is the part of a PeopleSoft migration most likely to be underestimated, and the source package is unusually direct about it. Among the canonical pain points listed in the adapter: PeopleCode, Application Engine and SQR estates are often larger than source owners expect.

The twelve surfaces

The source package inventories twelve customisation and integration surfaces with an effort indicator for each. The table is the map for the rest of this module.

PeopleCode: the hidden estate

PeopleCode carries the only very high rating, and its description is the sharpest sentence in the register: usually the largest hidden logic estate.

Application Engine: split before porting

Application Engine is rated high, with the business purposes of batch updates, integrations, calculations and close tasks. The register's migration approach is the important part: split data-change, orchestration and reporting Application Engine jobs into separate target patterns.

Application Designer: the extension-location decision

Application Designer modifications — custom records, fields, pages and components — are rated high, with the purpose of extending the delivered data model and user interface.

Integration surfaces

Four of the twelve surfaces are integration, and they are covered in depth by the Integration, Data & Analytics module. The development-side points are the effort ratings and the triage principles.

Reporting surfaces

SQR is rated high, with the register's classification instruction: operational versus analytical versus utility and report-control outputs. Its closing note is the one that changes plans: some SQRs are really data-processing jobs, not reports.

AWE and the configurable surfaces

AWE and approval logic is rated medium, targeting workflow plus Power Automate, with two instructions: rebuild high-value approvals only; simplify over-custom routing, and the warning that approval behaviour can also be embedded in PeopleCode.

Estimating without a conversion path

Because nothing converts, estimates cannot be built from object counts multiplied by a conversion rate. They have to be built from capabilities, and the register's effort indicators are the calibration.

Knowledge check

Summary

The customisation estate has no conversion path, which makes the inventory the deliverable and the triage the skill.