The following table illustrates the risks data field mapping when upgrading from P6 EPPM database (7.0 or 7.0 service packs).
Note: Some fields will migrate to text fields instead of new fields because certain fields no longer correspond. The new text fields are noted below.
Risks Fields Migration Table
P6 EPPM database (version 7.0 and 7.0 service packs) Risks Fields | P6 EPPM Risks Field |
|---|---|
Risk Id | id |
risk_name | name |
risk_descr | description |
status_code | status |
risk_type_id | category_id |
risk_control | notes |
table_name | table_name |
wbs_id | cause (with heading 'Applies to WBS' <WBS name>) |
rsrc_id | cause (with heading 'Applies to Resource' <resource name>) |
obs_id | cause (with heading 'Responsible Manager' <OBS name>) |
priority_type | cause (with heading 'Priority' <priority type>) |
add_date | cause (with heading 'Date Identified' <add_date in mmm-dd-yyyy format >) |
impact_date | cause (with heading 'Date Identified' <add_date in mmm-dd-yyyy format >) |
prbly_pct | cause (with heading 'Probability' <prbly_pct>) |
impact_work_qty | cause (with heading 'Impact - Labor Units' <impact_work_qty> - 2 decimals) |
impact_equip_qty | cause (with heading 'Impact - Nonlabor Units' <impact_equip_qty> - 2 decimals) |
impact_mat_qty | cause (with heading 'Impact - Material Units' <impact_mat_qty> - 2 decimals) |
Impact_expense_cost | cause (with heading 'Impact - Expenses' <impact_expense_cost> - 2 decimals) |