SIT vs. EIT - What Is The Difference?

SIT's are Key Flexfields. When you create new segment combinations,
the system will first check to see whether that combination already
exists in the table before creating a row. If the combination does
exist, the system only retrieves the ID of the row it found. The
system therefore has to scan through the whole SIT combinations
table. If this is very large, performance could be an issue.

vs.

EIT's are a type of Descriptive Flexfield. When you create new

segment combinations, the row is just inserted into the appropriate
table (without checking whether the combination already exists).
There is now full scan of the underlying table and so performance
shouldn't be affected by the size of the table. EIT's have advantages
in large scale or global implementations where you may want to
transfer large volumes of information between separate installations.

***

SIT's are primarily attached to people. They can also be used with
Jobs, Positions, and Activities (in OTA), but with skill meaning
(competencies).

vs.

EIT's can be attached to People, Assignment, Job, Position, Location

and Organization (via a classification)

***
The SIT form has a start date and end date associated with the SIT
row.

vs.

The EIT forms do not have start and end dates. If you want to create
dated information, then you would have to use two of the EIT
flexfield attributes to store this information.

***

SIT's have a folder that you can query to match certain criteria.Nav:
View> Lists> People by Special Information

vs.

EIT's do not have a pre-defined folder.

***

SIT's
For OTA, development is renaming their use of SIT's against
activities from "Skills" to more generic "Other Information." This is
a part of adding the real competencies to activities.

***

EIT's can be used to capture different country-specific information

for organizations, locations, people or assignments when your
operations cross national boundaries.
***

SIT's: Custom Form and TaskFlow security can be used with SIT's to
restrict access to information.

vs.

EIT's: Custom Form and TaskFlow security can be used with EIT's to
restrict access to information. EIT's have an extended security
option that lets you define access to all EIT's at the level of a
Responsibility - not just one at a time. Meaning you can also
restrict access to EIT's as part of a role-based security model.

***

For each SIT, you can define up to 30 fully validated segments of

information.

vs.

For each EIT, you can have up to 30 fully validated segments of

information as well as 20 DFF segments on the EIT.