Workday FDM Data Model
Planned
- Which Workday FCM modules or datasets are most important to you
-
The modules/datasets most important to us are those which support Budget to Actuals analysis (Journal Entries, Business Plan/Budget, Cost Center and Organization hierarchy) and those pertaining to the Procure-to-Payment cycle (requisitions, POs, Invoices, Payments, Vendors).
- The analytics or reporting outcomes you're trying to achieve
-
The ability to monitor revenue and expenses as they pertain to the fiscal budget as the fiscal year progresses.
-
The ability to measure the duration within the procure-to-pay cycle.
- Any dashboards, metrics, or business processes you hope Quick Start Models would accelerate
-
We would hope for a denormalized set of tables which can be queried simply with dimensional context without the need for 'transforming' data and having to resolve dimensional data via multiple joins to the worktags/custom worktags.
-
Official comment
Hi Zeid, thanks for opening this feature request and sharing these details of what you would like from a Workday FCM data model. It sounds like the highest value models for your use case would be:
- General ledger: journal entry activity with dimensional context resolved inline
- Budget vs actuals: budget and actuals paired on shared dimensions, with variance and year to date figures
- Procure to pay: requisition through payment on a single row, with stage dates
Given the detail you've shared, we'll start with the general ledger model and share it here for feedback once it's ready.
Please sign in to leave a comment.
Comments
1 comment