Penn Computing

University of Pennsylvania
Penn Computing << go backback
PENNERA_REQ_STAT_HIST Table - Data Element Index    Tables and Data Elements   PennERA Proposals Home   Data Warehouse Home


DWSP Schema

Records information on how the status of a request (within a funding cycle (proposal) for a sponsored project) has changed over time. A request is the portion of the requested amount for the proposal, that applies to a given budget period within the proposal, or to a supplement to a given budget period within the proposal. The PENNERA_REQ_STAT_HIST table includes the proposal's ID (INSTITUTION_NO), the request number, the status, the effective date of that status, and information on when and by whom the status data was entered. There is one PENNERA_REQ_STAT_HIST record per proposal, per request, per each change in the request's status.

Common Uses

  • Reporting on requests based on how their status has changed over time. ("How much time passed between when the request was placed in Pending status and when it became Awarded?")
Primary Key Indexed Data Elements Related Tables



  • There are two different unique identifiers for a proposal (funding cycle): INSTITUTION_NO and PROP_NO. INSTITUTION_NO is the identification number assigned by the University. PROP_NO is the identification number 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.
  • 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.
  • The REQUEST_NUMBER uniquely identifies a request within a proposal. Each request applies to one and only one budget period within the proposal; a budget period may include one or more requests. For information on the budget period to which a request applies, see the record in the PENNERA_REQUEST table for the INSTITUTION_NO (or PROP_NO) and the REQUEST_NUMBER.
  • The PENNERA_REQ_STAT_HIST table stores information on how the status of a request has changed over time. The current status of the request is also stored in the PENNERA_REQUEST table. For the current status for the proposal (funding cycle), see the PENNERA_PROPOSAL table. For more details on how the proposal's status has changed over time, use the PENNERA_PROP_STAT_HIST table.
  • Proposal records created on or after Oct. 9, 2006 may have been created in the Proposal Development (PD) module of PennERA. If such a proposal has not yet been submitted to its sponsor, there are no PENNERA_REQ_STAT_HIST records for any of its requests. (If the proposal record was created in PD, PENNERA_PROPOSAL.PD_FLAG = 'Y'. If the proposal has been submitted to the sponsor, its proposal status history includes a record for the 'Pending' status. The proposal status history is stored in the PENNERA_PROP_STAT_HIST table.)
  • PennERA stores two dates in the request status history record: the REQUEST_STATUS_DATE (the date the status went into effect), and the RECORDED_DATE (the date the request status history record was created).
    • When a proposal status history record is being created by a PennERA user, the values for the REQUEST_STATUS_DATE and the RECORDED_DATE have the system date as their default value. Before the record is saved, the REQUEST_STATUS_DATE is edited (if necessary) to reflect the date when the REQUEST_STATUS went into effect. The value of the RECORDED_DATE, however, is always the date when the proposal status history record was created. For example, if a request was Awarded as of 10/30/2003, and that change in status was recorded in PennERA on 11/13/2003, the request status history record's REQUEST_STATUS_DATE is 10/30/2003, and its RECORDED_DATE is 11/13/2003.
    • Some request status history records have a null value for the REQUEST_STATUS_DATE, the RECORDED_DATE, or both of them.
  • The Research Services System, or RSS, was used before October 14, 2003 to track information on sponsored projects. Records converted from this legacy system might have minimal information available in the PENNERA_REQ_STAT_HIST table.
  • Before April 27, 2005, the PennERA system stored status information at the period level rather than at the request and increment levels. A status history record for a given period was converted to a status history record for each and every request within that period as follows:
    Period status Request status
    Advance Account not converted; not a valid request status
    Awarded Awarded
    Future Future
    Future Pending Future Pending
    Pending Pending
    Revised Budget Requested Revised Budget Requested
    Unfunded Unfunded
    Withdrawn Withdrawn
    • The current status for a period (that is, the status current as of April 15, 2005) was converted to the current status for all requests within that period except when the current status for the period was Advance Account. In that case, the current status for all requests within the period was set to the status that the period had just before its status became Advance Account.
    • PERIOD_STATUS_DATE and MODIFIED_BY in a given period status history record were converted to REQUEST_STATUS_DATE and MODIFIED_BY in the corresponding request status history record for each request within the period.

The Proposal Tracking module of PennERA, used at Penn since October 14, 2003 to track information on proposed and awarded grants and contracts. Request status data has been available since April 27, 2005.

PennERA is the University's electronic research administration system, providing support to faculty and research administrators for all sponsored project activity at the University of Pennsylvania.

PENNERA_REQ_STAT_HIST Table - Data Element Index    Tables and Data Elements   PennERA Proposals Home   Data Warehouse Home

Questions about this page? Email us at

Information Systems and Computing
University of Pennsylvania
Information Systems and Computing, University of Pennsylvania