APAR status
Closed as documentation error.
Error description
When a query is run that displays relative date/time stamps, there are some cases when the resultant records are opened, the date/time stamps shown are different. This problem has been seen in TRIRIGA 3.5.0, 3.5.1.2, and later releases.
Local fix
N/A
Problem summary
When a report query is created against multi business objects, the driving metadata for query is the base business object of the module. In this case triTask is base bo. triPlannedStartDT and triPlannedEndDT fields have "Relative DateTime" flag property checked where as the underline record (triWorkTask) does not have the flag chaked so it displays the value in user timezone. Query displays the UTC value based on base BO flag which is checked.
Problem conclusion
Report query against mulitiple business objects reads the metadata from the base business object. For the datetime values to work correctly, "Relative" property on the field on base business object should match with the other business objects in the same module.
Temporary fix
Comments
APAR Information
APAR number
IV93276
Reported component name
TRI APPLCATION
Reported component ID
5725F26AB
Reported release
350
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-09
Closed date
2017-02-23
Last modified date
2017-02-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"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":"350","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 March 2022