Both Virginia and Janis are out (Janis all week) so I can’t discuss this with them. I will discuss the trans-pool processing with Virginia as soon as she returns. Looking at it from a cost/benefit/risk perspective, I would question the value of doing the same sort of testing for upload transactions, for these reasons: Upload transactions are simply passed through the system. Like all transactions, they inherit a budget number’s attributes for the biennium in which they are processed, meaning they will pick up the correct organization and pca defaults (if any) as they pass through FAS. We have already shown with the labor transactions that the budget number index, the pca indexes and OCAP processing work as intended. I would have to be convinced that there is some additional benefit to doing as extensive of a test for upload transactions.
Yes. The programming is being worked on this week. We will have to consult with Virginia to assess how and when we will test.
As mentioned above, we were unable to see Biennium 07 data in the test system. The test environment does not interact with the TSAT security system and thus does not support testing of switch usercodes. I don’t believe there is any risk associated with having different organization codes associated with different user logins. You can however, by entering .DATA in the test system, switch to a different user data org code. You would enter this immediately upon beginning a new driver session. All of the 07 biennium data, at the point in time the data was loaded in the test system, is there, so we want to test to insure that you can see that data and will work with you to that end.
We are limited by time and resources. We need to carefully assess the risks and focus on high value activities.