[ 
https://issues.apache.org/jira/browse/OFBIZ-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880889#action_12880889
 ] 

Swapnil Sawant commented on OFBIZ-3825:
---------------------------------------

Hi BJ, 

Following is what we have thought of : 

        - We will have 'sub-agreements' for various kind of leaves e.g. 
sub-agreement for sick leave/casual leave.This will be accomplished under 
'Agreement Items' sub-tab. 
   
        - How to associate corresponding number of leaves for each of the 
sub-agreement under 'Agreement Items' tab.Under 'Agreement Items' (after 
selecting a particular Agreement Item), 'Agreement Item' , 'Promotions' , 
'Terms' , 'Products' , 'Party' , ' Geo' tabs are there. Could you please 
elaborate more as to 'where and how' to 'add number of leaves' that will be 
credited to employee's account when we select 'Parent Agreement Id' and hit 
'Create' button under 'Employements -> Agreement Employment Appl' tab in HR 
(here functionality will be crediting leaves as per selected 'Agreement Id' 
"after" 'Create' button is hit) 

         - Leave benefits would be added under 'Employments -> Party benefits' 
tab for a particular 'Employment' as per decided 'agreeement'(lets say 
agreement id 'aggr1') for it. here leave benefits would be added under 
Employees account but number of leaves would be getting credited only after 
'Create' button hit under 'Employements -> Agreement Employment Appl' tab 
(after selecting agreement id 'aggr1' ) 
          
          - So the concept is ' leave benefits would be added to employee's 
account as per agreement decided'.When I am saying 'leave benefits would be 
added' I mean to say 'only specifying what benefits an employee would be 
getting' but 'for leave benefits , actual no. of leaves would not be credited 
at this stage. Actual leaves would be credited to his/her leaves benefit (sick 
leave or casual leave benefit) , only after 'Create' button hit under 
'Employements -> Agreement Employment Appl' tab depending on agreement choosen. 

            - Reason for deferring 'leaves credition' till 'assigning agreement 
to employment' is that it sounds logical to credit leaves to employee's account 
only after we assign any 'agreement' to it and not before that 

          Please let us know if this functionality is good to go :) 




> Proposal for adding new functionality in Leave sub tab under HR module
> ----------------------------------------------------------------------
>
>                 Key: OFBIZ-3825
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3825
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>    Affects Versions: SVN trunk
>         Environment: Windows XP, JDK 1.6 
>            Reporter: Swapnil Sawant
>            Priority: Minor
>             Fix For: SVN trunk
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
>  I wish to do some enhancement in existing Leave functionality taking Party 
> benefits into consideration in OFBiz.
>                   Existing functionalities :
>                       - Currently employee can create leave by selecting his 
> approver.
>                       -  Approver will approve the leave applied by the 
> employee.
>            
>                   New functionality :
>       - Admin party will credit leaves at the beginning of a financial year 
> for employees
>       - These leaves can be taken by employee under available benefits from 
> Party Benefit
>       - Party Benefits will be setup for each employee as per existing flow
>       - Whenever employee creates leave application, his/her benefits will be 
> checked for validation purpose(relation           will be set between leave 
> reason type and benefit type) along with exclusion of weekend and 
> organization wide           holidays.
>       - On leave approval, corresponding number of leaves would be deducted 
> from employee's leave account.
>       
>                  For implementing this, following modifications are being 
> thought of :
>       - Adding foreign key column 'benefitTypeId' in 'EmplLeaveReasonType' 
> (reference from 
>                       benefitType.benefitTypeId)
>       By maintaining this relation, each time employee creates a leave 
> application (with some leave reason type        Id),we can keep track of 
> 'availableTime' for this particular employee/party-benefitType combination
>       - We can have CreditEmplLeave,EmplLeave and Holiday tables as mention 
> in the below thread
> http://ofbiz.135035.n4.nabble.com/Proposal-for-adding-new-functionality-in-Leave-sub-tab-under-HR-module-td2250139.html#a2250139
> Following is a demo flow of above mentioned functionality :
>       1.Admin credits leaves for an employee.
>       2.Employee applies for leave for first time with  leave reason type as 
> 'Medical' (for time being lets assume 'Sick      Leave' is benefit type for 
> this leave reason type in 'EmplLeaveReasonType' table) 
>       3.Before creating leave application, we would check following two 
> things :
>               - If that employee has enough leave balance
>               - If employee has not crossed 'availableTime' threshold for 
> benefit type 'Sick Leave'(using Party   Benefits already setup through other 
> existing screen)
>                      4.After leave application is created, approver can 
> approve/reject it
>       5.Corresponding updations will be made in 'EmplLeave'(changing status 
> to approve/rejected) and  CreditEmplLeave tables(deduction if approved) 
> Thanks & Regards,
> Swapnil Sawant

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to