Shared Financial System (SFS)
Please send any SFS questions or comments about this site to:
Welcome to the SFS Operations Website!
As a part of our upgrade of the Shared Financial System (SFS) to PeopleSoft 9.1, we have also created a new SFS Operations website to provide you with all of the SFS business process documentation, forms, and news that you need in one easy-to-navigate location. We have attempted to refresh and migrate all of the documentation from the previous Operations site, but if something is missing, or you're not sure where something is located, please contact us at firstname.lastname@example.org. For any Financial procedures / policies that you can't find on this site, please visit http://www.uwsa.edu/fadmin/fap.htm.
SFS is the Financial System of the University of Wisconsin System and is on PeopleSoft version 9.1. The goal of SFS, and of the people who support it, is to provide a single integrated financial system that enables each institution to execute their core business processes in a streamlined and flexible environment that meets users' needs.
Tips and Tricks
Occasionally, when code or security changes are put into SFS, a user’s browser cache needs to be cleared in order to delete any previous “history” and force the browser to use the most current security or code. If an SFS support team member recommends that you “clear your cache”, the steps in the following link detail that process. Clearing Browser Cache
The below section outlines any known issues in SFS and resolutions to the issues.
Run Controls on Queries Which Contain Prompts
When scheduling a query that contains prompts, if an existing run control is used that was also being used by another query with prompts, the run control becomes unusable. The query and all subsequent queries will fail with the error ""First operand of . is NULL, so cannot access member Criteria (180,236) PSQUERY.MAIN.GBL.default 190 0-01-01 ExecQry.OnExecute Name.ExecQuery PCPC:3354 Statement 74 Called from PSQUERY.MAIN.GBL.default 190 0-01-01 ExecQry.OnExecute Name.ExecQuery Statement 138"
Until this PS bug is resolved, users should create a new run control for that query or rename the query before scheduling it.