• DATE_ENTERED
• EFFECTIVE_DATE
• ENTERED_BY_PENN_ID
• INSTITUTION_NO
• LAST_EXTRACT_DATE

• PROJID
• PROP_NO
• PROPOSAL_ACTIVITY
• PROPOSAL_ACTIVITY_COMMENTS
• PROPOSAL_ACTIVITY_ID

The date when the proposal activity record was created in PennERA. This might or might not be the same as the date when the proposal activity occurred. See also EFFECTIVE_DATE.

Note: The value of this data element sometimes includes not only the date, but also the time, although Business Objects displays only the date by default in reports. Business Objects users who set a condition on DATE_ENTERED and type a date value in the condition will find that Business Objects supplies 12:00:00 AM as the time. This does not matter if the value of DATE_ENTERED does not include the time, but if it does, that time is almost never 12:00:00 AM. Because conditions using an = (Equal to) operator will often not work as expected, use BETWEEN instead. For example, rather than setting the condition DATE_ENTERED Equal to 1/30/2008, set the condition DATE_ENTERED Between 1/30/2008 and 1/31/2008.

Example: 1/31/2008 4:13:12 PM

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the Updated Date field on the first line of the row of fields for the activity. (The row has multiple fields on the first line, and one field, for comments, on the second line.)

The date when the proposal activity occurred, as entered by the person who created the proposal activity record in PennERA. This might or might not be the same as the date when the proposal activity record was created in PennERA. See also DATE_ENTERED.

Note: The value of this data element sometimes includes not only the date, but also the time, although Business Objects displays only the date by default in reports. Business Objects users who set a condition on EFFECTIVE_DATE and type a date value in the condition will find that Business Objects supplies 12:00:00 AM as the time. This does not matter if the value of EFFECTIVE_DATE does not include the time, but if it does, that time is almost never 12:00:00 AM. Because conditions using an = (Equal to) operator will often not work as expected, use BETWEEN instead. For example, rather than setting the condition EFFECTIVE_DATE Equal to 1/22/2008, set the condition EFFECTIVE_DATE Between 1/22/2008 and 1/23/2008.

Example: 1/22/2008 11:06:43 AM

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the Effective Date field on the first line of the row of fields for the activity. (The row has multiple fields on the first line, and one field, for comments, on the second line.)

The Penn ID of the person who created the proposal activity record.

The name of the person who created the proposal activity record is PENNERA_PEOPLE.NAME where PENNERA_PEOPLE.PENN_ID = PENNERA_PROPOSAL_ACTIVITY.ENTERED_BY_PENN_ID

Example: 10021294

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the Penn ID of the person whose name is shown in the Updated By field on the first line of the row of fields for the activity. (The row has multiple fields on the first line, and one field, for comments, on the second line. ENTERED_BY_PENN_ID is not shown.)

The eight-digit sequence number used by the University to uniquely identify the proposal to which the activity applies. Note that the value for INSTITUTION_NO includes leading zeroes.

PENNERA_PROPOSAL_ACTIVITY includes three different identifiers for a proposal: INSTITUTION_NO, PROJID, and PROP_NO. INSTITUTION_NO is the proposal identifier that is recommended for use in reporting and in joining PennERA Proposals tables.

Example: 10003790

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the number shown in the Proposal field, in the upper right corner of the screen.

The date this proposal activity record was extracted from the PennERA Proposal Tracking system and loaded into the Data Warehouse.

Example: 3/31/2008

Values:
List of values not available.

The code used internally by the PennERA system to uniquely identify the proposal. The value for PROJID includes both letters and numerals.

PENNERA_PROPOSAL_ACTIVITY includes three different identifiers for a proposal: PROJID, INSTITUTION_NO, and PROP_NO. INSTITUTION_NO is the proposal identifier that is recommended for use in reporting and in joining PennERA Proposals tables.

Example: A8B99D6A420D42AEA4A577BA091B7544

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the PROJID for the INSTITUTION_NO shown in the Proposal field, in the upper right corner of the screen. (PROJID is not shown.

The 10-digit sequence number used internally by the PennERA system to identify the proposal within the Proposal Tracking (PT) and Proposal Development (PD) modules. Note that the value for PROP_NO includes leading zeroes.

(Within PT and PD, the combination of PROP_NO and INST_CODE uniquely identifies the proposal. Currently, the Data Warehouse stores only records whose INST_CODE is 'UPENN'. INST_CODE is not exported to the Data Warehouse.)

PENNERA_PROPOSAL_ACTIVITY includes three different identifiers for a proposal: PROP_NO, INSTITUTION_NO, and PROJID. INSTITUTION_NO is the proposal identifier that is recommended for use in reporting and in joining PennERA Proposals tables.

Example: 0000049848

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the PROP_NO for the INSTITUTION_NO shown in the Proposal field, in the upper right corner of the screen. (PROP_NO is not shown.)

A brief, standardized description of the proposal activity, which may be in upper case or in mixed case.

ORS logs activities for three areas. PROPOSAL_ACTIVITY begins with one of the following abbreviations (in upper case) to indicate the activity area:

• AR (accounts receivable and collections)
• MTA (material transfer agreements)
• PSC (PreAward-SRA(sponsored research agreements)-CTA(clinical trial agreements)) Note: this area also includes subcontracts for all instrument types. See also PENNERA_PROPOSAL.INSTRUMENT_TYPE.

If, for example, you wish to retrieve information only on accounts receivable and collections, you could set a condition specifying PROPOSAL_ACTIVITY LIKE 'AR%'. (Business Objects users would use the Matches Pattern operator instead of LIKE.)

In rare cases, due to a data entry error, the PennERA Proposal Tracking module's Activity Log screen may show an empty field (null value) for the standard description for the activity. That activity's PROPOSAL_ACTIVITY would be '.' in the Data Warehouse.

Examples: 'AR COLLECTION: RESPONSE FROM SPONSOR', 'MTA: Assigned to MTA negotiator'

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the Activity field on the first line of the row of fields for the activity. (The row has multiple fields on the first line, and one field, for comments, on the second line.)

Values:
List of values not available

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the unlabelled field on the second line of the row of fields for the activity. (The row has multiple fields on the first line, and one field, for comments, on the second line.)

The code used internally by the PennERA system to uniquely identify the proposal activity record. The value for PROPOSAL_ACTIVITY_ID includes both letters and numerals.

PROPOSAL_ACTIVITY_ID is needed as a unique identifier for the PENNERA_PROPOSAL_ACTIVITY record because there may be more than one proposal activity per proposal (INSTITUTION_NO), per EFFECTIVE_DATE or DATE_ENTERED, per PROPOSAL_ACTIVITY. More than one activity may have occurred on a given day. Also, because the Proposal Tracking Activity Log allows records to be entered but not updated, a given administrative activity for a proposal may have more than one PENNERA_PROPOSAL_ACTIVITY record, each with different comments.

Example: 434078CA99C6C012E043A57B5061C012

Values:
List of values not available.

PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): on the Activity Log screen for the proposal, the PROPOSAL_ACTIVITY_ID for row of fields for the activity. (The row has multiple fields on the first line, and one field, for comments, on the second line. The PROPOSAL_ACTIVITY_ID is not shown.)