| Data element |
Definition |
ADJUSTMENT_AMOUNT
Indexed - no
Format - number (13,2)
May be null? yes |
The dollar amount of the adjustment to the special budget
balance (specified by the SPECIAL_BUDGET_OBJECT) for the AWARD_FUND.
Values:
-99,999,999,999.99 to 99,999,999,999.99
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section; Adjustment $
|
ADJUSTMENT_COMMENTS
Indexed - no
Format - varchar2 (100)
May be null? yes |
Text describing the adjustment to the special budget
balance (specified by the SPECIAL_BUDGET_OBJECT) for the AWARD_FUND.
Examples: 'close-out', 'ADJ PBIL FOR FINAL FUND 540819', 'from fund
540990'
Values:
List of values not available.
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section; Adjustment
Comment |
ADJUSTMENT_DATE
Indexed - no
Format - date
May be null? yes |
The date and time the record was created in the PennERA Proposal Tracking
system for the adjustment to the special budget balance (specified by
the SPECIAL_BUDGET_OBJECT)
for
the
AWARD_FUND.
Business Objects hint: to select adjustments for a particular date
(say, 8/31/2004), set your query conditions to ADJUSTMENT_DATE is greater
than or equal to 8/31/2004 and ADJUSTMENT_DATE is less than 9/1/2004.
(The system will supply the time--12:00:00 AM--for both dates.) By
default, the time will not appear in your report, but you can change
the format of the cell if you desire.
Example: 8/31/2004 03:34:33 PM
Values:
List of values not available.
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section; Adjustment
Date |
ADJUSTMENT_TYPE
Indexed - yes
Format - varchar2 (34)
May be null? no |
The reason for the adjustment to the special budget balance
(specified by the SPECIAL_BUDGET_OBJECT) for the AWARD_FUND.
Values:
Award Restriction - the sponsor has stipulated that
a portion of the award (equal to the ADJUSTMENT_AMOUNT)
may not be spent
CarryOver-Unexpended Balances - the
ADJUSTMENT_AMOUNT is a residual amount of
unspent funding from one budget period of a sponsored
project, which the sponsor has allowed to be carried over
and to be used in the next authorized budget
period of the project
CarryOver-Unliquidated Obligations - the
ADJUSTMENT_AMOUNT is a residual amount of encumbered
funding from one budget period of a sponsored project, which
the sponsor has allowed to be carried over and to be used to
relieve the encumbrance in the next authorized budget period
of the project. (An example of an unliquidated obligation is
the amount of a purchase order for something ordered before
the end of a budget period but paid (liquidated) after the end
of that budget period.)
Conversion - the adjustment was made in July, 2004 as
part of the effort to convert the special budget process from a
manual process to an automated one
Closeout - the adjustment was made as part of the fund
closeout process, to ensure that the special budget reflects what
was actually spent on the project. (The residual amount is handled
per the sponsor's requirements.)
EDU Transfer - as authorized by the sponsor, the
ADJUSTMENT_AMOUNT has been transferred
from one federally-sponsored student aid fund to another
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section; Adjustment
Type |
AWARD_FUND
Indexed - yes
Format - char (6)
May be null? yes |
The 6-character code identifying the fund to which the adjustment applies.
A fund uniquely identifies a specific set of financial resources that needs
tracking
or
management. Funds for sponsored projects
begin with ‘5’.
See also FUND_RESPONSIBLE_ORG in this table, and AWARD_FUND in the
PENNERA_INCREMENT table.
Examples: 537997 ( '5-R01-AI48117-02'); 541102 ('2003-2005
SCHOLAR AWARD'’)
Values:
Refer to the FUND_CODES table for values.
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section; Fund Number
|
FUND_ADJ_PK
Indexed - yes
Format - number (9)
May be null? yes |
A sequence number that uniquely identifies a record in the PENNERA_FUND_ADJ
table. (More than one adjustment can be entered for a given special budget
for a given fund on a given day.) The
sequence
number is generated by the special budget process of the PennERA Proposal
Tracking system.
Values:
4321 to 999,999,999
PennERA source: STAGING.PROPOSALFUNDADJ.ADJ_ID |
FUND_RESPONSIBLE_ORG
Indexed - yes
Format - char (4)
May be null? no |
The 4-character code identifying the Organization responsible for managing
all of the money tracked by the AWARD_FUND. An Organization is a subdivision
of the University created for management purposes. An Organization belongs
to only one responsibility center, and its Organization code is unique.
That is, no two Organizations have the same value for FUND_RESPONSIBLE_ORG.
To facilitate Organization-based security, FUND_RESPONSIBLE_ORG is
set to '.' if it would otherwise be null.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; View fund; Responsible Org |
INSTITUION_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 fund adjustment 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,
INSTITUTION_NO is the one recommended for display in reports.
Example: 00216424
Values:
List of values not available
PennERA source: Login; Proposals;
Budget; Awarded; the proposal header (at the top of the screen); eight-digit
number at the beginning of the first line of the header |
LAST_EXTRACT_DATE
Indexed - no
Format - date
May be null? yes |
The date this fund adjustment record was extracted from the PennERA Proposal
Tracking system and loaded into the Warehouse.
Example: 10/28/2004 Values:
List of values not available. |
PAR_PI_PRIACADAPPT_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 Principal Investigator (PI) for
the proposal that is the parent of the proposal to which the fund adjustment
applies. If the proposal to which the fund adjustment
applies has no parent, PAR_PI_PRIACADAPPT_ORG_CODE
is ‘.’.
Currently, the Office of Research Services is not entering
data for parent proposals, so all instances of PAR_PI_PRIACADAPPT_ORG_CODE
have the value ‘.’.
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 how the primary academic appointment is determined, see the explanation
in the Cautions section of the documentation for the EMPLOYEE_GENERAL table.
PAR_PI_PRIACADAPPT_ORG_CODE reflects the primary academic appointment
org. of the PI for the parent proposal, as it was at the time of the
proposal (funding cycle). Once the funding cycle has ended, the
PAR_PI_PRIACADAPPT_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 PI for
the parent proposal has no employee information about a faculty job appointment
dating back to the time of the funding cycle, PAR_PI_PRIACADAPPT_ORG_CODE
is ‘.’.
To facilitate Organization-based security, records with a null value
for
PAR_PI_PRIACADAPPT_ORG_CODE have the value changed to '.' in the
Warehouse.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL.PAR_PI_PRI_ACAD_APPT_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO
|
PARENT_PI_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 Principal Investigator (PI) for
the proposal that is the parent of the proposal to which the fund adjustment
applies.
If the proposal to which the fund adjustment
applies has no parent, PARENT_PI_ERA_PRI_ORG_CODE
is ‘.’.
Currently, the Office of Research Services is not entering data
for parent proposals, so all instances of PARENT_PI_ERA_PRI_ORG_CODE
have the value ‘.’.
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').
PARENT_PI_ERA_PRI_ORG_CODE reflects the ERA primary org. of the PI for
the parent proposal, as it was at the time of the proposal (funding cycle).
Once the funding cycle has ended, the PARENT_PI_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 table.
To facilitate Organization-based security, records with a null value
for
PARENT_PI_ERA_PRI_ORG_CODE have the value changed to '.' in the
Warehouse.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL.PARENT_PI_ERA_PRI_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO |
PARENT_PI_HOME_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the home organization (‘org.’) for
the Principal Investigator (PI) for
the proposal that is the parent of the proposal to which the fund adjustment
applies. If the proposal to which the fund adjustment applies has no parent,
PARENT_PI_HOME_ORG_CODE is ‘.’.
Currently, the Office of Research Services is not entering data
for parent proposals, so all instances of PARENT_PI_HOME_ORG_CODE
have the value ‘.’.
The home org. is the org. that owns the person's employee record and
is responsible for its maintenance.
PARENT_PI_HOME_ORG_CODE reflects the home org. of the PI for the parent
proposal, as it was at the time of the proposal (funding cycle). Once
the funding cycle has ended, the PARENT_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 PI for
the parent proposal has no employee information dating back to the time
of the funding cycle, PARENT_PI_HOME_ORG_CODE is ‘.’.
To facilitate Organization-based security, records with a null value
for
PARENT_PI_HOME_ORG_CODE have the value changed to '.' in the Warehouse.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL.PARENT_PI_HOME_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO |
PARENT_PI_INV_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the investigator organization (‘org.’)
for the Principal Investigator (PI) for
the proposal that is the parent of the proposal to which the fund adjustment
applies. If the proposal to which the fund adjustment applies has no parent,
PARENT_PI_INV_ORG_CODE is ‘.’.
Currently, the Office of Research Services is not entering
data for parent proposals, so all instances of PARENT_PI_INV_ORG_CODE
have the value ‘.’.
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 example, if the proposal to which the fund adjustment applies
has INSTITUTION_NO 22222222, and its parent has INSTITUTION_NO 11111111,
then a record for INSTITUTION_NO 11111111 exists as a proposal in the
PENNERA_PROPOSAL table, and the parent PI (the PI for INSTITUTION_NO
11111111) exists in the PENNERA_PROPOSAL_INVESTIGATOR table
as an investigator associated with the proposal that has INSTITUTION_NO
11111111.
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, records with a null value
for
PARENT_PI_INV_ORG_CODE have the value changed to '.' in the Warehouse.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL.PARENT_PI_INV_ORG_CODE where PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO |
PARENT_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 Principal Investigator (PI) for
the proposal that is the parent of the proposal to which the fund adjustment
applies. If the proposal to which the fund adjustment applies has no parent,
PARENT_PI_PRI_APPT_ORG_CODE is ‘.’.
Currently, the Office of Research Services is not entering
data for parent proposals, so all instances of PARENT_PI_PRI_APPT_ORG_CODE
have the value ‘.’.
The primary appointment org. is the org. where the person has his or
her primary job appointment, per the University’s employee census
logic. For further information
on how the primary appointment is determined, see the explanation
in the Cautions section of the documentation for the EMPLOYEE_GENERAL table.
PARENT_PI_PRI_APPT_ORG_CODE reflects the primary appointment org. of
the PI for the parent proposal, as it was at the time of the proposal
(funding cycle). Once the funding cycle has ended, the
PARENT_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 PI for
the parent proposal has no employee information dating back to the time
of the funding cycle, PARENT_PI_PRI_APPT_ORG_CODE is ‘.’.
To facilitate Organization-based security, records with a null value
for
PARENT_PI_PRI_APPT_ORG_CODE have the value changed to '.' in the
Warehouse.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL.PARENT_PI_PRI_APPT_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO
|
PARENT_PROP_RESP_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code that identifies the organization responsible for
the proposal that is the parent of the proposal to which the fund adjustment
applies.
If the proposal to which the fund adjustment applies has no parent,
PARENT_PROP_RESP_ORG_CODE is ‘.’.
Currently, the Office of Research Services is not entering
data for parent proposals, so all instances of PARENT_PROP_RESP_ORG_CODE
have the value ‘.’.
To facilitate Organization-based security, records with a null value
for
PARENT_PROP_RESP_ORG_CODE have the value changed to '.' in the
Warehouse.
Example: 4261 (DM-Rheumatology)
Values:
Refer to the ORG_CODES table for values.
Source: PENNERA_PROPOSAL.PARENT_PROP_RESP_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO
|
PENDING
Indexed - yes
Format - number (10)
May be null? no |
A Yes/No flag indicating whether the fund adjustment has been
posted
in the General Ledger, or whether it is pending.
Values:
Y - yes, the adjustment is pending (it has not been posted
in the General Ledger)
N - no, the adjustment is not pending (it has been posted
in the General Ledger)
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section. If the adjustment
appears
under 'Pending Adjustments', PENDING is 'Y'; if it appears under
'Adjustment
History', PENDING is 'N' |
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 Principal Investigator (PI) for
the proposal to which the fund adjustment
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’.
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’.
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.
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.PI_ERA_PRIMARY_ORG_CODE
where PENNERA_PROPOSAL.INSTITUTION_NO =
PENNERA_FUND_ADJ.INSTITUTION_NO
|
PI_HOME_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the home organization (‘org.’) for
the Principal Investigator (PI) for
the proposal to which the fund adjustment
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 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.PI_HOME_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO
|
PI_INVESTIGATOR_ORG_CODE
Indexed - yes
Format - char (4)
May be null? yes |
The 4-character code for the investigator organization (‘org.’)
for the Principal Investigator (PI) for the proposal to which the fund
adjustment 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.
Source: PENNERA_PROPOSAL.PI_INVESTIGATOR_ORG_CODE
where PENNERA_PROPOSAL.INSTITUTION_NO =
PENNERA_FUND_ADJ.INSTITUTION_NO |
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 Principal Investigator (PI)
for the proposal to which the fund adjustment 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
how the primary academic appointment is determined, 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 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.PI_PRI_ACAD_APPT_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO
|
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 Principal Investigator (PI)
for the proposal to which the fund adjustment 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. For further information on
how the primary appointment is determined, see the explanation
in the Cautions section of the documentation for the EMPLOYEE_GENERAL table.
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 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.PI_PRI_APPT_ORG_CODE where
PENNERA_PROPOSAL.INSTITUTION_NO
= PENNERA_FUND_ADJ.INSTITUTION_NO
|
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 fund adjustment 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,
INSTITUTION_NO is the one recommended for display in reports.
Example: ‘0000000217’
Values:
List of values not available
PennERA source: STAGING.PROPOSALFUNDADJ.PROP_NO
|
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 fund adjustment 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: Login; Proposals;
Budget; Awarded; the proposal header (at the top of the screen); the four-digit
number between the dashes on the third first line
of the header
|
SPECIAL_BUDGET_OBJECT
Indexed - yes
Format - char (4)
May be null? no |
The 4-character code that identifies the special budget to which the
fund adjustment applies. See also COA_OBJECT and COA_ACCOUNT in
the BALANCES table.
Values:
PBIL - the authorized project billable amount
(the total amount that may be billed to the sponsor of the fund)
PBUD - the authorized project budget
(the total amount that may be spent on the project)
PTCS - the authorized project total cost sharing
(the total amount provided for the project by a source
other than the project's sponsor)
PennERA source: Login; Proposals;
Budget; Awarded; Fund/Acct Setup button; Funds section; Special Budgets button;
Adjustments section; Trans Type
|
