One Planning Model Across SAP, Oracle, Salesforce, Dynamics, and More
Teams using ERP, CRM, and other systems may be able to report across them, but planning still happens in spreadsheets. Imagine one governed model for forecasting and scenarios across applications using Microsoft Fabric.
Date: Oct. 21, 2026
Time: 11:00 AM EDT / 4:00 PM BST
Duration: 1 Hour
Format: Live Webinar
Plan Across Systems, Not Spreadsheets
Enterprises have a collection of applications: sales in Salesforce, finance in SAP or Oracle, maybe a custom application or two. That data may already be available in a warehouse or analytics platform. But what happens when it’s time to forecast, budget, set targets, or understand what an upcoming period could look like?
That’s when teams often resort to Excel and separate spreadsheets.
Whether you already have a warehouse or not, Fabric provides out-of-the-box functionality that gives analysts the ability to forecast, adjust assumptions, compare scenarios, and get approvals without managing separate files outside of the systems.
What You’ll Learn in this Session
Periodic planning across finance, sales, operations, and other teams requires the same underlying data, no matter which applications are used for ERP, CRM, or operations.
In this session, you’ll see how Fabric can support planning across those teams.
- Sales and Revenue Operations: Forecast by region, product, or salesperson, adjust targets, lock assumptions, and route changes for review.
- FP&A and Finance: Compare budget to forecast, analyze variance, model different scenarios, and incorporate approval workflows.
- Supply Chain and Operations: Plan demand by product or region, account for seasonal patterns, adjust assumptions, and use different forecasting approaches depending on the data.
With Fabric, statistical forecasting, planning workflows, collaboration, Teams notifications, and BI can work around the same data instead of being treated as separate artifacts.
Speakers
Speaker- JT Gorrell
VP Customer Success & PMO
With over 25 years of experience, JT has led enterprise initiatives across program delivery, ERP implementations, and organizational change. He works closely with executive leadership to drive successful Dynamics 365 outcomes and improve operational performance in complex environments.
Speaker- Emilie Toll
US Marketing Director
Emilie Toll works at the intersection of business and technology, helping organizations connect Microsoft business applications, data, automation, and AI solutions to real-world business outcomes. Her passion is helping business and IT leaders cut through complexity and make more informed technology decisions.
Reasons to attend this session
Planning Still Happens in Spreadsheets
Your reporting may already bring data from multiple systems together, but forecasting, budgeting, and operational planning still get rebuilt in separate files.
Keep the Logic Consistent
Keep assumptions, measures, and planning logic consistent across teams instead of recreating them every cycle.
Let Excel Be Excel
Excel is useful for analysis, but it should not have to be the database, integration layer, approval process, and calculation engine at the same time.
Plan for More than One Outcome
Start with historical data and forecasting methods, then adjust assumptions and compare best-case, expected, and worst-case scenarios.
Keep Decisions with the Numbers
Planning crosses finance, sales, operations, and leadership, so comments, approvals, and notifications should stay with the plan instead of getting scattered across email and separate files.