WHITE PAPER

Extra Information Typesin Oracle HRMS

Control Number: EIT 1.0Version: 1.0

Copy Number _____

2

Oracle HRMS Extra Information Types, Release 11

Copyright Oracle Corporation 1995All rights reserved. Printed in the U.S.A.Primary Authors: John Cafolla, Juliette FlemingContributors: Dinesh Arora, Martin BocuttThis software was not developed for use in any nuclear, aviation, masstransit, medical, or other inherently dangerous applications. It is thecustomer's responsibility to take all appropriate measures to ensure thesafe use of such applications if the programs are used for such purposes.This software/documentation contains proprietary information of OracleCorporation; it is provided under a license agreement containing restrictionson use and disclosure and is also protected by copyright law. Reverseengineering of the software is prohibited.If this software/documentation is delivered to a U.S. Government Agency ofthe Department of Defense, then it is delivered with Restricted Rights andthe following legend is applicable:Restricted Rights Legend Use, duplication, or disclosure by theGovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofDFARS 252.227-7013, Rights in Technical Data and Computer Software(October 1988).Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.If this software/documentation is delivered to a U.S. Government Agencynot within the Department of Defense, then it is delivered with “RestrictedRights", as defined in FAR 52.227-14, Rights in Data - General, includingAlternate III (June 1987).The information in this document is subject to change without notice. If youfind any problems in the documentation, please report them to us inwriting. Oracle Corporation does not warrant that this document is errorfree. No part of this document may be reproduced or transmitted in anyform or by any means electronic or mechanical, for any purpose without theexpress written permission of Oracle Corporation.

ORACLE, Oracle Alert, Oracle Financials, SQL*Plus are registered trademarks ofOracle Corporation

Oracle Application Object Library, Oracle General Ledger, Oracle Human Resources,Oracle Inventory, Oracle Manufacturing, Oracle Order Entry, Oracle Payables,Oracle Payroll, Oracle Project Accounting, Oracle Purchasing, Oracle Receivables,Oracle Reports, PL/SQL, SQL*TextRetrieval are trademarks of Oracle Corporation.

All other products or company names are used for identification purposes only, andmay be trademarks of their respective owners.

Copy Number _____

3

ContentsContents .......................................................................................................................3Extra Information in Oracle Human Resources ...........................................................5

What Are Extra Information Types?.....................................................................5Are EITs DateTracked? ........................................................................................6

Using Extra Information or Special Information for People ........................................6Security .................................................................................................................6Key Flexfield Combinations .................................................................................6Restricting Access to Extra Information ...............................................................7

Example Screenshots ...................................................................................................8Person EITs...........................................................................................................8Assignment EITs...................................................................................................9

Setup Steps for Extra Information Types ...................................................................10Adding Extra Information Types to a Responsibility..........................................11

APIs for Extra Information Types..............................................................................12User-Hooks With These APIs.............................................................................12

Appendix A: Reference Information .........................................................................13Location EIT.......................................................................................................13Organization EIT ................................................................................................13Job EIT ...............................................................................................................14Position EIT........................................................................................................14Person EIT ..........................................................................................................15Assignment EIT ..................................................................................................15

Appendix B: Organizations and Extra Information Types ........................................16HR_ORGANIZATION_UNITS.........................................................................16HR_ORGANIZATION_INFORMATION.........................................................17HR_ORG_INFORMATION_TYPES ................................................................17FND_COMMON_LOOKUPS............................................................................17HR_ORG_INFO_TYPES_BY_CLASS .............................................................18Adding New Organization Classifications And InformationTypes ..................................................................................................................18

Appendix C: Example Script to Register EITs .........................................................20

4

5

Extra Information in Oracle Human Resources

Extra Information Types, (EITs), are a new feature in Release 11 ofOracle HRMS. They allow you to set up unlimited amounts of extrainformation for six of the most important entities in HRMS. These are:

• Locations

• Organizations

• Jobs

• Positions

• People

• Assignments

For example, you could use EITs to capture different country-specificinformation for organizations, locations, people or assigments when youroperations cross national boundaries. Similarly, you might use EITs toadd details to assignment records in special circumstances, such asinformation about a leave of absence or extra information about atemporary assignment to a project.Note: In earlier releases of Oracle HRMS, the EITs for Organization

and Assignment were restricted for use only by developers. InRelease 11 there are a set of predefined EITs for Organizationand Assignment. You may add your own information types butyou must not change the definitions of the delivered EITs.

This paper provides the additional information you need to understandand implement EITs for users. Use this information in conjunction withyour Oracle HRMS Implementation Guide, and Oracle HR or Payroll User’sGuide. These provides the common setup information you need to definecustom restrictions for forms, task flows and responsibilities, and todefine descriptive flexfields.

What Are Extra Information Types?

Extra Information Types in Oracle HRMS are a kind of descriptiveflexfield. For each supported entity - such as job or location, you can setup any number of different EITs. And for each EIT you can define up to30 fully validated segments of information, (or 20 for organizations).Note: A special feature of EITs is that you can specify whether an

entity can have multiple entries of the EIT or only one entry.

6

Unlike the usual descriptive flexfield on the main entity, EITs are childentities with separate tables to hold the information you information youenter. This means that you can have multiple instances of an EIT foreach main record. With the exception of organizations, EIT data isviewed and entered in a separate form, which you can add as a task flowfrom the main entity. The form for Organizations is not controlled bytaskflow.

Are EITs DateTracked?

No. Extra information types are not date tracked. Even if the parententity is datetracked the extra information is not. However, if you wantto track changes to specific EITs you can define date segments for Startand End Dates and use multiple rows of the EIT to track change.

Using Extra Information or Special Information for People

From a user perspective, EITs for people seem to be very similar to theSpecial Information Types you may have used in the past. Now you canchoose to set up extra or special information types, or both. Both typesof information use flexfields to define the structure and validation of thesegments.

Security

Both types use CustomForm and TaskFlow security to restrict access tothe information. This means that you can restrict access to informationtypes as part of a specific user process. For example, in a ‘Transfer to theUK’ process you might want to enter additional UK specific information.You could design your user process to include a ‘UK Info’ window aspart of the taskflow process and restrict the window to display only UKinformation types.

EITs also have an extended security option that lets you define access toall EITs at the level of a Responsibility - not just one at a time. Thismeans that you can also restrict access to EITs as part of a role-basedsecurity model. For example, you might want to limit line-manageraccess to a set of EITs that include job, person and assignmentinformation types. You can do this more easily with EITs because youcan restrict access to all EITs at the level of a responsibility.

Key Flexfield Combinations

Special information is stored in a key flexfield combination table wherethe combination of segment values must be unique - a feature of all keyflexfields. Extra information is stored in a descriptive flexfield table

7

where the combination of segment values does not need to be checkedfor uniqueness. Each row in the Extra Information table is independentof every other row.

This means that EITs have performance advantages in large scale, orglobal, implementations where you may want to transfer large volumesof information between separate installations.

In general, you can use EITs or SITs to store additional information forpeople. Special Information Types will continue to be available and youmay have already used these to set up basic comparisons of people’sskills or qualifications with job or position requirements.

Note: If you are using this functionality in R.10 you might nowconsider whether you want to migrate to the new Qualificationsand Competence functionality that is available in R.11.

Restricting Access to Extra Information

You can restrict access to Extra Information Types in three ways:1. Using Menus and TaskFlows. Each EIT has its own form.

Without the EIT form a user cannot see or change any extrainformation for the entity.

Note: In the current release the EIT forms are not included in thepredefined menus and taskflows delivered with the products.You must add these forms into your own menus and taskflowsbefore you can see or use them.

2. Using CustomForm and TaskFlows to restrict EITs to specifcuser processes. For example, at the person level you mightdefine EITs to hold medical details, security information, andinformation required for working in other countries. In thissituation you might want to create two custom taskflows: Onewith a button for entering only medical details and another witha button for entering the other types of extra information.

3. Using Responsibility level security. For each responsibility, youmust select the EITs it can view.

Note: This security does not apply to extra information onorganizations. Also, CustomForm and TaskFlow restrictions willoverride the security you set up at Responsibility level.

8

Example Screenshots

The following screenshots show the Person and Assignment EIT forms.Using Person and Assignment EITs you can choose to partition personaland employment information according to your own business needs. Forexample you might want to record different types of information foremployees working across national boundaries.

Note: The screens for all the EITs have the common look and feel of alldescriptive flex windows. This means that you can use your newEITs as soon as you save your definitions. It also means that allyour definitions will upgrade automatically to the next releasewith the need to recode any custom forms.

Person EITs

Fig: 1 Person Extra Information Types

Fig: 2 Person Extra Information Type Detail

9

Assignment EITs

Fig: 3 Assignment Extra Information Types

Fig: 4 Assignment Extra Information Type Detail

Using responsibility level security and/or TaskFlow security you candetermine who has access to this information and the context in whichthey can view or change the information.

10

Setup Steps for Extra Information Types

The following is a summary of the steps you should follow. Details formany of these steps are included in the Implementation and User’sGuides for your HRMS products.

1. Define the EIT using the Descriptive Flexfield windows.

Note: Enter the names of each new Information Types as contextvalues.

Attention: There are some predefined EITs in Oracle HRMS. Thesedefinitions are a fundamental part of your Oracle HRMSinstallation and any change to them may lead to errors in theoperation of the system. Do not attempt to alter the definitionsof these protected flexfields or to add other segments to them. Itis possible that the product development group will use othersegments of these flexfields in the future. Any changes youmake can affect your ability to upgrade your sytem in the future.

2. Use SQL to insert a row for each EIT into the relevantInformation Type table. In this release there is no window toregister your new EITs with their parent entities.

Note: See the Reference Section to find the list of tables for eachEIT.

Attention: Oracle applications use a naming standard of a 2 or 3character product prefix followed by an underscore to name thepredefined EITs. To avoid current and future naming conflicts,you should adopt any other naming convention for your ExtraInformation Types. For example VISION_EXPAT_TAXABILITY.

3. Use the Information Types Security window to set upresponsibility level access to the EITs.

Note: This security does not apply to EITs on organizations. See:Adding Extra Information Types to a Responsibility.

4. Use the Form Customization window to restrict access to specificEITs within the appropriate forms.

5. Use the Define TaskFlow Nodes window to define new nodes forany CustomForm restrictions you have set up.

6. Use the Define TaskFlow window, or use Oracle Workflow, todefine and change taskflows to include any new nodes you haveset up.

Note: In this release the EIT windows are not included in thepredefined menus installed with the product. Also, in thisrelease the Location, Job and Position windows have their own

11

taskflows to support the EIT windows. Define new taskflows tolink:

− PERWSLEI to PERWSLOC for Locations

− PERWSJEI to PERWSDJT for Jobs

− PERWSPOI to PERWSPOS for Positions

Adding Extra Information Types to a Responsibility

You must add an Extra Information Type to a responsibility before a usercan access the information type in that responsibility. By not addinginformation types to a responsibility, you restrict the information typesthat a responsibility user can access.

To add information types to a responsibility:

1. Navigate to the Information Type Security window.

2. Choose a Responsibility Name from the list of availableresponsibilities.

The system displays a list of any Extra Information Typesalready associated with the responsibility you have chosen.

3. Add or delete information types for this responsibility.

4. Choose Copy Responsibility if you want to copy the extrainformation types you have associated with one responsibility toanother responsibility that you have already defined. After youhave copied a responsibility, you can make changes to the newresponsibility.

12

APIs for Extra Information Types

There are a number of publicly callable business process APIs for usewith EITs in Release 11.

Attention: You should not manually edit the API source code filessupplied by Oracle. If you do modify these packages, OracleApplications will be unable to support the product, andupgrades may not be possible. Oracle Applications onlysupports direct calls to the published APIs. Direct calls to anyother server-side package procedures or functions that arewritten as part of the Oracle HRMS Applications suite are notsupported.

User-Hooks With These APIs

All of these APIs include pre and post event user-hooks. These arelocations in the API code where additional customer-specific logic can beexecuted. When the API processing reaches a user-hook, the core APIprocessing stops and any customer-specific logic for that event isexecuted. Then, if no errors occur, the main API processing resumes afterthe user code is complete.

Row Handlers on the following tables support all the Row Handler user-hook event points (after insert; after update; after delete) :

• PER_LOCATION_EXTRA_INFO

• PER_ASSIGNMENT_EXTRA_INFO

• PER_JOB_EXTRA_INFO

• PER_PEOPLE_EXTRA_INFO

• PER_POSITION_EXTRA_INFO

For more information on APIs and User-Hooks you should read thetechnical essay on Calling APIs in the Implementation Guide.

13

Appendix A: Reference Information

The following list summarizes the tables and usernames associated withthe EIT descriptive flexfields.

Note: Each EIT also has a standard descriptive flexfield associated withit.

Location EIT

EIT Name: Extra Location Information(30 Segments)

Additional DF on EIT: Additional Extra Location Info Details(20 Segments)

Tables: HR_LOCATION_EXTRA_INFOHR_LOCATION_INFO_TYPES

Form: PERWSLEIF4 Define Location Extra Info

API name: create_location_extra_infoupdate_location_extra_infodelete_location_extra_info

Organization EIT

EIT Name: *Org Developer DF(20 Segments)

Additional DF on EIT: Additional Organization Information(20 Segments)

Tables: HR_ORGANIZATION_INFORMATIONHR_ORG_INFORMATION_TYPESHR_ORG_INFO_TYPES_BY_CLASS

Form: PERWSDORF4 Define Organization

API name:

14

Note: This EIT follows a different naming convention. Also, note thatyou must insert information intoHR_ORG_INFO_TYPES_BY_CLASS to identify whichclassifications of Organization can use each information type.Also note that the window for this EIT is part of the DefineOrganization form and is not included in TaskFlow security.

Job EIT

EIT Name: Extra Job Information(30 Segments)

Additional DF on EIT: Additional Extra Job Info Details(20 Segments)

Tables: PER_JOB_EXTRA_INFOPER_JOB_INFO_TYPES

Form: PERWSJEIF4 Define Job Extra Info

API name: create_job_extra_infoupdate_job_extra_infodelete_job_extra_info

Position EIT

EIT Name: Extra Position Information(30 Segments)

Additional DF on EIT: Additional Extra Position Info Details(20 Segments)

Tables: PER_POSITION_EXTRA_INFOPER_POSITION_INFO_TYPES

Form: PERWSPOIF4 Define Position Extra Info

API name: create_position_extra_infoupdate_position_extra_infodelete_position_extra_info

15

Person EIT

EIT Name: Extra Person Information(30 Segments)

Additional DF on EIT: Additional Extra Person Info Details(20 Segments)

Tables: PER_PEOPLE_EXTRA_INFOPER_PEOPLE_INFO_TYPES

Form: PERWSPEIF4 Define Person Extra Info

API name: create_person_extra_infoupdate_person_extra_infodelete_person_extra_info

Assignment EIT

EIT Name: *Further Assignment Information(30 Segments)

Additional DF on EIT: Assignment Extra Information(20 Segments)

Tables: PER_ASSIGNMENT_EXTRA_INFOPER_ASSIGNMENT_INFO_TYPES

Form: PERWSAEIF4 Define Assignment Extra Info

API name: create_assignment_extra_infoupdate_assignment_extra_infodelete_assignment_extra_info

Note: This EIT follows a different naming convention.

16

Appendix B: Organizations and Extra Information Types

Organizations are one of the HRMS building blocks shared with otherOracle Applications. The Organization Classification provides a way toidentify the different uses of Organizations across the applications. Foreach Classification there may be extra information required. EITs forOrganizations are linked through an Organization Classification and notdirectly to the Organization.

This means that you can restrict the types of information that appear foreach classification. This improves usability by allowing users to see theEITs in the context of the appropriate organization classification

Note: You can define your own additional Classifications forOrganizations.

The data model includes the following tables:

• HR_ORGANIZATION_UNITS

• HR_ORGANIZATION_INFORMATION

• HR_ORG_INFORMATION_TYPES

• FND_COMMON_LOOKUPS

• HR_ORG_INFO_TYPES_BY_CLASS

HR_ORGANIZATION_UNITS andHR_ORGANIZATION_INFORMATION are maintained using theDefine Organization form. The remaining tables hold the meta-data thatdefines what information can be held for each classification. These tablescontain predefined information that is created as part of the installationprocess.

Warning: You may add new definitions to these tables but you MUSTNOT modify or delete the predefined data. This information isrequired for the correct operation of your HRMS system.Changes to this data may invalidate your support agreement andmake it impossible for you to upgrade your installation.

HR_ORGANIZATION_UNITS

All organizations have a set of generic attributes such as name, start date,end date, location.

Every organization has one row in HR_ORGANIZATION_UNITS.

17

HR_ORGANIZATION_INFORMATION

In addition to the generic attributes, some types of organizations alsohave one or more sets of information that are logically groupedaccording to the ‘classification’ of the organization.

For example. An HR Business Group may have the followinginformation types:

• Business Group Information

• Budget Value Defaults

• PayMIX Information

• Project Burdening Hierarchy

• Reporting Categories (US specific)

• Reporting Statuses (US specific)

• Work Day Information (US specific)

By comparison, a Corporate Headquarters organization has only thegeneric attributes common to all organizations.

HR_ORGANIZATION_INFORMATION holds the actual extrainformation data for each organization.

HR_ORG_INFORMATION_TYPES

There is one row in this table for each EIT related to an organization. Thiscorresponds to an Org Developer DF flexfield structure.

Note: When you define Org Information Types you specify whetherthe relationship between the organization and its classificationspecific data is 1-to-1 or 1-to-many.

FND_COMMON_LOOKUPS

The ORG_CLASS lookup type holds the actual values for organizationclassifications.

Note: After installing Oracle Applications all Org Classifications areenabled. As part of your implementation you should disablethose classifications that are not appropriate to your enterprise.You may also define other classifications to support your ownbusiness needs.

18

HR_ORG_INFO_TYPES_BY_CLASS

This is an intersection table that defines the Org EITs that are appropriateto each Organization Classification. Usually, EITs are used by just oneClassification. However, you can register a specific EIT to any number ofdifferent Organization Classifications.

Adding New Organization Classifications And Information Types

To add support for a new type of organization you must perform thefollowing steps:

1. Define a new org classification (optional)

− Use the Quickcode Values form to enter a new value forlookup type = 'ORG_CLASS'

− Skip this step if your new org EIT applies to an existingclassification.

2. Define new organization information type(s)

− Add a new structure to the Organization Developer DFdescriptive flexfield. The structure must have as itscontext the name of the Organization Info Type.

− It's a protected descriptive flexfield, so you'll need tounset the protected flag before you can query theflexfield up on the Descriptive Flex segments form. Usethe Register Descriptive Flexfield form to manipulatethe protected flag.

− Make sure you reset the protected flag when you'vefinished.

ii) Seed a row into HR_ORG_INFORMATION_TYPES. The columns youshould seed are:

Column name Description

ORG_INFORMATION_ Name of the type (same as DDFcontext)

DESCRIPTION Description of the info type(translated)

19

DISPLAYED_ORG_INFORMATION_TYPE Displayed org info type name(translated)

NAVIGATION_METHOD 'GS' for single row; 'GM' formulti row

1. Define mapping from org info type to org classification

Do this by seeding a row into HR_ORG_INFO_TYPES_BY_CLASS:

Column name Description

ORG_CLASSIFICATION ORG_CLASS lookup code

ORG_INFORMATION_ Org info type

MANDATORY_FLAG ‘Y’ or ‘N’

20

Appendix C: Example Script to Register EITsWHENEVER SQLERROR EXIT FAILURE ROLLBACK;REM /* $Header: example.sql $ */REM ===============================================================REM SQL Script File Name : example.sqlREM Description : This sql script inserts informationREM types into the following tables:REM 1) PER_ASSIGNMENT_INFO_TYPESREM 2) HR_LOCATION_INFO_TYPESREM 3) PER_PEOPLE_INFO_TYPESREM 4) PER_POSITION_INFO_TYPESREM 5) HR_ORG_INFORMATION_TYPESREM 6) HR_ORG_INFO_TYPES_BY_CLASSREM ===============================================================

-- 1) Insert into PER_ASSIGNMENT_INFO_TYPES:--INSERT INTO PER_ASSIGNMENT_INFO_TYPES(INFORMATION_TYPE,ACTIVE_INACTIVE_FLAG,MULTIPLE_OCCURENCES_FLAG,DESCRIPTION,LEGISLATION_CODE,OBJECT_VERSION_NUMBER)SELECT '<Info Type Name>','Y','<Y for multi-row - N for single>',’<Description>’,'<legislation code US/GB/etc>',1FROM sys.dualWHERE not exists (SELECT 1 FROM PER_ASSIGNMENT_INFO_TYPES WHERE INFORMATION_TYPE = '<Info Type Name>');

--2) Insert into HR_LOCATION_INFO_TYPES:---INSERT INTO HR_LOCATION_INFO_TYPES(INFORMATION_TYPE,ACTIVE_INACTIVE_FLAG,MULTIPLE_OCCURENCES_FLAG,DESCRIPTION,LEGISLATION_CODE,OBJECT_VERSION_NUMBER)SELECT'<Location EIT Name>','Y','<Y for multi-row - N for single>',’<Description>’,'<legislation code US/GB/etc>',1FROM sys.dual

21

WHERE not exists (SELECT 1 FROM HR_LOCATION_INFO_TYPES WHERE INFORMATION_TYPE = '<Location EITName>');

--3) Insert into PER_PEOPLE_INFO_TYPES:---INSERT INTO PER_PEOPLE_INFO_TYPES(INFORMATION_TYPE,ACTIVE_INACTIVE_FLAG,MULTIPLE_OCCURENCES_FLAG,DESCRIPTION,LEGISLATION_CODE,OBJECT_VERSION_NUMBER)SELECT '<Person EIT Name>','Y','<Y for multi-row - N for single>',’<Description>’,'<legislation code US/GB/etc>',1FROM sys.dualWHERE not exists (SELECT 1 FROM PER_PEOPLE_INFO_TYPES WHERE INFORMATION_TYPE = '<Person EIT Name>');--

--4) Insert into PER_POSITION_INFO_TYPES:---INSERT INTO PER_POSITION_INFO_TYPES(INFORMATION_TYPE,ACTIVE_INACTIVE_FLAG,MULTIPLE_OCCURENCES_FLAG,DESCRIPTION,LEGISLATION_CODE,OBJECT_VERSION_NUMBER)SELECT'<Position EIT Name>','Y','<Y for multi-row - N for single>',’<Description>’,'<legislation code US/GB/etc>',1FROM sys.dualWHERE not exists (SELECT 1 FROM PER_POSITION_INFO_TYPES WHERE INFORMATION_TYPE = '<Position EIT Name>');

--5) Insert into HR_ORG_INFORMATION_TYPES:--- Note different parameters for this EIT-- Note different parameter value for single and multi-row--INSERT INTO HR_ORG_INFORMATION_TYPES(ORG_INFORMATION_TYPE,DESCRIPTION,DESTINATION

22

,DISPLAYED_ORG_INFORMATION_TYPE,FND_APPLICATION_ID,LEGISLATION_CODE,NAVIGATION_METHOD)SELECT '<Organization EIT Name>',’<Description>’,NULL,’<Display value on the Organization form>’,NULL,'<legislation code US/GB/etc>','<GM for multi-row - GS for single>'FROM sys.dualWHERE not exists (SELECT 1

FROM HR_ORG_INFORMATION_TYPESWHERE ORG_INFORMATION_TYPE = '<Organization EIT

Name>');

INSERT INTO HR_ORG_INFO_TYPES_BY_CLASS(ORG_CLASSIFICATION,ORG_INFORMATION_TYPE,MANDATORY_FLAG)SELECT '<Check lookup value for classification HR_BG for Business Group>', '<Organization EIT Name>','N'FROM sys.dualWHERE not exists (SELECT 1

FROM HR_ORG_INFO_TYPES_BY_CLASSWHERE ORG_INFORMATION_TYPE = '<Organization EIT

Name>'and

ORG_CLASSIFICATION = '< HR_BG for BusinessGroup>');

/

COMMIT;

EXIT;