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

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

Hi BJ,

As per your comments, we have come up with following flow :

Agreements creation : 

        -       Appropriate agreements will be created prior to recruitment 

        For example following steps would be followed to create Permanent 
employment agreement :

                1.  From 'Agreements' tab in 'Accounting', create an agreement 
for permanent employment
                2.  Once agreement is created, under 'Agreement Items' tab, we 
will add 'Leave' item(by selecting Agreement Item Type Id as 'Sub-agreement' 
from drop down) 
                3.  Now that we are automating the 'Leave Crediting' process, 
at this point in time we should decide on as to how many leaves should be 
credited if this agreement is selected for an employee.
                    i.e Leaves would be credited as per agreements ( as 
suggested by you)
                    Hence,how should we add 'no. of leaves' when we are under 
'Agreement Items' sub-tab ? Should we provide a new text box ?
        
        Similary, we will create agreements based on company 
locations/positions etc and attach 'no. of leaves to be automatically credited' 
with each of these agreements


Creating employement :

        -       Pre-requisite to creating employement is creating a party in 
party module for 'hired person' 
        -       For employement purpose, we would go to 'HR -> Employements' 
tab and select the above party id
        -       Once we hit submit on 'new employement creation', currently 
system is adding benifits automatically for that 'hired employee'
        -       After this, we would go to 'Agreement Employment Appl' sub-tab
        -       In this tab, we would select appropriate 'agreement id' (based 
on position he has been hired for i.e. permanent/contractual/location etc)
        -       Once done with above step, now we would select 'Agreement Item 
Seq Id' which was been created when we had created 'sub-agreement for Leave' 
for above selected agreement
        -       After all other relevant data is filled up, when we would hit 
'Create' button under this i.e. 'Agreement Employment Appl' sub-tab, then based 
on 'Agreement Id' selected , no. of leaves will be credited in 'Party Benefit' 
table for that employee (against 'Leave benefits')


This is the functionality we have thought of to start  our implementation with. 
Later on, we will come up with brief flow about 'aligning' this functionality 
with  other modules like Work Effort etc
        



> 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