| Data element |
Definition |
HISTORY_STATUS
Indexed - yes
Format - char (1)
May be null? yes |
A one-character code indicating whether the record stores the latest
(current) status for the increment, or an
earlier (historical) status for the increment.
Values:
C The record stores the current (latest) status
for the increment
H The record stores a historical (past) status
for the increment
|
INCREMENT_NUMBER
Indexed - yes
Format - varchar2(6)
May be null? no |
A sequence number uniquely identifying the increment within the proposal.
Each proposal (INSTITUTION_NO) has an INCREMENT_NUMBER ‘1’.
The maximum INCREMENT_NUMBER for a proposal is the number of increments
that apply to that proposal.
There is one PENNERA_INCR_STAT_HIST record per proposal (INSTITUTION_NO or
PROP_NO), per INCREMENT_NUMBER, per INCR_STAT_SEQUENCE_NO.
Examples: 3, 11
Values:
List of values not available
PennERA source (assuming the proposal record has been opened in the Proposal
Tracking module): Budget; Awarded; Award Information section; the row
number for the increment. (The first row in the Award Information section
is for INCREMENT_NUMBER 1, the second row is for INCREMENT_NUMBER 2, etc.)
|
INCREMENT_STATUS
Indexed - no
Format - varchar2 (24)
May be null? yes |
The status of the increment, per the sponsor’s response, effective
as of the INCREMENT_STATUS_DATE.
Values:
Advance Account--the funding for the increment is
an advance provided by the department administering
the project, in expectation of an award from the sponsor
Awarded--the funding for the increment is an award provided
by the sponsor
Future--the sponsor has notified the University
of its intent to award funding for the increment,
which applies to a future period (“out year”)
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget; Awarded; Award Information section;
the row for the increment (the first row in the Award Information section
is for INCREMENT_NUMBER 1, the second row is for INCREMENT_NUMBER 2, etc.);
Status link; below the Add section; the row
for the increment status history record; the
value shown in the
Status column
|
INCREMENT_STATUS_DATE
Indexed - no
Format - date
May be null? yes |
The date when the INCREMENT_STATUS went into effect.
In addition to the INCREMENT_STATUS_DATE, PennERA stores the RECORDED_DATE
(the date the increment status history record was created). When an
increment status history record is being created by a PennERA user, the
values
for the INCREMENT_STATUS_DATE and the RECORDED_DATE have the system date
as their default value. Before the record is saved, the INCREMENT_STATUS_DATE
is edited (if necessary) to reflect the date when the INCREMENT_STATUS
went into effect. The value of the RECORDED_DATE, however, is always
the date when the increment status history record was created. For example,
if an
increment was Awarded as of 10/30/2003, and that change in status
was recorded in PennERA on 11/13/2003, the increment status history record's
INCREMENT_STATUS_DATE is 10/30/2003, and its RECORDED_DATE is 11/13/2003.
The INCREMENT_STATUS_DATE always has a non-null value, but some increment
status history records have a null value for the RECORDED_DATE.
Example: 10/30/2003
Values:
List of values not available PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget; Awarded; Award Information section;
the row for the increment (the first row in the Award Information section
is for INCREMENT_NUMBER 1, the second row is for INCREMENT_NUMBER 2,
etc.); Status link; below the Add section; the row for the increment
status history record; the value shown in the Date column
|
INCREMENT_STATUS_FY
Indexed - no
Format - char (4)
May be null? yes |
The fiscal year at Penn in which the INCREMENT_STATUS_DATE falls.
Penn's fiscal year begins July 1 of one calendar year and ends June 30
of the next calendar year.
Example: 2004 (for an increment status history record whose
INCREMENT_STATUS_DATE is 10/30/2003)
Values:
List of values not available
|
INCR_STAT_SEQUENCE_NO
Indexed - yes
Format - number (10)
May be null? no |
A sequence number uniquely identifying the status history record within
the proposal and increment to which it applies. Each proposal and increment
(INSTITUTION_NO and INCREMENT_NUMBER) has an INCR_STAT_SEQUENCE_NO ‘1’.
The maximum INCR_STAT_SEQUENCE_NO for a proposal and increment is the
number of status history records for that increment (which applies to
that proposal).
There is one PENNERA_INCR_STAT_HIST record per proposal (INSTITUTION_NO
or PROP_NO), per INCREMENT_NUMBER, per INCR_STAT_SEQUENCE_NO.
Examples: 1, 5
Values:
List of values not available
PennERA's Proposal Tracking module does not display the increment
status sequence number.
|
INSTITUTION_NO
Indexed - yes
Format - char (8)
May be null? no |
The eight-digit sequence number used by the University to uniquely identify
the proposal whose increment status history is tracked by this PENNERA_INCR_STAT_HIST
record. Note that the value for INSTITUTION_NO includes leading zeroes.
Records with an
INSTITUTION_NO less than or equal to 05017400 were converted from the
Research Services System (RSS, the system used to track proposals and
awards before October 14, 2003). Other records are for proposals created
in PennERA.
There are two different unique identifiers for a proposal: INSTITUTION_NO
and PROP_NO. INSTITUTION_NO is used by the University. PROP_NO is used
internally by the PennERA system. For a given record, INSTITUTION_NO
will not have the same value as PROP_NO. While either one may be used
when joining PennERA Proposals tables, INSTITUTION_NO is the one recommended
for display in reports.
There is one PENNERA_INCR_STAT_HIST record per proposal (INSTITUTION_NO
or PROP_NO), per INCREMENT_NUMBER, per INCR_STAT_SEQUENCE_NO.
Example: 00216424
Values:
List of values not available
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): any screen for the proposal; the Proposal
Header (unlabelled, stationary section at the top of the screen); the
number in the Proposal box in the upper right corner of the screen |
LAST_EXTRACT_DATE
Indexed - no
Format - date
May be null? no |
The date this increment status record was extracted from the
PennERA Proposal Tracking system and loaded into the Warehouse.
Example: 12/16/2003
Values:
List of values not available. |
MODIFIED_BY
Indexed - no
Format - char (8)
May be null? yes |
The PennID of the person who entered (or last modified) the increment
status record by hand. The name of the person can be found in the PENNERA_PEOPLE
table.
If MODIFIED_BY
is null, the increment status record was entered via a program, rather
than by hand.
Example: ‘10022206’
Values:
List of values not available.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget; Awarded; Award Information section;
the row for the increment (the first row in the Award Information section
is for INCREMENT_NUMBER 1, the second row is for INCREMENT_NUMBER 2,
etc.); Status link; below the Add section; the row for the increment
status history record; the PennID of the person whose
name is shown in the Recorded By column
(the PennID is not shown) |
PROP_NO
Indexed - yes
Format - varchar2 (20)
May be null? no
|
The 10-digit sequence number used internally by the PennERA system to
uniquely identify the proposal whose increment status history is tracked
by this PENNERA_INCR_STAT_HIST record. Note that the value for PROP_NO
includes leading zeroes.
There are two different unique identifiers for a proposal: INSTITUTION_NO
and PROP_NO. INSTITUTION_NO is used by the University. PROP_NO is used
internally by the PennERA system. For a given record, INSTITUTION_NO
will not have the same value as PROP_NO. While either one may be used
when joining PennERA Proposals tables, INSTITUTION_NO is the one recommended
for display in reports.
There is one PENNERA_INCR_STAT_HIST record per proposal (INSTITUTION_NO
or PROP_NO), per INCREMENT_NUMBER, per INCR_STAT_SEQUENCE_NO.
Example: ‘0000000217’
Values:
List of values not available
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): any screen for the proposal; the Proposal
Header (unlabelled, stationary section at the top of the screen); the
PROP_NO for the INSTITUTION_NO (INSTITUTION_NO is the number in the
Proposal box in the upper right corner of the screen; PROP_NO is not
shown)
|
RECORDED_DATE
Indexed - no
Format - date
May be null? yes |
The date when the increment status history record was created in PennERA.
In addition to the RECORDED_DATE, PennERA stores the INCREMENT_STATUS_DATE
(the date the status went
into effect). When an increment
status history record is being created by a PennERA user, the values
for the INCREMENT_STATUS_DATE and the RECORDED_DATE have the system date
as their default value. Before the record is saved, the INCREMENT_STATUS_DATE
is edited (if necessary) to reflect the date when the INCREMENT_STATUS
went into effect. The value of the RECORDED_DATE, however, is always
the date when the increment status history record was created. For example,
if an increment was Awarded as of 10/30/2003, and that change in status
was recorded in PennERA on 11/13/2003, the increment status history record's
INCREMENT_STATUS_DATE is 10/30/2003, and its RECORDED_DATE is 11/13/2003.
The INCREMENT_STATUS_DATE always has a non-null value, but some increment
status history records have a null value for the RECORDED_DATE.
Example: 11/13/2003
Values:
List of values not available.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget; Awarded; Award Information section;
the row for the increment (the first row in the Award Information section
is for INCREMENT_NUMBER 1, the second row is for INCREMENT_NUMBER 2,
etc.); Status link; below the Add section; the row for the increment
status history record; the value shown in the Recorded Date column |
