Configuration workbook
One click produces a formatted Excel workbook of the pod configuration: lookups, profile options, price books, service queues and business units, with a cover page and sign-off block for design approval and handover.
Consultant workbench
The checks and documents every Oracle Fusion implementation needs, built into the same tool you query with. Read-only, and every run is logged.
Tool 1
Type the label you see on a Fusion page - "Bill-to Account", "Supplier Site", "Payment Terms" - and get the table and column, with join hints. Curated for ERP, SCM, HCM and CX, then backed by the pod's own data dictionary. Or enter a value you can see and find every column that holds it.
Tool 2
Upload the CSV you loaded. Map its columns to the Fusion table once; every row is matched on its key and each column compared, with numbers and dates normalised. Export the differences to Excel and the missing rows as a new import file.
Tool 3
Reads the standard interface error tables (AutoInvoice, customer import, payables invoice import, inventory transactions), groups errors by message, explains the usual fix and exports the failing rows with the message next to each, ready to correct and reload.
Tool 4
Lists users with privileged roles, users of terminated workers who still have access, inactive users still holding roles, and segregation-of-duties conflicts from a rule set you can edit. Export for the access review.
Tool 5
Tiles for what is stuck between systems: subscription bill lines not interfaced, AutoInvoice errors and backlog, import errors and failed scheduled processes - with the fix and the SQL behind each check.
Tool 6
One grade per pod from every validation pack, weighted by severity, with a trend and a printable scorecard for steering committees.
One click produces a formatted Excel workbook of the pod configuration: lookups, profile options, price books, service queues and business units, with a cover page and sign-off block for design approval and handover.
Take a data-dictionary snapshot before Oracle's quarterly update and compare it after: tables and columns added, removed or changed. Then run every saved query as a regression test and see which ones broke.
Design sign-off, each migration mock load, SIT and UAT, cut-over, hypercare and every quarterly update.