What problem does it solve? Operating Oracle Fusion Cloud ERP or E-Business Suite through an AI agent is risky because subledgers and the General Ledger are wired together through Subledger Accounting, so one action like validating an invoice or running Create Accounting can post journals, consume budget, and move cash. This Skill gives the agent the judgment to classify each action as read, write, committing, or destructive so consequential operations pause for human approval. ## Core Features & Use Cases - Action classification and gating: Maps Oracle ERP operation families (requisitions, POs, receipts, AP invoices, payments, GL journals, period changes) into read / write / committing / destructive tiers with explicit approval gates. - State-aware reasoning: Models object lifecycles (PO statuses through Finally Closed, invoice validation/hold/accounted/paid axes, period statuses) so the agent reads state before acting and re-reads at execute. - Gotchas and recovery playbooks: Documents 30 real failure chains (validation vs accounting, closed periods, hold release, Finally Close, batch partial failure) plus recovery patterns for reversals, voids, and cancellations. - Use Case: When asked to force payment on a held invoice, the agent recognizes that releasing a matching hold without fixing its cause is a destructive action requiring a named approver, and instead recommends fixing the mismatch and re-validating. ## Quick Start Ask the agent how to safely handle a 3-way match hold on an Oracle Payables invoice before the receipt is posted.
