Skip to main content
If you are a Planview customer, sign in to enable additional content.
Planview Customer Success Center

Data Content Changes for Planview Enterprise One release 16 – PRM to Planview Enterprise One release 17 – PRM

You are viewing content for Planview® Enterprise One release – Portfolio and Resource Management.

Database Changes from Planview Enterprise One release 16 – PRM to Planview Enterprise One release 17 – PRM

New Primary Structures

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

Renamed Structures

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

New Global Options

Option Number Description  

1753

Database name: Hide unaddressed requirements on the RMA and Requirements to Fill tile
User interface name: Hide Unaddressed Requirements Filter

2408

Database name:

Enable Indirect Access to Configured Screen Lifecycle Steps

User interface name: Enable Indirect Access to Configured Screen Lifecycle Steps

Removed Global Options

Option Number Description

1730

Include Allocation Effort Into Baselines

1731

Include Reserve Effort Into Baselines

1732

Include Requirement Effort Into Baselines

New Database Tables

The following tables are new in Planview Enterprise One release 17 – PRM:

FM_PERIOD_TYPE

PRM_RESET

ST_TEAM_AUTHORIZATION

TEAM_AUTHORIZATION

FM_PERIOD_TYPE

This table is used for labeling of period types. Only three levels of period types are allowed. The max (level number) represents the smallest time frame. That is, level number 3 represents months, whereas level number 2 represents quarters containing months.

Key

Field Name

Description

Type

Length

Required

pk,1 ak1,1

calendar_id

References the FM_CALENDAR.calendar_id to which the financial periods belong

(b)int

 

not null

pk,2

period_type

Designates the type of financial period

Example values:

  • Month
  • Quarter
  • Year

vc

10

not null

 

period_label

Description of period level

vc

50

not null

ak1,2

level_number

Only three levels of period types will be allowed

(s)int

 

not null

 

last_updated_on

The date and time for when the record was last updated

date

 

not null

 

last_updated_by

ID of user who last updated the record; that is, IP_USER.user_name

vc

10

not null

PRM_RESET

This table describes the restart of Planview Enterprise One from the application IIS based on the PRM_RESET feature for only an administrator role. Each server or cluster will individually log its IIS resets to PRM_RESET. If the supervising Microsoft Windows service encounters an exception or failure, it will be logged to the Windows Event log according to our usual conventions. PV_PROCESS_LOG is diagnostic in nature, so each server will log its own event, server name, when it happened, and who requested it and when that request was made.

PRM_RESET will have only one entry, which is the last request. The Windows event log will have record service, start, finish, and exception errors.

Key

Field Name

Description

Type

Length

Required

pk,1

last_requested_on

Date of last request

date

 

not null

 

last_requested_by

User who issued the request; friom IP_USER

vc

10

not null

ST_TEAM_AUTHORIZATION

This table provides the ability to baseline team information.

Key

Field Name

Description

Type

Length

Required

pk,1

baseline_code

Baseline code generated from sequences where sequence = 'baselinecatalog'

vc

10

not null

pk,2

planning_code Work entity; from the PLANNING_ENTITY table. For this field's value, the description can be found in the STRUCTURE table.

vc

10

not null

pk,3

team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams.

vc

10

not null
  start_date
  • Date: Inclusive this date

  • Null: Ignore start_date as criteria; that is, apply this Create/Delete from the beginning of time

The authorization is valid since this date.

date    
  finish_date
  • Date: Inclusive this date
  • Null: Ignore finish_date as criteria; that is, apply this Create/Delete to the end of time

The authorization is valid until this date.

date    
  last_updated_by ID of user who last updated the record; that is, IP_USER.user_name

vc

10

not null
  last_updated_on The date and time for when the record was last updated

vc

10

not null

TEAM_AUTHORIZATION

This table provides the ability to authorize a team.

Key

Field Name

Description

Type

Length

Required

pk,1

planning_code Work entity; from the PLANNING_ENTITY table. For this field's value, the description can be found in the STRUCTURE table.

vc

10

not null

pk,2

team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams.

vc

10

not null

 

start_date
  • Date: Inclusive this date

  • Null: Ignore start_date as criteria; that is, apply this Create/Delete from the beginning of time

The authorization is valid since this date.

date    

 

finish_date
  • Date: Inclusive this date
  • Null: Ignore finish_date as criteria; that is, apply this Create/Delete to the end of time

The authorization is valid until this date.

date    

 

last_updated_by ID of user who last updated the record; that is, IP_USER.user_name

vc

10

not null

 

last_updated_on The date and time for when the record was last updated

vc

10

not null

Data Type Changes to Existing Database Tables

The following changes apply only in a SQL Server environment.

Table Field Previous Type Length New Type Length Required

LONG_TEXT

line_text

vc 4000

nvc

4000

 

LONG_TEXT_A

line_text

vc 4000

nvc

4000

 

ST_LONG_TEXT

line_text

vc 4000

nvc

4000

 

Null Changes to Existing Database Tables

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

New Fields Added to Existing Database Tables

Table Field Description Type Length Required

ALLOCATION

team_code

From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams.

vc

10

 

COLUMN_ENTITY

last_updated_on

The date and time for when the record was last updated

date

 

 

COLUMN_SET_COL

last_updated_on

The date and time for when the record was last updated

date

 

 

COLUMN_SET_ROLE

last_updated_on

The date and time for when the record was last updated

date

 

 

EPM_STRATEGY

strategy_type

Because strategic planning is the solution for "WRM", this field extends the definition of what is included in that. As most organizations move to Agile development, they have found they manage concepts at different levels throughout the organization. As an organization turns strategy into action, it might be done through a theme rather than a program. This solution allows organizations to clearly define "program" in this new world where some are initiatives, themes, or programs, while also having business cases to fund and track value to market and release a product as projects and epics are executed on to develop and obtain the value.

By adding more flexibility for organizations to define the strategies they manage, they can create a more encompassing portfolio of all types of strategic action. This Planview-provided alternate structure must be associated to the Strategy structure and controls the labels for the lowest level of that structure. This alternate structure is similar to the Outcome Type alternate structure. This alternate structure has the following default values: Program, Initiative, Theme.

vc

10

 

EXT_INTERFACE

last_updated_on The date and time for when the record was last updated date

 

 

FEATURE_SET last_updated_on The date and time for when the record was last updated date    
FM_BUDGET note

Notes made at the entity level of the Financial Planning Detail screen. Such notes support entering information related to the overall plan (at the project level) and not just a line, which helps users track details, such as edits made as result of a change request, or who approved it and why, etc.

vc 4000  
FM_COLUMN_EXPRESSION

respect_icp_horizon_ind

Flag that controls whether a financial column in investment and capacity planning respects or ignores the planning horizon of a Planning portfolio.

vc 1  
FM_PERIOD fm_period_desc This description is generated, but a user can overwrite it. It must be unique within the same calendar and year. vc 50  

IP_USER

 

 

 

timed_invite_ind

Timed invitation indicator; Y indicates the relevant user is to be logged in only via a timed invitation; default is N

vc

1

 

invite_expires_on

This is the expiration time of the relevant invitation. If the invited user does not respond to the invitation before that time, the invitation is invalid.

date

 

 

invite_duration_hrs

Duration of usage: indicates how many hours the relevant user can access the application following the initial acceptance of the invitation

(s)int

2

 

inv_session_expires_on

Expiration time of usage: set at point of acceptance; adding Duration of usage to current time

date

 

 

IP_USER_A

 

 

 

timed_invite_ind

Timed invitation indicator; Y indicates the relevant user is to be logged in only via a timed invitation; default is N

vc

1

 

invite_expires_on

This is the expiration time of the relevant invitation. If the invited user does not respond to the invitation before that time, the invitation is invalid.

date

 

 

invite_duration_hrs

Duration of usage: indicates how many hours the relevant user can access the application following the initial acceptance of the invitation

(s)int

2

 

inv_session_expires_on

Expiration time of usage: set at point of acceptance; adding Duration of usage to current time

date

 

 

LIST_ITEM team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams. vc 10  

NOTIF_MAILER_PROC

last_updated_on The date and time for when the record was last updated date

 

 

NOTIF_QUEUE

last_updated_on The date and time for when the record was last updated date    

NOTIF_SCANNER_PROC

last_updated_on The date and time for when the record was last updated date    

ORG_RES_MODEL

last_updated_on The date and time for when the record was last updated date    

PARAM_EXCEPTION

last_updated_on The date and time for when the record was last updated date    

PARAM_PREFERENCE

last_updated_on The date and time for when the record was last updated date    

PORTAL

last_updated_on The date and time for when the record was last updated date    

PORTAL_INFO

last_updated_on The date and time for when the record was last updated date    

PORTAL_MEMBER

last_updated_on The date and time for when the record was last updated date    
PORTLET last_updated_on The date and time for when the record was last updated date    
PORTLET_CHART_PARAM last_updated_on The date and time for when the record was last updated date    
PORTLET_PARAM last_updated_on The date and time for when the record was last updated date    

PORTLET_RULE

last_updated_on The date and time for when the record was last updated date    
PRODUCT_WORK

last_updated_on

The date and time for when the record was last updated

date

 

 

last_updated_by

ID of user who last updated the record; that is, IP_USER.user_name

vc

10

 
RELEASE last_updated_on The date and time for when the record was last updated date    
RESERVE team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams. vc 10  
ROLE_DEFINITION last_updated_on The date and time for when the record was last updated date    
SEARCH_SET last_updated_on The date and time for when the record was last updated date    
ST_ALLOCATION team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams. vc 10  
ST_LIST_ITEM team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams. vc 10  
ST_RESERVE team_code From the Teams alternate structure. That alternate structure gives resource managers and administrators the ability to assign a resource to one or more teams, such as those used to develop Agile projects. The Teams alternate structure replaces the Obs structure, which was used in previous releases to define teams. vc 10  
TILE_ENTITY last_updated_on The date and time for when the record was last updated date    
TILE_PARAM last_updated_on The date and time for when the record was last updated date    
TILE_PREFERENCE last_updated_on The date and time for when the record was last updated date    
URL_WHITELIST last_updated_on The date and time for when the record was last updated date    
USER_PASSWORD last_updated_on The date and time for when the record was last updated date    
USER_PERIOD last_updated_on The date and time for when the record was last updated date    
VIRTUAL_COLUMN last_updated_on The date and time for when the record was last updated date    

Field Length Changes to Existing Database Tables

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

Data Mart Changes from Planview Enterprise One release 16 – PRM to Planview Enterprise One release 17 – PRM

New Data Mart Tables

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

New Data Mart Views

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

Data Type Changes to Existing Data Mart Tables

The following changes apply only in a SQL Server environment.

Table Field Previous Type Length New Type Length Required

DM_LONG_TEXT

line_text

vc 4000

nvc

4000

 

DM_NOTES_DIM

line_text

vc 4000

nvc

4000

 

DM_WORK_REQUEST_DIM

request_ldesc vc 4000

nvc

4000

 

Null Changes to Existing Data Mart Tables

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

New Fields Added to Existing Data Mart Tables

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

Field Length Changes to Existing Data Mart Tables

Planview Enterprise One release 17 – PRM does not include changes relevant to this section.

Unchanged Data Content

Planview Enterprise One release 17 – PRM does not include changes that impacted the use of Datasets.

Note: This article does not apply to this release. For information about database changes relevant to release 1615, click the link listed below. Otherwise, use the release selector at the top of this article to choose a different release.