Hi All,
In this post i am gonna talk about the audit details of a peoplesoft object in target system after it has been migrated from a source database.
For any peoplesoft object we can open in app d, we can view the user id it was last modified by and on which date.When we migrate an object from source to target, we use a valid userid and password to login to the target database to copy the objects.
After the object is moved to target instance, what would we see in the fields last updated by and last updated on ?Would this be the userid that we used to login to target database? Well the answer is no .
When we copy any object from source to target database, the last updated on field is updated to current date and last updated by value is just taken from the source database.So what we see in the last modified by field in source database for that particular object will be the value of last updated by in target database.
Impact : Therefore while looking at the last updated by value, we need to consider if that user explicitly changed the object or it has been migrated from some other database and the user did not make any changes.
Same case happens, if you find last updated by values as PPLSOFT and date is very recent its not mandatory that a patch has been applied, it could simply have been migrated from another database.
In this post i am gonna talk about the audit details of a peoplesoft object in target system after it has been migrated from a source database.
For any peoplesoft object we can open in app d, we can view the user id it was last modified by and on which date.When we migrate an object from source to target, we use a valid userid and password to login to the target database to copy the objects.
After the object is moved to target instance, what would we see in the fields last updated by and last updated on ?Would this be the userid that we used to login to target database? Well the answer is no .
When we copy any object from source to target database, the last updated on field is updated to current date and last updated by value is just taken from the source database.So what we see in the last modified by field in source database for that particular object will be the value of last updated by in target database.
Impact : Therefore while looking at the last updated by value, we need to consider if that user explicitly changed the object or it has been migrated from some other database and the user did not make any changes.
Same case happens, if you find last updated by values as PPLSOFT and date is very recent its not mandatory that a patch has been applied, it could simply have been migrated from another database.
No comments:
Post a Comment