Fast Formula, properly
Contexts, database items, routes and the seven building blocks. Why there is no
null, what DEFAULT actually protects against, and how to read a
compilation error.
Most Oracle HCM problems aren't knowledge gaps — they're the specific, undocumented behaviour of one feature under one configuration. I help teams get past those, either by teaching the underlying model or by working the actual problem with you.
abhishek.mohantyoracle@gmail.com Tell me the module and the symptom — that's enough to start.Sessions are built around real formulas, real data and real integrations, and they assume you'll be maintaining what you write. Delivered remotely, recorded if you want it.
Contexts, database items, routes and the seven building blocks. Why there is no
null, what DEFAULT actually protects against, and how to read a
compilation error.
The input contract, marker rows, parallel arrays, and the state machines behind continuous-hours and overtime rules. Built from a production formula, traced line by line.
Matrix formulas, accrual bands, carryover and ceiling behaviour, and the multi-country leave patterns that come up across APAC rollouts.
OPERATION routing, METADATA arrays, LINEREPEATNO passes and WSA caching — including where WSA is a correctness requirement rather than an optimisation.
Post Election Edit validation, cross-plan dependencies, rate periodization, and reading enrollment at a future effective date.
Logging idioms for every formula type, the profile options that silently discard output, and where each module actually writes its log.
File structure, business objects and discriminators, SourceSystemId and MERGE behaviour, and reading the error log well enough to fix a failed load without guessing.
Data models and SQL against the HCM schema, bursting, layout templates, secured list views, and scheduling reports that keep working after a release.
Subject areas and how they join, folder and attribute selection, filters and prompts, and where OTBI is the right tool versus where you should drop to BI Publisher.
Practical SQL against the HCM tables — joins, analytic functions, date-effective
rows and the _F table patterns that trip people up on their first
extract.
Integration patterns for HCM — adapters, mappings, scheduled versus event-driven flows, error handling and retries, and moving files in and out reliably.
One realistic requirement carried through the whole stack: extract with SQL, report in BI Publisher, load with HDL, integrate with OIC. This is where the pieces stop feeling separate.
Oracle HCM interviews rarely test definitions. They test whether you've hit the problem before — and whether you can explain what you did about it.
Fast Formula, HDL, BI Publisher, OTBI, SQL and OIC — the questions that come up for each, and the follow-ups that come after your first answer.
"A load failed for 200 of 5,000 rows — what do you check first?" The kind of question where a memorised answer falls apart on the second sentence.
Live, timed, with honest feedback afterwards on what was weak — including when the problem is delivery rather than knowledge.
Most candidates lose points describing work they genuinely did. We rehearse your actual rollouts into answers you can give under pressure.
You have something that compiles and mostly works. I read it and tell you where it breaks — the unguarded array read, the case-sensitive comparison, the missing reset that only shows up on a multi-day timecard.
Something works in test and fails in production, or works for most people and fails for a few. We work it together against your actual data and logs.
Before you build. Whether the rule belongs in configuration, a TER, a TCR or a workflow — and what a second country will do to the design you're about to commit to.
A short, honest read on an approach someone has proposed — including when the answer is that it's fine and you should proceed.
Include the module, what you expected, and what actually happened. If there's a formula or a log extract, paste it — it saves a round trip.
Availability varies with client commitments, so response times aren't guaranteed. Views on this site are personal and not those of any employer or client. Oracle and the Oracle product names referenced are trademarks of Oracle Corporation.