What's New in the Data Warehouse
Data Warehouse Fiscal Year End Maintenance
As you know, every year when the Institute fiscal year comes to an end, we need to perform maintenance on a number of Data Warehouse financial tables to enable the transition to the new fiscal year. This means that certain Data Warehouse financial tables are going to be unavailable for a short while.
This year, in consultation with the Office of the Vice President for Finance, we chose Sunday, July 1st as the day to do this work. On that day, you will be able to run Data Warehouse reports as long as they don't involve the following financial data tables:
These Data Warehouse financial tables will be taken off line for maintenance.
There is a slight possibility that the work will spill into the next day. We will be posting our progress on our web site at:
and on 3-down at:
However, in the previous several years we were able to complete the work in one day and we hope that this will be the case once again.
If you have and questions or concerns please feel free to email the Data & Reporting Services staff (email@example.com).
The Data Warehouse is available and operating normally after the scheduled system migration.
Data Warehouse Unavailable Memorial Day Weekend
The Data Warehouse will be unavailable from 5pm Friday May 25th till 9am Tuesday May 29th, so that we can move to a new machine.
Sorry for any inconvenience this might cause. Please send mail to firstname.lastname@example.org if you have any questions or concerns.
Change to Cost Object Number Ranges in SAP (and Data Warehouse)
In early February 2011, the number ranges allocated to different types of cost objects are going to change. Due to a large number of internal orders generated for Plant Maintenance, there will be a new number range for valid PM orders: from 5000000 to 5999999. This number range was previously reserved for project wbs numbers, but there are no valid project WBS numbers in it.
If you have any DW queries referencing cost object number ranges, their results may become incorrect after this change is implemented. The Data Warehouse team strongly encourages you to modify these queries and use the various type and category fields available in the Cost Collector table instead of number ranges -- please contact email@example.com if you want help with this. If you continue to use number ranges, they may need to be adjusted.
At the request of the VPF office, we are making enhancements to the Financial Detail view in the Data Warehouse that will go into effect on Tuesday, February 9, 2010.
Financial Detail — enhancements and modifications:
1. The table will contain all SMART financial documents, including those that involve Singapore cost objects. They will be identified by value "SING" in the Company_Code field. When querying by document number, please be aware that document numbers can be -- and are -- reused between company codes, so the same document number can occur in CUR, TECR, and SING.
2. To accommodate the new documents, fields Actual_Amount_LC (LC standing for "local currency") and Local_Currency will be added to Financial Detail. For Singapore documents, they will contain amounts in SGD and "SGD".
3. Since the removal of commitments from Financial Detail, the two fields Commitment_Amount and Actual_Commitment_Indicator are no longer useful, and are being removed to avoid confusion. Remember you can still get commitment information from Balances by Fiscal Period, Balances, and Summary Statement Detail.
4. Also at the request of the VPF office, a number of fields related to payment information will be added. They are: Check_Number, House_Bank, Probable_Payment_Date, and Check_Encashment_Date. The DTR report will be modified to include the check number, similarly to the SAP DTR. A separate notice will be posted on the Data Warehouse web page when this is done.
5. Lines with Gl Account 200080 (AP goods receipt / Invoice Receipt Clearing) will no longer be suppressed.
If you have existing queries using Financial Detail, you will need to sync them with the warehouse in order for the new fields to be available to you once they are in production next Tuesday. To do this, with the Query section active, from the Data Model Menu, choose “Sync with Database.” The new fields will appear at the bottom of the Financial Detail view, and you will be able to add them to your request line for inclusion in your reports.
If you have any questions or concerns please send e-mail to firstname.lastname@example.org.
Four obsolete fields which have not been populated since the new HR Payroll system went live on July 1, 2006 have been removed from the Appointment-related Detail tables to avoid confusion. If you have built a queries using any of these fields, you will need to synchronize your query with the Data Warehouse database in order to avoid errors. To do this, with the Query screen active, from the Data Model menu choose the "Sync with Database" command.
The fields are
They have been removed from the following tables:
Reduced downtime for weekly backup process:
Dear Data Warehouse Users:
I am happy to inform you that we have a new and improved MIT Data Warehouse backup process which will reduce the Saturday downtime from 4 hours to 10 minutes. In the past the Data Warehouse has been unavailable from 6:00pm – 10:00pm on Saturdays. Beginning this week, Saturday September 12th the Data Warehouse will be unavailable from 3:00pm until 3:10pm for weekly backup..
It is possible that in the future we may occasionally need the four hour window on Saturdays for maintenance. As usual you will be notified in advance.
If you have and questions or concerns please feel free to email the Data & Reporting Services staff (Warehouse@mit.edu).
A BrioQuery report entitled "Graduate Student Salary Distribution" is available to assist academic administrators in viewing cost distributions for graduate students. A new role, RPT ON DACCA FOR GRAD ADMIN, was recently created in the Roles Database with a corresponding role in the Data Warehouse. Graduate student academic administrators have been given auth orizations to run the report, which is available at: http://web.mit.edu/warehouse/metadata/reports/business_area/payroll.html#592.
Academic administrators may also find other existing reports that will be beneficial, which can be accessed with these new authorizations, at the above address. If you experience difficulties with your authorizations, please send email to email@example.com. If you have any questions about the reports or the data, please send email to firstname.lastname@example.org, and the Data Warehouse team will be happy to assist you.
Changes in Telephone Billing Methodology
Effective July 1, 2007 the Institute is no longer billing for long distance calling. The only charges DLCs will see on their statements or Data Warehouse Reports should be for IPASS or Calling Cards. For more information please read: New Telphone and Network Rate FY08.
Data Warehouse Macintosh OS/9 Users
Macintosh users who have been using BrioQuery running in classic mode (OS/9) to connect to the Data Warehouse were able to use this unsupported configuration prior to last week's upgrade. However, following the upgrade to Oracle 10g, we believe that this option is no longer available.
The recommended ways to connect to the Warehouse from a Macintosh are
- Hyperion Intelligence (Brio Web)
- Parallels Windows emulation software on the Macintosh
(Note that Parallels can be configured so that a few Windows applications can be run concurrently with standard Macintosh applications.)
We are exploring other options, but believe it is unlikely that we will find any other workable solutions. We regret any inconvenience this has caused. If you have any questions or concerns please feel free to email the IS&T/Data an d Reporting Services Team (email@example.com).