on 04-08-2010 10:42 AM
Dear Friends,
We are doing new ESS MSS implementation on ECC 6.0.
We have configured SAP R/3 to accomodate Collision of leaves in table V_T554Y (Global Time constraint raction) and we can create leave collision through PA30.
E.g: A person who has taken Annual Leave on a particular date can take sick leave on the same day. Sick leave will overwrite/delimit the Annual leave.
We are getting a collision error message while applying for the same leave (Sick leave in the above example) through ESS and not able to go further with the leave request. The same leave, I am able to create through PA30 in R/3.
Please suggest a solution.
Regards,
Preethi
Please note the checks of V_T554Y will not carried out extensively on ESS this is valid more so for PA30
Now for collision message there might be a leave which is colliding with the leave which is already posted in the
infotypes! Please follow the steps as in the note 1288919 to find the conflicting leave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sidharth, I know about the other leave which is creating collision, but I need to overwrite that with the current leave. My R/3 is supporting that. But here the issue is my ESS, which is not supporting this and giving an error while creating the new leave.
Please help me with the options I have to solve the issue?
I have same problem to you.
If the leave request is already maintained in PA30, the collision error message will raise and the request can not save to R/3.
Dear export, could you provide the solution about it, how can I update infotype based on request via portal approve. I know the collision message according to customizing V_554Y_B.
The leave request can not save data if the collision type is E(-The system does not allow you to create the new record, and
displays all collisions.), right?
Thanks a lot,
Anne
Hi,
Follow the path given below:
Img -> personnel management -> employee self-service ->service specific settings ->working time-> leave request->processing processess->define processing processes for each rule group-> select your rule group-> display-> Take account of Ongoing Requests --> uncheck both the options 'Check inclused unposted requests' and 'reamining leave without unposted requests'
Thanks,
Pinki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Then check T554s for the time contraint classes for the absent types and the table V_554Y_B for the reaction to collision:
There are 4 reactions:
A - The old record is delimited, all collisions are displayed.
E - The system does not allow you to create the new record, and
displays all collisions.
W - You can create the new record, but the old record
remains unchanged. All collisions are displayed.
N - As for W, but collisions are not displayed.
Thanks,
Pinki
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.