Katrina · CI/CD for Oracle EBS R12.2
Your EBS customizations in git. In PROD without a DBA typing commands at 2 AM.
Every FNDLOAD definition, PL/SQL package, form and BI Publisher template is versioned, built into an automated installer, and promoted through approval gates — with a full audit trail for every deployment.
| Pkg | Branch | Objects | TEST | UAT | PROD | Requested by | |
|---|---|---|---|---|---|---|---|
| #3812 | feature/xxar-aging | 14 · FNDLOAD ×3, PL/SQL ×9, BIP ×2 | installed | installed | gate · ticket | m.gonzalez | |
| #3811 | feature/xxgl-fah-batch | 6 · PL/SQL ×5, AOL ×1 | installed | installed | installed | f.martinez | |
| #3810 | feature/xxpo-approval-fwd | 9 · Forms ×2, PL/SQL ×6, XML ×1 | building | — | — | l.ferreyra |
How it works
One branch per development. One installer per package. One gate per environment.
Everything in git
Each development lives in its own branch: FNDLOAD definitions, PL/SQL, forms, BI Publisher templates, AOL objects.
Automated installer
Katrina builds the branch into an installer with the correct object ordering — plus the rollback package for the same release.
Gates per environment
TEST → UAT → PROD with an approval at each boundary. Segregation of duties: the requester never approves their own package.
PROD with a ticket
No production deploy without a change ticket. Every action logged: who, what, where, when — exportable for compliance.
Governance built in
Auditors like it as much as developers do.
Segregation of duties. The developer who requests a deploy can't approve it.
Branch-vs-environment verification. Katrina checks that what's in git matches what's actually installed before promoting.
Ticket-gated PROD. Production deploys require a linked change ticket. No exceptions, no overrides.
What it deploys
The objects EBS teams actually ship.
Built for R12.2: aware of online patching cycles (adop) and editioned objects. If your team ships it, Katrina versions and installs it.
Katrina + AI
Our MCP servers let Claude deploy through Katrina — same gates, same audit trail, same ticket-locked PROD.
See it run against a real R12.2 instance.
Thirty minutes, live — not slides. We'll build a package from a branch, walk an approval gate, and show the audit trail.