Incorrect LAST_UPD in S_SRM_REQUEST for Repeating Instance in RCRs

Hi Experts,

Today I came across a strange behavior in Siebel RCRs. Our Application is in PST Time Zone.

For example, the job “IS Testing Job” runs at 02:30:00 AM, following is the sequence of steps that’s happening:

1.    On “2014-Feb-13 04:01:29 AM”, job successfully ended and a next instance was created for “2014-Feb-14” with Status in ‘Queued’ and Last Update Date has the value ‘2014-Feb-13 04:01:29 AM’.

2.    Exactly at “2014-Feb-14 02:30:00 AM”, SRProc fetches the instance and submits the request to the target component (WfProcMgr) via SRBroker.

3.    After submitting the job, SRProc updates the Status as ‘Active’ and Actual Start Date as ‘2014-Feb-14 02:30:00 AM’. Now the Last Updated Date for instance is seen as ‘2014-Feb-13 06:30:00 AM’ (which is wrong).