The access form can be downloaded from the internet, Just follow the routing instructions.

Transcription

1 1 -- General Information 1.1 Introduction 1.2 Uses and Limitations 1.3 Access Procedures 1.4 Help Resources 1.5 Refresh Schedule 2 -- Table Information 2.1 Table Structure 2.2 Individual Table Descriptions 2.3 Table Joins 2.4 Key Fields 2.5 Views 3 -- Column/Field Information 3.1 Introduction 3.2 Column/Field Definitions 3.3 Column/Field Cross Reference 4 -- Appendix 4.1 Indexes 4.2 Additional Documentation 1 -- General Information.1 Introduction DWRA contains billing data for items ordered through Research Animal Resources. Information in this subject area includes descriptions of items ordered, unit price, total cost and account number..2 Uses and Limitations All tables in the Data Warehouse environment, including those from the Research Animal Resources (DWRA) tables, are intended primarily for institutional planning and projections, and ad hoc reporting purposes. As such they are intended to complement existing production reports. The primary benefit of having data in such an environment is that customers have direct access to the data using state of the art software technology, with the capability to design and run their own reports as the need arises, with minimal cost and effort. 1.3 Access Procedures Research Animal Resources will authorize access to the DWRA data to customers upon receipt of the access request and non-disclosure form. Contact the Helpdesk at or Todd Goerke at (612) for more information. The access form can be downloaded from the internet, Just follow the routing instructions.

2 1.4 Help Resources Because a problem may be due to several factors, it is important to have a variety of resources to turn to in seeking a solution. The chart below lists the available resource units and the kinds of questions each one can handle. In some cases expertise overlaps, so a given answer could be obtained from more than one place. RESOURCE CONTACT TOPICS PHONE Todd Goerke (612) Table access, Table content, Data element definitions, Refresh information (RAR) SQL questions, Performance questions, Important news and updates about table loads and availability To Subscribe: IDEA Listserv (IDEA-L) IDEA Data Warehouse customers have an electronic forum for information sharing about IDEA, the data, the migration, table loads, query and reporting tools, tips, tricks, etc. If you would like to join the IDEA-L Listserv, please follow the steps below. TO SUBSCRIBE To subscribe to the IDEA-L listserv: Data Warehouse Listserv 1)Send an to LISTSERV@umn.edu 2)Leave the subject line blank. 3)Add the following text on the 1st line: SUBSCRIBE IDEA-L your full name Example: SUBSCRIBE IDEA-L John Doe TO SEND IDEA-L Listserv Mail Once you are a member, you may send mail to the listserv using this address: IDEA-L@umn.edu TO UNSUBSCRIBE To unsubscribe to the IDEA-L listserv: 1)Send an to LISTSERV@umn.edu 2)Leave the subject line blank. 3)Add the following text on the 1st line: SIGNOFF IDEA-L Example: SIGNOFF IDEA-L Database access, Refresh information, Client/Server environment, Oracle questions, SQL (612) Help Desk Questions, Response time problems, IDEA Web Page questions, Log in questions/problems, Microcomputer software questions, Network questions (1-HELP).5 Refresh Schedule

3 The table in DWRA is loaded directly from the source twice a month, on the 10th and 25th. Note: The tables can be updated daily for changes Table Information 2.1 Table Structure The Data Warehouse at the University of Minnesota uses a relational database management system (Oracle). In relational data base systems, data are organized into tables of rows and columns. The tables are like files; they contain data with a common "theme". The rows of a table are like records within the file. Each column is like a data field, and represents an element that is common across the rows (records) of a table. 2.2 Individual Table Descriptions DWRA_ITEM This table contains detailed billing data for items ordered through Research Animal Resources. Information in the table includes descriptions of items ordered, unit price, total cost and account number. September 17, 2001, is the data start date for this table. New records are appended twice a month. # COLUMN NAME COLUMN_DESCR TYPE/SIZE TABLE SOURCE COLUMN SOURCE 1 protocol_number Protocol Number C(16) static file wf-bill-stock-id 2 item_description Item Description C(60) static file wf-bill-descr + wf-bill-descr2 3 quantity_shipped Quantity Shipped N(5.0) static file wf-bill-fill-qty 4 unit Unit C(6) static file wf-bill-unit-meas 5 unit_cost Unit Cost N(9.2) static file wf-bill-unit-price 6 ext_amt Extended Amount N(9.2) static file wp_bill_amount 7 trans_cd Transaction Code C(2) static file hardcoded 8 trans_no Transaction Number C(11) static file wf-bill-document-id 9 cust_nbr Customer Number C(6) static file wf-bill-cust 10 area Area C(3) static file wf-bill-area 11 org Organization C(4) static file wf-bill-org 12 suborg Sub org C(2) static file wf-bill-suborg 13 obj Object C(4) static file wf-bill-obj 14 subobj Sub Object C(2) static file wf-bill-subobj 15 order_nbr Order Number C(8) static file wf-bill-ordr-nbr 16 order_date Order Date D(7) static file wf-bill-order-date 17 billing_date Billing Date D(7) static file wf-bill-document-date 18 lcdate Load/Correction Date C(11) calculated calculated 19 acctg_pd Accounting Period C(2) dwfs_tran acctg_pd

4 20 fisc_yr Fiscal Year C(4) dwfs_tran fisc_yr 21 unq_key Unique Key N(22) system assigned system assigned.3 Table Joins First Table Linking Field Linking Field Second Table trans_cd trans_cd dwfs_tran trans_no trans_no dwfs_tran trans_cd trans_cd dwfs_tran_hist trans_no trans_no dwfs_tran_hist 2.4 Key Fields Table Name DWRA_ITEM Key Fields 2.5 Views There are no views Column/Field Information 3.1 Introduction This section describes the specific data elements or fields in the DWRA tables. Section 3.2 is a dictionary listing of all the elements (columns or fields) in alphabetic order. Included are full and short column names, column definitions, type, size, and some code definitions. It is intended to help users select and interpret DWRA data. Section 3.3 is a cross reference associating column names with the tables in which they occur. 3.2 Column/Field Definitions ACCTG_PD Accounting PeriodC2 The period to which accounting transactions apply. Values include: 01 = July 02 = August 03 = September 04 = October 05 = November 06 = December 07 = January 08 = February 09 = March 10 = April 11 = May 12 = June 13> = Closing Periods AREA AreaC3

5 DWFS/DWRA/DWUS: An area denotes the lowest unit of fiscal responsibility. It identifies a particular unit or department within a College or school. Generally, each department or unit has just one Area code. DWPY: An area denotes the lowest unit of fiscal responsibility. It identifies a particular unit or department within a college or school. Generally, each department or unit has just one area code. Setup table: ps_area_tbl (not a PS table, this is a DW created table) To see examples of area for your department, run this query: SELECT fisc_yr, area, area_name30, area_class, area_cls_name30 FROM ps_area_tbl WHERE fisc_yr = '2003' AND area='xxx' Replace the XXX with your area. The ps_area_tbl currently contains fiscal years 1993 to DWSP:Each Area code corresponds to a department or unit. ps_dwsp_room A four character CUFS ID. Area indicates the occupant (department) of all or a portion of the room at the Area level of the CUFS hierarchy. To see a list of areas for space data, run this query: SELECT area, area_name FROM ps_dwsp_cufs ORDER BY area BILLING_DATE Date the data was loaded into the table. CUST_NBR Billing DateD7 Customer NumberC5 Identification number assigned to the customer by University Stores. EXT_AMT Extended AmountN11.2 The total amount for a commodity line, calculated as quantity multiplied by unit cost. FISC_YR Fiscal YearC4 The four character fiscal year, which is any 12-month period for which institution monitors its annual accountability. At the University, this period is July 1? June 30. DWFS and DWRA: A year of business activity. At the University, the fiscal year begins July 1 and ends on June 30. Fiscal years are associated with all general ledger accounting and budget transactions. In many cases, the accounting and budget fiscal years are the same (see bud_fy), except for the size of the field and this data element is the accounting fiscal year. ps_dwy_dist: The fiscal year tied to the cufs_acct_cd. ps_dwpy_vac_sick: The fiscal year tied to the vacation sick record. ITEM_DESCRIPTION Description of the item purchased. LCDATE Item DescriptionC30 Load/Correction DateC11 : The date that the table was loaded from ADM (first and 16th of the month, indicated by lxx/xx/20xx), or loaded from the temp table with corrections from Research Animal Resources (daily, indicated by cxx/xx/20xx). dwus_item: The date that the table was loaded from ADM (first and 16th of the month, indicated by lxx/xx/20xx), or loaded from the temp table with corrections from University Stores (daily, indicated by cxx/xx/20xx). OBJ ObjectC4 An object code identifies the type of expenditure. Object codes are four characters long. For example, there are separate object codes for academic salaries, general operating supplies, and equipment. ORDER_DATE Order DateD7

6 : Date the order was placed with Research Animal Resources. dwus_item: Date the order was placed with University Stores. ORDER_NBR Order NumberC8 Number assigned to the order by University Stores. ORG OrganizationC4 DWFS/DWRA/DWUS: The lowest level of budgetary responsibility and accountability within an area. An organization, when combined with its fund and area, can be thought of as a pool of resources for which an individual or group or program is responsible. An org is not unique until combined with an area. PROTOCOL_NUMBER Protocol NumberC16 QUANTITY_SHIPPED The number of items shipped. SUBOBJ Quantity ShippedN5 Sub ObjectC2 A more detailed description of an expenditure. A sub-object with its related object is required on every accounting transaction. SUBORG Sub orgc2 User defined divisions within an organization. TRANS_CD Transaction CodeC2 The code which identifies the transaction. For example, EB = Expense Budget, PV = Payment Voucher. NOTE: Only the first two letters of a 3-letter transaction code will appear on the table. ie. PVA will appear as PV, POT will appear as PO. TRANS_NO Transaction NumberC11 DWFS: The number assigned to a document. The first three characters should identify the area originating the document. DWPY: This is the CUFS transaction number. The transactions are all journal vouchers. DWRA: The number assigned to a document. The first three characters will usually be 'RAR' indicating the transaction went through Research Animal Resources. DWUS: The number assigned to a document. The first three characters will usually be 'STR' indicating the transaction went through the University Stores. UNIT UnitC4 The user defined code for abbreviating a standard unit of measure. UNIT_COST Unit CostN9.3 The unit cost of the goods purchased, from the purchase order document. UNQ_KEY Unique KeyN A sequentially assigned number that makes each row in this table unique. 3.3 Column/Field Cross Reference Column Name acctg_pd area billing_date cust_nbr ext_amt fisc_yr item_description lcdate obj order_date Table Name

7 order_nbr org protocol_number quantity_shipped subobj suborg trans_cd trans_no unit unit_cost unq_key -- Appendix.1 Indexes Table Name Index Column Name DWRA_ITEM DWRA_ITEM_BX7 FISC_YR DWRA_ITEM DWRA_ITEM_X1 TRANS_CD DWRA_ITEM DWRA_ITEM_X2 TRANS_NO DWRA_ITEM DWRA_ITEM_X3 AREA DWRA_ITEM DWRA_ITEM_X4 ORG DWRA_ITEM DWRA_ITEM_X5 OBJ DWRA_ITEM DWRA_ITEM_X6 SUBOBJ.2 Additional Documentation Data Warehouse Home Page: OIT Data Security: OIT Policies, Standards, and Guidelines: Training Services Home Page: