APAR status
Closed as fixed if next.
Error description
If a task has a calendar and the 'Planned End' or the 'Actual End date/time' field values are updated, the Working Hours are not calculated correctly This problem can be seen by doing the following: 1. Open a new task 2. Name and save 3. Attach an availability calendar if the host project didn't already have one 4. Add planned start date 5. Add working hours 6. Save 7. Add an actual start date using hours different than the planned 8. Add actual end date 9. Note that the working hours do not seem to factor the calendar hours
Local fix
N/A
Problem summary
Task working hours are not calculating correctly. The issue was the values for the calendar fields (Year, Month, Day, etc) were not being correctly set. The fix is to set the Calendar fields exactly as we do for the other calculation methods.
Problem conclusion
Resolved a task record/Gantt chart issue where actual working hours and actual working days were not being correctly calculated when an actual end date value was entered. This is targeted to the 1h2017 release.
Temporary fix
Comments
APAR Information
APAR number
IV97838
Reported component name
TRI APPLCATION
Reported component ID
5725F26AB
Reported release
352
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-07-07
Closed date
2017-07-13
Last modified date
2017-07-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
None 999
Fix information
Applicable component levels
R352 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"352","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 March 2022