openerp-hr-experts team mailing list archive
-
openerp-hr-experts team
-
Mailing list archive
-
Message #00008
Re: Existing HR community modules
Hi!
Thanks! but my main aim is( as I told you) that both the process should be
related otherwise it will become a mess to manage assets. Suppose an
employee leaves a company then its contract will end but someone forgets to
release its asset. So, my point is simple no matter what module we will be
using but we must apply this functionality. And this was a must to have
requirement in one of the company where I implemented the OpenERP.
Second, the important thing will be the usability issue. The module
should have lesser number of steps to perform any task, try to keep as much
as possible every information in front of the user's view.
This is just a suggestion from me. Please correct me if I am wrong
somewhere. And I really ask the community members to give their input
because we can't reinvent the wheel again and again. So, everyone should
share their experience.
Thanks and Regards!
On Thu, Jul 26, 2012 at 8:50 AM, Ovnicraft <ovnicraft@xxxxxxxxx> wrote:
> Hello vivek, i am finishing what you said (and will upload ASAP), an
> employee with asset as responsible. but this as extension for asset
> management.
>
> Regards,
>
>
> On Wed, Jul 25, 2012 at 10:12 PM, vivek poddar <vivekimsit@xxxxxxxxx>wrote:
>
>> Hi,
>>
>> I was just wondering if the contact management and asset management are
>> closely related. For example, if we hire an employee then along with the
>> contract some asset will be assigned to him and as he leaves the company
>> the contract end and the assets assigned to him are back in the pool and
>> available for others.
>>
>> Thanks and Regards!
>>
>>
>> On Thu, Jul 26, 2012 at 4:55 AM, Ovnicraft <ovnicraft@xxxxxxxxx> wrote:
>>
>>>
>>>
>>> On Wed, Jul 25, 2012 at 4:55 AM, Daniel Reis <dreis.pt@xxxxxxxxxxx>wrote:
>>>
>>>> I found some extensions from the community, with valid extension to
>>>> build upon:
>>>>
>>>> http://bazaar.launchpad.net/~openerp-community/openobject-addons/trunk-addons-community/files
>>>>
>>>> I think it would be useful to fork or move them to this branch.
>>>> *Would a move be better than a copy/fork?*
>>>>
>>>>
>>>> Also, I'm sure that Payroll localizations add fields that are likely
>>>> candidates to be part of common hr/payroll extensions.
>>>> A quick review to my current HR system adds the following:
>>>> - Employee Analytic Account (Cost Centre)
>>>> - Income Tax type
>>>> - Social Security type.
>>>> - Contract reason (Hiring reason perhaps)
>>>> - Individual Contract type
>>>> - Collective labour agreement
>>>> - Labour Union
>>>>
>>>
>>> Yes i am agree with you, so i can work in hiring process, so
>>> hr_recruitment implements a good base but after hiring there is no contract
>>> created, i think in this process we can improve it and select contract
>>> type, wage, contract details, etc.
>>> In the same way when an employee ends a contract and both how take
>>> effect over job position when is hired this is busy (or maybe another word
>>> :) ) and when contract ends is available.
>>>
>>> Regards,
>>>
>>>
>>>> *Comments on these?
>>>> *
>>>> Regards
>>>> Daniel Reis
>>>> Securitas Portugal
>>>>
>>>>
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~openerp-hr-experts
>>>> Post to : openerp-hr-experts@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openerp-hr-experts
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Cristian Salamea
>>> @ovnicraft
>>>
>>> --
>>> Mailing list: https://launchpad.net/~openerp-hr-experts
>>> Post to : openerp-hr-experts@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openerp-hr-experts
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>>
>> -*- *Vivek Poddar* -*-
>>
>> *Technical consultant (OpenERP)*
>>
>> *Blog:http://vivekimsit.blogspot.in/
>> *
>>
>>
>
>
> --
> Cristian Salamea
> @ovnicraft
>
--
-*- *Vivek Poddar* -*-
*Technical consultant (OpenERP)*
*Blog:http://vivekimsit.blogspot.in/
*
References