PeopleSoft Learning

Following points that you need to know when applying bundles /patches to peoplesoft

1. Source Status means the condition of the object from the Source DB perspective; the Source DB is your DEMO.
2. Target Status means the condition of the object from the Target DB perspective; the Target DB is usually your DEV or TST environment.
3. The status is determined by PS during the compare process by looking at the LASTUPDOPRID of each object type. If the LASTUPDOPRID = ‘PPLSOFT’ the object will have a status of either CHANGED or UNCHANGED. If the LASTUPDOPRID <> ‘PPLSOFT’ the object will have a status of *CHANGED or *UNCHANGED. The other status is ABSENT, meaning the object doesn’t exist in one DB or the other.
4. The UPGRADE ACTION is what PS proposes to do with the object; DELETE the object from the Target DB, COPY the object from the Source to the Target DB or COPYPROP, copy properties of the object from the source to the target DB (Look at COPYPROP as the same as COPY).
5. The Take action is simply a default action recommended by PS – Upgrade this object or do not Upgrade this object.
6. The Copy Done flag simply indicates if the object has been copied, these values are reset when a project is copied from one DB to another.
7. If the object has a source / target status of CHANGED / *CHANGED, 9 times out of 10 you should go with the PS object overwrite. This means a customization will be overwritten; however, you know your customizations better than you know the changes PS is making so it is usually much easier to reapply customizations rather than apply new PS changes to your customized object.
8. If the object has a status combination of ABSENT / *CHANGED – unless you KNOW this is a bolt-on, in which case it would not be in the project to begin with, you should DELETE the object. If you do not delete objects that PS wants to delete, especially PeopleCode and RecFields, it can make the system very unstable, pages won’t pull up, error out, etc …