oracle-fusion-oss-revenue
Skill0 starsChanged 4 months agoUnlicenseView on GitHub
Expert knowledge for building, debugging, and reasoning about Oracle Fusion Subscription Management (OSS) revenue reporting via the Revenue Management (VRM) schema — especially BIP subscription revenue waterfall reports. Covers the OSS→VRM→XLA→GL data flow, the canonical table relationships, and the hard-won quirks (348-way OSS_PRODUCTS fan-out, version-skew POL drops, catch-up accounting dates, cross-currency T/F handling, satisfaction-event projection math). Use this whenever the user works with OSS subscriptions, VRM_ tables (VRM_SOURCE_DOCUMENTS, VRM_PERF_OBLIGATION_LINES, VRM_PERF_OBLIGATION_LIN_DISTS, VRM_POL_SATISFACTION_EVENTS, VRM_SOURCE_DOC_LINES, VRM_BILLING_LINE_DETAILS), revenue waterfalls, recognized/unrecognized revenue, TCV, subscription revenue projection, FUSION_OSS source documents, or any subscription-revenue SQL against Oracle Fusion. Trigger even when the user only mentions "the waterfall report," "OSS," "perf obligations," "POL," "POLD," or "subscription revenue" without naming tables.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ap-invoice-conversion-profilingSkill
- ar-transaction-conversion-profilingSkill
- ax-erp-sourceSkill
- bmn-issueSkill
- clear-promptSkill
- data-analysis-report-formatSkill
- digikey-brand-guidelinesSkill
- fa-asset-conversion-profilingSkill
- finance-data-profilingSkill
- gl-journal-conversion-profilingSkill
- groom-issuesSkill
- hackett-brand-guidelinesSkill
- hcm-config-readiness-reportSkill
- hcm-grades-data-profilingSkill
- hcm-job-conversion-profilingSkill
- hcm-location-conversion-profilingSkill
- hcm-organization-conversion-profilingSkill
- hcm-position-conversion-profilingSkill
- hcm-production-health-checkSkill
- hcm-salary-conversion-profilingSkill
- hcm-worker-data-profilingSkill
- inventory-onhand-conversion-profilingSkill
- meeting-summarySkill
- oic-iar-integration-reviewSkill
- oic-integration-buildSkill
- oic-integration-buildSkill
- oracle-fusion-bip-generatorSkill
- regal-brand-guidelinesSkill
- regal-gp-customer-researchSkill
- regal-report-builderSkill
- regal-report-formatSkill
- regal-technical-standardsSkill
- releaseSkill
- scm-integration-functional-specSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Start here, then read the reference file(s) matching the task.
- Very specific: line 42
Read data-model.md and the task-specific reference.
- Very specific: line 43
Write SQL in the user's mandated style (sql-style.md).
- Distinctive: line 44
Test against live data: before presenting. Wrap the query and check row counts and the audit invariants.
- Distinctive: line 45
Call out tenant-specific assumptions and any silent-failure risks in your explanation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Oracle Fusion OSS Revenue Reporting
This skill captures everything learned building the Subscription Waterfall Report — a BIP data model that produces a month-by-month projection of recognized and unrecognized revenue per subscription performance-obligation line, sourced from Oracle Subscription Management (OSS) through the Revenue Management (VRM) engine.
It exists because OSS→VRM revenue reporting is full of non-obvious traps. Several of them silently produce wrong numbers that look plausible (dropped lines, currency mislabels, 6-years-of-revenue-in-one-month) rather than erroring out. The reference files below encode the specific diagnostics and fixes that took many live-data iterations to discover.
When to use this skill
Use it for any task touching subscription revenue in Oracle Fusion: writing or debugging waterfall/revenue-recognition SQL, explaining where a number comes from, reconciling recognized vs. unrecognized vs. TCV, handling cross-currency contracts, or interpreting the OSS/VRM/XLA table graph. The user is a Hackett consultant (Jonathan) who builds these for end customers; the original end user of the waterfall report is Jay Surface.
How to navigate this skill
Start here, then read the reference file(s) matching the task. Each is self-contained — read the whole relevant file before writing SQL, because the gotchas are interdependent (e.g. the version-skew fix and the header-TCV dedup must be understood together).
| Reference file | Read it when... |
references/data-model.md | You need the table graph: what each OSS/VRM/XLA/GL table holds, the canonical join keys, grain at each level, and the OSS→VRM bridge. Read this first for any new query. |
references/gotchas-and-fixes.md | You're debugging wrong/missing/duplicated rows, or want the catalog of known traps (fan-out, version skew, catch-up dates, currency mismatch, recognition-math bug) with the exact diagnostic queries and fixes. The highest-value file. |
references/waterfall-report.md | You're working on the waterfall report specifically: its CTE architecture, bucket math, all column mappings, the audit invariants (Recog+Unrecog=TCV etc.), and the RTF layout. |
references/currency-tf.md | Anything involving currency: the (T)/(F) convention, transaction vs. contract vs. functional currency, FX rate sourcing, the at-or-before date semantics, multi-functional-currency ledgers. |
references/recognition-and-projection.md | You need the revenue-recognition model: POLD as engine-truth for past periods, satisfaction events for future projection, measurement models, terminations/modifications, catch-up bookings. |
references/environment-and-tooling.md | You're connecting via the hackett-fusion MCP server, validating against live data, or need tenant-specific values (Imagine COA, application IDs, conversion-type IDs). |
references/sql-style.md | You're writing SQL output for this user — the mandatory Oracle WHERE-join / formatting conventions. |
assets/waterfall_oss_aligned_reference.sql | The full, working, validated data-model SQL (~1490 lines). The authoritative implementation that every reference file describes. Open it to see any pattern in full context. |
Bedrock facts (true across everything below)
- Scope filter: OSS subscription revenue lives under
VRM_SOURCE_DOCUMENTS.DOCUMENT_TYPE_CODE = 'FUSION_OSS'. The report deliberately excludesFUSION_CONTRACTSandFUSION_OM. Almost every CTE re-applies theFUSION_OSSfilter. - The engine owns the numbers. The report reads VRM engine outputs (
net_line_amt,entered_cur_recog_rev_amt, POLD distributions); it does not re-derive revenue from scratch. When a value looks wrong, suspect the plumbing (joins, currency, period attribution), not the arithmetic. - Grain matters constantly. The natural reporting grain is the performance obligation line (POL). Source doc lines (VSD), OSS products, satisfaction events, and POLD distributions all sit at different grains and will fan out if joined naively. See
data-model.md. - Things fail silently. The worst OSS bugs return rows — just wrong ones. Always validate against live data with the audit invariants in
waterfall-report.mdand the diagnostics ingotchas-and-fixes.md. Never present SQL changes as "done" without running them when an MCP connection is available. - Tenant-specific values exist. COA segment meanings,
application_id = 10455, theProduct_Reportingcatalog, and conversion-type IDs are specific to the Imagine tenant. They're flagged everywhere they appear; seeenvironment-and-tooling.md.
Default working approach
- Confirm which tenant/environment is connected (
identify_environmenton the MCP) before trusting any live result — the connection has been observed silently switching between Imagine and other tenants mid-session. - Read
data-model.mdand the task-specific reference. - Write SQL in the user's mandated style (
sql-style.md). - Test against live data before presenting. Wrap the query and check row counts and the audit invariants. A change that "should be correct by construction" still gets run — that mindset has masked real typos and parse errors here before.
- Call out tenant-specific assumptions and any silent-failure risks in your explanation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

