Effective sequence concept is used in some key tables like Job. Job table has high volume of employee transaction data. There are multiple...
Effective sequence concept is used in some key tables like Job. Job table has high volume of employee transaction data. There are multiple types of transactions and they are all action driven. It is very likely in a business scenario that employee has same type of transaction more than once in the same day. For example: Employee can have a data change action happening on the same day more than once. In such a situation, for the same employment instance, we now have more than one row with the same effective date. In order to uniquely store this second transaction, we need another primary key which is where effective sequence comes into play. Hence Job table has a primary key structure: Employee id, employee record number, effective date and effective sequence.
