Duplicate PIDM's in Banner - When will SCT automate handling of?
I recently attended the 'Duplicate PIDM Management' session at Banner Summit 2008.
Someone in the audience stood up and asked why SCT hadn’t addressed the Duplicate Pidm problem, and why we were all in this room coming up with our own solutions. Someone else stood up and mentioned this project was always just under the list of priorities of enhancements each year.
Another user said he would go out to www.BANDEV.net and create a forum. Then we should all go out there and complain about the duplicate pidm problems. I didn't see anything out there, so I'm starting it.
Every school that uses Banner deals with this problem. Think of all the combined IT hours spent each year merging PIDM records. There needs to be a way to automate this process and I believe SCT needs to bump this up on their To-Do list.
Does anyone else have comments?
- sebunzey's blog
- Login or register to post comments
Comments
I'm the one who suggested Bandev
Ahhhh - you beat me to it. I'm still catching up on the week that was(wasn't?) when I was way 'down South'.
Indeed, everyone --- everyone has the same problem, everyone is dealing with it, largely independantly, and Sungard says nothing.
At UCFV, we have developed a large script that will do a seek-and-merge for two PIDMs. You can run it in 'audit' mode, or in 'do-the-work' mode. Both methods give a list of Banner tables that have rows containing the PIDMs in question - and will say "yes, I can merge these", "no, I can't merge these - a person will have to do some work", or "I have never seen this table before - I need help".
Audit mode generates the report. Do-the-work mode merges things together.
Problems? Of course, we have problems. To do the merge, we have to drop constraints on a number of Banner tables. With Banner Self Service up all the time, we risk database corruption everytime we do this ... and we can't figure a way around this. (any ideas, folks???)
There was a neat java program shown (intermittantly, while the power was up), that made an on-line list of tables and rows that each PIDM had - I want to take a closer look at that. This is a _much_ better way to show table conflicts than a report.
SO - I suspect we have 2 ways to go here:
- path 1 - compare notes and alternatives and collaboratively build a PIDM Merge tool
- path 2 - build a groundswell of noise that will get Sungard moving to build a tool once and for all.
Thoughts?
(and thanks for posting up the message, sebunzey!)
--- Michael
michael.bayrock@ucfv.ca
Duplicate PIDM is not a sct issue
as per my knowledge SCT said Duplicate PIDM is not their issue. WHo ever creates them they have to fix it. Please review another forum for what GWU does here at bandev in this forum
Copy paste this link in your browser http://www.bandev.net/node/97
Vipul Patel
Senior Enterprise Resource Plng Developer
The George Washington University
ISS/AdminApps/BannerApps
vpatel@gwu.edu