Attendee booking after a leaving action

Hello,
I have a problem when booking an amployee (PV00) after a leaving action.
The employee is active in HR until 28.2.2007 (leaving action for 1.3.2007) and training's days are from 26.2.2007 to 1.3.2007. As the employee is not active for all the training days, a error message occurs "Enter a valid attendee". Does the customizing allow to book an attendee althought he is not active for the complete training's duration (in thise case juste one day...)? The manager wants to "offer" this training's day.
We are not using Time Management.
Does anyone have a solution ?
Regards
Michel

Hi,
You will not be able to book him directly, but can be booked on that date as an external person for that particular business event.
Regards,
Amit
Reward all helpful replies.
Actually thats the only alternative left when an employee is terminated before the expiry of that event.To be more secure you can create a new relationship with your requirement to select in these cases.
Message was edited by:
Amit Khare

Similar Messages

Problem after Performing Leaving action related to OM

Scenario:
Hi this is the first time i am working in a an SAP HR environment where all most all components like OM,PA,Payroll,Time,PD etc is implemented in 4.6 Version.
I had seen in the production server that after performing the Leaving action of the employee his/her Postion will change to 999999(Default postion) when we view InfoType 0001 0r 0000.
But in case of 1 employee it did not change to 999999 after leaving action was performed.It still shows the Position what he held when he was Active.
Qn 1.In the above case which is right?
Qn.2 what should ideally happen in Standard SAP system in such case.
Q3. Can we change that postion to 99999 (default) of an employee whose status in Withdrawn?
Qn.4. Anyoption other than rehiring and terminating him to sove this?(is this option itself is right practise?)
TIP: I dont know if the end user properly followed the steps in doing the Leaving Action

Hi Abhilash,
If you are getting the default position then the Integration plogi - preli is set to 99999999. and you should get it for all the termination action. Check with the user if she had run the leaver action as per your infogroup (in case her user profile is not set up)
Ideally thats the way it is set up as we dont need a position for a Terminated employee, and that position can be filled up by someone else.
You can change it to 99999999 if all other positions are default as per your termination action.
Regards
Uday

Effect of leaving action on the Pre-booking end date

Consider a case ,the prebooking period of the Business Event type is 1 jan 2006 to 31 dec 2006.
Employee X,Y and Z have been prebooked for the above business event type.
But we put a leaving action for X for the date 30 Nov 2005 .(the leaving action was put in the system on 15 nov 2005)
For the employee y the leaving action is put for the date 31 jan 2006.(the leaving action is put in the system on 15 jan 2006)
and for the Employee Z the leaving action is put for the date 28Feb 2006 .(the leaving action is put in the system on 1 March 2006)
What will be the effect on the Pre-booking dates.
Kindly let us know .

Dominique,
Thank you for the detailed problem description. Although you posted it some ten hours ago I have just now finished reading it.
Form pages must be built so they can operate correctly when inline validation errors are displayed. The assumption (by the engine) is that session state (and package state) as it exists at the point the validations are performed is sufficient (and correct) to support the redisplay of the page without the need to fire on-load processes or computations. Session state or package state changes made by after-submit computations or after-submit/before computations/validations processes that prevent correct page behavior on the "validation redisplay" must be avoided.
The condition types Inline Validation Errors Displayed/No Inline Validation Errors Displayed can be used for on-load events/controls (processes, computations, regions, items, ...) for which you need finer control over this behavior.
Also, you can forgo the use of after-submit computations when the resulting alteration of session state would be inimical to proper "validation redisplay" behavior and use On Submit - After Computations and Validations processes instead.
I hope I have understood your situation and that this answer adequately answers your questions.
Scott

Leaving action

Hi Experts,
Pls guide me to solve the issue related to leaving action of emp in PA40.
When an employee left the company, which infotypes needs to be delimited.
Is it receommanded to put the practice to enter Run payroll up to, Do not account after in IT0003?
Can end user maintian IT0003 for left employee? or it can be possible for only exceptional circumstances?
What will be the recommanded porcess to release the pension in case of retired employee?
I want to get the complete information ,connection between IT0003 and leaving action.
Thanks & Regards,
Nirali P

Hi Nirali,
When an employee left the company, which infotypes needs to be delimited.
All the basic infotypes, like 0000,0001,0007,0008 and statutory infotypes of the country will be delimited. The best would be to check the standard configuration of SAP, where in SAP would have advised which infotypes to be delimited for leaving action.
Is it receommanded to put the practice to enter Run payroll up to, Do not account after in IT0003?
I would say , it would depend on company to company and scenario based. But mostly it is seen IT0003 is modified only in cases where exceptions are there.
Can end user maintian IT0003 for left employee? or it can be possible for only exceptional circumstances?
depends on the level of authorisation you are providing to to the end user
What will be the recommanded porcess to release the pension in case of retired employee?
Can you elaborate what u mean by this

Leaving action with IT0003

Hi Experts,
Pls guide me to solve the issue related to leaving action of emp in PA40.
When an employee left the company, which infotypes needs to be delimited.
Is it receommanded to put the practice to enter Run payroll up to, Do not account after in IT0003?
Can end user maintian IT0003 for left employee? or it can be possible for only exceptional circumstances?
What will be the recommanded porcess to release the pension in case of retired employee?
I want to get the complete information ,connection between IT0003 and leaving action.
Thanks & Regards,
Nirali P
Edited by: Nirali P on Aug 19, 2011 8:13 AM
Edited by: Nirali P on Aug 19, 2011 9:08 AM

Hi Nirali,
When an employee left the company, which infotypes needs to be delimited.
All the basic infotypes, like 0000,0001,0007,0008 and statutory infotypes of the country will be delimited. The best would be to check the standard configuration of SAP, where in SAP would have advised which infotypes to be delimited for leaving action.
Is it receommanded to put the practice to enter Run payroll up to, Do not account after in IT0003?
I would say , it would depend on company to company and scenario based. But mostly it is seen IT0003 is modified only in cases where exceptions are there.
Can end user maintian IT0003 for left employee? or it can be possible for only exceptional circumstances?
depends on the level of authorisation you are providing to to the end user
What will be the recommanded porcess to release the pension in case of retired employee?
Can you elaborate what u mean by this

Program for Leaving Action..

Dear All,
We have created a leaving action with set of Infotypes and certain actions and we have to carry out this action for about 5,000 employees.
Now user needs to have a certain program to carry out the action as it's not feasible to carry out manually for 5,000 employees.
Now my qestions to you all is
1. Do you have any Std Program which takes care of this
2. IS their any Std Function Module/BAPI exists which can be used
3. Do we need to write our own BTC/LSMW/etc
Kindly suggest.
FYI : I have already tried one program using the FM - HR_INFOTYPE_OPERATION but this FM is not working for Action - DELIMIT (LIS9) for various Info types so now wondering what to do next. Kindly suggest.
Thanks and have a nice day ahead.
Mit freundlichen Grüßen/Best regards,
Mangalagi S V

Dear All,
Thanks to all those who have responded to this.
Unfortunately I can't go for BDC also as I was told that they might add/delete certain info types for this particular action.
In my program, I am reading table T588M for the action and taking all the infotypes and the related action into my own internal table, after that I am generating the dynamic internal table for each infotype and then reading the Infotype using HR_READ_INFOTYPE and proceeding for related operations using HR_INFOTYPE_OPERATION but this LIS9 was not working so I have to check out as Suresh suggested. Hope every things goes fine with my coding...!!, any way it looks to be big exercise and needs lots of testing.
Thanks for your valuable inputs.
Regards,
Mangalagi S V

Leaving action 84 in PA40

Dear Expert,
Please let me know how to assign leaving action 84 only in tcode PA40 in a particular user, i have already assign parameter ID UGR with value 40, all action are appear there bu we have to provide leaving action 84 only, suggest me the object or any other steps which we have to take.
Thanks in advance
Sanjay Kumar Jha

>In your post you mentioned that you maintain UGR with a value 40 for the Leaving Action 84, and you want to configure only this action to a particular user.
>If the same UGR(as per your post 40) is maintained for all other Action types ?
>The answer is yes,then
(If you maintained the same same UGR(40) for all action types including Leaving action 84 and in the user profile of that particular user you maintained UGR as 40 then that user can access all the Action Types defined with UGR 40)
>Please maintain a different UGR(Say 88 ) for that particular action , and assign that different UGR (Say 88) to the profile of that particular user
>After made changes in the UGR for that particular action, please talk with you BASIS person and make changes regarding UGR(change UGR from 40 to the new one , here say 88) settings for that particular user's profile
Happy SAPing

Leaving action infogroup and operations

Hello experts,
in leaving action which all infotypes we should delimit by operation LIS9 ? why it is not advicd to delimit actions(0000) and organization assignment(0001) infotypes using this?

hi,
It is not advised to delimit 0000 & 0001 bcoz u want to see/analyse/report the details of employees who have seperated. Master data is not deleted for employees who have left the company.
SKR

HRA amount doubling in middle of month leaving action

HRA for an individual is 100 Rs per month. It is working fine for all the months during the employee's tenure in organization.
In case of leaving action/retirement action when an employee retires on 13th of April, AND then when i run payroll at end of month for that employee the system is giving HRA of 200 (doubling up) as it is creating two records of 01.04.2009 to 13.04.2009 and 14.04.2009 to 31.12.9999.
If an employee retires at end of month, then amount is coming as 100 only.
Can u please guide as to what to do. Do i need to write a rule or is there anything wrong with action as i have checked all processing classes 1 to 72 including 10, 20. No factoring is being done as this is a fixed amount wage type.
This is also happening in all other wage types in infotype 8 which have not factoring including Washing allowance and facility encashment, amount is getting doubled.
Basic and VDA are behaving fine as they are being factored.

Hi Tarun,
Just compare the HRA wage type's processing, cumulation classes with the basic wage type (which one is coming correct, with out doubling the amount).
And also compare the processing, cumulation classes with the standard HRA wage type. It may work.
Try it out and let me know.
Thanks & Regards
Bharathi

Change infotypes end date when delete leaving action for employee

Hello,
I created new infotype and when employee leaves its end date is changed for leaving date.
When leaving action is deleted ther is some least of infotypes that user can sign so the end date of selected infotypes will be changed to 31.12.9999. How can i add my infotipe to this list?
Thank you,
Paulina

Hi,
Maintain IT 0041 where in that table maintain employee start date of hiring and leaving date of employee bze in IT 0000 the dates will change as per action lets say if employee hire that date will be in IT 0000 action and if employee gets promotion date or leaving date that will store in IT 0000 by delimiting other actions
So maintain IT 0041 where you can pull dates from there if you maintain
End date will always be 31.12.9999 so check action start date you will get in sequence
Thanks
Edited by: Vibinsap on Mar 9, 2012 7:12 AM

Delimit several infotypes for Leaving Action

Hi,
I would like to know how to 'Send' or call a backend program to delimit infotypes called during the leaving action of the employee. thus calling several infotypes but sometimes configured in such a way it is dependent on the status of the EE or have PY record.
Thanks!

Hi Binoj,
thx. i tried this:
0000              MASSN     06     0     *     * TERMINATION - DELIMIT RECORDS*
0000              MASSN     06     10     P     T001P-MOLGA='34'
0000              MASSN     06     20     P     P0000-MASSN='10'
0000              MASSN     06     30     I     LIS9,9021,,,,,(P0000-BEGDA)
0000              MASSN     06     40     I     LIS9,9022,,,,,(P0000-BEGDA)
0000              MASSN     06     50     I     LIS9,9023,,,,,(P0000-BEGDA)
0000              MASSN     06     60     I     LIS9,9024,,,,,(P0000-BEGDA)
delimit process has been done..
but we still have to input delimit date
btw what is '/D' for?
looking forward to hearing from you.
best regards,
dhenny muliawaty (pei pei)

Important infotypes in a Leaving action

Hi Experts,
Plz tell me the important/ mandatory infotypes that needs to be included in a leaving action.
Also, tell me the important/mandatory infotypes that needs to be delimited during the leaving action so that no furthur payroll run can be done by the system.
regards
Kunal

Hi,
When you do the leaving action in IT0000, please delimit IT0002, IT0006, IT0014, IT0015, IT2001, IT2002, IT0207, IT0208, IT0209, IT0210, IT2010, IT0105, IT0185, IT0032 etc.
Do not delimit basic pay.
Hope this helps,
Reward points if helpful,
Thank You,

Date change in leaving action

Dear Experts,
I have a scenario where in SAP Master data employee's leaving action start date is 01.04.2011 and end date as 31.12.9999 where as in IDOC its start date of leaving action is 20.03.2011 and end date is 31.04.2011
Now user want me to maintain the IDoc record in sap, both start date and end date of the leaving action in that case how can i change bath the dates, as in PA41 if i will go only start date will be active but how can i maintain the end date.
or
as we have 2 actions for a person i.e. hiring and leaving
so the start date shall is change in the Hiring action start date place?? and
and end date shall i change in the start date of the leaving action??
please confirm me i am very much confisud
Replay ASAP, its very urgent
Thanks a ton in advance,

Hi,
Maintain IT 0041 where in that table maintain employee start date of hiring and leaving date of employee bze in IT 0000 the dates will change as per action lets say if employee hire that date will be in IT 0000 action and if employee gets promotion date or leaving date that will store in IT 0000 by delimiting other actions
So maintain IT 0041 where you can pull dates from there if you maintain
End date will always be 31.12.9999 so check action start date you will get in sequence
Thanks
Edited by: Vibinsap on Mar 9, 2012 7:12 AM

User id and Leaving action

hi experts,
there is a requirement from the client side.
when we pass the actions " Leaving and Retirement ", the system should ask for that particular employee's USER details and it should cancel the user authorization or cancel the USER NAME.(if that employee is a USER).
plz tell me any options r available.
regards
david

Hi
In the leaving action please maintain the infotype 0105 subtype 001 so that when the action is run that particular user id is delimited at that date.
R K

PA40 - Termination/Leaving Action - problems delimiting IT0014

Hi all,
For an upgrade from ecc 4.7 tot ECC 6.0 (ehp 4) I am testing some actions.
I've tested the Hire action and this test was successful. No Iu2019m testing the Termination/Leave Action. When I want to save the Organizational Assignment screen I get a message that the delimiting of IT0014 has failed.
Is anyone familiar with this problem? If so, could you tell me what I can do to solve this problem?
Thank you in advance!

Hi Ashley,
Please check SAP Note 1016799.
Regards,
Dilek

Attendee booking after a leaving action

Similar Messages

Maybe you are looking for