Understanding Status
This table lists the possible statuses for the source and target.
| Status | Description |
|---|---|
|
Same |
The ADS instance is the same in both databases. When an instance in one database has this status, its counterpart in the other database will have the equivalent status. |
|
Changed |
The ADS instance’s LASTUPDOPRID value is PPLSOFT and the LASTUPDDTTM value is greater than the date/time stamp of the comparison release database. This indicates that PeopleSoft modified the instance since the comparison release. |
|
Unchanged |
The ADS instance’s LASTUPDOPRID value is PPLSOFT and the LASTUPDDTTM value is less than or equal to the date/time stamp of the comparison release database. This indicates that PeopleSoft modified the instance prior to the comparison release. |
|
*Changed |
The ADS instance’s LASTUPDOPRID value is not PPLSOFT and the LASTUPDDTTM value is greater than the date/time stamp of the comparison release database. This indicates that a customer modified the instance since the comparison release. |
|
*Unchanged |
The ADS instance’s LASTUPDOPRID value is not PPLSOFT and the LASTUPDDTTM value is less than or equal to the date/time stamp of the comparison release database. This indicates that a customer modified the instance prior to the comparison release. |
|
Absent |
The ADS instance is found in the other database, but not in this one. When upgrading to a new PeopleSoft release, all new PeopleSoft instances should have Absent status in the target database and all of your custom instances should have Absent in the source database. |
|
%Changed |
The ADS instance does not contain any tracking data. All untracked ADS definitions will have the status %Changed. This status will also appear for tracked ADS definitions when the source project is in an older release that does not contain any tracking data. |