Timing Differences seen between Innovus & Tempus

Hi Experts ,

I see the following timing differences between Tempus & Innovus . 

The path which is matching in Innovus but failing in Tempus .

Pasting the headers of both the reports :

Tempus : Failing 

Path 1: VIOLATED (-0.0222 ns) Hold Check with Pin regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_dout_shadow_s_reg[0]/CK->D

               View: mission_Pff_ff_V0990_T125_Xrcmax_Fsvt35_clock_hold_T0_rcmax

              Group: jtag_tck

         Startpoint: (R) regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_shift_reg_s_reg[0]/CK

              Clock: (R) jtag_tck

           Endpoint: (F) regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_dout_shadow_s_reg[0]/D

              Clock: (R) jtag_tck

            N-Sigma: 4.5000

                       Capture                         Launch

         Clock Edge:+   0.0000                         0.0000

        Src Latency:+   0.0196  ( 0.0196, 0.000)       0.0079  (0.0079, 0.000)

        Net Latency:+   0.3363  ( 0.3298, 0.001) (P)   0.2755  (0.2813, 0.001) (P)

            Arrival:=   0.3559  ( 0.3494, 0.001)       0.2834  (0.2892, 0.001)

               Hold:+   0.0284  ( 0.0201, 0.002)

        Uncertainty:+   0.1400

        Cppr Adjust:-   0.0392  ( 0.0323, 0.002)

      Required Time:=   0.4852  ( 0.4773, 0.002)

       Launch Clock:=   0.2834  ( 0.2892, 0.001)

          Data Path:+   0.1685  ( 0.1856, 0.004)

              Slack:=  -0.0222  (-0.0025, 0.004)

Path 1: VIOLATED (-0.0222 ns) Hold Check with Pin regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_dout_shadow_s_reg[0]/CK->D
View: mission_Pff_ff_V0990_T125_Xrcmax_Fsvt35_clock_hold_T0_rcmax
Group: jtag_tck
Startpoint: (R) regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_shift_reg_s_reg[0]/CK
Clock: (R) jtag_tck
Endpoint: (F) regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_dout_shadow_s_reg[0]/D
Clock: (R) jtag_tck
N-Sigma: 4.5000

Capture Launch
Clock Edge:+ 0.0000 0.0000
Src Latency:+ 0.0196 ( 0.0196, 0.000) 0.0079 (0.0079, 0.000)
Net Latency:+ 0.3363 ( 0.3298, 0.001) (P) 0.2755 (0.2813, 0.001) (P)
Arrival:= 0.3559 ( 0.3494, 0.001) 0.2834 (0.2892, 0.001)

Hold:+ 0.0284 ( 0.0201, 0.002)
Uncertainty:+ 0.1400
Cppr Adjust:- 0.0392 ( 0.0323, 0.002)
Required Time:= 0.4852 ( 0.4773, 0.002)
Launch Clock:= 0.2834 ( 0.2892, 0.001)
Data Path:+ 0.1685 ( 0.1856, 0.004)
Slack:= -0.0222 (-0.0025, 0.004)

Innovus : Meeting 

Path 1: MET (0.027 ns) Hold Check with Pin regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_dout_shadow_s_reg[0]/CK->D
View: mission_Pff_ff_V0990_T125_Xrcmax_Fsvt35_clock_hold_T0
Group: REG2REG
Startpoint: (R) regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_shift_reg_s_reg[0]/CK
Clock: (R) jtag_tck
Endpoint: (F) regif/tc_platform_n22ullph_extended_reg_inst_jtag_data_reg_i_dout_shadow_s_reg[0]/D
Clock: (R) jtag_tck
N-Sigma: 4.500

Capture Launch
Clock Edge:+ 0.000 0.000
Src Latency:+ 0.187 (0.187, 0.000) 0.187 (0.187, 0.000)
Net Latency:+ 0.382 (0.373, 0.002) (P) 0.339 (0.346, 0.001) (P)
Arrival:= 0.569 (0.560, 0.002) 0.526 (0.533, 0.001)

Hold:+ 0.029 (0.019, 0.002)
Uncertainty:+ 0.140
Cppr Adjust:- 0.025 (0.016, 0.002)
Required Time:= 0.714 (0.704, 0.002)
Launch Clock:= 0.526 (0.533, 0.001)
Data Path:+ 0.201 (0.223, 0.005)
Slack:= 0.027 (0.052, 0.006)

I see a huge difference between clock latencies in both the reports.

Any comment/ Suggestions . 

My timing is badly failing in Tempus .

Thanks