Checkstyle Parameter Assignment Of Rents

Skip Headers

Extending Oracle HRMS

Extend Oracle HRMS Overview

This section describes how you can extend Oracle HRMS to better meet your enterprise's needs.

There are many ways you can configure Oracle HRMS to meet the needs of your business processes:

  • Linking windows together in a task flow to streamline data entry and processing

  • Designing your own windows to create user or task-specific windows

  • Restricting data access on windows to provide security and confidentiality

You can configure Oracle HRMS using one or any combination of these.

Before configuring any part of Oracle HRMS, it is advisable to plan ahead and decide which parts of the system you want to configure. For example, if you know that your users typically perform a task in a certain way, you can design windows to help them enter information more efficiently. You can also link windows together to help users move from one window to the next. If necessary, you can also restrict what information appears in lists of values and restrict access to certain types of information.

Key Concepts

This section describes some of the tools available to configure Oracle HRMS for your enterprise.

Alerts

Alerts enable you to inform, remind, and confirm information on your personal information, your direct reports, and your workforce. The alert triggers an email notification of an impending action, task, or change to information. For example, you can set up an alert to remind you when a new hire is due to start work.

See: Oracle HRMS Predefined Alerts

Flexfields

You can add data fields called flexfields to windows to hold any additional information you require. You can add:

  • Key flexfields to configure some of the most important parts of the system, including the names of jobs, positions and grades, details of payroll cost allocation, and analysis information for employees and other people.

  • Descriptive flexfields to add fields to windows to record additional information.

  • Extra Information Types to set up multiple categories of information for the most important entities in Oracle HRMS.

Protected Flexfields are predefined and protected flexfields supplied with Oracle HRMS.

User-Defined Tables

You can set up user tables to provide matrixes of valid values that vary. You can access these values from formulas, or your own forms or reports. The GET_TABLE_VALUE function is supplied for use in your formulas. Certain legislations include predefined user tables, for example, to hold values for payroll calculations.

Lookups

Lookups provide lists of valid values on certain fields throughout the system. For many lookups you can add your own values and change the predefined values. Lookups not only ensure that all users use the same terminology, but also speed up data entry.

CUSTOM Library Events

You can use CUSTOM Library Events to configure the logic that is executed at defined points within a window. Generic events are available to all Oracle Applications and Product Specific Events are also available to help you to apply business rules specific to Oracle HRMS.

APIs (called Application Programmatic Interfaces)

Oracle HRMS provides a set of PL/SQL packaged procedures and functions that together provide an open interface to the database.

Task Flows

You often need to use more than one window to complete many tasks. Oracle HRMS enables you to link these windows together using a task flow. Users can choose a button to bring up each window in turn without returning to the menu. For example, to enter personal information, you typically go from the People window, to the Address window, to the Special Information window and so on. Task flows speed up processes and reduce data entry error

See: Task Flow

Restricting Information

Restricting the type of information available on a window is useful as a security measure. For example, you can create versions of RPA windows to show only compensation information available to the logged-in user.

See: Windows You Can Configure Using CustomForm, , Oracle HRMS Configuring, Reporting, and System Administration GuideRestricted RPA, Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide

Currencies

You need to define the formats for displaying currency amounts. If required, you can use multiple currencies for entering information about employee compensation and benefits and you can also record your payment methods to employees in different currencies. You must enable at least one currency as the default currency for all information related to money in your system. This default is known as the Base Currency for your Business Group.

Workflow

Workflow

You use the Oracle HRMS Workflow tool to:

  • Create and maintain taskflows

    See: Task Flow (Oracle Workflow)

  • Configure the approval and notification workflow process for RPAs and for Within Grade Increases (WGIs).

    See: RPA and PD Workflow Overview

  • Configure the workflow process for budget worksheets based on user-defined routing lists, position hierarchies, or supervisory hierarchies. You restrict which users process transactions by defining routing and authorization rules.

Extend Oracle HRMS

You can extend Oracle HRMS to meet the needs of your enterprise.

You can configure Oracle HRMS by designing windows to match your specific business processes. You can also link windows together to form any number of flows required by your users. Configuring windows and taskflows enable your users to perform their tasks more efficiently.

How can you hold additional information?

You can add data fields to windows to hold any additional information you require. Flexfields are flexible fields that enable you to do this.

Then, when you click in a flexfield you have set up, a window opens, displaying segments into which you can enter data.

You can also set up your own tables to hold data such as agency-specific basic and special rate pay tables.

How can you ensure the same terminology is used and speed up data entry?

Oracle provides lists of values called QuickCodes for certain items of information. QuickCodes ensure that all users use the same terminology, making it easier to inquire and report on information. QuickCodes also speed up data entry because you can enter just enough to identify the value, and the system completes the entry.

Can you link windows together?

Oracle recognizes that to complete many tasks, you need to use more than one window. You can link these windows together in a task flow so that you can choose a button to bring up each window in turn without returning to the menu.

How is security affected by configuring windows?

Any windows that you configure behave in the same way as existing windows. Security is set by the user's security profile option and responsibility. However, you can configure the Find results window to enable users to see information for people outside of their security profile. They cannot change this information.

In addition, you can create windows that:

  • Restrict the list of values on certain fields or limit access to certain types of information

  • Use workflow so that any data changes must be approved before the changes are applied to the database. This applies to the windows that are based on templates.

Can you define currency formats?

You can define the formats for displaying currency amounts.

Flexfields

Flexfields

Flexfields are flexible fields that enable you to configure and extend Oracle Applications by adding fields to windows. There are two types of flexfield:

  • Key flexfields enable you to define additional information you want to record in existing fields.

  • Descriptive flexfields enable you to add fields to windows to record additional information.

    Extra Information Types (EITs) are a type of descriptive flexfield that enable you to set up unlimited amounts of extra information for eight of the most important entities in Oracle HRMS.

You can set up each flexfield to contain a number of segments, which act like separate fields.

When a user clicks in a flexfield you have set up, a window opens, displaying the segments that you have defined. For each segment, you can define:

  • Its prompt

  • The type of data it can contain

  • The values a user can enter

You can provide a list or range of valid values. You also control the size and display characteristics of each segment and the sequence in which the segments appear.

User-Definable Key Flexfields

In Oracle HRMS there are six user definable key flexfields, for each of which you can define up to 30 segments:

  • Job

  • Position

  • Grade

  • Competence

  • People Group

  • Personal Analysis

  • Cost Allocation

  • Collective Agreement Grades

The Personal Analysis and Collective Agreement Grades key flexfields can have an unlimited number of structures. All other flexfields can have only one structure each.

You can define up to 30 segments for each structure in all key flexfields except for the Collective Agreement Grades key flexfield. This can have up to 20 segments for each structure.

How Oracle HRMS Uses Key Flexfields

Oracle US Federal HR product predefines the Grade Flexfield. The product requires that you also include specific segments in the Position and Job flexfields. The Personal Analysis Flexfield has predefined values.

The People Group, Cost Allocation, and Competence Flexfields have no minimum requirements.

The Collective Agreement Grade flexfield is not supported for Oracle US Federal HR.

The following sections provide some general information about Oracle HRMS usage of the key flexfields. For detailed information on key flexfield descriptions and lookups, refer to US Federal Human Resource Key Flexfields.

Unique Identifiers

The Job, Position, Grade Name, and Competence flexfields enable you to create a unique name, which is a combination of separate components or segments. You can use these flexfields when you are defining the work structures and competencies that exist in your enterprise.

Tip: When you are defining your requirements for these key flexfields you should consider the following points:

  • The task of defining the segment combinations is normally restricted to one or two users only. Therefore, you may not need to use value sets, or cross validation rule options to control the values that can be entered.

    • The names that users see are made up of a combination of segment values. The segment values are displayed, not the meanings.

    • Avoid segments containing information that may change regularly. There is no history of changes to the combinations you create. For example, do not define minimum and maximum values for grades as segments of the Grade flexfield.

Analysis Information

The People Group and Personal Analysis flexfields enable you to add key information to records of employee assignments and people. You can use the individual segments of these flexfields to identify or report on specific groups of people.

Payroll Costing

The Cost Allocation key flexfield is used to collect and to accumulate costs associated with running a payroll.

Collective Agreement Grade Structures

The Collective Agreement Grades key flexfield enables you to create an unlimited number of grade structures. You use the individual segments of each grade structure to record the grade factors that are defined within a collective agreement.

Once the grade structure is recorded you can link it to a collective agreement and enter the required factor values for each reference grade in the Agreement Grades window.

What You Must Set Up

The key flexfields are central to Oracle HRMS, therefore you must create certain definitions before you can set up your Business Group.

For detailed information on key flexfield descriptions and lookups, refer to Oracle US Federal Human Resource Key Flexfields.

Job Key Flexfield

  • You can only define one structure per Business Group for each of these flexfields.

  • You must define a segment for the occupational series using the supplied value set. After defining the job key flexfield, you map this segment to the US Federal Organization Information.

  • You must define a structure name for these flexfields before you can define a Business Group.

  • You associate these structures with a Business Group in the Business Group Information window, which opens from the Organization window.

Position Key Flexfield

  • You can only define one structure per Business Group for each of these flexfields.

  • You must define four segments for the position title, position description number, sequence number, and agency code using the supplied value set. The Position Title segment must reside in the first five segments of the key flexfield. After you define the position key flexfield, you map these four segments to the US Federal Organization Information.

  • You must define a structure name for these flexfields before you can define a Business Group.

  • You associate these structures with a Business Group in the Business Group Information window, which opens from the Organization window.

  • It is essential to run the Create Key Flexfield DB Items process whenever you create or change the Position key flexfield definitions. See: Creating Key Flexfield Database Items.

Grade Key Flexfield

  • The application predefines the flexfield segments and the structure name for the Grade Key Flexfield. You must compile the flexfield.

  • You associate these structures with a Business Group in the Business Group Information window, which opens from the Organization window.

  • You run the Create Federal HR Valid Combinations for the Grade Key Flexfield process to enter the predefined grade and pay plan combinations for each business group you set up.

Competence Key Flexfield

  • You must define a structure name for this flexfield before you can define a Business Group.

  • You can only define one structure per Business Group for this flexfield.

  • You associate this structure with a Business Group in the Business Group Information window, which opens from the Organization window. This defines the key flexfield that is used when creating competencies specific to the Business Group.

  • You can create an additional key flexfield that can be used to create global competencies that are available across all Business Groups. You can, however, use the same key flexfield you have defined for the Business Group if you want. You define this key flexfield in the HR: Global Competence Flex Structure profile option.

  • You must specify one of the segments as the Default Attribute using the flexfield qualifier. You must also attach the Others flexfield qualifier to all other segments in the structure.

  • It is essential to run the Create Key Flexfield DB Items process whenever you create or change the Competence key flexfield definitions. See: Creating Key Flexfield Database Items.

People Group Key Flexfield

  • You can only define one structure per Business Group for this flexfield.

  • You do not create separate combinations of segments for the People Group flexfield. You enter values for each employee as part of the employee assignment.

  • You must define a structure name for this flexfield before you can define a Business Group.

  • You must define at least one segment for the People Group flexfield in order to be able to use the Assignment window.

  • It is essential to run the Create Key Flexfield DB Items process whenever you create or change the People Group key flexfield definition. See: Creating Key Flexfield Database Items.

Personal Analysis Key Flexfield

  • You can create any number of structures per Business Group for this flexfield. Each one represents a Special Information Type.

  • Each Special Information Type can have up to thirty fields (where each field is a segment of the flexfield).

  • You can set up cross-validation to ensure that users enter correct combinations of segments. You can also speed up data entry and minimize errors by defining an 'Alias' for common combinations of segment values.

  • You do not need to define any structures for the Personal Analysis flexfield before you can use Oracle HRMS.

  • You link each structure to a Business Group in the Special Information Types window while you are logged on to that Business Group.

  • You can customize windows to restrict access to specific Information Types.

Cost Allocation Key Flexfield

  • You can only define one structure per Business Group for this flexfield.

  • You can control the levels at which users can enter cost information by using the flexfield qualifiers.

  • You must define a structure name for this flexfield before you can define a Business Group.

  • A number of windows in Oracle HRMS check for the existence of a valid flexfield structure for Cost Allocation. You must define at least one segment for your Cost Allocation flexfield.

Collective Agreement Grades (CAGR) Key Flexfield

  • You can create any number of structures for this flexfield.

Important: If you are using the Italian legislation, do not create new structures for this flexfield. You must use the predefined structure, IT_CAGR, and you must not make changes to it. Otherwise, you may be unable to enter collective agreement grades for your assignments.

  • You can define up to 20 segments within each structure. Each segment refers to a grade factor that is available as part of the grade structure.

  • You must check the Allow Dynamic Inserts check box when defining the structure of this flexfield.

  • You do not need to define any structures for the Collective Agreement Grades flexfield before you can use Oracle HRMS.

  • You link each structure to a collective agreement in the Agreement Gradeswindow. The reference grades entered in this window are recorded against this combination.

  • You can enter values for each of the defined grade factors as part of each reference grade in the Agreement Grades window.

Flexfields: Open Key Window Profile Option

The way in which key flexfield windows open is controlled by the Flexfields:Open Key Window profile option. If this option is set to Yes, the flexfield window automatically pops open when the user navigates to the field. If it is set to No, users can open the flexfield by choosing Edit Field from the Edit menu or pressing CTRL+L. The default is Yes.

User Definable Descriptive Flexfields

The predefined fields in Oracle HRMS windows are designed to meet your core information requirements. However, like all enterprises, you may have special requirements that are best met by fields that you design yourself. Oracle HRMS provides a flexible mechanism called descriptive flexfields to enable you to add fields to windows.

All window blocks in which you can enter information contain a user definable descriptive flexfield. You decide in which blocks you want to record additional information. Each user definable descriptive flexfield has 20 segments that you can define. After you define a descriptive flexfield, Oracle HRMS treats the segments as part of the window.

The following figure illustrates the distinctive appearance of descriptive flexfields. When users click in a flexfield that you have set up, or choose Edit Field from the Edit menu, a window opens, displaying up to 20 segments that you have defined.

The way in which descriptive flexfield windows open is controlled by the Flexfields:Open Descr Window profile option. If this option is set to Yes, the flexfield window automatically pops open when the user navigates to the field. If it is set to No, users can open the flexfield by choosing Edit Field from the Edit menu or pressing CTRL+L. The default is Yes.

Segments

For each segment, you can define:

  • Its prompt

  • The type of data it can contain

  • The values a user can enter

You can provide a list or range of valid values. You also control the size and display characteristics of each segment and the order in which the segments appear.

Types of Descriptive Flexfield Segments

You can define two types of descriptive flexfield segments:

  • Global segments, which always appear in the window.

  • Context-sensitive segments, that appear only when a defined context exists. You can prompt the user to provide the context, or you can provide the context automatically from a reference field in the same block.

    For example, a segment holding information about an employee's disability might appear only when the Disabled field is checked.

Important: Some descriptive flexfields appear in more than one window. For example, the Additional Evaluation Details flexfield appears in the Job Evaluation window and the Position Evaluation window.

Check all of the windows that use a descriptive flexfield before you define any of the segments. This is especially important if you intend to make the flexfield context sensitive to another field. You must ensure that the reference fieldis present in all of the windows that use the flexfield.

See: Descriptive Flexfield List for a full list of user definable descriptive flexfields in Oracle HRMS.

Descriptive Flexfield List

The following table lists all the user definable descriptive flexfields in Oracle HRMS.

Additional Absence Details Absence Detail,
View Absence History
ABSENCES_<SEGMENT_NAME>
Additional Absence Type Details Absence Attendance Type ABSENCE_TYPES_<SEGMENT_NAME>
Additional Address Details Address,
Applicant Entry
Contact
PERSON_ADDRESSES_<SEGMENT_NAME>
Additional Application Details Applicant Entry,
Application,
Terminate Applicant
APPLICATIONS_<SEGMENT_NAME>
Additional Appraisal Details    
Additional Appraisal Template Details    
Additional Assessment Group Details    
Additional Assessment Type Details    
Additional Assessment Details Medical Assessment  
Additional Assignment Details Applicant Entry,
Application,
Assignment,
Assignment History
ASSIGNMENTS_<SEGMENT_NAME>
Additional Assignment Status Details Secondary Statuses  
Additional Balance Type Details Balance (Oracle Payroll only)  
Additional Benefit Contribution Details Benefit Contributions (US only)  
Additional Booking Details Applicant Interview,
Book Events,
Employee Review,
Event Bookings
 
Additional Budget Details Budget  
Additional Budget Values Details    
Additional Budget Version Details Budget  
Additional Calendar Information Budgetary Calendar (Oracle Payroll)  
Additional Candidate Information Election  
Additional Career Path Details Career Path Names  
Additional Checklist Item Details    
Additional COBRA Benefit Details COBRA Benefits (US only)  
Additional COBRA Coverage Details COBRA Coverage (US only)  
Additional COBRA Payment Details COBRA Payment (US only)  
Additional COBRA Status Details COBRA Status (US only)  
Additional Collective Agreement Details Collective Agreements  
Additional Coll. Agreed Grades Details Agreement Grades  
Additional Competence Details    
Additional Competence Element Details    
Additional Constituency Details Election  
Additional Contact Relationship Details Contact CONTACTS_<SEGMENT_NAME>
Additional Contract Details Contract  
Additional Delivery Method Details    
Additional Deployment Factor Details Work Choices, and Position Transaction (Work Choices tabbed region)  
Additional Disability Information Disabilities  
Additional Election Details Election  
Additional Element Entry Information Adjust Balance (Oracle Payroll only),
Element Entries,
View Element Entry History for Employee
 
Additional Element Link Information Element Link (Oracle Payroll)  
Additional Element Type Details Element (Oracle Payroll)  
Additional Establishment Att Details    
Additional Establishment Details    
Additional Evaluation Details Job,
Position
 
Additional Event Details Applicant Interview,
Employee Review,
Event Bookings
EVENTS_<SEGMENT_NAME>
Additional Grade Details Grade GRADES_<SEGMENT_NAME>
Additional Hierarchy Details Generic Hierarchy  
Additional Incident Details Work Incident  
Additional Job Details Job JOBS_<SEGMENT_NAME>
Additional Letter Details Letter  
Additional Location Details Location  
Additional Node Details Generic Hierarchy  
Additional Objectives Details    
Additional Organization Information Organization  
Additional Organization Payment Method Details Organizational Payment Method (Oracle Payroll)  
Additional Organization Structure Details Organization Hierarchy  
Additional Organization Unit Details Organization ORGANIZATION_<SEGMENT_NAME>
Additional Participants Details    
Additional Pay Scale Information Pay Scale  
Additional Pay Rate Details Grade Rate,
Scale Rate
 
Additional Payroll Action Details (Oracle Payroll)    
Additional Payroll Details Payroll PAYROLLS_<SEGMENT_NAME>
Additional Performance Ratings Details    
Additional Period Information Budgetary Calendar,
Period Dates (Payroll form)
 
Additional Period of Placement Details End Placement  
Additional Period Type Information Period Types  
Additional Person Analysis Details Special Information,
List People By Special Information
 
Additional Personal Details Applicant Entry,
Contact,
People,
People Folder
PEOPLE_<SEGMENT_NAME>
Additional PPM Details Personal Payment Method  
Add'l Person Type Usage Details Person Type Usage  
Additional Position Details Position,
Find Positions (Mass Move form)
POSITION_<SEGMENT_NAME>
Additional Position Structure Details Position Hierarchy  
Additional Previous Employer Details Previous Employment  
Additional Previous Job Details Previous Employment  
Additional Previous Job Usage Details Previous Job  
Additional Qualification Details    
Additional Qualification Types    
Additional Rating Level Details    
Additional Rating Scale Details    
Additional Recruitment Activity Details Recruitment Activity RECRUITMENT_ACTIVITIES_<SEGMENT_NAME>
Additional Requirement Details Job,
Position
 
Additional Requisition Details Requisition and Vacancy  
Additional Role Details Supplementary Roles  
Additional Salary Administration Details Salary Administration  
Additional Salary Basis Details Salary Basis  
Additional Standard Holiday Absence Details    
Additional Subjects Taken Details    
Add'l Succession Planning Det. Succession Planning page  
Additional Telephone Number Details Phone Numbers  
Additional Template Details People Management Configurator (Template Object)  
Additional Vacancy Details Requisition and Vacancy  
Additional Valid Grade Details Job,
Position
 
Additional Version Details Generic Hierarchy  
Additional Year Information Budgetary Calendar  
Assignment Extra Information Extra Assignment Information  
Extra Job Info Details Extra Job Information  
Extra Location Info Details Extra Location Information  
Extra Person Info Details Extra Person Information  
Extra Position Info Details    
Extra Previous Job Details Previous Employment  
Further Candidate Information Election  
Further Election Information Election  
Proposal Component Addl Info    
Review Addl Information    
Salary Survey Additional Information    
Survey Line Addnl Information    
Survey Mapping Add Info    

Descriptive Flexfields and Address Styles

Oracle HRMS supplies two predefined descriptive flexfields to hold address information in different styles for different countries. These are:

  • the Personal Address Information descriptive flexfield: This holds the address information of your employee or applicant.

  • the Location Address descriptive flexfield: This holds the address information of your locations.

Oracle HRMS holds the addresses of people and locations separately to enable you to record different information for tax reporting.

You can use these descriptive flexfields to add new address styles or to change the styles included in Oracle HRMS.

Important: If you change the predefined styles, your changes are overwritten when you upgrade Oracle HRMS. If you add new styles, your changes may be overwritten if new startup data contains address styles for these countries.

Address Styles

Address styles vary between countries, so Oracle HRMS provides descriptive flexfields that use context-sensitive segments to hold each line of an address. The Address Styles Flexfields table below details the title of the flexfield, its location and where it is used.

Address Style Flexfields in Oracle HRMS

Personal Address Information PER_ADDRESSES Address, Applicant Entry
Location Address HR_LOCATIONS Location, Organization

The available address styles are defined as the contexts for these flexfields. There are two types of address style:

Address styles are provided as startup data in these flexfields. If you require additional address styles, you need to define a new context and segments.

International Address Style

This style provides basic validation of address data. Oracle HRMS provides international address styles for many countries. This style can be used for both location and personal addresses. International address styles are named territory_code_GLB. For example, the Australian international address style is AU_GLB.

Territory codes can be found in the FND_TERRITORIES table.

If no international address style is available for your country, you can use the generic style (GENERIC) to enter your address information. This generic structure provides no validation.

Local Address Style

This style provides full validation of address data and is set up by a localization team. Where a local address style exists, it can usually be used for both location and personal addresses. Local address styles are named territory_code. For example, the Australian local address style is AU.

Where a local address style exists and the Business Group uses the legislation code for that country, the local address style is displayed as the default in the appropriate address entry window. Where no local address exists, the international style is the default.

US and Canadian users: the local address style for the US or Canada is only available when you have Vertex geocodes data installed.

Developer Flexfields

Oracle HRMS supplies developer key flexfields and developer descriptive flexfields. Your localization team has defined these flexfields, as required, to meet the specific legislative and reporting needs of your country.

The protected developer key flexfields are the Soft Coded Legislation key flexfield and the Bank Details key flexfield.

Of the developer descriptive flexfields, all except six are protected and cannot be amended. The remaining six have Extra Information Types that you can use to configure your application.

See: Extra Information Types (EITs), Oracle HRMS Configuring, Reporting, and System Administration Guide

The following table lists the developer descriptive flexfields, including EITs.

Developer Descriptive Flexfields in Oracle HRMS

Extra Job Information (EIT)    
Extra Location Information (EIT)    
Extra Person Information (EIT)    
Extra Position Information (EIT)    
Extra Previous Job Information PER_PREVIOUS_JOB_EXTRA_INFO Previous Employment
Further Absence Information (Additional Absence Detail Information) PER_ABSENCE_ATTENDANCES Absence Detail
Further Assignment Information (EIT)    
Further Budget Values Details    
Further Candidate Information PER_ELECTION_CANDIDATES Election
Further Canvas Properties HR_CANVAS_PROPERTIES_B People Management Configurator (Canvas Object)
Further Collective Agreement Information PER_COLLECTIVE_AGREEMENTS Collective Agreements
Further Competence Element Information PER_COMPETENCE_ELEMENTS  
Further Competence Element Outcomes Information PER_COMP_ELEMENT_OUTCOMES  
Further Competence Information PER_COMPETENCES Competencies
Further Competence Outcomes Information PER_COMPETENCE_OUTCOMES  
Further Contact Relationship Information PER_CONTACT_RELATIONSHIPS Contacts
Further Contract Information (Datetracked) PER_CONTRACTS_F Contracts
Further Contribution History Information    
Further Disability Information (Datetracked) PER_DISABILITIES_F Disabilities
Further Election Information PER_ELECTIONS Election
Further Element Information (Datetracked) PAY_ELEMENT_TYPES_F Element
Further Element Entry Information (Datetracked) PAY_ELEMENT_ENTRIES_F Element Entry
Further Establishment Information PER_ESTABLISHMENTS Schools/Colleges
Further Form Properties HR_FORM_PROPERTIES People Management Configurator (Form Object)
Further Item Properties HR_ITEM_PROPERTIES People Management Configurator (Item Object)
Further Job Information PER_JOBS Job
Further Medical Assessment Information PER_MEDICAL_ASSESSMENTS Medical Assessment
Further Payment Method Information (Datetracked) PAY_ORG_PAYMENT_METHODS_F Organizational Payment Method
Further Payroll Information (Datetracked) PAY_ALL_PAYROLLS_F Payroll
Further Period Details PER_TIME_PERIODS Payroll Periods
Further Period of Service Information (Add'l Periods of Service Information) PER_PERIOD_OF_SERVICE Terminate
Further Person Information (Datetracked) PER_PEOPLE_F People, Applicant Entry
Further Previous Employer Information PER_PREVIOUS_EMPLOYERS Previous Employment
Further Previous Job Information PER_PREVIOUS_EMPLOYERS Previous Employment
Further Previous Job Usage Information PER_PREVIOUS_JOB_USAGES Previous Job
Further Qualification Information PER_QUALIFICATIONS Qualifications
Further Role Information PER_ROLES Supplementary Roles
Further Subject Information PER_SUBJECTS_TAKEN Qualifications
Further Tab Page Properties HR_TAB_PAGE_PROPERTIES_B People Management Configurator (Tab Page Object)
Further Template Properties   People Management Configurator
Further Window Properties HR_WINDOW_PROPERTIES_B People Management Configurator (Window Object)
Further Work Incident Information PER_WORK_INCIDENTS Work Incidents
Org Developer DF    
State Tax Limit Rate Information    
Statutory Transaction Information    
Tax Signup Developer DF    

Your localization team determines which of these flexfields are required for your legislation, and what segments they should contain. The legislation of your business group determines which developer descriptive flexfields are displayed. This means that if your enterprise uses multiple business groups that have different legislations, different developer descriptive flexfields are displayed for business groups of each legislation.

Caution: Do not attempt to alter the definitions of the protected flexfields. These definitions are a fundamental part of Oracle HRMS. Any change to them may lead to errors in the operating of the system.

It is possible that Oracle HRMS will use other segments of these flexfields in the future. Therefore, do not add segments to any protected flexfield, as this may affect your ability to upgrade your system in the future.

Soft Coded Legislation Key Flexfield

This key flexfield holds legislation-specific information. The legislation of your business group determines the flexfield structure that you see.

Each localization team defines a flexfield structure, if required, which enables you to enter information specific to your legislation at the employee or contingent worker assignment level.

Bank Details Key Flexfield

This flexfield holds legislation-specific bank account information. The legislation of your business group determines the flexfield structure that you see. Each localization team defines a flexfield structure that allows you to record the bank account information relevant to your legislation. You enter this information in the Organizational Payment Method window and Personal Payment Method window.

Creating Key Flexfield Database Items

The Create Key Flexfield DB Items process turns data in key flexfields into database items that Oracle FastFormula can access. It is essential to run this process whenever you create or change the Grade, Job, Position, or People Group key flexfield definitions.

Submit the process from the Submit Requests window.

To create key flexfield database items

  1. Run the Create Key Flexfield DB Items process.

    Run this process whenever you create or change these key flexfield definitions.

    See: Running Reports and Programs, Oracle Applications User's Guide

Setting up the Job Key Flexfield

You define the Job key flexfield to hold information about the work structure that exists in your Business Group. The Job key flexfield stores the occupational series information.

To set up the Job key flexfield

  1. In the Key Flexfield Segments window, create a new Job Key Flexfield structure and name it, for example, US Government Job.

  2. In the Segments Summary window, define the first segment for the occupational jobs series using the supplied value set GHR_US_OCC_SERIES.

  3. Note the Name and Column fields for the occupational series segment. You refer to this information during implementation.

Setting up the Position Key Flexfield for Non-NFC Implementations

You define the Position key flexfield to hold information about the work structure that exists in your business group. The Position key flexfield stores the position title, agency code, and other position-related information.

To set up the Position key flexfield

  1. In the Key Flexfield Segments window, create a new Position Key Flexfield structure and name it, for example, US Federal Position.

  2. In the Segments Summary window, you must define four required US Federal Position segments using the supplied value sets.

    • Define Position Title (GHR_US_POSITION_TITLE) using one of the first five segments (Segment 1, 2, 3, 4, or 5)

      When you define the Position Key Flexfield, you must define the Position Title as one of the first five segments of the Position Key Flexfield structure. By restricting the location of the Position Title to one of these segments, you improve the performance of the To Position LOV (Lookup Value) on the Request for Personnel Action (RPA) form.

    • Using the remaining segments, define Position Description Number (GHR_US_POS_DESC_NUM), Sequence Number (GHR_US_SEQUENCE_NUM), and Agency/Subelement Code (GHR_US_AGENCY_CODE).

  3. Note the Name and Column fields for the four position segments. You refer to this information during implementation.

  4. You can define up to 30 segments within the structure.

    For the segments that you add, you can define a list of valid codes or values.

    See: User Definable Key Flexfields

Setting up the Position Key Flexfield for NFC Implementations

You define the Position key flexfield for NFC implementations to hold information such as the position title, OPM and NFC agency codes, and grade information.

When defining the segments, you must define the segment numbers and the prompts as instructed in the following steps.

See: Setting up the Position Key Flexfield for Non-NFC Implementations

To set up the Position key flexfield

  1. In the Key Flexfield Segments window, create a new Position Key Flexfield structure and name it, for example, US Federal Position

  2. In the Segments Summary window, define the first segment:

    • Sequence Number: 1

    • Name: Position Title

    • Window Prompt: Position Title

    • Column: Segment1

    • Value Set: GHR_US_POSITION_TITLE

    • Displayed: Checked

    • Enabled: Checked

  3. Click the Open button to display the Segments window, and define the following options:

    • Required: Checked

    • Enter an amount for the Display size and Description size based on your agency's requirements.

  4. Save your work.

  5. In the Segments Summary window, define the second segment:

    • Sequence Number: 2

    • Name: OPM Agency Code

    • Window Prompt: OPM Agency Code

    • Column: Segment2

    • Value Set: GHR_US_AGENCY_CODE

    • Displayed: Checked

    • Enabled: Checked

  6. Click the Open button to display the Segments window, and define the following options:

    • Required: Checked

    • Enter an amount for the Display size and Description size based on your agency's requirements.

  7. Save your work.

  8. In the Segments Summary window, define the third segment:

    • Sequence Number: 3

    • Name: NFC Agency Code

    • Window Prompt: NFC Agency Code

    • Column: Segment3

    • Value Set: GHR_US_NFC_AGENCY_CODE

    • Displayed: Checked

    • Enabled: Checked

  9. Click the Open button to display the Segments window, and define the following options:

    • Required: Checked

    • Enter an amount for the Display size and Description size based on your agency's requirements.

  10. Save your work.

  11. In the Segments Summary window, define the first segment:

    • Sequence Number: 4

    • Name: Personnel Office ID

    • Window Prompt: Personnel Office ID

    • Column: Segment4

    • Value Set: GHR_US_PERSONNEL_OFFICE_ID

    • Displayed: Checked

    • Enabled: Checked

  12. Click the Open button to display the Segments window, and define the following options:

    • Required: Checked

    • Enter an amount for the Display size and Description size based on your agency's requirements.

  13. Save your work.

  14. In the Segments Summary window, define the fifth segment:

    • Sequence Number: 5

    • Name: Position Number

    • Window Prompt: Position Number

    • Column: Segment5

    • Value Set: GHR_US_POS_DESC_NUM

    • Displayed: Checked

    • Enabled: Checked

  15. Click the Open button to display the Segments window, and define the following options:

    • Required: Checked

    • Enter an amount for the Display size and Description size based on your agency's requirements.

  16. Save your work.

  17. Click the Open button to display the Segments window, and define the following options:

    • Required: Unchecked (unlike the other options, this option is not selected)

  18. Save your work.

  19. In the Segments Summary window, define the seventh segment:

    • Sequence Number: 7

    • Name: Valid Grade

    • Window Prompt: Valid Grade

    • Column: Segment7

    • Value Set: GHR_GRADES

    • Displayed: Checked

    • Enabled: Checked

  20. Click the Open button to display the Segments window, and define the following options:

    • Required: Checked

    • Enter an amount for the Display size and Description size based on your agency's requirements.

  21. Save your work.

Creating Descriptive Flexfield Database Items

You can use descriptive flexfield segments in QuickPaint reports and formulas if there are database items for these segments.

See Descriptive Flexfield List for a list of flexfields for which you can create database items.

Submit the process from the Submit Requests window.

To create descriptive flexfield database items

  1. Run the Create Descriptive Flexfield DB Items process.

    Run this process whenever you create or change these descriptive flexfield definitions.

    See: Running Reports and Programs, Oracle Applications User's Guide

    Note: The process can only create database items for global segments. It does not create database items for context-sensitive segments.

Changing Default National Address Styles

National address styles, both international and local, are held and configured in the Personal Address Information and the Location Address descriptive flexfields. You can configure these styles using the Descriptive Flexfield Segments window.

You cannot construct any flexfield segment value sets with:

  • Profile options, $PROFILE$

  • Previous segment values, $FLEX$

  • Block.field references

  • Security rules

Note: You must ensure the Personal_Address or Location_Address protected flag is off.

To change the address style for any country, redefine those segments you do not want to use. Then define new segments to record your own information.

To alter an existing address style

  1. Enter Oracle Human Resources in the application field.

  2. Enter Personal Address Information or Location Address in the title field as appropriate.

  3. Run the query.

  4. Uncheck the Freeze Flexfield Definition check box.

    Note: Read the warning.

  5. Select the address style for your country.

    Note: Both international and local address styles are included in the list of context field values.

  6. Click the segments button.

    This opens a new window with the segment and value set information for the selected address style.

  7. Update the segments.

    Note: You must make the Country segment mandatory. Do not change the validation on any segment as this may invalidate existing data.

  8. Save your work, and open the Descriptive Flexfield Segments window. Make sure any new segments are enabled, and displayed.

  9. Check the Freeze Flexfield Definition check box.

  10. Choose the Compile button.

    When compilation is complete, exit your current login session, then log in again to see your updated styles.

To add an address style

  1. Enter Oracle Human Resources in the application field.

  2. Enter Personal Address Information or Location Address in the title field as appropriate.

  3. Run the query.

  4. Uncheck the Freeze Flexfield Definition check box.

    Note: Read the warning.

  5. Choose New from the File menu.

  6. Enter the country code in the code and name fields.

    Note: Ensure that the length of the country code in the Code field is not more than seven characters. Otherwise, Oracle HRMS displays an error when you try to select the address style and save the location.

  7. Enter a description and select the Segments button.

  8. Define the segments.

    Note: You can only use the columns provided by Oracle HR for your segments.

  9. Save your work.

    Note: Make sure any new segments are enabled. You can choose whether segments are displayed or not.

  10. Check the Freeze Flexfield Definition check box.

  11. Choose the Compile button.

    When compilation is complete, exit your current login session. Then log in again to see your updated styles.

Extra Information Types

Extra Information Types (EITs)

Extra Information Types are defined using descriptive flexfields. You can set up any number of different EITs for:

  • Location

  • Job

  • Position

  • Person

  • Assignment

  • Organization

  • Element types

  • Previous Job

  • Contacts

  • Role

Note: EITs for Organization are different because you can define which organization classification the EIT is available for.

For each EIT you can define up to 30 fully validated segments of information (or 20 for organizations).

Note: Oracle HRMS provides some predefined EITs. You may add your own information types, but you must not change the definitions of the delivered EITs.

Unlike the usual descriptive flexfields, EITs are child entities with separate tables to hold the information you enter. This means that you can have multiple instances of an EIT for each main record. When you define the EIT, you can specify whether you want to allow multiple instances. With the exception of organizations, EIT data is viewed and entered in a separate window which you can task flow.

The windows for all the EITs have the common look and feel of all the descriptive flexfield windows. This means that you can use your new EITs as soon as you save your definitions. Since flexfield definitions are preserved through upgrades, EITs do not require expensive recoding of configured forms with each new release.

For information about predefined EITs, see: Location Extra Information Types, Organization Extra Information Types, Person Extra Information Types, Position Extra Information Types, Assignment Extra Information Types.

Key Flexfield Combinations

EITs are very similar to Special Information Types (SITs). Oracle enables you to choose whether to set up extra or special information types, or both. Both types of information use flexfields to define the structure and validation of their segments.

However, SITs are stored in a key flexfield combination table where the combination of segments must be unique - a feature of all key flexfields. EITs are stored in a descriptive flexfield table where the combination of segment values do not need to form a unique key.

This means that EITs have performance advantages in large scale, or global implementations where you may want to transfer large volumes of information between separate installations.

Dates and EITs

EITs are not datetracked. Even if the parent entity, for example People, is datetracked, the extra information is not. However, if you want to track changes to specific EITs you can define date segments for Start and End Dates and use multiple rows of the EIT to track changes.

Extra Information Validation

The Extra Information flexfields have required data items that you must complete boefore saving the record. The Position Extra Information flexfield contains a Validate button, so that you can simultaneously save your changes and validate the data.

The system checks the data and notifies you in an error message if it finds any inconsistent data. You can then make the required corrections, and then choose the Validate button again to save and validate the data.

Extra Information Types (EITs) for US Federal

HR administrators or managers can update the assignment Telework information for their employees using the US Federal Telework Information EIT. HR administrators can use the Assignment, Extra Information window in Oracle HRMS and managers can use the Extra Information self-service page to provide the Telework details.

EITs and Security

Special and Extra Information types use CustomForm and Taskflow security to restrict access to information types as part of a specific user process. For example, in a Retirement process, you candesign your user process to include a separate federal service window as part of the taskflow and restrict the window to display only separation or termination-related information types.

EITs also have an extended security option to define access to all EITs at the responsibility level, not just one at a time. This means that you can also restrict access to EITs as part of a role-based security model. For example, you could limit line-manager access to a set of EITs that include job, person and assignment information types. You can do this more easily with EITs because you can restrict access to all EITs at the level of responsibility.

Restricting Access to Extra Information

You can restrict access to EITs using a combination of the following:

  • Menus and task flows : Without the EIT window a user cannot see or change any extra information for the entity.

  • CustomForm and task flows: This restricts EITs to specific user processes.

    For example, at the person level you might define EITs to hold medical details, security information and information required for working in other countries. In this situation you might want to create two task flows, the first with a button for entering only medical details and the second with a button for entering the other types of extra information

  • Responsibility level security: For each responsibility, you must select the EITs to be viewed. CustomForm and task flow restrictions provide additional security. You might specify that a responsibility can access an EIT, but users of this responsibility will not be able to view the extra information unless they have access to a window that displays it.

Note: This security does not apply to extra information on organizations.

Example Script for Registering Extra Information Types (EITs)

If you have created new organization EITs, you must create a SQL script to insert a row for each EIT into the relevant information type table. This is known as registering your information type. When you create your script, you can use the sample script provided as a guide.

Note: If you have created non-organization EITs, you use the concurrent process Register Extra Information Types (EITs) instead.

See: Register Extra Information Types (EITs)

Example Script to Register EITs

Setting Up Extra Information Types (Excluding Organization EITs)

The following steps explain how to set up Extra Information Types (EITs) to use in Oracle HRMS.

Note: EITs for organizations are set up differently. See: Setting Up Extra Information Types for an Organization Classification

  1. In the Descriptive Flexfield Segments window, select the relevant descriptive flexfield by title (for example, Extra Job Information). The descriptive flexfields available are:

    • Extra Location Information (30 Segments)

    • Extra Job Information (30 Segments)

    • Extra Position Information (30 Segments)

    • Extra Person Information (30 Segments)

    • Extra Element Information (30 Segments)

    • Further Assignment Information (30 Segments)

    • Previous Extra Job Information (30 Segments)

    • Contact Extra Information (30 Segments)

  2. Unprotect the relevant extra information type using the Register Descriptive Flexfield window. You must do this before you can query the flexfield in the Descriptive Flexfield window.

  3. Create a new record in the Context Field Values region of the Descriptive Flexfield window and enter the name of your new Information Type in the Code field. As these are context-sensitive descriptive flexfields, enter INFORMATION_TYPE in the Reference Field.

  4. Enter the segment values and compile in the same way as a standard descriptive flexfield.

    See: Defining Descriptive Flexfield Structures, Oracle Applications Flexfields Guide

    Important: There are some predefined EITs in Oracle HRMS. These definitions are a fundamental part of your Oracle HRMS installation and any change to them may lead to errors in the operation of the system. Do not attempt to alter the definitions of these developer flexfields or to add other segments to them. It is possible that Oracle will use other segments of these flexfields in the future. Any changes you make may affect your ability to upgrade your system in the future.

    For US Federal users: Do not prefix EIT definitions with GHR_US. This prefix is reserved for the predelivered US Federal definitions.

  5. Reset the protection in the Register Descriptive Flexfield window so the flexfield remains a protected descriptive flexfield.

  6. Run the Register Extra Information Types (EITs) concurrent program to insert a row for each EIT into the relevant Information Type table. The following table lists the tables for each EIT.

    Extra Information Type Tables

    Location HR_LOCATION_INFO_TYPES
    Job PER_JOB_INFO_TYPES
    Position PER_POSITION_INFO_TYPES
    Person PER_PEOPLE_INFO_TYPES
    Assignment PER_ASSIGNMENT_INFO_TYPES
    Previous Job PER_PREV_JOB_INFO_TYPES
    Contact PER_CONTACT_INFO_TYPES

    Important: Oracle applications use a standard 2- or 3-character product prefix followed by an underscore to name the predefined EITs. To avoid current and future naming conflicts, you should adopt a different naming convention for your Extra Information Types; for example CUSTOM_EXPAT_TAXABILITY.

  7. Use the Information Types Security window to set up responsibility level access to EITs.

    See: Setting Up Extra Information Types Against a Responsibility

    Your EIT will now be available anyone using the specified responsibilities. If you want to set up further security using CustomForm and task flow, continue with the next step.

  8. Use the Form Customization window to restrict access to specific EITs within the appropriate windows.

    See: Configuring a Window using CustomForm

  9. Use the Define Task Flow Nodes window to define new nodes for any CustomForm restrictions you have set up.

    See: Defining Task Flow Nodes

  10. Use the Define Task Flow window, or use Oracle Workflow, to define and change task flows to include any new nodes you have set up.

    See: Creating Task Flows Using Forms

    See: Creating Task Flows Using Workflow

Setting Up Extra Information Types for an Organization Classification

To add Extra Information Types (EITs) to an organization classification

  1. Define a new organization classification. You do not need to do this if you are setting up an EIT for a classification that already exists.

    Note: To define a new classification, enter a new value for the Lookup type ORG_CLASS in the Lookup Values window.

  2. Define the new EIT. See: Entering Table Values

    • Unprotect the Org Developer DF using the Register Descriptive Flexfield window. You must do this before you can query the flexfield on the Descriptive Flexfield window

    • Add the new structure for the EIT to the Org Developer DF descriptive flexfield using the Descriptive Flexfield Segments window. The structure must have as its context the name of the extra information type, and as this is a context sensitive descriptive flexfield you must enter C_ORG_INFORMATION_CONTEXT in the Reference Field. Compile in the same way as a standard descriptive flexfield.

    • Reset the protection, so the flexfield remains a protected descriptive flexfield.

  3. You need to enter rows into the following tables:

    • HR_ORG_INFORMATION_TYPES

    • HR_ORG_INFORMATION_TYPES_TL

    Oracle recommends that you write a script to carry out the HR_ORG_INFORMATION_TYPES_PKG.INSERT_ROW procedure to create the rows in the base table and translation table. The procedure uses the following parameters:

    X_ORG_INFORMATION_TYPE ORG_INFORMATION Name of the type (same as DDF context).
    X_DESCRIPTION DESCRIPTION Description of the extra information type.
    X_DISPLAYED_ORG_INFORMATION_TP DISPLAYED_ORG_INFORMATION_TYPE The Name of the Extra Information Type displayed in the Organization window.
    X_NAVIGATION_METHOD NAVIGATION_METHOD "GS" for single row, a user can only enter one extra information row for each organization. Alternatively, "GM" for multi row, a user can enter more than one row for each organization.
    X_LEGISLATION_CODE LEGISLATION_CODE Optionally, you can enter a legislation code to restrict to which business groups the EIT is available. If you do not enter a legislation code it will be valid for all business groups.
    X_DESTINATION DESTINATION This is set to Null.
    X_FND_APPLICATION_ID FND_APPLICATION_ID ID of application.
    X_CREATION_DATE CREATION_DATE Creation date.
    X_CREATED_BY CREATED_BY Created by (user ID).
    X_LAST_UPDATE_DATE LAST_UPDATE_DATE Date of last update.
    X_LAST_UPDATED_BY LAST_UPDATED_BY User ID of last person to update table.
    X_LAST_UPDATE_LOGIN LAST_UPDATE_LOGIN ID for the login session
  4. Specify for which organization classifications this EIT should be available.

    To do this, enter a row into HR_ORG_INFO_TYPES_BY_CLASS as shown in the following table:

    ORG_CLASSIFICATION ORG_CLASS lookup code
    ORG_INFORMATION_TYPE Org extra information type
    MANDATORY_FLAG Y (for Yes) or N (for No)

Setting Up Extra Information Types For a Responsibility

Before a user can access an Extra Information Type (EIT), you must attach the EIT to the user's responsibility. If you do not link your information types to a responsibility, users cannot access your information types.

Note: You can select EITs for any legislation to add to a responsibility in this window. Users of the Oracle HRMS professional user interface are restricted to seeing the information types for the legislation of the business group to which they have access. Self-service users are restricted to seeing information types for the legislation of the record they are working with.

Use the Information Type Security window to link EITs to a responsibility.

Note: If you have created new document types for the Documents of Record function, you also use the Information Type Security window to link these document types to a responsibility.

See: Creating Document Categories, Subcategories, and Types

To set up EITs for a responsibility

  1. Select the name of the responsibility to which to attach the EIT.

    Note: The responsibilities displayed belong to the same application as the responsibility that you have used to display the Information Type Security window, for example, Human Resources. If you want to link an EIT to a responsibility from another application, for example, Advanced Benefits, you must access the Information Type Security window from an Advanced Benefits responsibility. If necessary, add the Information Types Security function to your responsibility.

    Oracle HRMS displays a list of EITs already associated with the responsibility you have chosen.

  2. Enter or select the new EIT you want to link to the responsibility.

  3. Save your work.

To copy EITs between responsibilities

  1. Query the responsibility from which you want to copy.

  2. Select the Copy Responsibility button

  3. Enter the responsibility to which you want to copy.

    This responsibility is then displayed with the new EITs.

  4. Save your work.

Entering Extra Information

The RPA contains a taskflow button that displays Extra Information that's required before you update the RPA to the HR database..

From the RPA you can also taskflow to the Job, Position, Person, and Location forms to enter or change Extra Information that does not accompany the specific personnel action that you're processing, such as a change in position data when processing an appointment.

To enter Extra Information in the RPA

  1. Choose Extra Information.

  2. Choose the Extra Information type that you want to display.

  3. Place your cursor in the Details field and click the mouse field to view or enter Extra Information data.

    The Details field is blank unless you have previously entered data in the flexfield or the system has entered data after updating a Request for Personnel Action.

  4. Enter information in the appropriate segments.

To access Extra Information in the People, and Assignment windows

  1. Choose the Others taskflow button.

  2. Choose Extra Information.

  3. Choose the Extra Information type that you want to display.

  4. Place your cursor in the Details field and click the mouse field to view or enter Extra Information data.

    The Details field is blank unless you have previously entered data in the flexfield or the system has entered data after updating a Request for Personnel Action.

Running the Register Extra Information Types (EITs) Process

Use this process to register any new Extra Information Types (EITs) (excluding Organization EITs).

You run this process from the Submit Requests window.

To run the Register Extra Information Types (EITs) process

  1. In the Name field, select Register Extra Information Types (EITs).

    The Parameters window opens.

  2. In the Table Name field, select the table in which the EIT will be registered.

  3. In the Information Type field, select the extra information type created in the Descriptive Flexfield Segments window. The value in the Table Name field determines which information types are available.

  4. In the Multiple Rows field, specify whether multiple occurrences of the same infotype can exist.

  5. In the Legislation Code field, select the legislation code for the information type. The default value is the legislation code of the current business group.

    Note: If the information type is global, the legislation code value should be Null.

  6. Optionally, enter a description for information type.

  7. Choose the Submit button.

US Federal Information Tables

Assignment Extra Information Types

Key for the Type column in the extra information tables

D: Date

N: Number

X: Varchar or variable character field

Assignment Information Type Name: US Federal Assignment NTE Dates (GHR_US_ASG_NTE_DATES)

Assignment NTE Start Date none D none none
Assignment NTE none D none none
LWOP NTE Start Date none D none none
LWOP NTE none D none none
Suspension NTE Start Date none D none none
Suspension NTE none D none none
Furlough NTE Start Date none D none none
Furlough NTE none D none none
LWP NTE Start Date none D none none
LWP NTE none D none none
Sabbatical NTE Start Date none D none none
Sabbatical NTE none D none none

Assignment Information Type: US Federal Assignment Non-RPA (GHR_US_ASG_NON_SF52)

Date Arrived Personnel Office none D none none
Duty Status GHR_US_DUTY_STATUS X none validate segment with the Lookup type: no values seeded
Furlough Indicator GHR_US_FURLOUGH_IND      
Key Emergency Essential Empl GHR_US_ASGN_KEY_EMERG_ESSEN X none none
Non-Disclosure Agmt Status GHR_US_NON_DISCLOSURE_AGREE X none none
Date WTOP Exemption Expires none D none none
Part-time Indicator GHR_US_PART_TIME_INDICATOR X none none
Qualification Standards Waiver GHR_US_QUAL_STND_WAIVER X none validation: none
Trainee Promotion ID GHR_US_TRAINEE_PROMOTION_ID X none none
Date Trainee Promotion Expect none D none none
Special Employee Code GHR_US_SPCL_EMP_CODE X none none

Assignment Information Type: US Federal Assignment RPA (GHR_US_ASG_SF52)

Step or Rate GHR_US_STEP X R Step-In-Grade-Civ
Tenure GHR_US_TENURE X R none
Annuitant Indicator GHR_US_ANNUITANT INDICATOR X R none
Pay Rate Determinant GHR_US_PAY_RATE_DETERMINANT X R none
Calculation Pay Table GHR_US_PAY_TABLE_ID X none none
Work Schedule GHR_US_WORK_SCHEDULE X R duplicate of Work Schedule in Position Group 1
Part-Time Hours Biweekly GHR_US_PART_TIME_HOURS N none min 0, max 199.99

Assignment Information Type Name: US FEDERAL ASSIGNMENT PROBATIONS GHR_US_ASG_PROBATIONS

Date Initial Probationary Period Begins none D none none
Date Initial Probationary Period Ends none D none none

Assignment Information Type: US Fed Telework Information( GHR_US_FED_TELEWORK_INFO)

Telework Authorized GHR_US_TELEWORK_AUTH X R Default to 1 (Routine)
Telework Ineligibility Reason GHR_US_TELEWORK_INELIG_RSN X D  
Telework Denial Date   D    
Telework Agreement Start Date   D    
Telework Agreement End Date   D    
Telework Agreement Review Date        
Telework Schedule GHR_US_TELEWORK_SCHEDULE X    
Telework Training Complete Dt   D   Default from previous assignment record
Telework Termination Reason GHR_US_TERMINATION_RSN X    
Telework Terminated Date   D    
Telework Disability Accom     R Default to “No”

Location Extra Information Type

Key for the Type column in the extra information tables

D: Date

N: Number

X: Varchar or variable character field

Location Information Type: US Federal Location Information (GHR_US_LOC_INFORMATION)

Duty Station ID * GHR_US_DUTY_STATION_ID N * Duty Station Code/Loc Area/Loc Percent

* Duty Station ID is stored. The application retrieves and displays the Duty Station Code and Description from the GHR_DUTY_STATIONS_F table.

Organization Extra Information Types

The following Value Sets and Lookup Types will be used in the Job and Position Key Flexfields. See the Position Key Flexfield and Job Key Flexfield for additional details.

Key for the Type column in the extra information tables

D: Date

N: Number

Standard Checks

The Standard Checkstyle Checks are applicable to general Java coding style and require no external libraries. The standard checks are included in the base distribution.

The site navigation menu lets you browse the individual checks by functionality.

Checkstyle provides many checks that you can apply to your source code. Below is an alphabetical reference, the site navigation menu provides a reference organized by functionality.

AbbreviationAsWordInNameThe Check validate abbreviations(consecutive capital letters) length in identifier name, it also allow in enforce camel case naming.
AbstractClassName Ensures that the names of abstract classes conforming to some regular expression.
AnnotationLocationCheck location of annotation on language elements.
AnnotationOnSameLineThe check does verifying that annotations are located on the same line with their targets.
AnnotationUseStyleThis check controls the style with the usage of annotations.
AnonInnerLengthChecks for long anonymous inner classes.
ArrayTrailingCommaChecks if array initialization contains optional trailing comma.
ArrayTypeStyleChecks the style of array type definitions.
AtclauseOrderChecks the order of at-clauses.
AvoidEscapedUnicodeCharactersRestrict using Unicode escapes.
AvoidInlineConditionalsDetects inline conditionals.
AvoidNestedBlocksFinds nested blocks.
AvoidStarImportCheck that finds import statements that use the * notation.
AvoidStaticImportCheck that finds static imports.
BooleanExpressionComplexity Restricts nested boolean operators (&&, ||, &, | and ^) to a specified depth (default = 3).
CatchParameterNameChecks that catch parameter names conform to a format specified by the format property.
ClassDataAbstractionCouplingThis metric measures the number of instantiations of other classes within the given class.
ClassFanOutComplexityThe number of other classes a given class relies on.
ClassTypeParameterName Checks that class type parameter names conform to a format specified by the format property.
CommentsIndentationControls the indentation between comments and surrounding code.
ConstantNameChecks that constant names conform to a format specified by the format property.
CovariantEquals Checks that if a class defines a covariant method equals, then it defines method equals(java.lang.Object).
CustomImportOrder Checks that the groups of import declarations appear in the order specified by the user.
CyclomaticComplexityChecks cyclomatic complexity against a specified limit.
DeclarationOrder Checks that the parts of a class or interface declaration appear in the order suggested by the Code Conventions for the Java Programming Language.
DefaultComesLast Check that the is after all the s in a statement.
DescendantTokenChecks for restricted tokens beneath other tokens.
DesignForExtensionChecks that classes are designed for inheritance.
EmptyBlockChecks for empty blocks but does not validate sequential blocks.
EmptyCatchBlockChecks for empty catch blocks with few options to skip violation.
EmptyForInitializerPadChecks the padding of an empty for initializer; that is whether a space is required at an empty for initializer, or such spaces are forbidden.
EmptyForIteratorPadChecks the padding of an empty for iterator; that is whether a space is required at an empty for iterator, or such spaces are forbidden.
EmptyLineSeparatorChecks for blank line separators.
EmptyStatement Detects empty statements (standalone ';').
EqualsAvoidNull Checks that any combination of String literals is on the left side of an equals() comparison.
EqualsHashCode Checks that classes that override equals() also override hashCode().
ExecutableStatementCount Restricts the number of executable statements to a specified limit (default = 30).
ExplicitInitialization Checks if any class or object member explicitly initialized to default for its type value ( for object references, zero for numeric types and and for .
FallThroughChecks for fall through in switch statements Finds locations where a case contains Java code - but lacks a break, return, throw or continue statement.
FileLength Checks for long source files.
FileTabCharacterChecks to see if a file contains a tab character.
FinalClass Checks that class which has only private constructors is declared as final.
FinalLocalVariable Ensures that local variables that never get their values changed, must be declared final.
FinalParametersCheck that method/constructor/catch/foreach parameters are final.
GenericWhitespaceChecks that the whitespace around the Generic tokens < and > are correct to the typical convention.
HeaderChecks the header of the source against a fixed header file.
HiddenFieldChecks that a local variable or a parameter does not shadow a field that is defined in the same class.
HideUtilityClassConstructorMake sure that utility classes (classes that contain only static methods) do not have a public constructor.
IllegalCatchCatching java.lang.Exception, java.lang.Error or java.lang.RuntimeException is almost never acceptable.
IllegalImport Checks for imports from a set of illegal packages.
IllegalInstantiation Checks for illegal instantiations where a factory method is preferred.
IllegalThrowsThrowing java.lang.Error or java.lang.RuntimeException is almost never acceptable.
IllegalToken Checks for illegal tokens.
IllegalTokenText Checks for illegal token text.
IllegalType Checks that particular class are never used as types in variable declarations, return values or parameters.
ImportControlCheck that controls what packages can be imported in each package.
ImportOrderEnsures that groups of imports come in a specific order.
IndentationChecks correct indentation of Java Code.
InnerAssignment Checks for assignments in subexpressions, such as in .
InnerTypeLast Check nested (internal) classes/interfaces are declared at the bottom of the class after all method and field declarations.
InterfaceIsTypeImplements Bloch, Effective Java, Item 17 - Use Interfaces only to define types.
InterfaceTypeParameterName Checks that interface type parameter names conform to a format specified by the format property.
JavadocMethodChecks the Javadoc of a method or constructor.
JavadocPackageChecks that all packages have a package documentation.
JavadocParagraphChecks Javadoc paragraphs.
JavadocStyleCustom Checkstyle Check to validate Javadoc.
JavadocTagContinuationIndentationChecks the indentation of the continuation lines in at-clauses.
JavadocTypeChecks the Javadoc of a type.
JavadocVariableChecks that a variable has Javadoc comment.
JavaNCSSThis check calculates the Non Commenting Source Statements (NCSS) metric for Java source files and methods.
LeftCurly Checks the placement of left curly braces on types, methods and other blocks:
LineLengthChecks for long lines.
LocalFinalVariableName Checks that local final variable names conform to a format specified by the format property.
LocalVariableName Checks that local, non-final variable names conform to a format specified by the format property.
MagicNumber Checks for magic numbers.
MemberName Checks that instance variable names conform to a format specified by the format property.
MethodCountChecks the number of methods declared in each type declaration by access modifier or total count.
MethodLength Checks for long methods.
MethodName Checks that method names conform to a format specified by the format property.
MethodParamPad Checks the padding between the identifier of a method definition, constructor definition, method call, or constructor invocation; and the left parenthesis of the parameter list.
MethodTypeParameterName Checks that class type parameter names conform to a format specified by the format property.
MissingCtor Checks that classes (except abstract one) define a ctor and don't rely on the default one.
MissingDeprecated This class is used to verify that both the java.lang.Deprecated annotation is present and the @deprecated Javadoc tag is present when either is present.
MissingOverride This class is used to verify that the java.lang.Override annotation is present when the {@inheritDoc} javadoc tag is present.
MissingSwitchDefault Checks that switch statement has "default" clause.
ModifiedControlVariableCheck for ensuring that for loop control variables are not modified inside the for block.
ModifierOrder Checks that the order of modifiers conforms to the suggestions in the Java Language specification, sections 8.1.1, 8.3.1 and 8.4.3.
MultipleStringLiteralsChecks for multiple occurrences of the same string literal within a single file.
MultipleVariableDeclarations Checks that each variable declaration is in its own statement and on its own line.
MutableException Ensures that exceptions (defined as any class name conforming to some regular expression) are immutable.
NeedBraces Checks for braces around code blocks.
NestedForDepthRestricts nested blocks to a specified depth (default = 1).
NestedIfDepthRestricts nested if-else blocks to a specified depth (default = 1).
NestedTryDepthRestricts nested try-catch-finally blocks to a specified depth (default = 1).
NewlineAtEndOfFile Checks that there is a newline at the end of each file.
NoClone Checks that the clone method is not overridden from the Object class.
NoFinalizerChecks that no method having zero parameters is defined using the name finalize.
NoLineWrap Checks that chosen statements are not line-wrapped.
NonEmptyAtclauseDescription Checks that the at-clause tag is followed by description .
NoWhitespaceAfter Checks that there is no whitespace after a token.
NoWhitespaceBefore Checks that there is no whitespace before a token.
NPathComplexityChecks the npath complexity against a specified limit (default = 200).
OneStatementPerLineChecks that there is only one statement per line.
OneTopLevelClassChecks that each top-level class, interfaces or enum resides in a source file of its own.
OperatorWrap Checks line wrapping for operators.
OuterTypeFilenameChecks that the outer type name and the file name match.
OuterTypeNumberChecks for the number of defined types at the "outer" level.
OverloadMethodsDeclarationOrderChecks that overload methods are grouped together.
PackageAnnotationThis check makes sure that all package annotations are in the package-info.java file.
PackageDeclarationEnsures there is a package declaration and (optionally) in the correct directory.
PackageName Checks that package names conform to a format specified by the format property.
ParameterAssignment Disallow assignment of parameters.
ParameterName Checks that parameter names conform to a format specified by the format property.
ParameterNumber Checks the number of parameters that a method or constructor has.
ParenPadChecks the padding of parentheses; that is whether a space is required after a left parenthesis and before a right parenthesis, or such spaces are forbidden, with the exception that it does not check for padding of the right parenthesis at an empty for iterator.
RedundantImport Checks for imports that are redundant.
RedundantModifierChecks for redundant modifiers in interface and annotation definitions, final modifier on methods of final classes, inner declarations that are declared as , non public class constructors and enum constructors, nested enum definitions that are declared as .
Regexp A check that makes sure that a specified pattern exists (or not) in the file.
RegexpHeaderChecks the header of the source against a header file that contains a
RegexpMultilineImplementation of a check that looks that matches across multiple lines in any file type.
RegexpOnFilenameImplementation of a check that matches based on file and/or folder path.
RegexpSinglelineImplementation of a check that looks for a single line in any file type.
RegexpSinglelineJavaImplementation of a check that looks for a single line in Java files.
RequireThisChecks that code doesn't rely on the "this" default.
ReturnCount Restricts return statements to a specified count (default = 2).
RightCurly Checks the placement of right curly braces.
SeparatorWrap Checks line wrapping with separators.
SimplifyBooleanExpression Checks for overly complicated boolean expressions.
SimplifyBooleanReturn Checks for overly complicated boolean return statements.
SingleLineJavadoc Checks that a JavaDoc block which can fit on a single line and doesn't contain at-clauses
SingleSpaceSeparator Checks that non-whitespace characters are separated by no more than one whitespace.
StaticVariableName Checks that static, non-final variable names conform to a format specified by the format property.
StringLiteralEqualityChecks that string literals are not used with or .
SummaryJavadoc Checks that Javadoc summary sentence does not contain phrases that are not recommended to use.
SuperClone Checks that an overriding clone() method invokes super.clone().
SuperFinalize Checks that an overriding finalize() method invokes super.finalize().
SuppressWarnings This check allows you to specify what warnings that
ThrowsCount Restricts throws statements to a specified count (default = 4).
TodoComment A check for TODO comments.
TrailingComment The check to ensure that requires that comments be the only thing on a line.
Translation The TranslationCheck class helps to ensure the correct translation of code by checking property files for consistency regarding their keys.
TypecastParenPadChecks the padding of parentheses for typecasts.
TypeName Checks that type names conform to a format specified by the format property.
UncommentedMainDetects uncommented main methods.
UniquePropertiesDetects duplicated keys in properties files.
UnnecessaryParentheses Checks if unnecessary parentheses are used in a statement or expression.
UnusedImports Checks for unused import statements.
UpperEllChecks that long constants are defined with an upper ell.
VariableDeclarationUsageDistanceChecks the distance between declaration of variable and its first usage.
VisibilityModifierChecks visibility of class members.
WhitespaceAfter Checks that a token is followed by whitespace, with the exception that it does not check for whitespace after the semicolon of an empty for iterator.
WhitespaceAround Checks that a token is surrounded by whitespace.
WriteTag Outputs a JavaDoc tag as information.

Holder Checks

These checks aren't normal checks and are usually associated with a specialized filter to gather information the filter can't get on it's own.

SuppressWarningsHolder Maintains a set of check suppressions from annotations.

One thought on “Checkstyle Parameter Assignment Of Rents

Leave a Reply

Your email address will not be published. Required fields are marked *