CA PPM: Project Team Last_Updated_date is updated automatically

Document ID : KB000109966
Last Modified Date : 13/08/2018
Show Technical Document Details
The field 'Last Updated Date' from the Project Team record (Project - Team) is updated automatically by CA PPM.  Why? 
This causes confusion to the users because they did not make any changes to the Project Team records from the CA PPM UI.
The 'Last_Updated_Date' in the Project Team (PRTEAM) record is updated by the Time Slicing job when it completes.   The completion date and time of the Time Slicing job replaces the prior Last Updated Date. 

1. user(aaaa) updates the Team tab, and Last_Updated_Date = 8/1/2018 

2. On 8/2/2018, user(admin) updates the Calendar for user(aaaa) and runs the Time Slicing job.  The PRTEAM record becomes: 
Last_Updated_Date = 8/2/2018

The action of updating the Resource Calendar forces a reslice of the PRTEAM.  If the Time Slicing job detects any object records with slice_status = 1 (record needs to be sliced),  it will process it and update the core tables (ex: INV_INVESTMENT, PRTEAM, etc.) with the date/time that the Time Slicing job last processed.

Additional Information:

A.This is not a defect, working as designed. The reason that the record is updated is that the time slicing job is updating data in the record based on the changes to the resources' availability calendar. The same thing will happen on tasks. This update is provided for security and compliance reasons to indicate that the data in the record has been modified.

The Audit Trail captures changes via a database trigger and logs the changed values in the CMN_AUDITS table. From this table, we display the before and after changes for a particular attribute under the "Audit" tab. This issue comes into play because we do not log a Studio datatype information in the CMN_AUDITS table. So, a database NUMBER, DATE, MONEY etc may differ with a Studio NUMBER, DATE, MONEY, PERCENT etc

Therefore, this is the reason why it is by design and so we must find out what the PM/user is doing specifically as that is the insight into why when reviewing the audit trail, to not assume the actual user did it. The audit trail merely tracks a change, and this does not infer the actual resource actually made the change directly.