Database design of claim management system?

Question

0.00/5 (No votes)

See more:

I have come across a complex scenario where I have to design a database for a in-house project of my company. The project is claim management system where employee can

submit their different claims i.g medical, traveling etc. But this claims will also have to get approval from specific managers before they are accepted. Here the heirarchy of

the approval managers can b different based on the designation of the employee and type of the claim. Lets suppose for a medical claim if employee designation is Senior Software

Engineer then their claim gets first approved by Team Lead then from Manager. For the same designation for a traveling allowance claim will directly approved by Director. If

designation is manager then for his medical claim, he will get directly approval from Director. So far, I have come across following tables,

ClaimTypes(ClaimId, Claim)

EmployeeDesignation(Id, Designation, Manager(parentId))

ClaimApprovalLevel(Id, ClaimId, designationId, Approvallevel, approvalAuthority)

But here I am confused that what if a same employee of same designation need approval from two different managers ? Is my solution viable if there has to be added further heirarchies of managers in future ?

Posted 28-Jan-16 1:05am

touseef4pk

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

W∴ Balboos, *GHB* · Answer 1 · 2016-01-28T04:41:00

We use such a system here (hierarchical approval chain) for Leave Approval, Software and Hardware requests, purchases, &etc: JavaScript/PHP/SQL.

It works rather well, too, as no one can ever lose a paper on their desktop. Also, it has a built in annoyance feature so that emails are periodically dispatched to the next-in-line approver until they do their job. It even branches, in the case of purchases, to different chains based upon the $ amount.

The chains you want should give an order and terminate when the max value for that particular chain is reached - this should be gotten dynamically so you can implement multiple such hierarchies for various purposes.

The details, unfortunately, are company property unless they say otherwise. The concept, however, of multiple chains with multiple tiers is really the general case for such problems.