openerp-hr-experts team mailing list archive
-
openerp-hr-experts team
-
Mailing list archive
-
Message #00005
Re: Existing HR community modules
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
Follow ups
References