Tag Archives: Funding Action

When can I delete a Funding Action?

To delete an item in SPAERC, you must have the OSP System Admin ASTRA role.

For Funding Actions, you can delete one

  • regardless of status
  • with or without a parent
  • whether or not it is in a Cycle

If the FA has a non-Subcontract child item, the “Mid-Hierarchy Delete” dialog will display.

Exceptions: You cannot delete an FA while it has a Subcontract child.

If an application has a related advance request, you will see an information box on its child Funding Action that states, “This funding action has a parent eGC1 with advances in which cost share and non-fiscal compliance responses may have been updated.”

The following image shows an example of this.

advance budget links on funding action

The information box will include a link to the related advance, as well as the status and date. If additional advances were processed in the last ~18 months of the award cycle, they will also be listed in the information box. To determine which advance is related to the funding action, hover over the Cycle Details tab, or click View Cycle Details.

NOTE: Any advances that exceed the maximum duration of 18 months will not appear in the funding action information box. The advance will, however, continue to display in the Cycle Details.

Click the ADV# link within the funding action information box. The SAGE Advance Budget request will open in a new tab. You will have view-only access. By default, the Request Summary page will be open. Scroll down to the Cost Share and Non-Fiscal Compliance sections to view the latest information, as shown in the following image.

associated advance non-fiscal compliance data in sage

To delete an item in SPAERC, you must have the OSP System Admin ASTRA role.

For Funding Actions, you can delete one

  • regardless of status
  • with or without a parent
  • whether or not it is in a Cycle

If the FA has a non-Subcontract child item, the “Mid-Hierarchy Delete” dialog will display.

Exceptions: You cannot delete an FA while it has a Subcontract child.

February 2019 SAGE Maintenance Release

General SAGE Suite Maintenance Items


Submission deadline warning notification no longer sent for RRF eGC1s

Principal Investigators and Preparers of eGC1s to the Royalty Research Fund (RRF) will no longer receive the automated email sent from SAGE 3-6 days prior to the Sponsor Deadline when the proposal is marked as not ready for submission. This notification was not applicable to RRF proposals and caused confusion.

SAGE Budget

Add links to connected eGC1s and Budgets on SAGE task lists

When an eGC1 is connected to a SAGE Budget, links between the two will now display on the My eGC1s and My Budgets task lists, making it quicker and easier to navigate between the two.

my e g c 1 page showing connected budget link

my budgets page showing connected e g c 1 link

Prefix and/or Suffix fields added for personnel in SAGE Budget

Users can now enter a Prefix and/or Suffix for personnel in SAGE Budget. These will display on the Budget worksheet, and when using the Grant Runner Budget Sync feature will flow directly to the NIH RR Detailed Budget form on the connected eGC1. This ensures personnel will display on the sponsor form with their preferred titles/credentials.

Budget Sync performance improvements

The new Grant Runner Budget Sync feature has been optimized to now perform faster, allowing users to complete their proposals more quickly.

SAGE Grant Runner

Allow Grant Runner eGC1s to route with Grants.gov and NIH errors

The Certify & Route page of the eGC1 has been updated to make routing choices more clear and intuitive.

Additionally, when using a Grant Runner eGC1, as long as the eGC1 is marked “Ready to Submit” = No, users will now be allowed to route their eGC1s for review while there are still outstanding NIH and Grants.gov errors.

A new warning displays on Certify & Route page when there are grants.gov and/or NIH errors:

example of warning message


Add Award Modification Number to Cycle View

The Cycle view in SPAERC has been updated to include a “Mod Nbr” column to reflect Award Modification Numbers on Funding Actions and Modification Numbers on Subaward Actions.

Changes to Defaulting Behavior on Funding Actions

Defaulting logic for the Disposition and Carryover fields on Funding Actions has been revised to improve data accuracy.

  • If Payment type is changed to Cost Reimbursable from another value, then the Disposition of Balance field is reset to “Not Applicable”
  • If Payment type is changed to Letter of Credit from another value, then the Disposition of Balance field is reset to “Not Applicable”
  • If Sponsor is changed to Royalty Research Fund (RRF) from another value, then
    • Disposition of Balance field is reset to “Return to Sponsor”
    • Carryover is reset to “Automatic Carryover”
  • If SNAP is checked after a value is already set in the Carryover field, then the Carryover value is reset to “Automatic Carryover”

OSP Team C assignment updates

The rules that govern who the default OSP reviewer will be for eGC1s that have been routed for review have been updated to facilitate the appropriate eGC1s being assigned to OSP’s new Contracts Team. eGC1s will be assigned to the Team C Administrator under the following conditions:

  • Application Type = Non-Award Agreement (new) or Non-Award Agreement (continuation)
  • After the Fact (ATF) is marked “Yes” and the Sponsor Type is “Private Industry” or “Foreign Private Industry”


Add validation in SERA for missing short title

The Short Title on Funding Actions is now required in SERA prior to save in order to resolve an error that occurred when the Short Title was saved blank.

September 2018 Maintenance Release

Goal: Improve Award Data Quality & Transparency

Add link to MyResearch funding status details page from eGC1

For eGC1s that are in the Status of Approved, Awarded, or Denied by Sponsor, there will be two places where a user can link directly to MyResearch, to view processing details like holds placed on items, or comments left by OSP or GCA as funding actions are being set up.

  • eGC1 task list, via eGC1 Status hotlink
  • eGC1 left navigation

For eGC1s that are in Composing, Routing, or In OSP status, the left navigation element will not be shown, and the hotlink from the eGC1 status on tasklist will behave as it currently does (Routing or In OSP status takes a user to the Approvals page; Composing items have no hotlink on Status).

Add New Fields and “Terms & Conditions” section to the Funding Action

In order to streamline the award setup process and provide clarity on the terms and conditions, the following new fields will be added to the Funding Action in SPAERC and SERA:

  • Carryover (options: Requires Sponsor Approval, Automatic Carryover, Subject to Sponsor Limitations)
  • Carryover Explanation (when subject to sponsor limitations)
  • Disposition of Balance (options: UW to Retain, Return to Sponsor, Subject to Sponsor Limitations, Not Applicable)
  • Disposition Explanation (when subject to sponsor limitations)

There are three additional fields also added to the funding action that will improve our reporting, analytics, and sponsor award lookup capabilities:

  • Award Modification Number
  • Originating Sponsor Award Number
  • Non-Monetary Amount

In order to provide a more consolidated area for setup and viewing of award terms, a new section called Terms & Conditions will be added to the Funding Action. The new fields above, plus the previously labeled “GCA Flags” will bundle under this section, along with Payment Type and Equipment.

Changes to eFunding Action Receipt (Notification) to Campus (SAGE-327, SAGE-206)

The new Funding Action fields listed above will be added to the eFA Receipt PDF, which is sent to campus when GCA completes processing of a new action. The new Terms and Conditions section referenced above will be added as well, and all available data in that section of the FA will display. These changes will give campus more comprehensive information on new awards, and will match the language of the FA with that of SPAERC and SERA, which will aid communications between campus, OSP and GCA.

The body of the email that contains the FA Receipt PDF will now include an explanatory statement related to budget setup, to clarify that budget data will not appear in MyFinancial Desktop, Grant Tracker, and Ariba until the day after budget setup is completed in the Finance System.

Add New Fields to GCA Pending Actions Report

The new funding action data fields will be added to the GCA Pending Actions Report in SERA.

Default Funding Action Fields when the Sponsor is Royalty Research Fund

To streamline award setup when the Sponsor is Royalty Research Fund (RRF), many of the Funding Action fields will default a value but remain editable.

Update SPAERC Funding Action tabbing for accessibility and efficiency

SPAERC users can now easily tab through the fields of the Funding Action and perform their entry using only the keyboard and with a logical flow. This change will bring the funding action up to accessibility standards and provide users with added efficiency gains through less scrolling and repositioning of the cursor.

Goal: Comply with Sponsor System-to-System Requirements

Grant Runner Update to New Grants.Gov Header and Hash SAGE-70)

Grants.Gov has changed the way that proposal submission data files are to be structured, with the addition of a new header and hash. The changes will allow for a cleaner way of identifying a unique funding opportunity and formset, through introduction of a PackageID into the header. The Grant Runner system is updated to comply with this new change.

Grant Runner Update to New Grants.Gov Web Services (SAGE-71, SAGE-193, SAGE-204)

Grants.Gov has replaced the web services that provide funding opportunity details and submission status, to new ones, coinciding with the new PackageID introduction referenced above. Grant Runner is updated to now call the following new services:

  • GetOpportunityList
  • GetSubmissionList

Goal: Improve Technical Infrastructure & Monitoring

The following SAGE technical work supports the goal of improving monitoring of new SAGE work being released. Tentative

  • Additional unit tests added to Non-Fiscal Compliance section
  • Preliminary release and monitoring of new services to be utilized by Budget Sync October release

Goal: Deliver small enhancements that add clarity for users or deliver high value capabilities

FIDS: Minor Language Change on Submit Disclosure Page

The affirmation statement found on the FIDS Complete Disclosure page was changed to remove a School of Medicine-specific reference that could more generally apply. The statement now includes the agreement to include “further details of my financial interests, as requested by the Office of Research and, when applicable, the Office of the Vice Dean for Research, or their equivalent in my school/college…”.

AUMS: Language change in Consult Email

The email that AUMS applicants receive when a consult with the Occupational Health Nurse is required has been updated with new contact information and guidance, due to recent organizational and business process changes in EHS.