UPDATE 8/15/18: The Business Unit, MCV09, is limited to UMS Accounting Office use; PeopleSoft security should only return MCV09 data for UMS accounting users.
If you are not in the UMS Accounting Office, but do have data for MCV09 returning in some queries, please contact DARTS@maine.edu for assistance.
FROM: Darla Reynolds, Director of Accounting
DATE: July 13, 2018
SUBJECT: Impact of New Business Unit on Queries & Reports
I have added a new business unit, MCV09, to our financials system (e.g., general ledger, AP, etc.) for use in FY19 and beyond.
This new business unit is NOT a part of the University of Maine System (UMS) legal entity or reporting unit; therefore you should not include it in data pulled for the UMS.
If you run queries/reports to retrieve data for the UMS as a whole, rather than just your campus, your queries/reports may need to be changed to ensure that they do not include data for business unit MCV09. EVERY query/report should include a criterion for BUSINESS UNIT as illustrated below.
Include or update a criterion for BUSINESS UNIT as shown below for the most utilized reporting tools and data records/sources:
Reporting Tool | Data Record/Source | Item/Chartfield | Condition | Values to Specify |
Discoverer | GLSNAP | Business Unit | LIKE | UMS% |
GL Inquiry Page | User sets Search Criteria on the page | Business Unit | Lookup by Business Unit Tree | UMS* |
PS Query | UM_GLQ_REPRTING table | BUSINESS_UNIT | in tree UMS_BUSINESSUNIT | UMS |
PS Query | LEDGER | BUSINESS_UNIT | in tree UMS_BUSINESSUNIT | UMS |
PS Query | JRNL_LN | BUSINESS_UNIT | in tree UMS_BUSINESSUNIT | UMS |
| nVision | Scopes | BUSINESS_UNIT | UMS_BUSINESSUNIT tree nodes | UMS |
*As of the date this document was created, GL Inquiry did not return data for this tree node. A change to the reporting table update process is in progress to correct this. | ||||
Who is responsible for making the needed changes? If you use:
- Discoverer queries, YOU will need to make the noted changes.
- GL Inquiry, YOU will need to make the noted changes.
- PRIVATE PS queries/reports YOU will need to make the noted changes.
- PUBLIC PS queries which start with "UMS_DTS", the DARTS team will make the changes.
- Other PUBLIC PS queries/reports that need to be changed, please let me or the DARTS team know so that we can ensure the changes are made.
- nVision reports, I have already updated the business unit criterion for the impacted scopes.
As always, please let me know if you have any questions.
Additional coding option:
You can also Include or update a criterion for DEPTID as shown below for the most utilized reporting tools and data records/sources. If you specify business unit as noted above, you should not need to specify anything for department.
Reporting Tool | Data Record/Source | Item/Chartfield | Condition | Value to Specify |
Discoverer | GLSNAP | Deptid | NOT LIKE | 9% |
GL Inquiry page | User sets Search Criteria on the page | Department | Lookup by Department Tree | * |
PS Query | UM_GLQ_REPRTING table | DEPTID | not in tree UMS_DEPT_ORG | NON_UMS |
PS Query | LEDGER | DEPTID | not in tree UMS_DEPT_ORG | NON_UMS |
PS Query | JRNL_LN | DEPTID | not in tree UMS_DEPT_ORG | NON_UMS |
*Department id cannot be used as the single criterion for pulling UMS-wide data from GL Inquiry because only one tree node can be specified in GL Inquiry. Because of the way the underlying tree is structured, we cannot create a new parent node under which the UMS departments can be placed as we did for the business unit chartfield. | ||||
REPORT-388
-
change queries related to new business unit - MCV09
Closed