[
https://issues.apache.org/jira/browse/OFBIZ-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880963#action_12880963
]
BJ Freeman edited comment on OFBIZ-3825 at 6/21/10 8:12 PM:
------------------------------------------------------------
I am not clear about the place of sub agreements.
agreement ID 86749 (page 147 vol I)
this agreement is for a entry level job postion.created from the Companies
Template for that position.
The agreement has AgreementItems
one of those AgreementItems is a productID for Sickleave.
using the format on page 153
termtype total amount sick leave
termvalue 10
new sequence termtype number of hours for one hour of sickleave
termvalue 180
new sequence termtype needs approval over
termvalue 0
new sequence termtype employers paid percent
termvalue 100
you can specify any and all terms for a leave/benefits this way.
for each type of leave/benefits would be a product with the terms
Once an employee is hired these agreements are copied then are associated with
the employee partyID. The reason is the agreements for this employee will
change and should not affect the standard company templates.
For instance they get a pay raise that increased their terms for leave.
The previous would be an thru date of the new terms from date.
To get the partybenefits cost you use product pricing, take from
Position.paygrade (page335), with pricing Subtype (page 88) and the Estimated
Product Cost (page 94-95)
The nightly service would
1) Build new partybenefits for new employees
2) Review the terms and add parybenefits type Sick leave available time (page
320)
all the above is automated, except for building the company templates, and
possibly assigning the agreement to the party at interview time. these
assignments are linked to the company templates till the party is hired.
The employee benefit page will list all the partybenefits type they have and
the available time.
Then the requester can check which benefit type they want to request up to the
available time.
this take them to a page where they can modify the time that is now label
"amount to use". this then puts a through date on the current record and create
a new record with the available being less than that ask for.
this is then sent as a communication event to the approver.
should the approver not approve then the thrudate of the new record is added
and new record with the old available time is created. And another
communication event of the results is sent the requester. This allows for an
audit of requests and denials.
Note: these are also added to payroll (not in the book) and use the payment
method type "benifits" and the partybenefits are listed.
I borrowed the communication event from Inquiry of the alternative performance
review (page 332)
as you can see the is non specific from a model point of view and can be used
for all types of benefits. The only thing that changes is the code to work with
the types needed. The specific code can be added to the main routine as it is
required or can access a config record of a service that is been activated.
Most of that is general enough you can pass a set of parms to it .
was (Author: bjfreeman):
Jira been down for last 8 hrs
waiting for it to finish indexing to comment
=========================
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>
> 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.
