Oracle Smart View is an Excel add-in that connects the familiar Excel environment directly to Oracle EPM applications — Oracle PBCS, EPBCS, FCCS, Oracle Analytics Cloud, and other Oracle platforms. With Smart View installed, a finance analyst can retrieve planning data or consolidation results directly into an Excel worksheet, navigate the EPM dimension hierarchy from within Excel, submit budget inputs back to the planning application, and produce ad hoc analyses that combine EPM data with other information sources — all without leaving Excel. For finance teams where Excel is the primary analytical tool, Smart View is the interface through which most of them will experience the EPM application on a day-to-day basis.
Why Smart View Matters for EPM Adoption
Oracle EPM’s web-based planning forms are adequate for entering structured plan inputs through a predefined grid. They are not adequate for the analytical work that finance teams need to do alongside the planning process — building comparisons across multiple periods, combining EPM data with ERP data in the same analysis, creating bespoke layouts that do not match any standard form. Smart View fills this gap. A CFO who wants to see the Q3 budget submission from the Saudi entity alongside the most recent rolling forecast and the prior year actuals, formatted in a way that suits a specific board presentation, can pull that analysis into Excel through Smart View in minutes. Without Smart View, producing the same output would require separate report extracts from multiple sources and manual assembly.
What Good Smart View Governance Looks Like
Smart View’s connection to live EPM data is its strength and its governance risk. When finance team members submit data back to the EPM through Smart View forms, they are writing to the production planning application. A user who submits incorrect data through a Smart View form has modified the live plan — and if the form does not have adequate input validation, the error may not be detected until the budget review. Smart View governance requires clear rules about which users can submit data (not all Smart View users should have write access), which forms support submission versus read-only retrieval, and how submission errors are identified and corrected.
Where Smart View Creates Problems
Smart View creates governance problems when finance team members build local Excel models that pull data from EPM through Smart View, add local calculations, and distribute the resulting spreadsheet as the organisation’s management pack. The spreadsheet becomes the de facto management report, the EPM data inside it is correct, but the local calculations and formatting are ungoverned. When the spreadsheet is updated next month, the local calculations may or may not be consistent with the prior version, and the management pack starts to diverge from the EPM data it was meant to present. Smart View is most valuable when it is used to retrieve EPM data into a governed Excel template — not as a data feed for locally managed spreadsheet models.
How Loop Wise Solutions Works with Smart View
We include Smart View template design in every EPM implementation — building a set of governed, version-controlled Excel templates that use Smart View connections to retrieve EPM data for the standard management reporting views. These templates are maintained by the finance team as a governed deliverable, updated at each reporting period, and used consistently across the organisation rather than having each finance team member build their own local version of the same report.
