A PAC can only have an FA as its parent, and an FA can only have an Application as its parent. If the PAC you want to change has an FA parent, you would have to go through the following steps:
Before you send a Funding Action to GCA, it must be in Approved status. To approve it, open the FA, and then click Approve in the left navigation menu. After it is approved, the Send to GCA link displays in the left navigation menu, if there are no Holds. Click this link to send the FA to GCA. The associated application will be changed from Approved to Awarded status as soon as the FA is sent to GCA.
Once the FA is sent, it displays a pink banner with “In GCA” and is no longer editable by OSP. This means you can view but not change any of the information in the FA.
Only individuals with the OSP System Administrator ASTRA role can delete Admin Actions, Funding Actions, or Subcontracts. If you have the System Administrator role, you’ll see a Delete option under the Actions + button next to the item. If you do not have this role, you will need to consult with someone who does.
To delete an item in SPAERC, you must have the OSP System Admin ASTRA role.
For Funding Actions, you can delete one
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.
You must click on the associated check box to include any of the optional Body Text or Closing sections in the email (including “Free Text”).
The SAGE/SPAERC system automatically generates and sends several email messages during eGC1 routing and after OSP approval.
For information about email messages associated with approvals, review Approvals: Reviewer Notifications.
Also review the following sections in the Communications chapter:
The OSP Notes page displays any information provided by an OSP staff member in the OSP Notes field. OSP Notes also displays system-generated information about changes in status, assignments, and holds, and the creation of auto-generated documents. If the application was created by copying another, that is indicated and includes the number of the original eGC1.
The History & Comments page provides an overview of all actions related to approvals, from when the application is first completed to when it is approved by OSP, including withdrawals, returns, and re-completions. For Grant Runner and Adobe package applications, submission status is also displayed here. History & Comments also includes any comments entered by campus users or OSP when processing the application. If the application was created by copying another, that is indicated and includes the number of the original eGC1.
If a campus unit cannot find a specific sponsor when using the Sponsor Chooser, they should follow the instructions which appear on that page.
The instructions read:
If you cannot locate the sponsor in our database, please complete the following three steps:
If a person is an Owner (PI, Admin Contact, Budget Contact, eGC1 Preparer) or has Read/Write status, either directly assigned on the eGC1 or through the Global Edit ASTRA role, they can update the Contacts & Access page.
If the eGC1 has a connected budget, then the Budget Preparer is also an Owner.
SAGE checks that all of the required fields have data and all required attachments are in place for the Grant Runner forms. In addition, SAGE checks for any NIH errors or warning. You cannot complete an eGC1 if any errors are present.
The application would be one that involves the use of vertebrate animals (non-fiscal compliance question AU-1 = Yes). The Animal Subjects node appears as an approver if the application is After-the-Fact (ATF). If not ATF, then if the Application Type is Transfer from Another Institution or Supplement and Extension.
Otherwise, the node is added “just-in-time” when the sponsor notifies the PI that the proposal has received a fundable score. The PI or other application owner adds Animal Subjects to the Approval Graph as an ad hoc Watcher. This sends an email notification to the Animal Subjects reviewers and gives them access to the application.
Just-in-time application types are:
For more information, see Approvals: Compliance Reviewers.
If the user opened the item before you exited, they will need to close out and then re-open to switch from read-only access to read-write. If you had not properly exited the item by either using “Save & Close” or “Back to Spaerc Tasklist”, you can re-open the item, and exit properly to clear your hold on it. Then the user should re-open it.
Send an email to email@example.com; if necessary, they will consult with ORIS. However, if the system is down or you are receiving a 99 error, call the ORIS Help Desk directly at (206) 685-8335 and leave a voice mail. The desk is staffed Monday through Friday, 8:00AM to 5:00PM.
All Admin Actions have the same choices for attachment types, so changing from one AA type to another should not be a problem. If you’re changing an Admin Action into a Funding Action, the only attachment type in common is Internal (UW) Document. See the Common AA Fields section of the User Guide for more information.
After you make changes to your Tasklist Options, click Update View to see the results of those changes. This changed view is temporary and will be used only until you log out of SPAERC or close your browser window.
If you want to save a particular view of a tasklist as its standard one, click the Actions button, and then select Save Tasklist Settings.
Try opening the Tasklist Options and clicking Clear Sorting to clear any existing sort order, then click the column you want to sort on. Sorting is cumulative in SPAERC, which means that if you click a second column without clearing the existing sort order, items will be sorted by the first column and then the second column.
Note: You can also sort items in your tasklist by using the Initial Sorting for Items section of the Tasklist Options, then updating the view.