Special Information types (SIT) and Extra Information Types (EIT)

Differences between SIT and EIT

Special Information Types (SIT)	Extra Information Types (EIT)
Belongs to Key Flex Fields family	Belongs to Descriptive Flex Fields family
Special Information Types: Jobs (Job Requirements) People (Person Analyses) Positions (Position Requirements)	List of Extra Information  Types: Location Extra Information Pay Element Type Extra Information Contact Extra Information Job Extra Information People Extra Information Position Extra Information Previous Job Extra Information Vehicle Allocation Extra Information Vehicle Repository Extra Information
To implement security on SIT, you need to create a custom Form / Taskflow	EITs can have additional security at responsibility level applied
SIT are date track enabled with two fields Start Date and End Date readily available.	EIT’s we have explicitly create two extra fields to enable capture star date and end date. This is not date track, but we can track the history of the records.

Requirement: We need to capture following two fields against an employee

Segment1	Qatari National (Yes / No)
Segment2	Color Blind (Yes / No)

Data captured using SIT

Example1:

If two employees are Qatari National and not Color Blind, then one record is created in the table PER_ANALYSIS_CRITERIA as per below:

ANALYSIS_CRITERIA_ID	START_DATE_ACTIVE	END_DATE_ACTIVE	SEGMENT1	SEGMENT2
10001	01-JAN-2014		Yes	No

Now data in the table PER_PERSON_ANALYSES is stored as per below and you will find same ANALYSIS_CRITERIA_ID for both the employees

PERSON_ANALYSIS_ID	ANALYSIS_CRITERIA_ID	PERSON_ID
2512	10001	121
2513	10001	123

Example2:

If two employees are Qatari National, one is Color Blind and other is not Color Blind; then two records are created in the table PER_ANALYSIS_CRITERIA.

ANALYSIS_CRITERIA_ID	START_DATE_ACTIVE	END_DATE_ACTIVE	SEGMENT1	SEGMENT2
10001	01-JAN-2014		Yes	No
10002	01-JAN-2014		Yes	Yes

Now data in the table PER_PERSON_ANALYSES is stored as per below and you will find two different  ANALYSIS_CRITERIA_ID for the employees

PERSON_ANALYSIS_ID	ANALYSIS_CRITERIA_ID	PERSON_ID
2512	10001	121
2513	10002	123

Data captured using EIT

Example1:

If two employees are Qatari National and not Color Blind, then two records are created in the table PER_PEOPLE_EXTRA_INFO.

PERSON_EXTRA_INFO_ID	PERSON_ID	PEI_INFORMATION1	PEI_INFORMATION2
50001	121	Yes	No
50002	123	Yes	No

Example2:

If two employees are Qatari National, one is Color Blind and other is not Color Blind; then two records are created in the table PER_PEOPLE_EXTRA_INFO.

PERSON_EXTRA_INFO_ID	PERSON_ID	PEI_INFORMATION1	PEI_INFORMATION2
50001	121	Yes	No
50002	123	Yes	Yes

How to decide between and SIT and EIT:

1. SIT's should be used where data is infrequently changed, or where there is a good deal of commonality of values held against your user population to make the storing of the unique combinations effective. If everyone had completely different values for the SIT segment combinations then (in my opinion) this would be a poor use of a SIT and would be better served in an EIT.
2. If you want to restrict the values at the responsibility level, it will be better to go for EIT than SIT.
3. Data in EIT against an employee record will be visible to all the users that have access to the Employee creation/query screen. On the contrary, using HR Workflow security, we can make SIT to become visible for the responsibility that we desire.
4. You can define as many contexts as you desire for special information type key Flexfield

Please refer the below URL on how to setup an SIT:

http://oracle.anilpassi.com/special-information-types-sit-in-hrms-4.html

Please refer the below URL on how to setup an EIT:

http://oracle.anilpassi.com/differences-between-eit-and-sit-in-hrms.html