1. Creating a NAL DOR Data Run
Purpose
Use this procedure to create a NAL DOR Data Run
Procedure
- Click Action Button
- Select Reports>DOR>DOR Data Run>The DOR Data Runs dialog will render
- Click the green plus at the upper left hand of the dialog
- Year – this is the year of the DOR Data
- As of Accepted Roll Correction – user selects the roll correction number for the year selected
- Preliminary Certification – user may run report as of preliminary Certification
NOTE: The Preliminary Certification process must be run to select this option
- Certification – user may run report as of Certification
NOTE: The Certification process must be run to select this option
- Options
- Include Confidential owner – will include owners accounts that are flagged confidential in export
- Include Social Security Number –will include social security numbers in export
- Allow DOR Data Delete – will allow the run to be deleted at Data Run list.
4. Click OK to proceed or Cancel to cancel the operation.
2.Viewing DOR Data Export Errors
Purpose
Use this procedure to review your data errors in your related NAL DOR run.
Procedure
- Click Action Button
- Select Reports>DOR>DOR Data Run
- The DOR Data Runs dialog will render
- Select the Data Run you desire to review
- Click View DOR Data
- User can filter the DOR Errors by hovering over DOR Level # and DOR Edit # to review particular errors.
- To Open property, highlight property and click ‘Open Property’
- To Export the errors to a spreadsheet, click ‘Export’
- To Update Status, highlight the property and click ‘Update Status’
- User can filter the DOR Errors by hovering over DOR Level # and DOR Edit # to review particular errors.
NOTE: Changing the status will not drop the property from your error list. It will simply change the status from Active to Complete. To drop the property off the list, user will run a new data run.
3.Viewing DOR Errors at Property Level
Purpose
Use this procedure to review the DOR errors at the individual property level
Procedure
- Open Property
- Go to Commands>View DOR Errors
- Year – select year desired
- Data Run – user may select the Data Runs available for the selected year
- Export –Export Errors to a spreadsheet
- Update Status – User may change the status from active to complete when they complete the error correction.
NOTE: This will not drop the error from the error run list. It will simply update the status. For the error to be removed, user must create a new data run
4.Export DOR Data
Purpose
Use this procedure to export the DOR Data Run. Data exported can be sent to the DOR by selecting the exported files.
Procedure
NOTE: To find export files, user will identify where the export path. To do this, go to Action Button>Tools>System Configuration>Import/Export Paths
- Click Action Button
- Select Reports>DOR>DOR Data Run
The DOR Data Runs dialog will render
- Select the Data Run you desire to review
- Click ‘Export DOR Data’. The following dialog will appear
- Select Submission Type
- Click Export
5.Print Limitation Report
Purpose
Use this procedure to print or preview a Limitation Report
Procedure
- Click PACS Application Button
- Select Reports>DOR>DOR Data Run
The DOR Data Runs dialog will render
- Select the Data Run you desire to review
- Select the ‘Print Limitation Report’
- Select Preview or Print
6.DOR Reports in .xlsx format for DOR Consumption
Purpose
DR 403, DR 489 and DR 489V, EB, PC in .xlsx format for DOR consumption
Procedure
Added ability for DR-403 and DR-489 report Export to actual Excel template.
- PACS Menu –> Reports –> DOR –> DR-403
- Choose Excel in report output options.
The reports have been sent to the DOR for verification and acceptance. DOR approved.
NOTE: The spreadsheet that is created DOES NOT contain any formulas. Therefore, updating an amount that should be added to another to change results will not happen. If a user would like to use the numbers generated in the locked spreadsheet, the user can copy the values needed to produce their spreadsheet. The spreadsheet produced by PACS 10.0 for these reports is locked so that the results set in the file will always match the data in the pacs tables.
In addition, the server that houses the production database, must have Excel on residing on it to make sure this occurs.