| Level | What it is |
|---|---|
| Project | One client conversion — the top-level container. |
| Cycle | One full practice run of the conversion. Each is faster than the last because ORCA remembers. |
| Entity | One Oracle business object (Worker, Assignment, Payroll) with its own template, mappings, and state. |
Create a project
Start a project
Go to Projects → Create Project, type a Project Name (ORCA derives a short ID from it), and pick the Source System (e.g. PeopleSoft, SAP, Workday, ADP, UKG / Kronos, or CSV).
Start a cycle
New cycle
In the project, click New Cycle, give it a Cycle ID (e.g.
cycle-0), and choose the Oracle Connection the cycle loads against.The cycle carries the connection — everything it loads or queries runs through that pod. There’s no separate “start” button; you advance a cycle by editing its status.
Add entities
In the Entities card, use + Add Entity to pick from the templates loaded for this pod (Worker, Assignment, Salary, Payroll, …). Each row shows Status, Files, Errors, Iteration, and an Attention flag.Oracle entities have a real dependency order (Organization / Location first, Payroll last) and the conversion respects it — but the grid does not render a load-order column today. Treat sequencing as consultant knowledge, not a screen.
Next steps
The conversion lifecycle
From POC to prod cutover across cycles and environments.
Inside an entity
Source data, mappings, preview, run, and learnings.