Smart View support questions, answered clearly.

Oracle Smart View Support is the ongoing service that keeps the Excel side of an EPM estate working for every user: add-in version management and deployment, connection setup after server changes, template and report pack maintenance, Smart View function and VBA repairs, performance troubleshooting, user provisioning questions that surface in Excel, and standby cover at month-end when the packs are due. It is distinct from Oracle’s product support, which covers defects in the add-in but not your workbooks, your desktop estate or your reporting calendar. Namandla provides it as a managed service with a named senior consultant.

Because Smart View is where finance meets the EPM applications, and it is the layer with the most moving parts: hundreds of desktops, Microsoft 365 updates that arrive without warning, Office bitness, add-in versions that drift, connection URLs that change after an upgrade or migration, and workbooks built by people who have since left. When a board pack will not refresh on the morning it is due, the cause is almost always in this layer. Support exists so that the desktop estate is standardised, the templates are maintained and someone can act while the pack is being produced.

A typical Namandla Smart View support scope covers add-in version standardisation and packaged deployment through Group Policy, SCCM or Intune; compatibility checks before Office and EPM updates; shared and private connection maintenance; report pack and template maintenance including Smart View functions, cascades and Query Designer queries; VBA macro repairs; user issue resolution with defined response times; performance troubleshooting on the desktop and the server; user guidance and short training sessions; quarterly health checks; and priority standby during month-end and budget cycles.

Usually, and the improvements are on both sides. On the desktop: templates redesigned to retrieve only the members needed, suppression switched on, functions consolidated into grids, Excel calculation set to manual during refresh, and add-in options tuned. On the server: Analytic Provider Services sizing and settings for on-premises Essbase and Planning, and retrieval limits and form design in the cloud. A health check measures refresh times for the packs that matter, identifies the drivers and fixes them in order of impact. A pack that took twenty minutes refreshing in two is a normal outcome.

A structured review across three layers. Desktop: add-in versions in use, Office versions and bitness, deployment method, connection configuration and options. Workbooks: the critical report packs and planning templates, how they retrieve, how many functions they carry, macros and cascades, and whether they still match the current outlines. Server: provider services sizing on-premises or form and query design in the cloud, concurrent user load at month-end, and error logs. The output is a written findings report with prioritised fixes, each with effort and expected effect, plus a version standard for the estate.

Yes. Namandla provides standby cover at month-end, budget and forecast cycles, with a consultant available to resolve refresh failures, connection errors, form submission problems, macro faults and performance issues while packs are being produced and planners are submitting. Before a cycle we test the critical packs and templates against the current server, confirm that connections and versions are correct on the desktops that will be used, and check that any recent outline change has not broken a function or a cascade.

Yes. Typical improvements are converting export-and-paste packs to refreshable templates, replacing thousands of individual functions with ad hoc grids or forms, building cascades so that entity packs are generated rather than copied, standardising connection setup so new users are productive on day one, and scripting month-end refreshes with VBA where a scheduled pack makes sense. Every template change is tested against the prior period’s numbers. The aim is a pack that refreshes on demand and a planning template that submits without re-keying.

Yes, at the client end. Support covers connections to Essbase, Planning, HFM, Financial Reporting and every EPM Cloud service, the Smart View extensions for Planning administration, Narrative Reporting and Enterprise Data Management, drill-through to FDMEE and Data Integration from Excel, and workbooks that combine several applications on different sheets. When the servers change, through an upgrade, a migration to the cloud or a new URL, support re-points the connections and re-tests the packs so users notice nothing.

Yes. Smart View is often the user-facing part of an EPM upgrade or cloud migration: the add-in must be upgraded across the desktop estate, connections re-pointed, templates and functions re-tested against the new environment, and macros adjusted where the connection method changed. Namandla handles the compatibility assessment, the packaged deployment, the template regression testing and the user communication, timed so that the cutover does not land in the middle of a reporting cycle. For cloud migrations the workbooks usually survive; the connections and the version do not.

By keeping the packs refreshing from the server rather than from memory: templates that point at current members after outline changes, functions that return values rather than errors, cascades that still cover every entity, and connections that reach the right environment (a surprising number of wrong numbers come from a pack refreshed against test). Support also removes the stale-paste habit by making the refreshable pack easier than the export. Accuracy problems in Excel reporting are usually template maintenance problems, and template maintenance is what the service is for.

Support that works from the reporting calendar and the update calendar rather than from incident tickets. In practice that means testing the certified add-in version against each Microsoft 365 and EPM update before it reaches users, deploying versions centrally rather than reactively, checking critical packs after every outline change, watching provider services load at month-end, and keeping a register of the templates that matter and who owns them. It also means telling you when a risk exists, such as a pack that only one person can refresh or a version that will lose cloud compatibility, before it becomes a failed month-end.

Outsourcing makes sense when Smart View problems currently land on the EPM administrator or the IT service desk, neither of whom owns the workbooks, when the desktop estate is large or remote, or when the critical packs were built by people who have left. It makes less sense if you have a finance systems team that maintains templates and manages the add-in centrally. Namandla’s managed support is designed to work alongside an internal team and the IT service desk, taking the specialist and standby work while your team keeps ownership, and to hand knowledge back rather than hold it.

Break-fix support responds after a pack has failed to refresh, bills by the incident and learns your templates during the call, usually on the morning the pack is due. Managed support knows your critical workbooks, your desktop estate and your calendar, tests before updates rather than after, keeps the version standard and carries responsibility for the packs being ready. Break-fix suits a small, stable user base with a capable finance systems team. For an organisation whose board reporting runs through Smart View, managed support is usually cheaper over a year, because the incidents that happen at month-end are the expensive ones.

By measurable results on the estate you already own: packs that refresh in minutes, planners submitting from Excel without re-keying, fewer month-end incidents, a desktop estate that upgrades without disruption, and finance users who use the applications they were licensed for instead of exports. The return is highest where users have quietly gone back to spreadsheets because Smart View “does not work here”; that is almost always a deployment and template problem, and fixing it recovers value from applications that are already paid for.

Namandla is a South African consultancy whose senior team has supported Smart View across Essbase, Planning, HFM and Oracle EPM Cloud for about two decades, and the consultant assigned to your estate is the one who answers when a pack will not refresh. We work on the whole chain, from server settings to template design to desktop deployment, and we are independent on which EPM platform sits behind Excel. Where AI can help with commentary and review, we apply it to the data already in your packs, with human review. Contact info@namandla.com or 087 188 3388.