Saturday, February 23, 2013

PeopleTool Objects Compare Report Status

When you  go through PeopleSoft compare report, first thing you will be interested to know is whether an object is changed or not. To determine this you will look into the compare status of each object definition. In this doodle we will discuss about the different compare status you can see in the compare report. We will also discuss how the Application Designer compare process determines on this compare status.

PeopleSoft shows the following statuses on Compare Reports.

Same - The compared definitions are defined the same in both databases that are compared. Such definitions need not be migrated to the other database.

Absent -  This status is shown when the definition is present in one of the databases but not in the other. If the target database does not have the definition, it may have to be migrated.

Unknown -  This is the default status for all non-comparison definitions. PeopleSoft doesn’t compare the definitions that show this status. They may have to be compared manually or using a non-PeopleSoft utility.

Changed -  This status states that there is a change in the definitions that are being compared, across the databases. This also states that the change was carried out by PeopleSoft (Oprid PPLSOFT)

*Changed - This status states that there is a change in the definitions that are being compared, across the databases. But unlike the previous status, in this case, the change was carried out NOT by PeopleSoft.

Unchanged -  Unlike the meaning of this status, there were changes found in this case as well. But the date time stamp on such definitions is prior to the release date time stamp on the compared databases. It also states that the change was carried out by PeopleSoft.

*Unchanged - This status is similar in meaning to the above status except that the changes to the objects in this case was carried out NOT by PeopleSoft.

Application designer determines one of the above compare status based on certain rules. Values of two fields LASTUPDDTTM and LASTUPDOPRID in PeopleTools object definition tables such as PSRECDEFN, PSPNLDEFN etc play major role in determining the compare status of each object.

  • LASTUPDDTTM field in PeopleTools object definition tables stores a date/time stamp of when the object was last modified.
  • LASTUPDOPRID field in PeopleTools object definition tables stores the OPRID of who made the modification. Proprietary OPRID is PPLSOFT for delivered modifications by ORACLE.

The compare process will check whether the object’s LASTUPDDTTM value is greater or lesser than the RELEASEDTTM value for the comparison release level (stored in PSRELEASE) to determine whether the object has changed. The compare process also checks LASTUPDOPRID to determine who has changed the object.Based on these two values determines the compare status by applying the below rules: 
  • If the LASTUPDDTTM of the definition (PS_JOB etc) in the database is less than release table's RELEASEDTTM from PSRELEASE and LASTUPDOPRID is PPLSOFT,the status for this object in Compare Report will be "Unchanged".

  • If the LASTUPDDTTM of the definition (PS_JOB etc) in the database is greater than release table's RELEASEDTTM from PSRELEASE and LASTUPDOPRID is PPLSOFT, the status for this object in Compare Report will be "Changed"

  • If the LASTUPDDTTM of the definition (PS_JOB etc) in the database is greater than release table's RELEASEDTTM from PSRELEASE and LASTUPDOPRID is not PPLSOFT, the status for this object in Compare Report will "*Changed".

  • If the LASTUPDDTTM of the definition (PS_JOB etc) in the database is less than release table's RELEASEDTTM from PSRELEASE and LASTUPDOPRID is not PPLSOFT, the status for this object in Compare Report will "*Unchanged".

2 comments: