conflict with absense

[Former Member]

Hi Experts,

I have got an issue in IT2001 which says "Conflict with Absence". This issue is happening only when the leave is applied through ESS Portal, but if the same is tried through ECC it is just showing us a collision check and if we continue it is allowing us to proceed further.

Attached are the screenshots explaining my issue in detail. Appreciate if you could help me the solution to over come this issue.

Through R/3.

Absence type 06UL – Unauthorized Leave available for 3 days,

  If Leave is applied through R/3 it is allowing us after showing the collision check as mentioned below.

Through ESS

Regards,

Akshay

Only Through ESS it
is not allowing. Please help.

[Former Member]

Hi Experts ,

I was able to change the error into warning through BADI  nut now while posting the leave through RPTARQPOST i am getting the same error . please suggest how to enhance ( some BADI or user exits for this program) as i am unable to find one.

Thanks

Akshay

[siddharthrajora]

if there is a conflict of absence, it ll be hard error! we dont allow overlapping absence or attendance, even rptarqpost will just report hard collision error. Collision check like PA30 wont be available, it just present error in ESS or in backed report as i explained earlier.

[Former Member]

There is encountered if there is a leave request from ESS that has not yet been approved/rejected by the approval authority. You can verify this using tcode PTARQ, Check documents. The employee will not be allowed to apply again for the same period until the existing leave application is acted upon.

[Former Member]

Hi Tania ,

i have checked the tcode . there is nothing pending with the pernr .

Please help.

Thanks

Akshay

[former_member219272]

i think from your screen shot my understanding is

in IT2001 absence type 06UL - Unauthorized Leave

is maintained between

05.08.2013 to 05.08.2013

06.08.2013 to 06.08.2013

07.08.2013 to 07.08.2013

for the same employeee

in ECC backend in IT2001 you are maintaining for absence type 03PL privilage leave

05.08.2013 to 07.08.2013

so it is giving a collision where as when you try from ESS it is giving a error message

i believe you waned to change the error message into a warning message?

why do you want to override an absence 06UL - Unauthorized Leave to 03PL privilage leave?

[Former Member]

Hi ,

I want to override. It is possible in R/3 but not in portal.

Thanks

Akshay

[former_member219272]

try in R/3 to make the overriding happen

i believe may not allow you to save i believe

[former_member219272]

please have a look at the below link

Move to HR - Change HR Abscence record collison error messages to warning message in SAP CATS - Port...

[former_member219272]

before making any changes

want to know why you want to override

i dont think it should be allowed

what happens HR user maintain this entry in PA30 in IT2001? then manager approvers another leave type for the same day it will be overwriten then there is not history or audit in this

[Former Member]

Hi Vijay ,

yeah there is nothing history nor audit . and i have checked the link and done the setting accordingly  but the message is still error.

Thanks

Akshay

[Former Member]

Hi ,

As it is a functionality in PA30 , we want it in ESS as well.

Thanks

Akshay

[jagan_gunja]

Whatever is in CATS would not be part of Audit log (or infotype records change report).

As the others have mentioned, you should not be allowing conflicts in any environment R/3 or otherwise.

In CATS you need to ensure it is not allowed as in R/3.

In ESS it is possible the validation may not be as in R/3.  This can happen if decoupled infotype framework is not used. This needs to be checked and the same function should be used as in R/3.

[siddharthrajora]

collision checks are not available in Leave Request

this was discussed a while ago, Read here

http://scn.sap.com/thread/3828286

[Former Member]

Hi Siddhart ,

I checked the thread link given by you .

So it means that its not possible in ESS even through ABAP coding?

Thanks

Akshay

[siddharthrajora]

Thats correct, it wont be easy, as Leave request was built on Time managers workplace and not meant to have similar functionality like PA30. I would recommend to stick with standard hence we had released many notes to explain this functionality.