OFBiz › OFBiz - Dev

Proposal for adding new functionality in Leave sub tab under HR module

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Swapnil Sawant

Proposal for adding new functionality in Leave sub tab under HR module

Hi,

I wish to do some enhancement in existing Leave functionality in OFBiz.

Existing functionalities :

- Currently employee can create leave by selecting his approver.

- Approver will approve the leave applied by the employee.

New functionalities are :

- Admin party can credit leave balance to only at the beginning of financial year to a party's leave account

- When employee creates a leave application, weekends and organization wide holidays won't be considered as a part of leave application.

- Whenever employee's leave application is approved, corresponding no. of leaves will get deducted from his/her account

- Employee will be able to see his/her current leave balance.

So for this :
I have decided to added a new field "noOfLeaves" in EmplLeave Table.
And for crediting the leaves and holidays I have created two new entityes as shown below.
CreditEmplLeave table keeps track of the current leave balance for an employee.
Holiday will maintain all the holidays in an organization.

<entity entity-name="EmplLeave"

package-name="org.ofbiz.humanres.employment"

title="Employee Leave Entity">

<field name="partyId" type="id-ne"/>

<field name="leaveTypeId" type="id-ne"/>

<field name="emplLeaveReasonTypeId" type="id-ne"/>

<field name="fromDate" type="date-time"/>

<field name="thruDate" type="date-time"/>

<field name="noOfLeaves" type="fixed-point"/>

<field name="approverPartyId" type="id-ne"/>

<field name="leaveStatus" type="short-varchar"/>

<field name="description" type="description"/>

<prim-key field="partyId"/>

<prim-key field="leaveTypeId"/>

<prim-key field="fromDate"/>

<relation type="one" fk-name="EMPL_LEAVE_PRTY" rel-entity-name="Party">

<key-map field-name="partyId"/>

</relation>

<relation type="one" fk-name="EMPL_LEAVE_ELETP" rel-entity-name="EmplLeaveType">

<key-map field-name="leaveTypeId"/>

</relation>

<relation type="one" fk-name="EMP_LEAV_REAS_ELTP" rel-entity-name="EmplLeaveReasonType">

<key-map field-name="emplLeaveReasonTypeId"/>

</relation>

<relation type="one" fk-name="EMPL_LEAVE_APPR" title="Approver" rel-entity-name="Party">

<key-map field-name="approverPartyId" rel-field-name="partyId"/>

</relation>

</entity>

<entity entity-name="CreditEmplLeave"

package-name="org.ofbiz.humanres.employment"

title="Credit Employee Leave Entity">

<field name="partyId" type="id-ne"/>

<field name="totalLeaves" type="fixed-point"/>

<prim-key field="partyId"/>

<relation type="one" fk-name="CRED_EMPL_LEAVE_PRTY" rel-entity-name="Party">

<key-map field-name="partyId"/>

</relation>

</entity>

<entity entity-name="Holiday"

package-name="org.ofbiz.humanres.employment"

title="Holiday's in organization">

<field name="holidayId" type="id-ne"/>

<field name="holiday" type="description"/>

<prim-key field="holidayId"/>

</entity>

Please give your suggestions on this.

Thanks & regards,

Swapnil Sawant

________________________________
This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

______________________________________________________________________

BJ Freeman

Re: Proposal for adding new functionality in Leave sub tab under HR module

I would suggest using the Party benifits.
this would allow more flexiblity for enterprises.
take a look at the datamodel and discusssion stating on page 319 vol I
of datamodel book.
the calculation should be a service that can be selected, though you
only need provide the one you are suggesting.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

Swapnil Sawant sent the following on 6/10/2010 2:13 AM:

> Hi,
>
> I wish to do some enhancement in existing Leave functionality in OFBiz.
>
> Existing functionalities :
>
> - Currently employee can create leave by selecting his approver.
>
> - Approver will approve the leave applied by the employee.
>
> New functionalities are :
>
> - Admin party can credit leave balance to only at the beginning of financial year to a party's leave account
>
> - When employee creates a leave application, weekends and organization wide holidays won't be considered as a part of leave application.
>
> - Whenever employee's leave application is approved, corresponding no. of leaves will get deducted from his/her account
>
> - Employee will be able to see his/her current leave balance.
>
> So for this :
> I have decided to added a new field "noOfLeaves" in EmplLeave Table.
> And for crediting the leaves and holidays I have created two new entityes as shown below.
> CreditEmplLeave table keeps track of the current leave balance for an employee.
> Holiday will maintain all the holidays in an organization.
>
> <entity entity-name="EmplLeave"
>
> package-name="org.ofbiz.humanres.employment"
>
> title="Employee Leave Entity">
>
> <field name="partyId" type="id-ne"/>
>
> <field name="leaveTypeId" type="id-ne"/>
>
> <field name="emplLeaveReasonTypeId" type="id-ne"/>
>
> <field name="fromDate" type="date-time"/>
>
> <field name="thruDate" type="date-time"/>
>
> <field name="noOfLeaves" type="fixed-point"/>
>
> <field name="approverPartyId" type="id-ne"/>
>
> <field name="leaveStatus" type="short-varchar"/>
>
> <field name="description" type="description"/>
>
> <prim-key field="partyId"/>
>
> <prim-key field="leaveTypeId"/>
>
> <prim-key field="fromDate"/>
>
> <relation type="one" fk-name="EMPL_LEAVE_PRTY" rel-entity-name="Party">
>
> <key-map field-name="partyId"/>
>
> </relation>
>
> <relation type="one" fk-name="EMPL_LEAVE_ELETP" rel-entity-name="EmplLeaveType">
>
> <key-map field-name="leaveTypeId"/>
>
> </relation>
>
> <relation type="one" fk-name="EMP_LEAV_REAS_ELTP" rel-entity-name="EmplLeaveReasonType">
>
> <key-map field-name="emplLeaveReasonTypeId"/>
>
> </relation>
>
> <relation type="one" fk-name="EMPL_LEAVE_APPR" title="Approver" rel-entity-name="Party">
>
> <key-map field-name="approverPartyId" rel-field-name="partyId"/>
>
> </relation>
>
> </entity>
>
>
>
> <entity entity-name="CreditEmplLeave"
>
> package-name="org.ofbiz.humanres.employment"
>
> title="Credit Employee Leave Entity">
>
> <field name="partyId" type="id-ne"/>
>
> <field name="totalLeaves" type="fixed-point"/>
>
> <prim-key field="partyId"/>
>
> <relation type="one" fk-name="CRED_EMPL_LEAVE_PRTY" rel-entity-name="Party">
>
> <key-map field-name="partyId"/>
>
> </relation>
>
> </entity>
>
> <entity entity-name="Holiday"
>
> package-name="org.ofbiz.humanres.employment"
>
> title="Holiday's in organization">
>
> <field name="holidayId" type="id-ne"/>
>
> <field name="holiday" type="description"/>
>
> <prim-key field="holidayId"/>
>
> </entity>
>
>
>
>
> Please give your suggestions on this.
>
>
>
>
>
> Thanks& regards,
>
>
>
> Swapnil Sawant
>
>
>
>
>
>
>
>
> ________________________________
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>
> ______________________________________________________________________

Swapnil Sawant

RE: Proposal for adding new functionality in Leave sub tab under HR module

Hi BJ,

Could you please elaborate a bit more on "using the Party benefits" ?

-----Original Message-----
From: BJ Freeman [mailto:[hidden email]]
Sent: Friday, June 11, 2010 1:31 PM
To: [hidden email]
Subject: Re: Proposal for adding new functionality in Leave sub tab under HR module

I would suggest using the Party benifits.
this would allow more flexiblity for enterprises.
take a look at the datamodel and discusssion stating on page 319 vol I
of datamodel book.
the calculation should be a service that can be selected, though you
only need provide the one you are suggesting.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

Swapnil Sawant sent the following on 6/10/2010 2:13 AM:

Swapnil Sawant

RE: Proposal for adding new functionality in Leave sub tab under HR module

Hi BJ,

Did you mean the sub-section 'Party Benefit' under section 'Benefits Definition and Tracking' ?

Thanks,
Swapnil Sawant

-----Original Message-----
From: Swapnil Sawant
Sent: Wednesday, June 16, 2010 11:14 AM
To: [hidden email]
Subject: RE: Proposal for adding new functionality in Leave sub tab under HR module

Hi BJ,

Could you please elaborate a bit more on "using the Party benefits" ?

-----Original Message-----
From: BJ Freeman [mailto:[hidden email]]
Sent: Friday, June 11, 2010 1:31 PM
To: [hidden email]
Subject: Re: Proposal for adding new functionality in Leave sub tab under HR module

I would suggest using the Party benifits.
this would allow more flexiblity for enterprises.
take a look at the datamodel and discusssion stating on page 319 vol I
of datamodel book.
the calculation should be a service that can be selected, though you
only need provide the one you are suggesting.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

Swapnil Sawant sent the following on 6/10/2010 2:13 AM:

______________________________________________________________________

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

______________________________________________________________________

______________________________________________________________________

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

______________________________________________________________________

BJ Freeman

Re: Proposal for adding new functionality in Leave sub tab under HR module

yes

Swapnil Sawant sent the following on 6/15/2010 11:12 PM:

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

> Hi BJ,
>
> Did you mean the sub-section 'Party Benefit' under section 'Benefits Definition and Tracking' ?
>
>
> Thanks,
> Swapnil Sawant
>
> -----Original Message-----
> From: Swapnil Sawant
> Sent: Wednesday, June 16, 2010 11:14 AM
> To: [hidden email]
> Subject: RE: Proposal for adding new functionality in Leave sub tab under HR module
>
> Hi BJ,
>
> Could you please elaborate a bit more on "using the Party benefits" ?
>
>
> -----Original Message-----
> From: BJ Freeman [mailto:[hidden email]]
> Sent: Friday, June 11, 2010 1:31 PM
> To: [hidden email]
> Subject: Re: Proposal for adding new functionality in Leave sub tab under HR module
>
> I would suggest using the Party benifits.
> this would allow more flexiblity for enterprises.
> take a look at the datamodel and discusssion stating on page 319 vol I
> of datamodel book.
> the calculation should be a service that can be selected, though you
> only need provide the one you are suggesting.
>
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com<http://www.specialtymarket.com/>
>
> Systems Integrator-- Glad to Assist
>
> Chat Y! messenger: bjfr33man
> Linkedin
> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>
>
> Swapnil Sawant sent the following on 6/10/2010 2:13 AM:
>> Hi,
>>
>> I wish to do some enhancement in existing Leave functionality in OFBiz.
>>
>> Existing functionalities :
>>
>> - Currently employee can create leave by selecting his approver.
>>
>> - Approver will approve the leave applied by the employee.
>>
>> New functionalities are :
>>
>> - Admin party can credit leave balance to only at the beginning of financial year to a party's leave account
>>
>> - When employee creates a leave application, weekends and organization wide holidays won't be considered as a part of leave application.
>>
>> - Whenever employee's leave application is approved, corresponding no. of leaves will get deducted from his/her account
>>
>> - Employee will be able to see his/her current leave balance.
>>
>> So for this :
>> I have decided to added a new field "noOfLeaves" in EmplLeave Table.
>> And for crediting the leaves and holidays I have created two new entityes as shown below.
>> CreditEmplLeave table keeps track of the current leave balance for an employee.
>> Holiday will maintain all the holidays in an organization.
>>
>> <entity entity-name="EmplLeave"
>>
>> package-name="org.ofbiz.humanres.employment"
>>
>> title="Employee Leave Entity">
>>
>> <field name="partyId" type="id-ne"/>
>>
>> <field name="leaveTypeId" type="id-ne"/>
>>
>> <field name="emplLeaveReasonTypeId" type="id-ne"/>
>>
>> <field name="fromDate" type="date-time"/>
>>
>> <field name="thruDate" type="date-time"/>
>>
>> <field name="noOfLeaves" type="fixed-point"/>
>>
>> <field name="approverPartyId" type="id-ne"/>
>>
>> <field name="leaveStatus" type="short-varchar"/>
>>
>> <field name="description" type="description"/>
>>
>> <prim-key field="partyId"/>
>>
>> <prim-key field="leaveTypeId"/>
>>
>> <prim-key field="fromDate"/>
>>
>> <relation type="one" fk-name="EMPL_LEAVE_PRTY" rel-entity-name="Party">
>>
>> <key-map field-name="partyId"/>
>>
>> </relation>
>>
>> <relation type="one" fk-name="EMPL_LEAVE_ELETP" rel-entity-name="EmplLeaveType">
>>
>> <key-map field-name="leaveTypeId"/>
>>
>> </relation>
>>
>> <relation type="one" fk-name="EMP_LEAV_REAS_ELTP" rel-entity-name="EmplLeaveReasonType">
>>
>> <key-map field-name="emplLeaveReasonTypeId"/>
>>
>> </relation>
>>
>> <relation type="one" fk-name="EMPL_LEAVE_APPR" title="Approver" rel-entity-name="Party">
>>
>> <key-map field-name="approverPartyId" rel-field-name="partyId"/>
>>
>> </relation>
>>
>> </entity>
>>
>>
>>
>> <entity entity-name="CreditEmplLeave"
>>
>> package-name="org.ofbiz.humanres.employment"
>>
>> title="Credit Employee Leave Entity">
>>
>> <field name="partyId" type="id-ne"/>
>>
>> <field name="totalLeaves" type="fixed-point"/>
>>
>> <prim-key field="partyId"/>
>>
>> <relation type="one" fk-name="CRED_EMPL_LEAVE_PRTY" rel-entity-name="Party">
>>
>> <key-map field-name="partyId"/>
>>
>> </relation>
>>
>> </entity>
>>
>> <entity entity-name="Holiday"
>>
>> package-name="org.ofbiz.humanres.employment"
>>
>> title="Holiday's in organization">
>>
>> <field name="holidayId" type="id-ne"/>
>>
>> <field name="holiday" type="description"/>
>>
>> <prim-key field="holidayId"/>
>>
>> </entity>
>>
>>
>>
>>
>> Please give your suggestions on this.
>>
>>
>>
>>
>>
>> Thanks& regards,
>>
>>
>>
>> Swapnil Sawant
>>
>>
>>
>>
>>
>>
>>
>>
>> ________________________________
>> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>>
>> ______________________________________________________________________
>
>
> ______________________________________________________________________
>
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>
> ______________________________________________________________________
>
> ______________________________________________________________________
>
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>
> ______________________________________________________________________
>

BJ Freeman

Re: Proposal for adding new functionality in Leave sub tab under HR module

In reply to this post by Swapnil Sawant

https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=PartyBenefit

https://demo-stable.ofbiz.apache.org/webtools/control/ArtifactInfo?type=entity&uniqueId=PartyBenefit

with benefit types and periods it seem to cover all the requirments.
I use the party from and to when the leave is mandated by union Agreement.
I have added the agreement ID
the agreement can also be part of the employee hiring, so this would be
part of the AddPartyBenefit (humanres/widget/forms/EmploymentForms.xml)
you can have type leave agreed upon, leave earned, leave approved,
leave used.
you can have many records of leave used.
and SECA can keep the totals.

in the records with leaved approved you can partyfrom the approver
to the party with the leave cumming.
Number of leaves can be computed by finding the appropriate type for a party

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

Swapnil Sawant sent the following on 6/15/2010 10:43 PM:

> Hi BJ,
>
> Could you please elaborate a bit more on "using the Party benefits" ?
>
>
> -----Original Message-----
> From: BJ Freeman [mailto:[hidden email]]
> Sent: Friday, June 11, 2010 1:31 PM
> To: [hidden email]
> Subject: Re: Proposal for adding new functionality in Leave sub tab under HR module
>
> I would suggest using the Party benifits.
> this would allow more flexiblity for enterprises.
> take a look at the datamodel and discusssion stating on page 319 vol I
> of datamodel book.
> the calculation should be a service that can be selected, though you
> only need provide the one you are suggesting.
>
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com<http://www.specialtymarket.com/>
>
> Systems Integrator-- Glad to Assist
>
> Chat Y! messenger: bjfr33man
> Linkedin
> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>
>
> Swapnil Sawant sent the following on 6/10/2010 2:13 AM:
>> Hi,
>>
>> I wish to do some enhancement in existing Leave functionality in OFBiz.
>>
>> Existing functionalities :
>>
>> - Currently employee can create leave by selecting his approver.
>>
>> - Approver will approve the leave applied by the employee.
>>
>> New functionalities are :
>>
>> - Admin party can credit leave balance to only at the beginning of financial year to a party's leave account
>>
>> - When employee creates a leave application, weekends and organization wide holidays won't be considered as a part of leave application.
>>
>> - Whenever employee's leave application is approved, corresponding no. of leaves will get deducted from his/her account
>>
>> - Employee will be able to see his/her current leave balance.
>>
>> So for this :
>> I have decided to added a new field "noOfLeaves" in EmplLeave Table.
>> And for crediting the leaves and holidays I have created two new entityes as shown below.
>> CreditEmplLeave table keeps track of the current leave balance for an employee.
>> Holiday will maintain all the holidays in an organization.
>>
>> <entity entity-name="EmplLeave"
>>
>> package-name="org.ofbiz.humanres.employment"
>>
>> title="Employee Leave Entity">
>>
>> <field name="partyId" type="id-ne"/>
>>
>> <field name="leaveTypeId" type="id-ne"/>
>>
>> <field name="emplLeaveReasonTypeId" type="id-ne"/>
>>
>> <field name="fromDate" type="date-time"/>
>>
>> <field name="thruDate" type="date-time"/>
>>
>> <field name="noOfLeaves" type="fixed-point"/>
>>
>> <field name="approverPartyId" type="id-ne"/>
>>
>> <field name="leaveStatus" type="short-varchar"/>
>>
>> <field name="description" type="description"/>
>>
>> <prim-key field="partyId"/>
>>
>> <prim-key field="leaveTypeId"/>
>>
>> <prim-key field="fromDate"/>
>>
>> <relation type="one" fk-name="EMPL_LEAVE_PRTY" rel-entity-name="Party">
>>
>> <key-map field-name="partyId"/>
>>
>> </relation>
>>
>> <relation type="one" fk-name="EMPL_LEAVE_ELETP" rel-entity-name="EmplLeaveType">
>>
>> <key-map field-name="leaveTypeId"/>
>>
>> </relation>
>>
>> <relation type="one" fk-name="EMP_LEAV_REAS_ELTP" rel-entity-name="EmplLeaveReasonType">
>>
>> <key-map field-name="emplLeaveReasonTypeId"/>
>>
>> </relation>
>>
>> <relation type="one" fk-name="EMPL_LEAVE_APPR" title="Approver" rel-entity-name="Party">
>>
>> <key-map field-name="approverPartyId" rel-field-name="partyId"/>
>>
>> </relation>
>>
>> </entity>
>>
>>
>>
>> <entity entity-name="CreditEmplLeave"
>>
>> package-name="org.ofbiz.humanres.employment"
>>
>> title="Credit Employee Leave Entity">
>>
>> <field name="partyId" type="id-ne"/>
>>
>> <field name="totalLeaves" type="fixed-point"/>
>>
>> <prim-key field="partyId"/>
>>
>> <relation type="one" fk-name="CRED_EMPL_LEAVE_PRTY" rel-entity-name="Party">
>>
>> <key-map field-name="partyId"/>
>>
>> </relation>
>>
>> </entity>
>>
>> <entity entity-name="Holiday"
>>
>> package-name="org.ofbiz.humanres.employment"
>>
>> title="Holiday's in organization">
>>
>> <field name="holidayId" type="id-ne"/>
>>
>> <field name="holiday" type="description"/>
>>
>> <prim-key field="holidayId"/>
>>
>> </entity>
>>
>>
>>
>>
>> Please give your suggestions on this.
>>
>>
>>
>>
>>
>> Thanks& regards,
>>
>>
>>
>> Swapnil Sawant
>>
>>
>>
>>
>>
>>
>>
>>
>> ________________________________
>> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>>
>> ______________________________________________________________________
>
>
> ______________________________________________________________________
>
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>
> ______________________________________________________________________
>

BJ Freeman

Re: Proposal for adding new functionality in Leave sub tab under HR module

also you can use a groovy files to marshal the statistics you need to
display, and do the calculations and/or created services to calculate
the different stats, that you call in a groovy before display.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

BJ Freeman sent the following on 6/16/2010 12:50 PM:

> https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=PartyBenefit
>
>
> https://demo-stable.ofbiz.apache.org/webtools/control/ArtifactInfo?type=entity&uniqueId=PartyBenefit
>
>
> with benefit types and periods it seem to cover all the requirments.
> I use the party from and to when the leave is mandated by union Agreement.
> I have added the agreement ID
> the agreement can also be part of the employee hiring, so this would be
> part of the AddPartyBenefit (humanres/widget/forms/EmploymentForms.xml)
> you can have type leave agreed upon, leave earned, leave approved, leave
> used.
> you can have many records of leave used.
> and SECA can keep the totals.
>
> in the records with leaved approved you can partyfrom the approver
> to the party with the leave cumming.
> Number of leaves can be computed by finding the appropriate type for a
> party
>
>
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation
> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com <http://www.specialtymarket.com/>
>
> Systems Integrator-- Glad to Assist
>
> Chat Y! messenger: bjfr33man
> Linkedin
> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>
>
>
> Swapnil Sawant sent the following on 6/15/2010 10:43 PM:
>> Hi BJ,
>>
>> Could you please elaborate a bit more on "using the Party benefits" ?
>>
>>
>> -----Original Message-----
>> From: BJ Freeman [mailto:[hidden email]]
>> Sent: Friday, June 11, 2010 1:31 PM
>> To: [hidden email]
>> Subject: Re: Proposal for adding new functionality in Leave sub tab
>> under HR module
>>
>> I would suggest using the Party benifits.
>> this would allow more flexiblity for enterprises.
>> take a look at the datamodel and discusssion stating on page 319 vol I
>> of datamodel book.
>> the calculation should be a service that can be selected, though you
>> only need provide the one you are suggesting.
>>
>> =========================
>> BJ Freeman
>> http://bjfreeman.elance.com
>> Strategic Power Office with Supplier
>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>
>> Specialtymarket.com<http://www.specialtymarket.com/>
>>
>> Systems Integrator-- Glad to Assist
>>
>> Chat Y! messenger: bjfr33man
>> Linkedin
>> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>>
>>
>>
>> Swapnil Sawant sent the following on 6/10/2010 2:13 AM:
>>> Hi,
>>>
>>> I wish to do some enhancement in existing Leave functionality in OFBiz.
>>>
>>> Existing functionalities :
>>>
>>> - Currently employee can create leave by selecting his approver.
>>>
>>> - Approver will approve the leave applied by the employee.
>>>
>>> New functionalities are :
>>>
>>> - Admin party can credit leave balance to only at the beginning of
>>> financial year to a party's leave account
>>>
>>> - When employee creates a leave application, weekends and
>>> organization wide holidays won't be considered as a part of leave
>>> application.
>>>
>>> - Whenever employee's leave application is approved, corresponding
>>> no. of leaves will get deducted from his/her account
>>>
>>> - Employee will be able to see his/her current leave balance.
>>>
>>> So for this :
>>> I have decided to added a new field "noOfLeaves" in EmplLeave Table.
>>> And for crediting the leaves and holidays I have created two new
>>> entityes as shown below.
>>> CreditEmplLeave table keeps track of the current leave balance for an
>>> employee.
>>> Holiday will maintain all the holidays in an organization.
>>>
>>> <entity entity-name="EmplLeave"
>>>
>>> package-name="org.ofbiz.humanres.employment"
>>>
>>> title="Employee Leave Entity">
>>>
>>> <field name="partyId" type="id-ne"/>
>>>
>>> <field name="leaveTypeId" type="id-ne"/>
>>>
>>> <field name="emplLeaveReasonTypeId" type="id-ne"/>
>>>
>>> <field name="fromDate" type="date-time"/>
>>>
>>> <field name="thruDate" type="date-time"/>
>>>
>>> <field name="noOfLeaves" type="fixed-point"/>
>>>
>>> <field name="approverPartyId" type="id-ne"/>
>>>
>>> <field name="leaveStatus" type="short-varchar"/>
>>>
>>> <field name="description" type="description"/>
>>>
>>> <prim-key field="partyId"/>
>>>
>>> <prim-key field="leaveTypeId"/>
>>>
>>> <prim-key field="fromDate"/>
>>>
>>> <relation type="one" fk-name="EMPL_LEAVE_PRTY" rel-entity-name="Party">
>>>
>>> <key-map field-name="partyId"/>
>>>
>>> </relation>
>>>
>>> <relation type="one" fk-name="EMPL_LEAVE_ELETP"
>>> rel-entity-name="EmplLeaveType">
>>>
>>> <key-map field-name="leaveTypeId"/>
>>>
>>> </relation>
>>>
>>> <relation type="one" fk-name="EMP_LEAV_REAS_ELTP"
>>> rel-entity-name="EmplLeaveReasonType">
>>>
>>> <key-map field-name="emplLeaveReasonTypeId"/>
>>>
>>> </relation>
>>>
>>> <relation type="one" fk-name="EMPL_LEAVE_APPR" title="Approver"
>>> rel-entity-name="Party">
>>>
>>> <key-map field-name="approverPartyId" rel-field-name="partyId"/>
>>>
>>> </relation>
>>>
>>> </entity>
>>>
>>>
>>>
>>> <entity entity-name="CreditEmplLeave"
>>>
>>> package-name="org.ofbiz.humanres.employment"
>>>
>>> title="Credit Employee Leave Entity">
>>>
>>> <field name="partyId" type="id-ne"/>
>>>
>>> <field name="totalLeaves" type="fixed-point"/>
>>>
>>> <prim-key field="partyId"/>
>>>
>>> <relation type="one" fk-name="CRED_EMPL_LEAVE_PRTY"
>>> rel-entity-name="Party">
>>>
>>> <key-map field-name="partyId"/>
>>>
>>> </relation>
>>>
>>> </entity>
>>>
>>> <entity entity-name="Holiday"
>>>
>>> package-name="org.ofbiz.humanres.employment"
>>>
>>> title="Holiday's in organization">
>>>
>>> <field name="holidayId" type="id-ne"/>
>>>
>>> <field name="holiday" type="description"/>
>>>
>>> <prim-key field="holidayId"/>
>>>
>>> </entity>
>>>
>>>
>>>
>>>
>>> Please give your suggestions on this.
>>>
>>>
>>>
>>>
>>>
>>> Thanks& regards,
>>>
>>>
>>>
>>> Swapnil Sawant
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ________________________________
>>> This Email may contain confidential or privileged information for the
>>> intended recipient (s) If you are not the intended recipient, please
>>> do not use or disseminate the information, notify the sender and
>>> delete it from your system.
>>>
>>> ______________________________________________________________________
>>
>>
>> ______________________________________________________________________
>>
>> This Email may contain confidential or privileged information for the
>> intended recipient (s) If you are not the intended recipient, please
>> do not use or disseminate the information, notify the sender and
>> delete it from your system.
>>
>> ______________________________________________________________________
>>
>
>

Swapnil Sawant

RE: Proposal for adding new functionality in Leave sub tab under HR module

Hi BJ,

Thanks for your reply.

I have mentioned about overall functionality taking Party Benefits into consideration in below JIRA.

https://issues.apache.org/jira/browse/OFBIZ-3825

Thanks & Regards,

Swapnil Sawant

-----Original Message-----
From: BJ Freeman [mailto:[hidden email]]
Sent: Thursday, June 17, 2010 1:36 AM
To: [hidden email]
Subject: Re: Proposal for adding new functionality in Leave sub tab under HR module

also you can use a groovy files to marshal the statistics you need to
display, and do the calculations and/or created services to calculate
the different stats, that you call in a groovy before display.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

BJ Freeman sent the following on 6/16/2010 12:50 PM: