Earlier this week, I helped a customer who wanted to use PeopleSoft nVision to do ledger-based reporting in EPM. Because their ledger and business unit structure was the same between their PeopleSoft Financials application and EPM, this was pretty easy.

The secret is the view NVS_LEDGER_VW, which nVision uses to find all the info it needs to access a ledger. The customer updated their Ascential maps to load the tables that were used in this view, and nVision magically worked.

There are some caveats to this approach, however.

1. The ledger definitions in Financials did not have to be modified to work in EPM. THis is important, because the pages used to maintain ledgers have not been implemented in EPM. Therefore, if you make changes to the tables or chartfields used, you will need to either modify the view or make changes directly to the tables.
2. The setid and business unit mappings are set up properly in nVision (and match the business units in the ledger definition). Again, one approach may be to modify the tables under the view or view itself, if you cannot use the same setids and business units in your finanical system.

Another approach is to do Query-based nVision reports (which is how the delivered EPM nVision reports access data). However, Query-based nVision reports do not know how to use timespans (which is pretty important).

Labels: nVision