Data element |
Definition |
INSTITUTION_NO
Indexed - yes
Format - char (8)
May be null? yes |
The eight-digit sequence number used by the University to uniquely identify
the proposal to which the request applies. 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_REQUEST record per proposal (INSTITUTION_NO or
PROP_NO) per REQUEST_NUMBER. (Though PERIOD_NUMBER is part of the physical
primary key for the PENNERA_REQUEST table, it is not part of the logical
primary key for the table.)
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 on the first line of the Proposal Header
text |
LAST_EXTRACT_DATE
Indexed - no
Format - date
May be null? yes |
The date this request record was extracted from the PennERA Proposal
Tracking system and loaded into the Warehouse.
Example: 10/28/2003
Values:
List of values not available.
|
PAR_PI_PRIACADAPPT_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
This data element is reserved for future use.
|
PAR_PI_PRIACADAPPT_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
This data element is reserved for future use.
|
PARENT_PI_ERA_PRI_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
This data element is reserved for future use. |
PARENT_PI_ERA_PRI_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
This data element is reserved for future use.
|
PARENT_PI_HOME_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
This data element is reserved for future use.
|
PARENT_PI_HOME_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
This data element is reserved for future use. |
PARENT_PI_INV_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
This data element is reserved for future use. |
PARENT_PI_INV_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
This data element is reserved for future use. |
PARENT_PI_PENN_ID
Indexed - no
Format - char (8)
May be null? yes |
This data element is reserved for future use. |
PARENT_PI_PRI_APPT_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
This data element is reserved for future use. |
PARENT_PI_PRI_APPT_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
This data element is reserved for future use. |
PARENT_PROP_RESP_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
This data element is reserved for future use. |
PARENT_PROP_RESP_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
This data element is reserved for future use. |
PERIOD_NUMBER
Indexed - yes
Format - number (10)
May be null? no |
A sequence number uniquely identifying the budget period within the
proposal to which the request applies. Each proposal (INSTITUTION_NO)
has
a PERIOD_NUMBER ‘1’. The maximum PERIOD_NUMBER for a proposal
is the number of budget periods for that proposal.
There is one PENNERA_REQUEST record per proposal (INSTITUTION_NO or
PROP_NO) per REQUEST_NUMBER. (Though PERIOD_NUMBER is part of the physical
primary key for the PENNERA_REQUEST table, it is not part of the logical
primary key for the table.) Examples: 3, 11
Values:
List of values not available
PennERA source (assuming the proposal record has been opened in the Proposal
Tracking module): Budget;
Requested; Requested Budget section; the row for the request; the value in
the Applied to Period column (The first row in the Requested Budget section
is for REQUEST_NUMBER 1, the second row is for REQUEST_NUMBER 2, etc.)
|
PI_ERA_PRIMARY_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the ERA primary organization (‘org.’)
for the person identified by the PI_PENN_ID. That is the Principal Investigator
for the proposal to which the request applies.
The ERA primary org. is the org. flagged as the primary department in
the person’s PennERA Profile. Although it is used to secure certain
data elements in the Data Warehouse, the ERA primary org. is not used
by the University’s business processes.
For Penn staff, the ERA primary org. is the primary (job) appointment
org. For Penn faculty, it is the primary academic (job) appointment org.,
which will not be the same as primary appointment org. for those faculty
holding administrative positions. For Penn employees whose job appointments
are all on the executive payroll, ERA primary org. is ‘8000’ ('General
University Special '). For Penn students, the ERA primary org. is the
organizational equivalent of their home Division (for example, ‘0200’,
School of Arts and Sciences.) For investigators from the University of
Pennsylvania Health System (UPHS), the ERA primary org. is ‘2100’ ('Health
System '). For members of the research community who are otherwise not
affiliated with Penn, the ERA primary org. is ‘8760' ('Research
Services'). PI_ERA_PRIMARY_ORG_CODE reflects the ERA primary
org. of the PI for the proposal, as it was at the time of the proposal
(funding cycle).
Once the funding cycle has ended, the PI_ERA_PRIMARY_ORG_CODE is no longer
updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL table. (If the proposal
was not awarded, the dates for the funding cycle are the REQUESTED_PROJECT_START
and REQUESTED_PROJECT_END in the PENNERA_PROPOSAL table.)
To facilitate Organization-based security, PI_ERA_PRIMARY_ORG_CODE is
set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. Source: PENNERA_PROPOSAL_INVESTIGATOR. ERA_PRIMARY_ORG_CODE where PENNERA_PROPOSAL_INVESTIGATOR.
PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
PI_ERA_PRIMARY_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PI_ERA_PRIMARY_ORG_CODE.
That identifies the ERA primary organization (‘org.’) for the
person identified by the PI_PENN_ID--the Principal Investigator for the
proposal to which the request applies.
The ERA primary org. is the org. flagged as the primary department in
the person’s PennERA Profile. Although it is used to secure certain
data elements in the Data Warehouse, the ERA primary org. is not used
by the University’s business processes. PI_ERA_PRIMARY_SCHOOL_CODE reflects the ERA primary school of the PI
for the proposal, as it was at the time of the proposal (funding cycle).
Once the funding cycle has ended, the PI_ERA_PRIMARY_SCHOOL_CODE is no
longer updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL table. (If the proposal
was not awarded, the dates for the funding cycle are the REQUESTED_PROJECT_START
and REQUESTED_PROJECT_END in the PENNERA_PROPOSAL table.)
If the PI_ERA_PRIMARY_ORG_CODE is '.', the PI_ERA_PRIMARY_SCHOOL_CODE
is also '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the
same as the first 2 characters of the CNAC.
Source: PENNERA_PROPOSAL_INVESTIGATOR. ERA_PRIMARY_SCHOOL_CODE where
PENNERA_PROPOSAL_INVESTIGATOR. PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
PI_HOME_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the home organization (‘org.’) for
the person identified by the PI_PENN_ID. That is the Principal Investigator
for the proposal to which the request applies.
The home org. is the org. that owns the person's employee record and
is responsible for its maintenance.
PI_HOME_ORG_CODE reflects the home org. of the PI for the proposal,
as it was at the time of the proposal (funding cycle). Once the funding
cycle has ended, the PI_HOME_ORG_CODE is no longer updated. The dates
for the funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL table. (If the proposal was not awarded, the
dates for the funding cycle are the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END
in the PENNERA_PROPOSAL table.) If the PI for the proposal has no employee
information dating back to the time of the funding cycle, PI_HOME_ORG_CODE
is '.'. (Because the PI_HOME_ORG_CODE is one of the data
elements used to secure the data, it is set to '.' if it would
otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. Source: PENNERA_PROPOSAL_INVESTIGATOR. HOME_ORG_CODE where PENNERA_PROPOSAL_INVESTIGATOR.
PENN_ID = PENNERA_REQUEST. PI_PENN_ID
|
PI_HOME_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PI_HOME_ORG_CODE.
That is the home organization (‘org.’) for the person identified
by the PI_PENN_ID--the Principal Investigator for the proposal to which
the request applies.
The home org. is the org. that owns the person's employee record and
is responsible for its maintenance.
PI_HOME_SCHOOL_CODE reflects the home school of the PI for the proposal,
as it was at the time of the proposal (funding cycle). Once the funding
cycle has ended, the PI_HOME_SCHOOL_CODE is no longer updated. The dates
for the funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL table. (If the proposal was not awarded, the
dates for the funding cycle are the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END
in the PENNERA_PROPOSAL table.) If the PI for the proposal has no employee
information dating back to the time of the funding cycle, PI_HOME_SCHOOL_CODE
is '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the
same as the first 2 characters of the CNAC.
Source: PENNERA_PROPOSAL_INVESTIGATOR.HOME_SCHOOL_CODE where PENNERA_PROPOSAL_INVESTIGATOR.
PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
PI_INVESTIGATOR_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the investigator organization (‘org.’)
for the person identified by the PI_PENN_ID. That is the Principal Investigator
for the proposal to which the request applies.
Although it is used to secure certain data elements in the Data Warehouse,
the investigator org. is not used by the University’s business
processes.
For a given investigator associated with a proposal, the investigator
org. is the org. specified (on the Office of Research Services Proposal
Transmittal and Approval Form) as the 'Dept. Administering Project' (the
PROPOSAL_RESP_ORG_CODE). An exception to this rule is that, if the PROPOSAL_RESP_ORG_CODE
is neither the investigator's ERA primary org. nor an org. where the
investigator has a job appointment, when the investigator's data is entered
for the proposal in PennERA, the investigator org. is chosen from among
those orgs., based on its being the one that is most closely related
to the PROPOSAL_RESP_ORG_CODE. In other words:
- if the investigator has only one org, then that org. is chosen; otherwise,
- if the investigator has an org. that is the same as the PROPOSAL_RESP_ORG_CODE,
then that org. is chosen; otherwise
- the investigator's orgs. are sorted in ascending order, and the first
org. whose org. code is greater than or equal to the PROPOSAL_RESP_ORG_CODE
is chosen; otherwise,
- if the investigator has no org. whose org. code is greater than or
equal to the PROPOSAL_RESP_ORG_CODE, the investigator's ERA primary
org. is chosen
To facilitate Organization-based security, PI_INVESTIGATOR_ORG_CODE is
set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. PennERA source (assuming
the proposal record has been opened in the Proposal Tracking module): General; Personnel; the code in the Department column for the person
flagged as the PI
|
PI_INVESTIGATOR_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PI_INVESTIGATOR_ORG_CODE.
That is the investigator organization (‘org.’) for the person
identified by the PI_PENN_ID--the Principal Investigator for the proposal
to which the request applies.
Although it is used to secure certain data elements in the Data Warehouse,
the investigator org. is not used by the University’s business
processes.
If the PI_INVESTIGATOR_ORG_CODE is '.', the PI_INVESTIGATOR_SCHOOL_CODE
is also '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC. Source: ORG_CODES.CENTER_CODE where PENNERA_REQUEST. PI_INVESTIGATOR_ORG_CODE
=ORG_CODES.ORGANIZATION_CODE
|
PI_PENN_ID
Indexed - no
Format - char (8)
May be null? yes |
The Penn ID of the Principal Investigator for the proposal to which the
request applies.
The PennID is the 8-digit identification number assigned to a person
by the Penn Community system. No two persons have the same PennID. However,
a person may have more than one PennID. For example, say Dr. John Doe
had a sponsored project in 1990, but his Social Security number was not
recorded in the Research Services System (RSS, the system then used to
track proposals and awards). Dr. Doe left the University after project
ended. When the RSS data was converted to PennERA, there was no record
in Penn Community for Dr. Doe. Because his Social Security number was
not available, a PennERA-specific PennID (beginning with a ‘P’)
was created for him. In 2003, Dr. Doe returned to the University, and
was assigned a numeric PennID (for example, 10039706). Dr. Doe would
then have two PennIDs, but one could not tell from looking at
the data that both PennIDs identify the same person.
See also PARENT_PI_PENN_ID and REQUEST_RESP_INVESTIGATOR
Examples: ‘P1000194’ (Lisa Jay); ‘10006336’ (Herman
Gluck)
Values:
Refer to the PENNERA_PEOPLE Table for values.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): General; Personnel; the PennID for the
person flagged as the PI (the PennID is not shown)
|
PI_PRI_ACAD_APPT_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the organization (‘org.’) of the
primary academic job appointment for the person identified by the PI_PENN_ID.
That is the Principal Investigator for the proposal to which the request
applies.
The primary academic appointment org. is the org. where the person has
his or her primary academic job appointment. If the person has more than
one academic job appointment, the primary academic appointment is the
one with the most important faculty class. For further information on
the primary academic appointment, see the explanation in the Cautions
section of the documentation for the EMPLOYEE_GENERAL Table.
PI_PRI_ACAD_APPT_ORG_CODE reflects the primary academic appointment
org. of the PI for the proposal, as it was at the time of the proposal
(funding cycle). Once the funding cycle has ended, the PI_PRI_ACAD_APPT_ORG_CODE
is no longer updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL table. (If the proposal
was not awarded, the dates for the funding cycle are the REQUESTED_PROJECT_START
and REQUESTED_PROJECT_END in the PENNERA_PROPOSAL table.) If the PI for
the proposal has no employee information about a faculty job appointment
dating back to the time of the funding cycle, PI_PRI_ACAD_APPT_ORG_CODE
is '.'. (Because the PI_PRI_ACAD_APPT_ORG_CODE
is one of the data elements used to secure the data, it is set to '.'
if it would
otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. Source: PENNERA_PROPOSAL_INVESTIGATOR. PRIMARY_ACADEMIC_ORG_CODE where
PENNERA_PROPOSAL_INVESTIGATOR. PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
PI_PRI_ACAD_APPT_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PI_PRI_ACAD_APPT_ORG_CODE.
That is the organization (‘org.’) of the primary academic job
appointment for the person identified by the PI_PENN_ID--the Principal
Investigator for the proposal to which the request applies.
The primary academic appointment org. is the org. where the person has
his or her primary academic job appointment. If the person has more than
one academic job appointment, the primary academic appointment is the
one with the most important faculty class.
PI_PRI_ACAD_APPT_SCHOOL_CODE reflects the primary academic appointment
school of the PI for the proposal, as it was at the time of the proposal
(funding cycle). Once the funding cycle has ended, the PI_PRI_ACAD_APPT_SCHOOL_CODE
is no longer updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL table. (If the proposal
was not awarded, the dates for the funding cycle are the REQUESTED_PROJECT_START
and REQUESTED_PROJECT_END in the PENNERA_PROPOSAL table.) If the PI for
the proposal has no employee information about a faculty job appointment
dating back to the time of the funding cycle, PI_PRI_ACAD_APPT_SCHOOL_CODE
is '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC. Source: PENNERA_PROPOSAL_INVESTIGATOR. PRIMARY_ACADEMIC_SCHOOL_CODE
where PENNERA_PROPOSAL_INVESTIGATOR. PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
PI_PRI_APPT_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the organization (‘org.’) of the
primary job appointment for the person identified by the PI_PENN_ID. That
is the Principal Investigator for the proposal to which the request applies.
The primary appointment org. is the org. where the person has his or
her primary job appointment, per the University’s employee census
logic. If the person has more than one job appointment, the primary appointment
is determined as follows: if the person has a standing faculty appointment,
that is the person’s primary appointment. If the employee has a
job whose personnel class is SS (Support Staff), US (Unionized Staff)
or ST (Student), that is the primary appointment. If most of the person’s
pay comes from his or her academic jobs, the highest paid academic job
is the primary appointment. If most of the person’s pay comes from
his or her administrative jobs, the highest paid administrative job is
the primary appointment.
PI_PRI_APPT_ORG_CODE reflects the primary appointment org. of the PI
for the proposal, as it was at the time of the proposal (funding cycle).
Once the funding cycle has ended, the PI_PRI_APPT_ORG_CODE is no longer
updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL table. (If the proposal
was not awarded, the dates for the funding cycle are the REQUESTED_PROJECT_START
and REQUESTED_PROJECT_END in the PENNERA_PROPOSAL table.) If the PI for
the proposal has no employee information dating back to the time
of the funding cycle, PI_PRI_APPT_ORG_CODE is '.'. (Because the PI_PRI_APPT_ORG_CODE
is one of the data elements used to secure the data, it is set to '.'
if it would
otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. Source: PENNERA_PROPOSAL_INVESTIGATOR. PRIMARY_APPT_ORG_CODE where PENNERA_PROPOSAL_INVESTIGATOR.
PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
PI_PRI_APPT_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PI_PRI_APPT_ORG_CODE.
That is the organization (‘org.’) of the primary job appointment
for the person identified by the PI_PENN_ID--the Principal Investigator
for the proposal to which the request applies.
The primary appointment org. is the org. where the person has his or
her primary job appointment, per the University’s employee census
logic.
PI_PRI_APPT_SCHOOL_CODE reflects the primary appointment school of the
PI for the proposal, as it was at the time of the proposal (funding cycle).
Once the funding cycle has ended, the PI_PRI_APPT_SCHOOL_CODE is no longer
updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL table. (If the proposal
was not awarded, the dates for the funding cycle are the REQUESTED_PROJECT_START
and REQUESTED_PROJECT_END in the PENNERA_PROPOSAL table.) If the PI for
the proposal has no employee information dating back to the time
of the funding cycle, PI_PRI_APPT_SCHOOL_CODE is '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC. Source: PENNERA_PROPOSAL_INVESTIGATOR. PRIMARY_APPT_SCHOOL_CODE where
PENNERA_PROPOSAL_INVESTIGATOR. PENN_ID = PENNERA_REQUEST.PI_PENN_ID
|
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 to which the request applies. 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_REQUEST record per proposal (INSTITUTION_NO or
PROP_NO) per REQUEST_NUMBER. (Though PERIOD_NUMBER is part of the physical
primary key for the PENNERA_REQUEST table, it is not part of the logical
primary key for the table.)
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 on the first line of the Proposal Header text; PROP_NO is not
shown)
|
PROPOSAL_RESP_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code that identifies the organization responsible for
the proposal to which the request applies.
To facilitate Organization-based security, PROPOSAL_RESP_ORG_CODE is
set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): General; Summary; Associated Department
section; the code listed in the Department column for the row flagged
as Primary
|
PROPOSAL_RESP_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the PROPOSAL_RESP_ORG_CODE
-- the organization responsible for the proposal to which the request applies.
If the PROPOSAL_RESP_ORG_CODE is '.', the PROPOSAL_RESP_SCHOOL_CODE
is also '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC.
Source: ORG_CODES.CENTER_CODE where PENNERA_REQUEST. PROPOSAL_RESP_ORG_CODE
=ORG_CODES.ORGANIZATION_CODE
|
REQRESPINV_ERA_PRI_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the ERA primary organization (‘org.’)
for the person identified by the REQUEST_RESP_INVESTIGATOR. That is the
investigator responsible for the request (who might or might not be the
Principal Investigator for the proposal to which the request applies).
The ERA primary org. is the org. flagged as the primary department in
the person’s PennERA Profile. Although it is used to secure certain
data elements in the Data Warehouse, the ERA primary org. is not used
by the University’s business processes.
For Penn staff, the ERA primary org. is the primary (job) appointment
org. For Penn faculty, it is the primary academic (job) appointment org.,
which will not be the same as primary appointment org. for those faculty
holding administrative positions. For Penn employees whose job appointments
are all on the executive payroll, ERA primary org. is ‘8000’ ('General
University Special '). For Penn students, the ERA primary org. is the
organizational equivalent of their home Division (for example, ‘0200’,
School of Arts and Sciences.) For investigators from the University of
Pennsylvania Health System (UPHS), the ERA primary org. is ‘2100’ ('Health
System '). For members of the research community who are otherwise not
affiliated with Penn, the ERA primary org. is ‘8760' ('Research
Services'). REQRESPINV_ERA_PRI_ORG_CODE reflects the ERA
primary org. of the investigator responsible for the request, as it
was at the time of
the proposal (funding cycle). Once the funding cycle has ended, the
REQRESPINV_ERA_PRI_ORG_CODE is no longer updated. The dates for the
funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL record for the INSTITUTION_NO. (If
the proposal was not awarded, the dates for the funding cycle are
the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.)
To facilitate Organization-based security, REQRESPINV_ERA_PRI_ORG_CODE
is set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. Source: PENNERA_PROPOSAL_INVESTIGATOR.ERA_PRIMARY_ORG_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_ERA_PRI_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the REQRESPINV_ERA_PRI_ORG_CODE.
That identifies the ERA primary organization (‘org.’) for the
person identified by the REQUEST_RESP_INVESTIGATOR--the investigator responsible
for the request. (This might or
might not be the Principal Investigator for the proposal to which the request
applies.)
The ERA primary org. is the org. flagged as the primary department in
the person’s PennERA Profile. Although it is used to secure certain
data elements in the Data Warehouse, the ERA primary org. is not used
by the University’s business processes. REQRESPINV_ERA_PRI_SCH_CODE
reflects the ERA primary school of the investigator responsible for the
request, as it was at the time of
the proposal (funding cycle). Once the funding cycle has ended, the
REQRESPINV_ERA_PRI_SCH_CODE is no longer updated. The dates for the
funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL record for the INSTITUTION_NO. (If
the proposal was not awarded, the dates for the funding cycle are
the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.)
If the REQRESPINV_ERA_PRI_ORG_CODE is '.', the REQRESPINV_ERA_PRI_SCH_CODE
is also '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC. Source: PENNERA_PROPOSAL_INVESTIGATOR.ERA_PRIMARY_SCHOOL_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_HOME_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the home organization (‘org.’) for
the person identified by the REQUEST_RESP_INVESTIGATOR. That is the investigator
responsible for the request (who
might or might not be the Principal Investigator for the proposal to which
the request applies).
The home org. is the org. that owns the person's University employee
record and is responsible for its maintenance.
REQRESPINV_HOME_ORG_CODE reflects the home org. of the investigator
responsible for the request, as it was at the time of the proposal
(funding cycle). Once the funding cycle has ended, the REQRESPINV_HOME_ORG_CODE
is no longer updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL record for the INSTITUTION_NO.
(If the proposal was not awarded, the dates for the funding cycle
are
the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.) If the investigator
responsible for the request has no employee information dating back
to the time of the funding cycle, REQRESPINV_HOME_ORG_CODE is '.'.
(Because the REQRESPINV_HOME_ORG_CODE is one of the data elements used
to secure the data, it is set to '.' if it would
otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL_INVESTIGATOR.HOME_ORG_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_HOME_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the REQRESPINV_HOME_ORG_CODE.
That is the home organization (‘org.’) for the person identified
by the REQUEST_RESP_INVESTIGATOR--the investigator responsible for the
request. (This might or might
not be the Principal Investigator for the proposal to which the request
applies.)
The home org. is the org. that owns the person's University employee
record and is responsible for its maintenance.
REQRESPINV_HOME_SCH_CODE reflects the home school of the investigator
responsible for the request, as it was at the time of the proposal
(funding cycle). Once the funding cycle has ended, the REQRESPINV_HOME_SCH_CODE
is no longer updated. The dates for the funding cycle are the AWARDED_PROJECT_START
and AWARDED_PROJECT_END in the PENNERA_PROPOSAL record for the INSTITUTION_NO.
(If the proposal was not awarded, the dates for the funding cycle
are the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.)
If the investigator responsible for the request has no employee information
dating back to the time of the funding cycle, REQRESPINV_HOME_SCH_CODE
is '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values. The
code for a school or center is the same as the
first 2 characters of the CNAC.
Source: PENNERA_PROPOSAL_INVESTIGATOR.HOME_SCHOOL_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_INV_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the investigator organization (‘org.’)
for the person identified by the REQUEST_RESP_INVESTIGATOR. That is the
investigator responsible for the request (who might or might not be the
Principal Investigator for the proposal to which the request applies).
Although it is used to secure certain data elements in the Data Warehouse,
the investigator org. is not used by the University’s business
processes.
For a given investigator associated with a request, the
investigator org. is the org. specified as the Associated Department
for the request
(the REQUEST_RESP_ORG_CODE). An exception to this rule is that, if
the REQUEST_RESP_ORG_CODE is neither the investigator's ERA primary
org. nor an org. where the investigator has a job appointment, when
the investigator's data is entered for the request in PennERA, the
investigator org. is chosen from among those orgs., based on its being
the one that is most closely related to the REQUEST_RESP_ORG_CODE.
In other words:
- if the investigator has only one org, then that org. is chosen;
otherwise,
- if the investigator has an org. that is the same as the REQUEST_RESP_ORG_CODE,
then that org. is chosen; otherwise
- the investigator's orgs. are sorted in ascending order, and the
first org. whose org. code is greater than or equal to the REQUEST_RESP_ORG_CODE
is chosen; otherwise,
- if the investigator has no org. whose org. code is greater than
or equal to the REQUEST_RESP_ORG_CODE, the investigator's ERA primary
org. is chosen
To facilitate Organization-based security, REQRESPINV_INV_ORG_CODE
is set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values. PennERA source (assuming
the proposal record has been opened in the Proposal Tracking module): the org.
portion of the value selected from the investigator pick list when the Request
Responsible Investigator data was entered for the request. Once
the data has been entered, the Proposal Tracking module does not display
the
REQRESPINV_INV_ORG_CODE;
but
in most cases, it can be deduced. First, find the name of the investigator
responsible for the request (Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request [the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.]; the name of the first person listed in the Personnel
section). Then look for that person's investigator org. (General; Personnel;
the code in the Department column for the row whose Name column matches the
name of the investigator
responsible for the request). If the person's investigator org. changed over
the course of the proposal, the person has one row for each investigator
org., and you cannot deduce the REQRESPINV_INV_ORG_CODE.
|
REQRESPINV_INV_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the REQRESPINV_INV_ORG_CODE.
That is the investigator organization (‘org.’) for the person
identified by the REQUEST_RESP_INVESTIGATOR--the investigator responsible
for the request. (This might or
might not be the Principal Investigator for the proposal to which the request
applies.)
Although it is used to secure certain data elements in the Data
Warehouse, the investigator org. is not used by the University’s
business processes.
If the REQRESPINV_INV_ORG_CODE is '.', the REQRESPINV_INV_SCH_CODE
is also '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values. The
code for a school or center is the same as the
first 2 characters of the CNAC. Source: PENNERA_PROPOSAL_INVESTIGATOR.INVESTIGATOR_SCHOOL_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_PRI_APPT_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the organization (‘org.’) of the
primary job appointment for the person identified by the REQUEST_RESP_INVESTIGATOR.
That is the investigator responsible for the request (who might or might
not be the Principal Investigator for the proposal to which the request
applies).
The primary appointment org. is the org. where the person has his
or her primary job appointment, per the University’s employee
census logic. If the person has more than one job appointment, the
primary appointment is determined as follows: if the person has a standing
faculty appointment, that is the person’s primary appointment.
If the employee has a job whose personnel class is SS (Support Staff),
US (Unionized Staff) or ST (Student), that is the primary appointment.
If most of the person’s pay comes from his or her academic jobs,
the highest paid academic job is the primary appointment. If most of
the person’s pay comes from his or her administrative jobs, the
highest paid administrative job is the primary appointment.
REQRESPINV_PRI_APPT_ORG_CODE reflects the primary appointment org.
of the investigator responsible for the request, as it was at the time
of the proposal (funding cycle). Once the funding cycle has ended,
the REQRESPINV_PRI_APPT_ORG_CODE is no longer updated. The dates for
the funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL record for the INSTITUTION_NO. (If
the proposal was not awarded, the dates for the funding cycle are the
REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.) If the investigator
responsible for the request has no employee information dating back
to the time of the funding cycle, REQRESPINV_PRI_APPT_ORG_CODE is '.'.
(Because the REQRESPINV_PRI_APPT_ORG_CODE is one of the data elements
used to secure the data, it is set to '.' if it would
otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL_INVESTIGATOR.PRIMARY_APPT_ORG_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_PRI_APPT_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the REQRESPINV_INV_ORG_CODE.
That is the investigator organization (‘org.’) for the person
identified by the REQUEST_RESP_INVESTIGATOR--the investigator responsible
for the request. (This might or
might not be the Principal Investigator for the proposal to which the request
applies.)
The primary appointment org. is the org. where the person has his
or her primary job appointment, per the University’s employee
census logic.
REQRESPINV_PRI_APPT_SCH_CODE reflects the primary appointment school
of the investigator responsible for the request, as it was at the
time of the proposal (funding cycle). Once the funding cycle has
ended, the REQRESPINV_PRI_APPT_SCH_CODE is no longer updated. The
dates for the funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL record for the INSTITUTION_NO. (If
the proposal was not awarded, the dates for the funding cycle are
the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.) If the investigator
responsible for the request has no employee information dating back
to the time of the funding cycle, REQRESPINV_PRI_APPT_SCH_CODE is
'.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC.
Source: PENNERA_PROPOSAL_INVESTIGATOR.PRIMARY_APPT_SCHOOL_CODE
where PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_PRIACADAP_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the organization (‘org.’) of the
primary academic job appointment for the person identified by the REQUEST_RESP_INVESTIGATOR.
That is the investigator responsible for the request (who might or might
not be the Principal Investigator for the proposal to which the request
applies).
The primary academic appointment org. is the org. where the person
has his or her primary academic job appointment at the University.
If the person has more than one academic job appointment, the primary
academic appointment is the one with the most important faculty class.
For further information on the primary academic appointment, see the
explanation in the Cautions section of the documentation for the EMPLOYEE_GENERAL Table.
REQRESPINV_PRIACADAP_ORG_CODE reflects the primary academic appointment
org. of the investigator responsible for the request, as it was at
the time of the proposal (funding cycle). Once the funding cycle has
ended, the REQRESPINV_PRIACADAP_ORG_CODE is no longer updated. The
dates for the funding cycle are the AWARDED_PROJECT_START and AWARDED_PROJECT_END
in the PENNERA_PROPOSAL record for the INSTITUTION_NO. (If
the proposal was not awarded, the dates for the funding cycle are the
REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.) If the investigator
responsible for the request has no employee information about a faculty
job appointment dating back to the time of the funding cycle, REQRESPINV_PRIACADAP_ORG_CODE
is '.'. (Because the REQRESPINV_PRIACADAP_ORG_CODE is one of the data
elements
used to secure the data, it is set to '.' if it would
otherwise be null.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL_INVESTIGATOR.PRIMARY_ACADEMIC_ORG_CODE where
PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQRESPINV_PRIACADAP_SCH_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code for the school or center for the REQRESPINV_PRIACADAP_ORG_CODE.
That is the organization (‘org.’) of the primary academic job
appointment for the person identified by the REQUEST_RESP_INVESTIGATOR--the
investigator responsible for the request. (This might or might not be
the Principal Investigator for the proposal to which the request applies.)
The primary academic appointment org. is the org. where the person
has his or her primary academic job appointment at the University.
If the person has more than one academic job appointment, the primary
academic appointment is the one with the most important faculty class.
REQRESPINV_PRIACADAP_SCH_CODE reflects the primary academic appointment
school of the investigator responsible for the request, as it was
at the time of the proposal (funding cycle). Once the funding cycle
has ended, the REQRESPINV_PRIACADAP_SCH_CODE is no longer updated.
The dates for the funding cycle are the AWARDED_PROJECT_START and
AWARDED_PROJECT_END in the PENNERA_PROPOSAL record for the INSTITUTION_NO.
(If the proposal was not awarded, the dates for the funding cycle
are the REQUESTED_PROJECT_START and REQUESTED_PROJECT_END.) If the
investigator responsible for the request has no employee information
about a faculty job appointment dating back to the time of the funding
cycle, REQRESPINV_PRIACADAP_SCH_CODE is
'.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC.
Source: PENNERA_PROPOSAL_INVESTIGATOR.PRIMARY_ACADEMIC_SCHOOL_CODE
where PENNERA_PROPOSAL_INVESTIGATOR.PENN_ID = PENNERA_REQUEST.REQUEST_RESP_INVESTIGATOR
|
REQUEST_NUMBER
Indexed - yes
Format - varchar2 (40)
May be null? yes |
A sequence number uniquely identifying the request within the proposal
to which it applies. Each proposal (INSTITUTION_NO) has an REQUEST_NUMBER ‘1’.
The maximum REQUEST_NUMBER for a proposal is the number of requests for
that proposal.
There is one PENNERA_REQUEST record per proposal (INSTITUTION_NO or
PROP_NO) per REQUEST_NUMBER. (Though PERIOD_NUMBER is part of the physical
primary key for the PENNERA_REQUEST table, it is not part of the logical
primary key for the table.) Examples: 2, 13
Values:
List of values not available
PennERA source (assuming the proposal record has been opened in the Proposal
Tracking module): Budget; Requested; Requested Budget section;
the row number for the request. (The first
row in the Requested Budget section is for REQUEST_NUMBER 1, the second row
is for REQUEST_NUMBER 2, etc.)
|
REQUEST_RESP_INVESTIGATOR
Indexed - no
Format - char (8)
May be null? yes |
The Penn ID of the investigator responsible for the request. The request
responsible investigator is one of the investigators associated with the
proposal. However, it may or may not be the same person as the Principal
Investigator for the proposal.
See also PI_PENN_ID and PARENT_PI_PENN_ID
Example: 10108345 (LAUFER,TERRI M)
Values:
Refer to the PENNERA_PEOPLE table for values.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request [the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.]; the PennID of the first person listed in
the Personnel section. (The
PennID is not displayed.)
|
REQUEST_RESP_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code that identifies the Organization (org.) responsible
for the request. To facilitate Organization-based security,
REQUEST_RESP_ORG_CODE is set to '.' if it would otherwise be null.
Note that the value of REQUEST_RESP_ORG_CODE may be inaccurate for some
records. For request records created on or after Oct. 10,
2006, in PennERA's Proposal Development
(PD) module, the REQUEST_RESP_ORG_CODE reflects the ERA primary org.
of the person who created the request record. That person's ERA primary
org. might or might not be the org. that is responsible
for the request. (If
the record was created in PD, PENNERA_PROPOSAL.PD_FLAG = 'Y'. For more
information on the ERA primary org., see the documentation on PENNERA_PEOPLE.ERA_PRIMARY_ORG.)
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request [the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.]; Budget Detail section; the code at the beginning
of the value for Associated Department
|
REQUEST_RESP_SCHOOL_CODE
Indexed - yes
Format - char (2)
May be null? yes |
The 2-character code that identifies the school or center for the Organization
responsible for administering the science and the money for the request.
If the REQUEST_RESP_ORG_CODE is '.', the REQUEST_RESP_SCHOOL_CODE
is also '.'.
Example: 40 (School of Medicine)
Values:
Refer to the CNAC_CODES Table for values.
The code for a school or center is the same
as the first 2 characters of the CNAC.
Source: ORG_CODES.CENTER_CODE where PENNERA_REQUEST.REQUEST_RESP_ORG_CODE
=ORG_CODES.ORGANIZATION_CODE
|
REQUEST_STATUS
Indexed - no
Format - varchar2 (24)
May be null? yes |
The current status of the request, per the sponsor’s response
to the request.
Note that REQUEST_STATUS will be null if the request belongs to a
proposal whose PennERA record was created in Proposal Development
(PD) and the proposal has not yet been submitted to its sponsor. (If
the record was created in PD, PENNERA_PROPOSAL.PD_FLAG = 'Y'. If the
proposal has been submitted to the sponsor, it has a PENNERA_PROP_STAT_HIST
record for the 'Pending' status.)
For the effective date of the current status of the request,
or for more details on how the request's status has changed over time,
use the PENNERA_REQ_STAT_HIST
table.
Values:
Awarded--the sponsor has awarded funding for the
request
Future--the sponsor has notified the University
of its intent to award funding for the request,
which applies to a future period (“out year”)
Future Pending--the sponsor has notified
the University of its intent to award funding
for the request, and the Principal Investigator has
applied for a non-competing continuation for
the period to which the request applies
Pending--the Office of Research Services has
given its approval for the request to be
submitted to the sponsor; the request is
pending a decision by the sponsor
Revised Budget Requested--the sponsor has asked that the
Principal Investigator submit a revised budget for the
request
Unfunded--the sponsor has notified the University that it
will not award funding for the request
Withdrawn--the Principal Investigator has withdrawn the
request from consideration by the sponsor
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget;
Requested; Requested Budget section; the row for the request; the value in
the Status column (The first row in the Requested Budget section
is for REQUEST_NUMBER 1, the second row is for REQUEST_NUMBER 2, etc.)
|
REQUEST_SUBMITTED_DATE
Indexed - no
Format - date
May be null? yes |
The date when the request was approved to be submitted to the sponsor.
This may differ from the date the proposal was submitted to the sponsor.
For example, if the
request is for a supplement to the first period for the proposal, the
REQUEST_SUBMITTED_DATE will differ from the date the proposal was submitted
to the sponsor.
If the request record was created in PennERA via the SOMERA Interface,
how the REQUEST_SUBMITTED_DATE is populated depends on the REQUEST_NUMBER.
If the REQUEST_NUMBER is 1, the REQUEST_SUBMITTED_DATE was initially
populated with the same value as the PENNERA_PROPOSAL.SUBMITTED_DATE
(the Status Date in SOMERA). If the REQUEST_NUMBER is not 1, the REQUEST_SUBMITTED_DATE
remains null until the School of Medicine provides the value and the
Office of Research Services enters it into PennERA. (SOMERA is the School
of Medicine’s Electronic Research Administration system.)
Example: 07/15/2002
Values:
List of values not available.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request (the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.); Request Specific
Information
section; Submitted Date
|
REQUEST_TYPE
Indexed - no
Format - varchar2 (29)
May be null? yes |
The type of request for funding for a budget period.
Values:
Budget Period
Supplement
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget;
Requested; Requested Budget section; the row for the request; the value in
the Type column. (The first row in the Requested Budget section
is for REQUEST_NUMBER 1, the second row is for REQUEST_NUMBER 2, etc.)
|
REQUESTED_COST_SHR_CASH
Indexed - no
Format - number (13,2)
May be null? yes |
Not currently used |
REQUESTED_COST_SHR_IN_KIND
Indexed - no
Format - number (13,2)
May be null? yes |
Not currently used |
REQUESTED_COST_SHR_OTHER
Indexed - no
Format - number (13,2)
May be null? yes |
Not currently used |
REQUESTED_COST_SHR_TOTAL
Indexed - no
Format - number (13,2)
May be null? yes |
The total dollar amount of cost sharing associated with the request.
Cost sharing is the amount of funding provided for the sponsored project
that does not come from the sponsor. REQUESTED_COST_SHR_TOTAL is the total
amount of cost sharing to be provided by all cost sharing sources combined.
For example, the University proposes a project estimated to have a total
cost of $100,000. The sponsor is asked to pay 75% ($75,000) and the University
offers to pay 25% ($25,000). The $25,000 is the cost-sharing component.
Note that, regardless of the current
status of the request ('Pending', 'Awarded', etc.), the value of REQUESTED_COST_SHR_TOTAL
reflects what was requested, not what was awarded. REQUESTED_COST_SHR_TOTAL is populated only for requests whose records
were entered or updated since October 14, 2003. The value is null
for all other records.
Values:
0 to 99,999,999,999.99 PennERA source (assuming the proposal record
has been opened in the Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request (the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.); Project Detail section; Total Institution Costs
|
REQUESTED_DIRECT_COSTS
Indexed - no
Format - number (13,2)
May be null? yes |
Total dollar amount designated to be paid by the sponsor for direct costs
for the request. Direct costs are clearly identifiable costs related to
a specific project. (For
example, salaries, wages, and equipment fall under direct costs.)
REQUESTED_DIRECT_COSTS + REQUESTED_INDIRECT_COSTS = REQUESTED_TOT_SPON_COSTS
Note that, regardless of the current status of the request ('Pending',
'Awarded', etc.), the value of REQUESTED_DIRECT_COSTS reflects what
was requested, not what was awarded. Values:
0 to 99,999,999,999.99 PennERA source (assuming the proposal record
has been opened in the Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request (the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.); Project Detail section; Sponsor Total Direct Costs
|
REQUESTED_INDIRECT_COSTS
Indexed - no
Format - number (13,2)
May be null? yes |
Total dollar amount designated to be paid by the sponsor for indirect
costs for the request. Indirect costs are costs that are not specific to
the sponsored project, but that
are incurred by the University in support of the sponsored project. (For
example, utilities and laboratory space fall under indirect costs.) Indirect
costs are also known as Facilities and Administrative (F&A) costs or
overhead.
REQUESTED_DIRECT_COSTS + REQUESTED_INDIRECT_COSTS = REQUESTED_TOT_SPON_COSTS
Note that, regardless of the current status of the request ('Pending',
'Awarded', etc.), the value of REQUESTED_INDIRECT_COSTS reflects what
was requested, not what was awarded. See also REQUESTED_MTDC
Values:
0 to 99,999,999,999.99 PennERA source (assuming the proposal record
has been opened in the Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request (the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.); Project Detail section; F&A
|
REQUESTED_MTDC
Indexed - no
Format - number (13,2)
May be null? yes |
Not currently used. |
REQUESTED_NONSPON_COSTS
Indexed - no
Format - number (13,2)
May be null? yes |
The total dollar amount of non-sponsor costs associated with the request.
Non-sponsor costs are the total costs (direct and indirect) associated
with the request that are being requested from funding sources other than
the sponsor.
REQUESTED_NONSPON_COSTS + REQUESTED_TOT_SPON_COSTS =
REQUESTED_TOTAL_COSTS
Note that, regardless of the current status of the request ('Pending',
'Awarded', etc.), the value of REQUESTED_NONSPON_COSTS reflects what
was requested, not what was awarded. See also REQUESTED_COST_SHR_TOTAL.
Values:
0 to 99,999,999,999.99 PennERA source (assuming the proposal record
has been opened in the Proposal Tracking module): Budget;
Requested; Requested Budget section; click on the View or Edit icon in the
row for the request (the first row in the Requested Budget section is for
REQUEST_NUMBER 1, the
second
row
is
for REQUEST_NUMBER 2, etc.); Project Detail section; Total Institution Costs |
REQUESTED_PERIOD_END_DATE
Indexed - no
Format - date
May be null? yes |
The requested end date for the budget period to which the request applies.
The budget period is a discrete period of time for which the sponsor is
asked to commit funds that can be expended by the University for the sponsored
project.
Example: 01/31/2004
Values:
List of values not available.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): First, find the period for the request (Budget;
Requested; Requested
Budget section;
the
row for
the
request;
the value in
the Applied to Period column. [The first row in the Requested Budget section
is for REQUEST_NUMBER 1, the second row is for REQUEST_NUMBER 2, etc.]). On
the same screen, in the Budget Summary section, in the row whose Year/Period
value is the period for
the request, the REQUESTED_PERIOD_END_DATE is in the End column.
|
REQUESTED_PERIOD_END_FY
Indexed - no
Format - char (4)
May be null? yes |
The fiscal year at Penn in which the REQUESTED_PERIOD_END_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 a request whose
REQUESTED_PERIOD_END_DATE is December 31, 2003)
Values:
List of values not available.
|
REQUESTED_PERIOD_START_DATE
Indexed - no
Format -date
May be null? yes |
The requested beginning date for the budget period to which the request
applies. The budget period is a discrete period of time for which the sponsor
is asked to commit funds that can be expended by the University for the
sponsored project.
Example: 02/01/2003
Values:
List of values not available.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): First, find the period for the request (Budget;
Requested; Requested Budget section; the row for the request; the value
in the Applied
to Period column. [The first row in the Requested Budget section is for
REQUEST_NUMBER 1, the second row is for REQUEST_NUMBER 2, etc.]). On
the same screen, in the Budget Summary section, in the row whose Year/Period
value is the period for the request, the REQUESTED_PERIOD_END_DATE
is in the Start column.
|
REQUESTED_PERIOD_START_FY
Indexed - no
Format -date
May be null? yes |
The fiscal year at Penn in which the REQUESTED_PERIOD_START_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 request whose
REQUESTED_PERIOD_START_DATE is July 1, 2003)
Values:
List of values not available |
REQUESTED_TOT_SPON_COSTS
Indexed - no
Format -number (13,2)
May be null? yes |
The total dollar amount of all costs (direct and indirect) associated
with the request that are being requested from the sponsor.
REQUESTED_DIRECT_COSTS + REQUESTED_INDIRECT_COSTS = REQUESTED_TOT_SPON_COSTS REQUESTED_NONSPON_COSTS + REQUESTED_TOT_SPON_COSTS =
REQUESTED_TOTAL_COSTS
Note that, regardless of the current status of the request ('Pending',
'Awarded', etc.), the value of REQUESTED_TOT_SPON_COSTS reflects what
was requested, not what was awarded. Values:
0 to 99,999,999,999.99 PennERA source (assuming the proposal record
has been opened in the Proposal Tracking module): Budget; Requested; Requested
Budget section; click on the View or Edit icon in the row for the request (the
first row in the Requested Budget section is for REQUEST_NUMBER 1, the second
row is for REQUEST_NUMBER 2, etc.); Project Detail section; Total Sponsor Costs
|
REQUESTED_TOTAL_COSTS
Indexed - no
Format -number (13,2)
May be null? yes |
The total dollar amount of all costs (direct and indirect) associated
with the request that are being requested from all funding sources combined.
REQUESTED_NONSPON_COSTS + REQUESTED_TOT_SPON_COSTS =
REQUESTED_TOTAL_COSTS
Note that, regardless of the current status of the request ('Pending',
'Awarded', etc.), the value of REQUESTED_TOTAL_COSTS reflects what
was requested, not what was awarded. Values:
0 to 99,999,999,999.99 PennERA source (assuming the proposal record
has been opened in the Proposal Tracking module): Budget; Requested; Requested
Budget section; click on the View or Edit icon in the row for the request (the
first row in the Requested Budget section is for REQUEST_NUMBER 1, the second
row is for REQUEST_NUMBER 2, etc.); Project Detail section; Total Project Costs
|
SCHOOL_LOG_NUMBER
Indexed - yes
Format -varchar2 (60)
May be null? yes |
The identification number that is assigned to the request by the school
that is responsible for the request.
If the request record was created in PennERA via the SOMERA Interface,
how the SCHOOL_LOG_NUMBER is populated depends on the REQUEST_NUMBER.
If the REQUEST_NUMBER is 1, the SCHOOL_LOG_NUMBER was initially populated
with the value of the Log Number for the SOMERA record that was
fed to PennERA via the Interface. If the REQUEST_NUMBER is not 1, the
SCHOOL_LOG_NUMBER remains null until the School of Medicine provides
the value and the Office of Research Services enters it into PennERA.
(SOMERA is the School of Medicine’s Electronic Research Administration
system.)
Example: 93-0418 (an identification number assigned by the School of
Medicine)
Values:
List of values not available.
PennERA source (assuming the proposal record has been opened in the
Proposal Tracking module): Budget; Requested; Requested
Budget section; click on the View or Edit icon in the row for the request (the
first row in the Requested Budget section is for REQUEST_NUMBER 1, the second
row is for REQUEST_NUMBER 2, etc.); Request
Specific Information section; School Log Number
|
SPONSOR_CODE
Indexed - yes
Format -char (5)
May be null? yes |
The 5-character numeric code that uniquely identifies the sponsor for
the proposal to which the request applies.
Codes less than or equal to 599999 were assigned to the sponsor by InfoEd
(the vendor of the PennERA software). Codes greater than or equal to
60000 were assigned to the sponsor by the Office of Research Services.
Example: 09470 (NATIONAL INSTITUTES OF HEALTH).
Values:
Refer to the PENNERA_SPONSOR Table for values.
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
sponsor code for the
sponsor named
on the second line of the Proposal Header text (SPONSOR_CODE is not shown)
|