JOC Cockpit raises errors when users click the "Late" Button in the Daily Plan view

Current Situation

• When the JOC Cockpit uses PostgreSQL as the database user clicks the "Late" button in the Daily Plan, it throws an error:
  com.sos.commons.hibernate.exception.SOSHibernateQueryException: could not extract ResultSet: 0 ERROR: operator does not exist: interval >= integer Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts. Position: 1172 [select p.id as plannedOrderId,p.submissionHistoryId as submissionHistoryId,p.controllerId as controllerId,p.workflowName as workflowName, p.workflowPath as workflowPath,p.orderId as orderId,p.orderName as orderName,p.scheduleName as scheduleName, p.schedulePath as schedulePath,p.calendarId as calendarId,p.submitted as submitted,p.submitTime as submitTime,p.periodBegin as periodBegin,p.periodEnd as periodEnd,p.repeatInterval as repeatInterval,p.plannedStart as plannedStart, p.expectedEnd as expectedEnd,p.created as plannedOrderCreated,o.id as orderHistoryId, o.startTime as startTime, o.endTime as endTime, o.state as state from DBItemDailyPlanOrder p left outer join DBItemHistoryOrder o on p.orderId = o.orderId where p.controllerId = :controllerId and p.startMode=:startMode and ((o.state <> 0 and o.startTime - p.plannedStart >= 60) or (o.state is null and p.plannedStart < :currentTime) ) and p.submissionHistoryId in (select id from DBItemDailyPlanSubmission where submissionForDate=:submissionForDate) ][currentTime=2022-10-04 13:35:43,controllerId=controller_4422,submissionForDate=2022-10-04 00:00:00,startMode=0]
• When the JOC Cockpit uses an another dbms and user clicks the "Late" button in the Daily Plan, the Late calculation not throws an error but can be wrong.

Desired Behavior

• When clicking the "Late" button in the Daily Plan view, when the JOC Cockpit uses the PostgreSQL database, then it should not throw an error.
• The Late calculation should work correctly.