« September 2006 | Main | November 2006 »
October 30, 2006
Tuition rates
The Western Tuition Promise has features affecting accounts receivable and admissions. AR has new fee rates created for each year of 4 that the promise runs. The easiest scenerio is a new freshman starts out in year one and is guarenteed the same rate for 4 years. Other scenerios include transfer students and dual enrollment students. The 4 years starts when the student is admitted. Transfer students are a special case. The number of flat years they get depends on the number of earned hours transfered.
We need to be able to track these students in order to generate any kind of reporting on them. Admissions thought the best way to do this was to create a cohort during the admissions process. Currently there is a couple of table triggers on saradap that sticks the basic tuition rate on admitted students. I motified the insert and update table triggers to put in new the rates dependent on admit term, residency, and levl. In addition I need to create the cohort soo I stuck a table trigger on sarappd tied to the admit decision, residency, admit term, and levl.
Posted by wendlerb at 1:52 PM | Comments (0)
October 26, 2006
Cron job repeats
Yesterday when cedar dropped from the cluster, there was a glitch in the system causing all the cron jobs to be run multiple times. It has something to do with the system clock. The feed ran several times and so we felt it best to reset the flags and run it through again. There is a script feed_reset.sql that you have to stick a date in to use but it works well for that. The financial aid program, swbrdll, also ran multiple times putting on sometimes 9 times the amount of direct loans on a student record. I removed these records in tbrmemo and direct_pre_memo and let the process run again last night. This morning it looks like this worked real well.
Posted by wendlerb at 8:20 AM | Comments (0)
October 24, 2006
Admissions - credit card
We've had a problem with double charges on this app since it was created 3 programmers ago. The applicant as near as we can tell hits the back button and resubmits the credit card payment button.
We've tried:
Logic not to accept the 2nd mouse click - this works until they use back button.
Record lock - We locked a record for update and don't commit till we return to wou_web package. This prevents double clicking causing new pidm and id generation along with the double hit to the credit card server.
Wording - this helped some?
Spriden/tbraccd check - Since ssn is passed into credit card process, we decided to look and see if spriden record exists and if it does whether a transaction occured in last 24 hrs. Still got a double charge about 2 minutes apart.
Spriden Check - just checking for spriden record. Stay tuned...
Posted by wendlerb at 9:24 AM | Comments (0)
October 19, 2006
Swbmisc
This old report was not picking up any debit entries. I discovered it wouldn't any time you entered in any index or fopal in the paramters but would if you left them blank. Turns out the code was looking at charge fields only against parameters and debits are all pay fields. I stuck some or statements in there and got it to work.
Posted by wendlerb at 10:45 AM | Comments (0)
October 13, 2006
Mass Time
I put Wou mods onto the newest version of phpmtim. Ran into a problem with students getting kicked out who have a start date other than the first day of the month. There is a flag that checks payperiod dates and kicks out the error message payrill was getting on phrderr. I commented this out and so I hope this solves it.
In addition, phpltim was modified. This is the program that loads the mass time table phrmtim. In the past we broke the labor distribution for acct 10503 into a 25/75 split with GEN987 or GEN988 depending on the year. Now, we don't want these two indexes set up with a prog code. We want the prog code to come from the 25% index. This is what pzpttim now does.
Posted by wendlerb at 1:13 PM | Comments (0)
October 10, 2006
Oracle Forms Developer
Oracle Forms 10.1.2.0.2 is now reay for testing with banner.
I have the app on my h drive and have installed it on one of the machines in the office. You must use installer to deinstall previous versions, erase directories and oracle reg key. Then run the install again and follow through. We also need a newer version of PLSQL Developer to work with this oracle version. All forms will not be able to be brought in on the old 9i version once they have been converted
Posted by wendlerb at 11:40 AM | Comments (0)