Some update, my issue turn out to be a program bug, fixed after apply notes 1550092, 1789084, 1793434 and 1868681.
And some more information about this data source, in case someone hit the same problem, it may also cause by:
1) Wrong setting in V_T569R for "05 Earliest recalculation date" and "06 Latest time data carry-over"
Reason: Only data between the configured date range will be loaded
2) Data source run parallel with time evaluations or other time data extractions (i.e. data source 0HR_PT_*)
Reason: All mentioned process will cause EE lock, 0HR_PT_2 will ignore the EE if failed to lock the EE, 0HR_PT_2 will pick up the ignored EE again in next try.