nVision Report Requests & Scopes

nVision Report Requests & Scopes

PS/nVision – Key Terms • Trees – Specifies how your data should be summarized or rolled up for reporting purposes. • TableSet – Contains the rules by which data is processed. The BU contains all the actual data and a setID identifies each TableSet. • Business Unit – Uses SHARE setID • Account – Uses SHARE setID • Department – Specific setID for each BU (This is why only certain depts are valid for certain BU’s)

PS/nVision – Key Terms • Layout – The report you want to run • Scope – Who you want to run the report for. Your parameters (Consolidated, BU and or Departments) • Report Request – Attaches a layout and scope to run your report for user specified As Of Date • Process Monitor – Check status of Report Request • Report Manager – One option to pull up delivered reports • Report Console – 2nd option to pull up reports • Drill to PIA – Excel Drill Down (PeopleSoft Internet Architecture) • Nplosion – Detail within the report (number 2 button)

PS/nVision Layouts • During design phase Symphony stakeholders identified what standard reports would be built for all HM’s. • Layout is an Excel Template with specified report parameters. • Layouts can’t be modified or changed. If a HM wants something changed they would have to submit a Service Request and Goverance Team would have to approve. • Inventory of Layouts (Reports) including report samples and job aids can be found on AHU website on the Peoplesoft Report Catalog page. http://ascensionstcs.adayana.net/courses/Symphony%20UPK/Report_Catalog/ReportCatalog.html

PS/nVision Layouts • PS/nVision reports are built using Excel developer tool, based on a request for a report. HM’s will not have access to this tool. • There are check figures within most reports. If an error message shows up please log a service now incident ticket with the Peoplesoft Reporting team. • If you unhide Column A and Row 1 you will see the report logic (tree nodes, time spans, etc.) • nVision only pulls data at the intersection of defined logic in a row and column. You can drill down into the details of these intersections. You cannot drill down on anything calculated by a formula.

PS/nVision Scopes • Scope – Who you want to run the report for. Common Scope definitions include (there are others): • Consolidated Ministry • Business Unit – All Departments • Business Unit – Department Tree Node • Business Unit – Selected Department • PS/nVision Scopes use the BU SetID. • (Remember TableSet) – MDS Business Rule for departments. • PeopleSoft PS/nVision Scope Job Aid Available on AHU website on the Peoplesoft Report Catalog page: http://ascensionstcs.adayana.net/courses/Symphony%20UPK/Report_Catalog/ReportCatalog.html

Standard PS/nVision Scopes

PS/nVision Scopes - Modify • To modify an existing Scope: • From the Home page, navigate to Main Menu>Reporting Tools>PSnVision>Define Scope. Enter Your BU in SetID: Select Search. • The Search results are displayed and you can select the Scope you wish to modify from the Search Results values. IMPORTANT NOTE: Scopes are public for all to use and modify, so ALWAYS check your scope definition before running an nVision report.

PS/nVision Scopes - Modify Path to define existing Scope Enter BU and click Search Pick a Scope to modify See Job Aid for detailed instructions on modifying a Scope

PS/nVision Scopes – Create New • To create a New Scope: • From the Home page, navigate to Main Menu>Reporting Tools>PSnVision>Define Scope.Click on Add A New Value tab. Enter your BU in SetID. Type a name in Report Scope. Click Add. • The Peoplesoft Reporting team has built a standard set of Scopes for each BU of your Ministry based on the Standard BU and Department trees. These scopes can only be modified within those trees. To utilize customized reporting trees, a new scope would need to be created. See Job Aid or open a request ticket through Service Now and have it assigned to the PS Reporting team for additional assistance. • Note: You are unable to copy a scope, but you can delete them.

PS/nVision Scopes – Create New Path to Add a New Scope Enter your BU in SetID and a name in Report Scope. Click add. See Job Aid for detailed instructions on creating a new Scope

New Scope Definition Set Up • Description – Type anything to describe the Scope • Business Unit – Enter same Bus Unit as SetID • Field Combination Table – Leave Blank (Not Used) • Field Name – Select BUSINESS_UNIT or DEPTID • (See additional screenshots for selection) • How Specified – Pick from Drop Down • (See additional screenshots for explanation) • Business Unit Keyed Tree – Leave Unchecked • Tree Name or Value Table (depending on How Specified Selection) - Pick from: • BU Tree Name = AH_BUSUNIT_TREE • BU Table Name = BUS_UNIT_TBL_GL • Dept Tree Name = AH_DEPT_TREE • Dept Table Name = DEPT_TBL • Note: These are the Standard selections, but you can choose alternate reporting trees if desired. Note: When Tree Name is selected, leave Level blank (it is not used). • Select Value – Pick Tree Node value or Detail Value based on earlier selection. Use the + button to add a second page to specify Dept selections. Remember To Save!!! When choosing BUSINESS_UNIT or DEPTID for Field Name, use these selections within the Lookup Glass. Unused Selections All Detail Values All Nodes At Selected Levels Children at a Level Selected Summary ChrtFld Nodes • How Specified - Explanations • Detail – Selected Parents – Uses Tree Nodes, will give you a report for every BU or Dept rolling up to the tree node selected (can pick more than one tree node if desired). Use if you want a report for every BU or Dept • Selected Detail Values – Uses Tables, gives you the option of selecting 1 or more individual values for which to run a report. • Selected Tree Nodes – Uses Tree Nodes, gives you the option to select 1 or more tree nodes to run a report.

Scope Examples – All Details Of Node BU – All Details Of Selected Parent This type of scope would run a separate report for each BU under the selected node. You can pick a whole Ministry node or any combination of other tree nodes. Note: you can also do this with department nodes as well.

Scope Examples - Business Unit Values BU – Selected Detail Values This type of scope would run a separate report for each BU selected. You can add or remove individual BU values from the list. Note: When you don’t specify Departments in your scope, it assumes all departments.

Scope Examples – Selected Tree Nodes BU – Selected Tree Nodes This type of scope would run a separate summary report for each Tree Node selected. You can add or remove tree nodes. Note: you can also do this with department nodes as well.

Scope Examples – BU/Dept Scope Page 1 BU – Selected BU & Department This type of scope would run a report for selected departments of the selected BU. There are 2 pages to this setup. The department s are on the second page. Note: you can also do this with BU & Department tree nodes as well.

Scope Examples – BU/Dept Scope Page 2 BU – Selected BU & Department This scope will run for as many departments selected on this page. You can only add departments that are active for the BU selected on page 1 of this scope.

Scope Summary • Standard scopes have been set up for all BU’s using the standard BU and Dept trees. Those scopes can be modified by anyone, so ALWAYS check your scope before you use it to run a report. New scopes would need to be created for any alternate reporting trees created by your Ministry. • HM may request help in building new scopes. Right now enter a REQ by calling AHIS 877 – 635 – 0535 and have them assign the ticket to the PeopleSoft Reporting Team. • Scope Questions?

Report Requests • Attaches a layout and scope to kick of your report for the user selected as of date. • Very Important – Your report request has to use the same BU as your scope. • Standard Report Requests have been created for each BU of your Ministry. • Suggested Naming Convention • AH (Ascension Health) & Report Name (Layout Names) • AH-R001, AH-R002, etc. (Example Report names) • Alternative – FLP-R001, NAS-R001, MOB-R001

Report Requests • To use or modify a Report Request: • From the Home page, navigate to Main Menu>Reporting Tools>PSnVision>Define Report Request. Enter Your BU: Select Search. • The Search results are displayed and you can select the Report Request you wish to modify from the Search Results values. • If you select the Add New Value tab you can create a new report request from scratch, but you can clone Report Requests so it may be easier to clone a report request and modify it then it is to create a brand new one.

Report Request - Example Has to be same BU as Scope BU Standard Report Id Name Suggested Report name (can be modified to your liking) Layout Name. Have to key in exactlyor report will not run. As Of Reporting Date is Specify and enter last day of month for which you want data. Type has to be Web Format has to be Excel Check/Modify Scope & Delivery Templates before running report

Report Request – Scope Delivery Template Link Select Hour Glass to select your scope. Can check your scope settings or modify the scope by selecting the Scope Definition link. Empty boxes should not be populated. Naming Convention of the report output. %RID% - Report ID %RTT% - Report Title %SFV% - Scope Value %BUV% - BU %ASD% - As Of Date Hit OK once done to accept changes.

Report Request – More Options • Notice there are other tabs. Report R014 and R015 use Query Prompts so use that tab to set up the Query Definition • Copy/Clone Request • You can copy request to another BU or Clone it and modify it and save as a new request • Delete Request • Transfer to Rep Book • Process Monitor Link • Use link to make sure report has finished • Report Manager Link • Use link to access completed report • Share/Save Private

Report Request – Advanced Options Tab Enable nPlosion should be checked if you want the report nPloded to the details Data from Requesting BU Only is typically unchecked, especially if you are running a Scope with multiple BU’s. Depending on your scope definition will depend if this box needs selected.

Report Request - Running Once all options have been verified and set up to your specifications, hit Save & Run Report. Note: Although rare, keep in mind that someone else could be modifying the same report request at the same time as you.

Report Request – Process Scheduler Could schedule report to run for a different Day/Time Box needs selected Output options Default for both. Hit OK to Run. This brings you back to request page.

Report Request Once back to this screen you can select the link to the Process monitor to see status or your request or Report Manager to access the completed report. You can also navigate anywhere else within PeopleSoft.

Process Monitor You can change to see how many days you want. Recommend only a few weeks. To check status of report request go to Process Monitor. Make sure you have the proper USERID and Server Selected, if able. Report is done running when it says Success and Posted. Refresh as needed. Select details to cancel or to see error messages. Click Go Back To Report Request.

Pulling Up a Report – Report Manager Access the Report Manager through link on Report Request page or navigate to Main Menu>Reporting Tools>Report Manager. Select the Administration Tab to see reports available: Select the hyperlink to open in Excel or save to a location of your choice.

Pulling Up a Report – Report Console First time you go to console will need to select Preference link and accept or change your preferences. Amount of days you want reports to show up and naming conventions. After you hit the ok button reports will start to show up.

Drill to PIA – Excel Drill Down Add In Within an Excel report that you ran through Report Request, you can drill down into the details for further information using the Drill To Pia Excel Add In Tool. Notice the unhidden Column A and Row 1 which shows the nVision report logic (normally hidden). You can drill into the individual account details which were nPloded (#2) or the account node totals since those were populated by the nVision process (Column B, C, P, Q. Rows 18 thru 40). You can not drill into anything calculated by a formula (Column D, E, R and Row 41).

PS/nVision – Common Issues • Scope BU is not the same as Report Request BU. • User did not check scope before running report and scope is not what they were wanting. • Within the report request someone changed the preferred settings of Web/Excel. When that happens the report will still show as success but will not show up in Report Manager. • User did not validate report results by drilling down after the report was ran. • User inserted or deleted rows or columns which can throw of the drill down functionality results. • If getting error message and everything checks it means the server is down and you should log a ticket. • Most users just know how to pull up report request and hit the run button. Super Users will need to assist!!

Reporting - QUESTIONS???? I need help! I better call the AHIS help desk at 877–635–0535 and log a Request ticket with the Peoplesoft Reporting team. This report is not working as designed or I got an error message. Make it an Incident ticket! I sure do love all of these reports, but maybe anew report or enhancement could benefit all the Ministries. I should open a Request ticket to see if it gets approved!

nVision Report Requests & Scopes