Time Constraint - 2011

[former_member182377]

Hi SAP Guru's

I have a requirement to stop the duplication occurs in IT2011,,currently system allows duplication. hence i wanted to stop it.

So i went to Time constraint table i gave the value as E and captured the changes in the TR, moved it to Test system , But test system doesnt reflect the change...

Is this a standard behavior of the system or any other special way need to be carried out for IT2011, would you please explain?

Thanks

Sriram

[vianshu · Accepted solution]

Hi Sriram,

How are you bringing in time events from time recording system to IT2011?

Regards,

Vivek

[former_member182377 · Accepted solution]

Hi Vivek.

we are bringing the time events to SAP through an interface which updates the data daily

Thanks

Sriram

[vianshu · Accepted solution]

Are you updating the interface table CC1TEV and then the posting program SAPCDT45 is posting to IT2011? Please confirm.

[former_member182377 · Accepted solution]

Hi Vivek,

yes we are,, because i could see in the table CC1TEV 200+ entries are there , and also job has been scheduled for the program SAPCDT45, which means yes they are doing ,

Please see the screenshot of CC1TEV, but i could see data's only for yesterday.. is this the way it works ?

Regards

Sriram

[vianshu · Accepted solution]

The data in CC1TEV depends on the frequency of your interface runs. The higher the frequency of run, the more latest data you will see.

Go to table V_T705B and create reaction 2 for status A00. This will ensure that duplicate time events are not posted.

I hope this will resolve your issue.

Regards,

Vivek

[former_member182377 · Accepted solution]

Hi Vivek,

Thanks for the guidance. i could see now in the table currently reaction has been set as 1,, which means it will allow duplicate entries right???

Because recently two times interface ran with same data and duplication occured in the TEVEN table as well..

so if i change it to 2,, there wont be no repeating right?

Thanks

Sriram

[vianshu · Accepted solution]

Yes, please change it to 2 and the system will not post duplicate entries in TEVEN table.

Regards,

Vivek

[former_member182377 · Accepted solution]

Hi Vivek,

Thank you very much for your quick guidance as always you are much helpful. 

Regards

Sriram

[former_member182377 · Accepted solution]

Hi Vivek.

thanks for your help so far,, i have successfully uploaded the files and moved in to the Teven table.. now i  have checked reaction indicator of A00 to 2 and checking duplication is occurring or not..

let you know once i complete my testing

Thanks

Sriram

[former_member182377 · Accepted solution]

Hi Vivek,

I have tested , test was successful, but sorry i said wrongly that reaction indicator for A00 has been set to 1,, it was actually set to 0, hence system allowed duplicated entries.

I changed the reaction indicator to 2 and i tested posting duplicate entries in teven.. system rejected when i tried to post the events.  i changed the reaction indicator to 1 and i tested posting duplicate entries.. but system put those entries in error pool. i couldn't see the entries in TEVEN table..

So both reaction indicator 1 and 2 stopping the duplicate entries isn't so?

Thanks

Sriram

[vianshu · Accepted solution]

2 is meant for stopping duplicate entires. Do an F4 for A00 and you will find what 1 stands for. Don't remember the functionality of return value 1.

Regards,

Vivek Barnwal

[former_member182377 · Accepted solution]

Hi Vivek,

Thanks for your help so far.. its been great.. reaction indicator also stops duplication, but it moves the things to error pool.. where reaction indicator 2 completely stops the duplication and rejected the entries itself.

Thanks

Sriram

[Former Member]

Time constraint is not the right concept to use for IT2011. It is not a normal Infotype with begda and endda.

You'll find useful settings in table T705B. One of them allows you to set a tolerance period within which th system considers bookings coming from the time clock as one. Say, you set it to 30 secs. An employee clocks in 08:35:15 and again 08:35:40. then the first one in overridden by the second. I don't remember which entry in T705b it is, but easy to spot.

Best wiches

Sven

[former_member182377]

Hi sven.

thank you so much for your reply ,, will check the things for sure in that table T705B

Thanks

Sriram

[harishtk1]

I do not think your Time Constraint will work for IT 2011 in the same way tt works for other Time related infotypes. 2011 is not an infotype as such it is a display interface for the TEVEN table and all the Time Events are stored there actually.

[former_member182377]

Hi Harish.

I tried out in Development system. it worked. but unable to move it to Test system.

Thanks

Sriram

[harishtk1]

Are you saying your transport is not going through? That is odd - Have you checked whether the contents are saved in the Transport Request?

[former_member182377]

Hi Hari,

Yes, it is..TR popping up i could see client number , infotype and time class have captured.

But changes are not moving. i have tried in two system i guess its a standard behavior. both systems changes are not moving.

Thanks

Sriram