Changes to DW Data Set Dictionaries 

advertisement
Changes to DW Data Set Dictionaries
As of August 9, 2011, the format of the Data Warehouse data dictionaries is changing to prepare for future Data
Warehouse data sets. There are minor changes to both the data model diagrams and text portions of the dictionaries.
This document provides a detailed explanation of the changes. For a summarized version, see Summary of Data
Dictionary Changes. Here is a sample of the new data dictionary format.
Note: These changes do not apply to the Development data set or any of the legacy data sets.
Differences in the data model diagrams:
A) Join lines will now connect directly to the table/entity.
i) The brackets previously built around multiple elements to illustrate multiple element joins no longer exist.
ITS is using a new modeling tool which imposes an industry standard.
ii) Join lines will no longer start and end at the element(s) involved in the join. Instead, they will start and end
at table borders.
iii) For detailed information about joins, see description of joins between tables (macro‐enabled Excel file).
B) Previously tables/views with a different refresh rate from the rest of the data set or that were owned by a different
schema were depicted with dashed lines outlining them. They now have a text note above them.
C) Views are now indicated by dashed lines. See B) above for additional implications of this change. The view outlines
are also rounded.
D) The elements(s) that make up the key for a table are now denoted by (PK) following the element name rather than
having the element name underlined.
E) Views no longer indicate which element(s) make up the key.
F) Tables/views that are abbreviated to save space may now show additional elements beyond the table key
element(s) and those elements used in joins. This is because the new modeling tool displays the table/view
elements in physical order. The only way to minimize the table/view display box to hide elements that are listed
after those needed as keys or as join elements.
G) Secured tables were previously indicated by a thick border. They now have a text note above them.
H) Join lines are consolidated when:
a. The fields used in the joins are exactly the same for all tables being considered.
AND
b. The optionality of the joins is the same for all tables being considered
AND
c. The cardinality (one‐to‐many, many‐to‐many) is the same for all tables being considered
I) Minor rearranging of tables on a model page may have occurred to reduce the crossing of join lines.
8/1/2011
1
Changes to DW Data Set Dictionaries
Old model format
C
B
E
A
F
G
H
D
8/1/2011
2
Changes to DW Data Set Dictionaries
New model format
C
B
Check Status
CURR_ACCOUNT_VW
ACCOUNT
CNVCHARTFD
JRNL_HEADER
(See Page 8)
SHORTCODE (PK)
SHORTCODE_DESCR50
SHORTCODE_STATUS
JOURNAL_ID (PK)
JOURNAL_DATE (PK)
CURR_FUND_VW
SHORTCODE_STATUS_DESCRSHORT
FUND_CODE
(See Page 4)
FUND_CODE
DEPTID
PROGRAM_CODE
CLASS
PROJECT_GRANT
(See Page 8)
CURR_FN_DEPT_VW
(See Page 20)
DEPTID
(See Page 8)
A
REV_EXP_JRNL_LN_VW
JOURNAL_ID
JOURNAL_DATE
JOURNAL_LINE
ACCOUNT
CURR_PROGRAM_VW
PROGRAM_CODE
REV_EXP_ACT_LEDGER
E
ACCOUNT (PK)
(See Page 8)
FUND_CODE (PK)
DEPTID (PK)
FUND_CODE
DEPTID
PROGRAM_CODE
PROGRAM_CODE (PK)
CLASS (PK)
PROJECT_GRANT (PK)
CLASS
PROJECT_GRANT
JRNL_LN_REF
CURR_CLASS_CF_VW
CLASS
FISCAL_YEAR (PK)
ACCOUNTING_PERIOD (PK)
DOLLAR_AMOUNT
STATISTIC_AMOUNT
DOLLAR_AMOUNT
JOURNAL_LINE_DESCR
STATISTIC_AMOUNT
FISCAL_YEAR
ACCOUNTING_PERIOD
(See Page 8)
CURR_PROJECT_GRANT_VW
PROJECT_GRANT
PROJECT_GRANT_EFFDT
PROJECT_GRANT_EFF_STATUS
PROJECT_GRANT_TITLE
CAL_DETP_TBL
FISCAL_YEAR (PK)
JRNL_LN_RECON_FLG
JRNL_LN_RECON_LAST_UPDATE_BY
JRNL_LN_RECON_LAST_UPDATE_DT
PROJECT_GRANT_TYPE
MINORITY_SUB
PROJ_GRANT_STATUS
ACCOUNTING_PERIOD (PK)
CAL_MONTH_CODE
CAL_MONTH_DESCR
CAL_YEAR
JRNL_LN_RECON_NOTE
H
PROJECT_GRANT_START_DT
PROJECT_GRANT_END_DT
INITIAL_FUND_CODE
ACCTG_PERIOD_BEGIN_DT
ACCTG_PERIOD_END_DT
F
INITIAL_DEPTID
(See Page 8)
PERSONAL_DATA
EMPLID (PK)
G
(See Page 8)
Secured Table
ENDOWMENT_SHARE
FUND_CODE (PK)
DEPTID (PK)
CLASS (PK)
PRJ_GRT_RPTS
PROJECT_GRANT (PK)
MERCHANT_AUTHORIZED_USER
PROJ_GRT_RPT_TYPE (PK)
MERCHANT_NUM (PK)
REPORT_FREQ (PK)
EMPLID (PK)
MERCHANT_AUTH_LAST_UPDATE_BY
MERCHANT_AUTH_LAST_UPDATE_DTTM
PROJ_GRT_RPT_TYPE_DESCR
PROJ_GRT_RPT_TYPE_DESCRSH
PROJECT_GRANT_EFFDT
QTR_END_DT (PK)
(See Page 6)
Secured Table
ENDOW_DIST
REPORT_MONTH
RPT_DAYS_CMPL
USER_CERTIFICATION
EMPLID (PK)
CERT_TYPE (PK)
CERT_DESCR300
CERT_EXPIRE_DT
PRJ_GRT_RPDTL
PROJECT_GRANT (PK)
PROJ_GRT_RPT_TYPE (PK)
REPORT_FREQ (PK)
PROJ_GRT_ACT_ENDDT (PK)
PROJ_GRT_RPT_TYPE_DESCR
CERT_LAST_ATTEMPT_DT
CERT_LAST_ATTEMPT_RSLT
FUND_CODE (PK)
DEPTID (PK)
D
CLASS (PK)
ENDW_DIST_EFFDT (PK)
ENDW_DIST_LN (PK)
PROJECT_GRANT_EFFDT
PROJ_GRT_RPT_DUE_DT
PROJ_GRT_RPT_CONTACT_CD
PROJ_GRT_RPT_CNTCT_EMPLID
PROJ_GRT_RPT_CNTCT_NAME
PROJ_GRT_RPT_STAT
ENDOWMENT_EFF_STATUS
ENDW_DIST_FUND_CODE
ENDW_DIST_DEPTID
ENDW_DIST_CLASS
ENDW_DIST_PROGRAM_CODE
ENDW_DIST_PROJECT_GRANT
Legend
PK
(See Page 6)
=
Key Field
=
One to One
=
One to Many
GLSTATUS
=
Many to Many
DW_DATA
=
Outer Join
EXTRACT_DT
LOAD_DT
DW_OWNER
8/1/2011
PROJ_GRT_RPT_TYPE_DESCRSH
REPORT_FREQ_DESCR
Secured Table
=
Secured Table
Check Status
=
Check Status Table
for refresh date
=
View
PROJ_GRT_RPT_STAT_DESCR
PROJ_GRT_RPT_STAT_DESCRSH
PROJ_GRT_BILLD_AMT
PROJ_GRT_RPT_STRT_DT
PROJ_GRT_SNT_DEPT_DT
PROJ_GRT_RET_DEPT_DT
PROJ_GRT_GVN_SUPR_DT
PROJ_GRT_APPR_SUPR_DT
PROJ_GRT_COMPLT_DT
PROJ_GRT_EXT_REQST
PROJ_GRT_EXT_REQST_DESCR
PROJ_GRT_EXT_REQST_DESCRSH
PROJ_GRT_RPT_COMMENT
3
Changes to DW Data Set Dictionaries
Differences in the text portion of the data dictionaries:
1) Wrapping of table, view, and element names is automatic instead of manual.
2) For elements used in multiple data sets, a row will display for each data set in which they are used (i.e., logical name,
definition, examples), rather than being combined into one row. Elements used in multiple tables within the same
data set will continue to be combined into one row.
3) The text “Examples of valid values:” will display in every cell in the “Examples of Valid Values” column.
8/1/2011
4
Changes to DW Data Set Dictionaries
Old Dictionary Format
Physical Element Name
ACCOUNT_GRP_ISR_
BUDGET
Logical Element
Name
Account Group
Institute for Social
Research (ISR)
Budget Code
Format
Type
Character
Format Data Set
Length
6
M_GLDW1
Table Locations
Account Group
Sponsored
Programs Volume
Research
Description
Class Code
Character
30
M_GLDW1
ACCOUNT_TBL
CURR_ACCOUNT_VW
R
A textual description of the code
used to group accounts by
sponsored research.
Character
5
M_SMDW2
PLANT_WORKREQUEST_
DETAIL
RM_ORA_CHARTFIELDS
SVY_ORA_CHARTFIELDS
R
M_GLDW1
PROJECT_GRANT_TBL
CLASS_CF_TBL
A code used to group related
activities directed towards the
accomplishment of a set of
common identifiable objectives or
purposes.
ACCOUNT_TBL
CURR_ACCOUNT_VW
1
ACCOUNT_GRP_SP_VOL_
RES_DESCR
CLASS
2
8/1/2011
Securit Element Definition
y Code
R
A code used to associate
expense accounts with higherlevel budgetary accounts used for
ISR Budget. Note: sourced from
the BUD_TRAN_ACCT_ISR tree.
Examples of Valid
Values
911100 = Administrative
Salaries;
911550 =
Respondents/Subjects;
911900 = Research
Supplies & Services
Salaries and Wages;
Transfers and
Distributions;
Indirect Cost
11000 = General
Academic Instruction;
21000= Departmental
Research;
72000 = Utilities;
1100x = Gen Acad InstrICRX
5
3
Changes to DW Data Set Dictionaries
New Dictionary Format
Physical Element Name
Logical Element
Name
ACCOUNT_GRP_ISR_BUDG Account Group
ET
Institute for Social
Research (ISR)
Budget Code
Format
Type
Character
Format Data Set
Length
6
M_GLDW1
Table Locations
ACCOUNT_TBL
1
ACCOUNT_GRP_SP_VOL_R Account Group
ES
Sponsored
Programs Volume
Research Code
Character
20
M_GLDW1
ACCOUNT_TBL
Security Element Definition
Code
R
A code used to associate expense
accounts with higher-level
budgetary accounts used for ISR
Budget. Note: sourced from the
BUD_TRAN_ACCT_ISR tree.
R
2
Examples of Valid
Values
"Examples of Valid
Values:"911100 =
Administrative Salaries;
911550 =
Respondents/Subjects;
911900 = Research
Supplies & Services
A code used to group accounts by "Examples of Valid
Values:"SAL_AND_WAG
sponsored research. Note:
ES = Salaries and Wages;
sourced from the
TRANSFERS_AND_DIST
SP_VOL_RESRCH_ACCT tree.
= Transfers and
Distributions;
INDIRECT_COST =
Indirect Cost
"Examples of Valid
A code used to group related
Values:"11000 = General
activities directed towards the
Academic Instruction;
accomplishment of a set of
common identifiable objectives or 21000= Departmental
Research; 72000 =
purposes.
Utilities; 1100x = Gen
Acad Instr-ICRX
"Examples of Valid
A code used to group related
Values:"11000 = General
activities directed towards the
Academic Instruction;
accomplishment of a set of
common identifiable objectives or 21000= Departmental
Research; 72000 =
purposes.
Utilities; 1100x = Gen
Acad Instr-ICRX
3
CLASS
Class Code
Character
5
M_GLDW1
CLASS_CF_TBL
PROJECT_GRANT_TBL
R
CLASS
Class Code
Character
5
M_SMDW2
PLANT_WORKREQUEST_
DETAIL
RM_ORA_CHARTFIELDS
SVY_ORA_CHARTFIELDS
R
8/1/2011
6
Download