1. Oracler HRMS
..........................................................................................
Technical Reference Manual
..........................................................................................
..........................................................................................
Release 11i
..........................................................................................
..........................................................................................
..........................................................................................
..........................................................................................
..........................................................................................
..........................................................................................
CAUTION!
..........................................................................................
This document contains proprietary,
..........................................................................................
confidential information that is the exclusive
property of Oracle Corporation.
..........................................................................................
See back cover for
important information.
..........................................................................................
..........................................................................................
..........................................................................................
..........................................................................................
4. Oracler HRMS Technical Reference Manual
Release 11i
To order this book, ask for Part No. A82927–01
Copyright E 1996, 2000. Oracle Corporation. All rights reserved.
Major Contributors: John Woodward, Louise Raffo, Julia Margetson, Andrew Moran, Mark Rowe, Mark Swaine, Kevin Kelley, Keith Ekiss,
Charles Hudson, Michael Laverty, Janet McCandless.
Contributors: Alvin Roussel, Martin Bocutt, Ole Lunddahl, Rohini Panchapakesan, Martin Reid, Sarju Shah, John Thuringer.
This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle Corporation; it is
provided under an Oracle Corporation agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and
other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to
safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or
a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential
Information of third parties such as Oracle Corporation and instructing such employees and agents of these requirements for this TRM; (c)
restricting disclosure of this TRM to those of your employees who have a ”need to know” consistent with the purposes for which this TRM was
disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends
or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or
by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. You should not use this
TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle Corporation products.
The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter,
please report them to us in writing. Oracle Corporation does not warrant that this TRM is error–free. This TRM is provided to customer ”as–is”
with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle’s agreements.
Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this
TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee’s
responsibility to take all appropriate fail–safe, back–up, redundancy and other measures to ensure the safe use of such applications if the
Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs.
Restricted Rights Legend
This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are ’commercial computer software’ and
use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the
applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal
Acquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the TRM and the Programs associated with this
TRM shall be subject to the restrictions in FAR 52.227–14, Rights in Data –– General, including Alternate III (June 1987). Oracle Corporation, 500
Oracle Parkway, Redwood City, CA 94065.
Oracle is a registered trademark, and CASE*Exchange, Enabling the Information Age, Hyper*SQL, NLS*Workbench, Oracle7, Oracle8, Oracle 8i,
Oracle Access, Oracle Application Object Library, Oracle Discoverer, Oracle Financials, Oracle Quality, Oracle Web Customers, Oracle Web
Employees, Oracle Work in Process, Oracle Workflow, PL/SQL, Pro*Ada, Pro*C, Pro*COBOL, Pro*FORTRAN, Pro*Pascal, Pro*PL/I, SmartClient,
SQL*Connect, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, and SQL*Report are trademarks or registered trademarks of Oracle
Corporation. Other names may be trademarks of their respective owners.
5. CAUTION
T his Technical Reference Manual in any form –– software or printed
matter –– contains proprietary, confidential information that is the
exclusive property of Oracle Corporation. If you do not have a valid
contract with Oracle for the use of this Technical Reference Manual or
have not signed a non–disclosure agreement with Oracle covering this
Technical Reference Manual, then you received this document in an
unauthorized manner and are not legally entitled to possess or read it.
Use, duplication, and disclosure are subject to restrictions stated in
your contract with Oracle Corporation.
9. CHAPTER
1 Introduction
T he Oracle HRMS Technical Reference Manual provides the
information you need to understand the underlying structure of Oracle
HRMS. After reading this manual, you should be able to convert your
existing applications data, integrate your existing applications with
your Oracle HRMS application, and write custom reports for your
Oracle HRMS application, as well as read data that you need to
perform other tasks.
This chapter introduces you to the Oracle HRMS Technical Reference
Manual, and explains how to use it.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1–1
10. Introduction
At Oracle, we design and build applications using Oracle Designer, our
systems design technology that provides a complete environment to
support developers through all stages of a systems life cycle. Because
we use a repository–based design toolset, all the information regarding
the underlying structure and processing of our applications is available
to us online. Using Oracle Designer, we can present this information to
you in the form of a technical reference manual.
This Oracle HRMS Technical Reference Manual contains detailed,
up–to–date information about the underlying structure of Oracle
HRMS. As we design and build new releases of Oracle HRMS
applications, we update our Oracle Designer repository to reflect our
enhancements. As a result, we can always provide you with an Oracle
HRMS Technical Reference Manual that contains the latest technical
information as of the publication date. Note that after the publication
date we may have added new indexes to Oracle HRMS to improve
performance.
About this Manual
This manual describes the Oracle Applications Release 11i data model,
as used by Oracle HRMS; it discusses the database we include with a
fresh install of Oracle Applications Release 11i. If you have not yet
upgraded to Release 11, your database may differ from the database we
document in this book.
If you have upgraded from a previous release, you might find it helpful
to use this manual with the appropriate Oracle Applications Product
Update Notes manual. The product update notes list database changes
and seed data changes in Oracle HRMS between releases. The Oracle
Applications Product Update Notes Release 11 manual describes the
changes between release 10.7 and release 11, and the Oracle Applications
Product Update Notes Release 11i manual describes the changes between
release 11 and release 11i.
You can contact your Oracle representative to confirm that you have
the latest technical information for Oracle HRMS. You can also use
OracleMetaLink which is accessible through Oracle’s Support Web
Center ( http://www.oracle.com/support/elec_sup ).
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1–2 Oracle HRMS Technical Reference Manual
11. Finding the Latest Information
The Oracle HRMS Technical Reference Manual contains the latest
information as of the publication date. For the latest information we
encourage you to use OracleMetaLink which is accessible through
Oracle’s Support Web Center ( http://www.oracle.com/support/elec_sup ).
Audience
The Oracle HRMS Technical Reference Manual provides useful guidance
and assistance to:
• Technical End Users
• Consultants
• Systems Analysts
• System Administrators
• Other MIS professionals
This manual assumes that you have a basic understanding of
structured analysis and design, and of relational databases. It also
assumes that you are familiar with Oracle Application Object Library
and your Oracle HRMS application. If you are not familiar with the
above products, we suggest that you attend one or more of the training
classes available through Oracle Education (see: Other Information
Sources: page 1 – 9).
How This Manual is Organized
This manual contains two major sections, High–Level Design and
Detailed Design.
High–Level Design
This section, Chapter 2, contains database diagrams, and lists each
database table and view that Oracle HRMS uses. This chapter also has
a list of modules.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1–3
12. Detailed Design
This section, Chapter 3, contains a detailed description of the Oracle
HRMS database design, including information about each database
table and view you might need for your custom reporting or other data
requirements.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1–4 Oracle HRMS Technical Reference Manual
13. How to Use This Manual
The Oracle HRMS Technical Reference Manual is a single, centralized
source for all the information you need to know about the underlying
structure and processing of your Oracle HRMS application. For
example, you can use this manual when you need to:
• Convert existing application data
• Integrate your Oracle HRMS application with your other
applications systems
• Write custom reports
• Define alerts against Oracle Applications tables
• Configure your Oracle Self–Service Web Applications
• Create views for decision support queries using query tools
• Create business views for Oracle Discoverer
You need not read this manual cover to cover. Use the table of contents
and index to quickly locate the information you need.
Here are several examples of how you might use the Oracle HRMS
Technical Reference Manual:
Example #1
Suppose you are designing a program to load data about people from
your existing human resource system into Oracle Human Resources.
Your first step is to look at the Table List section of Chapter 2 for a table
names resembling People. (Keep in mind that Oracle Human Resource
tables have intuitive names).
Once you locate the right table (PER_ALL_PEOPLE_F), you can refer to
the Table and View Definitions section of Chapter 3 for a detailed
description of the table and its columns. You can examine the column
descriptions to ensure that your custom application references the
correct columns. Then you can look at the Database Diagrams section
in Chapter 2 to identify the tables related to PER_ALL_PEOPLE_F. You
can examine these related table descriptions to ensure that your
application references any other tables holding information relevant to
your application.
Example #2
Suppose you are writing a report to list the elements you have defined
in Oracle Human Resources. You should use the Table List in Chapter
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1–5
14. 2 to locate the table PAY_ELEMENT_TYPES_F. Then you can examine
the column descriptions in the Table and View Definitions section of
Chapter 3 to learn what columns you should display in your report and
how you should display them.
How Not To Use This Manual
Do not use this manual to plan modifications
You should not use this manual to plan modifications to your Oracle
HRMS application. Modifying Oracle HRMS limits your ability to
upgrade to future releases of your Oracle HRMS application. In
addition, it interferes with our ability to give you the high–quality
support you deserve.
We have constructed your Oracle HRMS application so that you can
customize it to fit your needs without programming, and you can
integrate it with your existing applications through interface tables.
However, should you require program modifications, you should
contact our support team (see: Other Information Sources: page 1 – 9).
They can put you in touch with Oracle Services, the professional
consulting organization of Oracle. Their team of experienced
applications professionals can make the modifications you need while
ensuring upward compatibility with future product releases.
Do not write data into non–interface tables
Oracle reserves the right to change the structure of Oracle Applications
tables, and to change the meaning of, add, or delete lookup codes and
data in future releases. Do not write data directly into or change data
in non–interface tables using SQL*Plus or other programming tools
because you risk corrupting your database and interfering with our
ability to support you.
Moreover, this version of the Oracle HRMS Technical Reference Manual
does not contain complete information about the dependencies
between Oracle HRMS applications tables. Therefore, you should write
data into only those tables we identify as interface tables. If you write
data into other non–interface tables, you risk violating your data
integrity since you might not fulfill all the data dependencies in your
Oracle HRMS application.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1–6 Oracle HRMS Technical Reference Manual
15. You are responsible for the support and upgrade of the logic within the
procedures that you write, which may be affected by changes between
releases of Oracle Applications.
Do not rely on upward compatibility of the data model
Oracle reserves the right to change the structure of Oracle HRMS
applications tables, and to change the meaning of, add, or delete
lookup codes and other data in future releases. We do not guarantee
the upward compatibility of the Oracle HRMS applications data model.
For example, if you write a report that identifies concurrent requests
that end in Error status by selecting directly from Oracle Application
Object Library tables, we do not guarantee that your report will work
properly after an upgrade.
About Oracle Application Object Library
The Oracle HRMS Technical Reference Manual may contain references to
tables that belong to Oracle Application Object Library. Oracle
Application Object Library is a collection of pre–built application
components and facilities for building Oracle Applications and
extensions to Oracle Applications. Oracle Application Coding
Standards use the Oracle Application Object Library and contains
shared components including but not limited to –– forms, subroutines,
concurrent programs and reports, database tables and objects,
messages, menus, responsibilities, flexfield definitions and online help.
Attention: Oracle does not support any customization of
Oracle Application Object Library tables or modules, not even
by Oracle consultants. (Oracle Application Object Library
tables generally have names beginning with FND_%.)
Accordingly, this manual does not contain detailed information
about most Oracle Application Object Library tables used by
your Oracle HRMS application.
A Few Words About Terminology
The following list provides you with definitions for terms that we use
throughout this manual:
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1–7
16. Relationship
A relationship describes any significant way in which two tables may
be associated. For example, rows in the Journal Headers table may
have a one–to–many relationship with rows in the Journal Lines table.
Database Diagram
A database diagram is a graphic representation of application tables
and the relationships between them.
Summary Database Diagram
A summary database diagram shows the most important application
tables and the relationships between them. It omits tables and
relationships that contribute little to the understanding of the
application data model. Typically, a summary database diagram shows
tables that contain key reference and transaction data.
Module
A module is a program or procedure that implements one or more
business functions, or parts of a business function, within an
application. Modules include forms, concurrent programs and reports,
and subroutines.
Application Building Block
An application building block is a set of tables and modules (forms,
reports, and concurrent programs) that implement closely–related
database objects and their associated processing. Said another way, an
application building block is a logical unit of an application.
Lookups
Lookups, formerly known as QuickCodes, let you define general
purpose, static lists of values for window fields. Lookups allow you to
base your program logic on lookup codes while displaying
user–friendly names in a list of values window. Lookups simplify
name and language changes by letting you change the names your end
users see, while the codes in your underlying programs remain the
same.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1–8 Oracle HRMS Technical Reference Manual
17. Form
A form is a module comprised of closely related windows that are used
together to perform a task. For example, the Enter Journals form in
Oracle General Ledger includes the Enter Journals window, the Batch
window, and the More Actions window among others. The Enter
Journals window is the main window, and from it, you can use buttons
to navigate to other windows in the form. The form name usually
corresponds to the main window in the form, and is frequently a
window you open directly from the Navigator.
Other Information Sources
There are additional information sources, including other
documentation, training and support services, that you can use to
increase your knowledge and understanding of Oracle Designer, Oracle
Application Object Library, and your Oracle HRMS application. We
want to make these products easy for you and your staff to understand
and use.
Oracle Designer Online Documentation
The online help for Oracle Designer describes how you can use Oracle
Designer for your development needs.
Oracle Applications Developer’s Guide
This guide contains the coding standards followed by the Oracle
Applications development staff. It describes the Oracle Application
Object Library components needed to implement the Oracle
Applications user interface described in the Oracle Applications User
Interface Standards. It also provides information to help you build your
custom Developer forms so that they integrate with Oracle
Applications.
Oracle Applications User Interface Standards
This manual contains the user interface (UI) standards followed by the
Oracle Applications development staff. It describes the UI for the
Oracle Applications products and how to apply this UI to the design of
an application built using Oracle Forms 6.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1–9
18. Oracle HRMS applications User Guide
Your user guide provides you with all the information you need to use
your Release 11i Oracle HRMS application. Each user guide is
organized for fast, easy access to detailed information in a function–
and task–oriented organization.
Oracle Self–Service Web Applications Online Documentation
This documentation describes how Oracle Self–Service Web
Applications enable companies to provide a self–service and secure
Web interface for employees, customers, and suppliers. Employees can
change their personal status, submit expense reports, or request
supplies. Customers can check on their orders, and suppliers can share
production schedules with their trading partners. This documentation
is available in HTML only.
Oracle Applications Flexfields Guide
This guide provides flexfields planning, setup and reference
information for the Oracle HRMS implementation team, as well as for
users responsible for the ongoing maintenance of Oracle Applications
product data. This manual also provides information on creating
custom reports on flexfields data.
Oracle Workflow Guide
This manual explains how to define new workflow business processes
as well as customize existing Oracle Applications–embedded workflow
processes. You also use this guide to complete the setup steps
necessary for any Oracle Applications product that includes
workflow–enabled processes.
Oracle Alert User Guide
This manual explains how to define periodic and event alerts to
monitor the status of your Oracle Applications data.
Multiple Reporting Currencies in Oracle Applications
If you use the Multiple Reporting Currencies feature to report and
maintain accounting records in more than one currency, use this
manual before implementing Oracle HRMS. This manual details
additional steps and setup considerations for implementing Oracle
HRMS with this feature.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1 – 10 Oracle HRMS Technical Reference Manual
19. Multiple Organizations in Oracle Applications
If you use the Oracle Applications Multiple Organization Support
feature to use multiple sets of books for one Oracle HRMS installation,
use this guide to learn about setting up and using Oracle HRMS with
this feature. This book describes the Oracle Applications organization
model, which defines business units and the relationships between
them in an arbitrarily complex enterprise. Functional and technical
overviews of multiple organizations are presented, as well as
information about how to set up and implement this feature set in the
relevant Oracle Applications products.
Oracle Manufacturing, Distribution, Sales and Service Open
Interfaces Manual
This manual contains up–to–date information about integrating with
other Oracle Manufacturing applications and with your other systems.
This documentation includes open interfaces found in Oracle
Manufacturing.
Oracle Applications Messages Manual
The Oracle Applications Messages Manual contains the text of
numbered error messages in Oracle Applications. (Oracle Applications
messages begin with the prefix ”APP–”.) It also provides information
on the actions you take if you get a message. Note: This manual is
available only in HTML format.
Installation and System Administration
Oracle Applications Installation Release Notes
This manual contains a road map to the components of the release,
including instructions about where to access the Release 11i
documentation set.
Oracle Applications Concepts
Designed to be the first book the user reads to prepare for an
installation of Oracle Applications. It explains the technology stack,
architecture, features and terminology for Oracle Applications Release
11i. This book also introduces the concepts behind and major uses of
Applications–wide features such as MRC, BIS, languages and character
sets (NLS, MLS), BIS, Self–Service Web Applications and so on.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1 – 11
20. Installing Oracle Applications
Describes the One–Hour Install process, the method by which Release
11i will be installed. This manual includes all how–to steps, screen
shots and information about Applications–wide post–install tasks.
Using the AD Utilities
This manual contains how–to steps, screen shots and other information
required to run the various AD utilities such as AutoInstall, AutoPatch,
AD Administration, AD Controller, Relink and so on. It also contains
information about when and why you should use these utilities.
Upgrading Oracle Applications
This manual contains all the product specific pre and post–upgrade
steps that are required to upgrade products from Release 10.7 (NCA,
SC and character–mode) or Release 11 of Oracle Applications. This
manual also contains an overview chapter that describes all the tasks
necessary to prepare and complete a upgrade of Oracle Applications.
Oracle Applications System Administrator’s Guide
This manual provides planning and reference information for the
Oracle Applications System Administrator. It contains information on
how to define security, customize menus and manage concurrent
processing.
Oracle Applications Product Update Notes
This book contains a summary of each new feature we added since
Release 11, as well as information about database changes and seed
data changes that may affect your operations or any custom reports
you have written. If you are upgrading from Release 10.7 you also
need to read Oracle Applications Product Update Notes Release 11.
Oracle Self–Service Web Applications Implementation Manual
This manual describes the setup steps for Oracle Self–Service Web
Applications and the Web Applications Dictionary.
Oracle Human Resources Implementation Manual
This manual contains up–to–date information about new Oracle HRMS
applications features and guides you step–by–step through setting up
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1 – 12 Oracle HRMS Technical Reference Manual
21. and integrating your Oracle HRMS application. The Oracle Human
Resources Implementation Manual helps you use your Oracle HRMS
application to its fullest.
Oracle Applications Implementation Wizard User Guide
If you are implementing more than one Oracle product, you can use the
Oracle Applications Implementation Wizard to coordinate your setup
activities. This guide describes how to use the wizard.
Other Information
Training
Oracle Education offers a complete set of training courses to help you
and your staff master Oracle Applications. We can help you develop a
training plan that provides thorough training for both your project
team and your end users. We will work with you to organize courses
appropriate to your job or area of responsibility.
Training professionals can show you how to plan your training
throughout the implementation process so that the right amount of
information is delivered to key people when they need it the most. You
can attend courses at any one of our many Educational Centers, or you
can arrange for our trainers to teach at your facility. In addition, we
can tailor standard courses or develop custom courses to meet your
needs.
Support
From on–site support to central support, our team of experienced
professionals provides the help and information you need to keep your
Oracle HRMS application working for you. This team includes your
Technical Representative, Account Manager, and Oracle’s large staff of
consultants and support specialists with expertise in your business
area, managing an Oracle server, and your hardware and software
environment.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Introduction 1 – 13
22. About Oracle
Oracle Corporation develops and markets an integrated line of
software products for database management, applications
development, decision support and office automation, as well as Oracle
Applications. Oracle Applications provides the E–Business Suite, a
fully integrated suite of more than 70 software modules for financial
management, internet procurement, business intelligence, supply chain
management, manufacturing, project systems, human resources and
sales and service management.
Oracle products are available for mainframes, minicomputers, personal
computers, network computers, and personal digital assistants,
enabling organizations to integrate different computers, different
operating systems, different networks, and even different database
management systems, into a single, unified computing and information
resource.
Oracle is the world’s leading supplier of software for information
management, and the world’s second largest software company. Oracle
offers its database, tools, and application products, along with related
consulting, education and support services, in over 145 countries
around the world.
Thank You
Thanks for using Oracle HRMS applications and this technical
reference manual!
We appreciate your comments and feedback. At the beginning of this
manual is a Reader’s Comment Form that you can use to explain what
you like or dislike about your Oracle HRMS application or this
technical reference manual. Mail your comments to the following
address or call us directly at (650) 506–7000.
Oracle Applications Documentation Manager
Oracle Corporation
500 Oracle Parkway
Redwood Shores, California 94065
U.S.A.
Or, send electronic mail to appsdoc@us.oracle.com.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
1 – 14 Oracle HRMS Technical Reference Manual
23. CHAPTER
2 High–Level Design
T his chapter presents a high–level design for Oracle HRMS that
satisfies the business needs we specify during Strategy and Analysis. It
contains database diagrams for Oracle HRMS application building
blocks, lists of database tables and views, and a list of modules.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–1
24. Overview of High–Level Design
During High–Level Design, we define the application components
(tables, views, and modules) we need to build our application. We
specify what application components should do without specifying the
details of how they should do it.
You can refer to this High–Level Design chapter to quickly acquaint
yourself with the tables, views, and modules that comprise Oracle
HRMS applications. And, you can prepare yourself to understand the
detailed design and implementation of Oracle HRMS.
Summary Database Diagram
The Summary Database Diagram section graphically represents the
most important application tables and the relationships between them.
It omits tables and relationships that contribute little to the
understanding of the application data model. Typically, a summary
database diagram shows tables that contain key reference and
transaction data.
We prepare a summary database diagram to describe, at a conceptual
level, the key information on which our business depends. Later, we
refine this summary database diagram, breaking it into multiple
database diagrams (generally, one per application building block) to
represent all the tables and relationships we need to implement our
application in the database.
Review the Summary Database Diagram section to see at a glance the
major tables and relationships on which your Oracle HRMS application
depends.
Database Diagrams
The Database Diagrams section graphically represents all Oracle HRMS
applications tables and the relationships between them, organized by
building block.
Use this section to quickly learn what tables each Oracle HRMS
application building block uses, and how those tables interrelate. Then,
you can refer to the Table and View Definitions sections of Chapter 3
for more detailed information about each of those tables.
Table Lists
The Table List sections list the Oracle HRMS applications tables.
Because a product might not include at least one table for each type,
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–2 Oracle HRMS Technical Reference Manual
25. this Technical Reference Manual might not include each of the
following sections.
Public Tables
Use the Public Table List section to quickly identify the tables you are
most interested in. Then, you can refer to the Table and View
Definitions sections of Chapter 3 for more detailed information about
those tables.
In addition, this manual may contain full documentation for one or
more of the following Application Object Library tables: FND_DUAL,
FND_CURRENCIES, and FND_COMMON_LOOKUPS.
Internal Tables
This section includes a list of private, internal tables used by Oracle
HRMS; we do not provide additional documentation for these tables.
View Lists
The View List sections list the Oracle HRMS views, with one section for
each type of view. Because a product might not include at least one
view for each type, this Technical Reference Manual might not include
each of the following sections.
Use this section to quickly identify the views you are most interested
in. Then, you can refer to the Table and View Definitions sections of
Chapter 3 for more detailed information about those views.
Public Views
This section lists views that may be useful for your custom reporting or
other data requirements. The list includes a description of the view,
and the page in Chapter 3 that gives detailed information about the
public view.
Web Views
This section lists views that you may need to configure your
Self–Service Web applications. The list includes a description of the
view, and the page in Chapter 3 that gives detailed information about
the web view.
Forms and Table Views
This section lists supplementary views that are not essential to the
Release 11i data model, but simplify coding or improve performance
for Oracle Developer.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–3
26. Internal Views
This section includes each private, internal view that Oracle HRMS
uses.
Single–Organization Views
This section lists the Oracle HRMS views that we added to take the
place of various tables that are now partitioned by operating unit, to
support multiple sets of books within a single installation of Oracle
HRMS.
Multiple Reporting Currency Views
This list includes views that were created to support the Multiple
Reporting Currencies feature.
MultiLingual Views
This section lists views that were created to allow certain seed data to
be available in multiple national languages simultaneously.
Module List
The Module List section briefly describes each of the Oracle HRMS
applications modules. This section lists forms, reports, and concurrent
programs.
A form is a module comprised of closely related windows that are used
together to perform a task. For example, the Enter Journals form in
Oracle General Ledger includes the Enter Journals window, the Batch
window, and the More Actions window. The Enter Journals window is
the main window, and from it, you can use buttons to navigate to other
windows in the form. The form name usually corresponds to the main
window in the form, and is frequently a window you can open directly
from the Navigator.
The Reports and Concurrent Programs lists include processes you can
submit from the Submit Requests window or other windows, as well as
processes that are submitted automatically by Oracle HRMS. Use your
user’s guide to learn more about reports and concurrent processes.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–4 Oracle HRMS Technical Reference Manual
27. Summary Database Diagram
Summary Database Diagrams are included for Oracle Government
Human Resources and Oracle Statutory Sickness Pay/Statutory
Maternity Pay.
Summary Database Diagrams graphically represent the most important
tables and the relationships between them. They describe at a
conceptual level, the key information on which your application
depends.
These diagrams show tables that contain key reference and transaction
data, and omit tables and relationships that contribute little to the
understanding of the data model. For example, a foreign key
relationship shown between two tables may actually be implemented
by an intervening table, not shown in these diagrams.
For more detailed graphical representations of Oracle HRMS
applications tables and the relationships between them, see the
Database Diagrams section in this chapter.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–5
28. Database Diagramming Conventions
We use the following notational conventions in our database diagrams:
Figure 2 – 1
Database Diagram
Conventions Server Model Diagram Elements and Notation Recursive foreign key
(Pig's Ear)
Title Bar
Column/attribute
details section
Relational Table
Foreign key
constraint Arc
EMP
Delete rule indicator
Primary key column (#*) # * EMPNO
Mandatory column (*) * DEPTNO
DEPT
Values in the foreign key # * DEPTNO
must match the primary key
* DNAME
Mandatory and Optional Foreign Keys
A Value entered in the column in the foreign key
must match a value in the primary key column.
A Value entered in the column in the foreign key
must match either a value in the primary key column,
or else it must ne null.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–6 Oracle HRMS Technical Reference Manual
29. Tables – are the basic unit of storage in the database. A hand symbol
preceding the title in the table’s title bar indicates that the table is not
owned by this application but shared with another.
Foreign key constraint – is a type of referential integrity constraint for
checking the integrity of data entered in a specific column or set of
columns. This specified column or set of columns is known as the
foreign key.
Delete rule indicator – determines the action to be taken when an
attempt is made to delete a related row in a join table. A line through
the foreign key constraint, as shown on the above diagram, indicates
that this action is restricted.
Arcs – specify that, for any given row in a table, a value must be
entered in one of the arc columns. The remaining columns within the
arc must be null.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–7
30. Database Diagrams
This section graphically represents all Oracle HRMS applications tables
and the relationships between them, organized by building block. Use
this section to quickly learn what tables each Oracle HRMS application
building block uses, and how these tables interrelate. Then, you can
refer to the Table and View Definitions sections of Chapter 3 for more
detailed information about each of those tables.
This section contains a database diagram for each of the following
Oracle HRMS application building blocks:
• Diagram 1: Absences
• Diagram 2: Assignment Set Criteria
• Diagram 3: Career
• Diagram 4: Contracts
• Diagram 5: Core Payroll
• Diagram 6: Costing
• Diagram 7: DateTrack
• Diagram 8: Elements
• Diagram 9: Element Templates
• Diagram 10: Employee
• Diagram 11: FastFormulas
• Diagram 12: Grades
• Diagram 13: Organization
• Diagram 14: Payroll Process Actions
• Diagram 15: Payments
• Diagram 16: Recruitment
• Diagram 17: Taskflow
• Diagram 18: US Geocodes
• Diagram 19 : US State Tax Information
• Diagram 20: US Wage Attachments
• Diagram 21: US Workers Compensation
Some tables, especially important reference tables, appear in more than
one database diagram. When several building blocks use a table, we
show that table in each appropriate database diagram.
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–8 Oracle HRMS Technical Reference Manual
31. There are also the following Summary Database Diagrams:
• Diagram 22: Oracle Government Human Resources Summary
Database Diagram
• Diagram 23: Oracle Statutory Sickness Pay/Statutory
Maternity Pay Summary Database Diagram
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–9
55. Public Table List
This section lists each public database table used by Oracle Human
Resources, Oracle Self Service Human Resources, Oracle Government
Human Resources, Oracle Payroll and Oracle Statutory Sickness
Pay/Statutory Maternity Pay. The section also provides a brief
description of each of those tables. The page reference is to the table
description in Chapter 3.
Note that ”public” tables are not necessarily intended for write access
by custom code; Oracle Corporation supports write access using only
standard Oracle Applications forms, reports, and programs, or any
SQL write access to tables explicitly documented as API tables. For
more information, see the How Not To Use This Manual section of this
book’s Introduction.
The applications listed above use the following Public tables:
Table Name Description
BEN_BENEFICIARIES_F List of the beneficiaries of a specific benefit program. (See
page 3–8)
BEN_BENEFIT_CLASSIFICATIONS Classification for a particular benefit, eg pension, health,
life insurance, flex plan. (See page 3–9)
BEN_BENEFIT_CONTRIBUTIONS_F Default contributions payable for cover by a specific
benefit. (See page 3–11)
BEN_COVERED_DEPENDENTS_F Dependents covered by specific benefit plans. (See page
3–13)
BEN_VALID_DEPENDENT_TYPES Types of dependent relationship that are valid for cover by
a specific benefit. (See page 3–14)
DT_COLUMN_PROMPTS Default prompts for columns in DateTrack History views.
(See page 3–15)
DT_COLUMN_PROMPTS_TL Default prompts for columns in DateTrack History views.
(See page 3–16)
DT_DATE_PROMPTS Obsolete in Release 11i. (See page 3–17)
DT_DATE_PROMPTS_TL Default prompts for effective start date and end date
columns in DateTrack History views. (See page 3–18)
DT_TITLE_PROMPTS Default window titles for DateTrack History views. (See
page 3–19)
DT_TITLE_PROMPTS_TL Default window titles for DateTrack History views. (See
page 3–20)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–33
56. FF_ARCHIVE_ITEMS Archive recording results of evaluating database items.
(See page 3–21)
FF_ARCHIVE_ITEM_CONTEXTS Context values for retrieving FF_ARCHIVE_ITEMS. (See
page 3–22)
FF_COMPILED_INFO_F Compiled versions of user–defined formulas. (See page
3–23)
FF_CONTEXTS Identifies the context for specific formulas, for example
EMPLOYEE_ID. (See page 3–24)
FF_DATABASE_ITEMS Basic items of data in the application database. (See page
3–26)
FF_FDI_USAGES_F Compiler generated description of data items used in a
formula. (See page 3–28)
FF_FORMULAS_F Formula definitions and text. (See page 3–29)
FF_FORMULA_TYPES Used to define groups of formulas to associate with
formula contexts. (See page 3–31)
FF_FTYPE_CONTEXT_USAGES Contexts for a specific formula type. (See page 3–32)
FF_FUNCTIONS FastFormula Function definitions. (See page 3–33)
FF_FUNCTION_CONTEXT_USAGES Contexts required by a function. (See page 3–35)
FF_FUNCTION_PARAMETERS Definitions of parameters for a specific FastFormula
function. (See page 3–36)
FF_GLOBALS_F Global Values and data types. (See page 3–37)
FF_LOOKUPS Lookups used specifically for FastFormula. (See page 3–39)
FF_QP_REPORTS QuickPaint report definitions. (See page 3–40)
FF_ROUTES FROM and WHERE clauses of a SQL statement for a
specific database item. (See page 3–41)
FF_ROUTE_CONTEXT_USAGES A single usage of a context as a bind variable in the ROUTE
sql statement. (See page 3–42)
FF_ROUTE_PARAMETERS Parameters that can be passed to a ROUTE to restrict the
number of rows returned by the ROUTE. (See page 3–43)
FF_ROUTE_PARAMETER_VALUES Values provided for route parameters by a database item.
(See page 3–45)
FF_USER_ENTITIES Table and selection criteria combination used to define
database items. (See page 3–46)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–34 Oracle HRMS Technical Reference Manual
57. FND_APPLICATION No table description
FND_COMPILED_ID_FLEX_STRUCTS No table description
FND_CURRENCIES No table description
FND_DATA_GROUP_UNITS No table description
FND_DESCR_FLEX_CONTEXTS No table description
FND_FORM No table description
FND_ID_FLEX_STRUCTURES No table description
FND_PRODUCT_DEPENDENCIES No table description
FND_PRODUCT_INSTALLATIONS No table description
FND_RESPONSIBILITY No table description
FND_SESSIONS No table description
FND_TERRITORIES No table description
GHR_BREAKDOWN_CRITERIA Holds the criteria used to run the breakdown report. (See
page 3–48)
GHR_BREAKDOWN_RESULTS A temporary table used to produce the breakdown report
(See page 3–49)
GHR_COMPLAINTS Holds information for processing a complaint. (See page
3–50)
GHR_COMPLAINT_ACTIONS Holds the actions for a complaint. (See page 3–54)
GHR_COMPLAINT_BASES Holds the bases for a complaint issue. (See page 3–55)
GHR_COMPLAINT_COSTS Holds the costs involved in the complaint. (See page 3–56)
GHR_COMPLAINT_ISSUES Holds the issues that are pertaining to a given (See page
3–57)
GHR_COMPLAINT_PEOPLE Holds the complainants who are involved in the complaint
action. (See page 3–59)
GHR_CPDF_TEMP Temporarily stores information required to generate
various CPDF reports. (See page 3–60)
GHR_DUAL_ACTIONS Stores First NOAs and all its associated second NOAs that
can be processed in a dual action. (See page 3–62)
GHR_DUAL_PROC_METHODS Stores the process method for the first and the second
NOA codes. (See page 3–63)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–35
58. GHR_DUTY_STATIONS_F This table holds information about duty stations. (See page
3–64)
GHR_EVENTS This table stores various events. (See page 3–65)
GHR_EVENT_HISTORY It stores various events happening during RPA process
and definition of Position. (See page 3–66)
GHR_FAMILIES Holds information about a family. (See page 3–67)
GHR_GROUPBOXES Groupboxes defined to be used by workflow (See page
3–68)
GHR_GROUPBOX_USERS Defines the members of the Groupbox (See page 3–69)
GHR_INTERFACE This is a general purpose table for various interfaces with
Federal HR system. (See page 3–70)
GHR_LOCALITY_PAY_AREAS_F This table stores information about locality pay areas. (See
page 3–76)
GHR_MASS_ACTIONS_PREVIEW This table is used to show the Employee/Position detail to
the user based on the selection criteria (See page 3–77)
GHR_MASS_AWARDS Used to store the details of the Mass Award (See page 3–80)
GHR_MASS_AWARD_CRITERIA_COLS Used to store the Selection Criteria items used in Mass
Awards (See page 3–81)
GHR_MASS_AWARD_CRITERIA_VALS Used to store the values for the selection criteria in the
Mass Awards (See page 3–82)
GHR_MASS_REALIGNMENT This table is used to store criteria for mass realignment.
(See page 3–83)
GHR_MASS_SALARIES This table stores the criteria and status for mass salary
action. (See page 3–85)
GHR_MASS_SALARY_CRITERIA This table stores the additional criteria for a mass salary
action. (See page 3–86)
GHR_MASS_TRANSFERS This table stores the additional criteria for a mass transfer
action. (See page 3–87)
GHR_MASS_TRANSFER_CRITERIA This table stores the additional criteria for a mass transfer
action. (See page 3–88)
GHR_NATURE_OF_ACTIONS This table holds a list of nature of action codes. (See page
3–89)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–36 Oracle HRMS Technical Reference Manual
59. GHR_NOAC_LAS Stores NOA and the associated Legal Authorities (See page
3–90)
GHR_NOAC_REMARKS Stores NOA and the associated Remarks (See page 3–91)
GHR_NOA_FAMILIES Stores Families and associated NOAs (See page 3–92)
GHR_NOA_FAM_PROC_METHODS This table is intersection between families and personnel
actions. (See page 3–93)
GHR_PAYROLL This table is used by payroll interface to get data for
SF113A report. (See page 3–94)
GHR_PAY_PLANS Defines the Pay Plans (See page 3–95)
GHR_PAY_PLAN_WAITING_PERIODS Defines the waiting period of the Pay Plans (See page 3–96)
GHR_PA_DATA_FIELDS This table holds the fields that are available on the request
for personnel action form and the extra information. (See
page 3–97)
GHR_PA_HISTORY Stores the history of all the transactions performed on
certain tables. (See page 3–98)
GHR_PA_REMARKS Stores Remark codes for the Personnel Action (See page
3–106)
GHR_PA_REQUESTS Stores all the information about the Request to Personnel
Action. (See page 3–107)
GHR_PA_REQUEST_EI_SHADOW Stores all the columns of the corresponding record of
GHR_PA_REQUEST_EXTRA_INFO. (See page 3–114)
GHR_PA_REQUEST_EXTRA_INFO Stores additional information based on information types.
(See page 3–116)
GHR_PA_REQUEST_INFO_TYPES Defines information types to be used in Extra Information.
(See page 3–119)
GHR_PA_REQUEST_SHADOW Stores all the columns of the corresponding record of
GHR_PA_REQUESTS. (See page 3–120)
GHR_PA_ROUTING_HISTORY Routing History details of the PA Request (See page 3–122)
GHR_PD_CLASSIFICATIONS Classification details of a Position Description. (See page
3–124)
GHR_PD_ROUTING_HISTORY Routing History details of Position Description (See page
3–125)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–37
60. GHR_POIS Contains information related to Personnel Office Identifier
(See page 3–127)
GHR_POSITION_DESCRIPTIONS Federal Position Description details (See page 3–128)
GHR_PREMIUM_PAY_INDICATORS It holds a list of premium pay indicators. (See page 3–130)
GHR_PROCESS_LOG It contains log information about various batch process.
(See page 3–131)
GHR_REMARKS It holds a list of remarks that are used to enter against a
request for personnel action. (See page 3–132)
GHR_RESTRICTED_PROC_METHODS It is intersection between a restricted form and personnel
action data fields (See page 3–133)
GHR_RIF_CRITERIA It holds the criteria used to retrieve people to produce a
reduction in force (RIF) register. (See page 3–134)
GHR_RIF_REGISTERS It is a temporary table used to list the people who match
the criteria. (See page 3–135)
GHR_ROUTING_GROUPS Routing Group information (See page 3–137)
GHR_ROUTING_LISTS Routing List details (See page 3–138)
GHR_ROUTING_LIST_MEMBERS Routing List members detail (See page 3–139)
GHR_S_FND_COMMON_LOOKUPS Temporary tables used to seed GHR data to
FND_COMMON_LOOKUPS (See page 3–140)
GHR_S_FND_COMMON_LOOKUP_TYPES Temporary tables used to seed GHR data to
FND_COMMON_LOOKUP_TYPES (See page 3–141)
HR_ALL_ORGANIZATION_UNITS Organization unit definitions. (See page 3–142)
HR_ALL_ORGANIZATION_UNITS_TL Translated organization unit name definitions. (See page
3–144)
HR_ALL_POSITIONS_F Position definition information. (See page 3–145)
HR_API_BATCH_MESSAGE_LINES Results and messages generated during batch API
processing. (See page 3–150)
HR_API_HOOKS Lists the hook points which are available in each API
module. (See page 3–151)
HR_API_HOOK_CALLS Lists which extra logic, package procedures or formula,
should be called from the API hook points. (See page
3–153)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–38 Oracle HRMS Technical Reference Manual
61. HR_API_MODULES Holds details of the business processes and row handlers.
(See page 3–155)
HR_API_TRANSACTIONS Kiosk processes in progress (See page 3–156)
HR_API_TRANSACTION_STEPS Kiosk workflow data rows (See page 3–157)
HR_API_TRANSACTION_VALUES Kiosk workflow data columns and values (See page 3–158)
HR_API_USER_HOOK_REPORTS Used to hold HR_API_USER_HOOK error information if
this exists otherwise no information is held. (See page
3–159)
HR_APPLICATION_OWNERSHIPS Primary keys for entities which enable identification of
products that use each piece of startup data. (See page
3–160)
HR_ASSIGNMENT_SETS Formula definitions that identify sets of assignments. (See
page 3–161)
HR_ASSIGNMENT_SET_AMENDMENTS Identifies explicit include and exclude rules for an
assignment set. (See page 3–162)
HR_ASSIGNMENT_SET_CRITERIA Identifies individual criteria in the definition of an
assignment set. (See page 3–163)
HR_AUDITS Main audit table that records the transactions carried out
on an audited table from its shadow table. (See page 3–165)
HR_AUDIT_COLUMNS Column changes for specific audit transactions. (See page
3–166)
HR_CALENDARS Dated instances of a repeating pattern. (See page 3–167)
HR_CALENDAR_USAGES Assignments of calendars to individual entities. (See page
3–168)
HR_COMMENTS Central repository for comments. (See page 3–170)
HR_EXCEPTION_USAGES Identifies usage of defined exceptions to a repeating
pattern. (See page 3–171)
HR_INCOMPATIBILITY_RULES Incompatibility rules for navigation units. (See page 3–172)
HR_JP_PARAMETERS This table holds unique id for Japanese legislative specific
data in order not to hard–code Multibyte characters in
Japanese localization code objects. (See page 3–173)
HR_LEGISLATION_INSTALLATIONS Status of each product/legislation combination installed
(See page 3–175)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–39
62. HR_LEGISLATION_SUBGROUPS Subgroups in a legislation, such as individual states in the
USA. (See page 3–176)
HR_LOCATIONS_ALL Work location definitions. (See page 3–177)
HR_LOCATIONS_ALL_TL Translated location codes and descriptions. (See page
3–180)
HR_LOCATION_EXTRA_INFO Extra information for a location. (See page 3–181)
HR_LOCATION_INFO_TYPES Types of extra information that may be held against a
Location. (See page 3–184)
HR_NAVIGATION_CONTEXT_RULES Context specific rules for taskflow navigation. (See page
3–185)
HR_NAVIGATION_NODES Taskflow node definitions. (See page 3–186)
HR_NAVIGATION_NODE_USAGES Intersection table between HR_WORKFLOWS,
HR_NAVIGATION_NODES and
HR_NAVIGATION_PATHS. (See page 3–187)
HR_NAVIGATION_PATHS Taskflow navigation path details. (See page 3–188)
HR_NAVIGATION_UNITS Information about potential navigation options in a
taskflow. (See page 3–189)
HR_NAV_UNIT_GLOBAL_USAGES Global variable usage by specific navigation unit. (Form or
block). (See page 3–190)
HR_ORGANIZATION_INFORMATION Additional attributes of an organization, dependent on
class or organization information type. (See page 3–192)
HR_ORG_INFORMATION_TYPES Information types that are used to add information for an
organization. (See page 3–195)
HR_ORG_INFO_TYPES_BY_CLASS Defines organization information types for specific
organization classifications. (See page 3–196)
HR_PATTERNS A repeating time pattern, eg a work pattern, SSP qualifying
pattern or a resource schedule. (See page 3–197)
HR_PATTERN_BITS A defined period of time used to construct a pattern. (See
page 3–198)
HR_PATTERN_CONSTRUCTIONS Decomposition of a repeating pattern into its individual
’bits’ of time. (See page 3–199)
HR_PATTERN_EXCEPTIONS An exception to a repeating pattern. (See page 3–201)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–40 Oracle HRMS Technical Reference Manual
63. HR_PATTERN_PURPOSES Potential purpose for the parent pattern, eg ’Work Pattern’,
’Resource schedule’, etc. (See page 3–203)
HR_PATTERN_PURPOSE_USAGES Valid combinations of entities and pattern purposes. (See
page 3–204)
HR_PUMP_BATCH_EXCEPTIONS Holds data pump processing exception (error) information.
(See page 3–212)
HR_PUMP_BATCH_HEADERS Stores information on a batch to be loaded by the data
pump. (See page 3–213)
HR_PUMP_BATCH_LINES Each rows stores the information required to make an API
call. OUT–parameter values are written back after the API
call. (See page 3–214)
HR_PUMP_BATCH_LINE_USER_KEYS User keys and their associated information is stored here
on the creation of entities that require user keys. (See page
3–219)
HR_PUMP_DEFAULT_EXCEPTIONS Lists API modules that do not conform to the API
parameter defaulting rules. (See page 3–220)
HR_PUMP_MAPPING_PACKAGES Lists PL/SQL packages that contain the parameter
mapping functions used by data pump generated code. If
module_package and module_name are both null then the
mapping functions may be used by all APIs. (See page
3–221)
HR_PUMP_MODULE_PARAMETERS Holds seeded information about API parameters for data
pump code generation. (See page 3–222)
HR_PUMP_RANGES Controls the parallelisation of the work when the data
pump is running on multiprocessor platforms. (See page
3–223)
HR_PUMP_REQUESTS Holds information on data pump concurrent requests
currently running. (See page 3–224)
HR_QUESTIONNAIRES Questionnaires used within SSHR. (See page 3–225)
HR_QUEST_ANSWERS Answers for a questionnaire. (See page 3–226)
HR_QUEST_ANSWER_VALUES Answer values for a questionnaire. (See page 3–227)
HR_QUEST_FIELDS Fields of a questionnaire. (See page 3–228)
HR_SOFT_CODING_KEYFLEX Legislation specific information for payrolls, organizations
and assignments. (See page 3–229)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–41
64. HR_STU_EXCEPTIONS (See page 3–231)
HR_STU_HISTORY Versions of HRMS Startup data installed (See page 3–232)
HR_SUMMARY Holds all data for the Generic Summary Process. (See page
3–233)
HR_TIPS Help components used within SSHR. (See page 3–234)
HR_REPORT_LOOKUPS Reports Select /Sort Parameter QuickCodes defined for
Oracle Payroll Applications Year end Reports. (See page
3–237)
HR_WORKFLOWS Taskflows in Oracle HRMS. (See page 3–235)
HR_WORKING_PERSON_LISTS Holds a list of people who constitute a user current list,
used in the Line Manager Web pages (See page 3–236)
PAY_ACCRUAL_BANDS Length of service bands used in calculating accrual of paid
time off. (See page 3–1)
PAY_ACCRUAL_PLANS PTO accrual plan definitions, (Paid time off). (See page 3–2)
PAY_ACTION_CLASSIFICATIONS Payroll Action Type classifications. (See page 3–4)
PAY_ACTION_CONTEXTS Assignment Action Contexts. (See page 3–5)
PAY_ACTION_INTERLOCKS Assignment action interlock definitions to control rollback
processing. (See page 3–6)
PAY_ACTION_PARAMETERS Global parameters to control process execution. (See page
3–7)
PAY_ALL_PAYROLLS_F Payroll group definitions. (See page 3–8)
PAY_ASSIGNMENT_ACTIONS Action or process results, showing which assignments have
been processed by a specific payroll action, or process. (See
page 3–12)
PAY_ASSIGNMENT_LATEST_BALANCES Denormalised assignment level latest balances. (See page
3–14)
PAY_ASSIGNMENT_LINK_USAGES_F Intersection between PAY_ELEMENT_LINKS_F and
PER_ALL_ASSIGNMENTS_F. (See page 3–15)
PAY_BACKPAY_RULES Balances to be recalculated by a RetroPay process. (See
page 3–17)
PAY_BACKPAY_SETS Identifies backpay, or RetroPay sets. (See page 3–18)
PAY_BALANCE_BATCH_HEADERS Batch header information for balance upload batch. (See
page 3–19)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
2–42 Oracle HRMS Technical Reference Manual
65. PAY_BALANCE_BATCH_LINES Individual batch lines for the balance upload process. (See
page 3–20)
PAY_BALANCE_CLASSIFICATIONS Information on which element classifications feed a
balance. (See page 3–22)
PAY_BALANCE_CONTEXT_VALUES Localization balance contexts. (See page 3–23)
PAY_BALANCE_DIMENSIONS Information allowing the summation of a balance. (See
page 3–24)
PAY_BALANCE_FEEDS_F Controls which input values can feed a balance type. (See
page 3–26)
PAY_BALANCE_SETS Allows related balances to be grouped for reporting
purposes. (See page 3–28)
PAY_BALANCE_TYPES Balance information. (See page 3–29)
PAY_BALANCE_TYPES_TL Translated balance type definitions (See page 3–31)
PAY_BATCH_CONTROL_TOTALS Holds user defined control totals for the Batch Element
Entry process. (See page 3–32)
PAY_BATCH_HEADERS Header information for a Batch Element Entry batch. (See
page 3–33)
PAY_BATCH_LINES Batch lines for a Batch Element Entry batch. (See page
3–35)
PAY_CALENDARS Details of user defined budgetary calendars. (See page
3–38)
PAY_CA_EMP_FED_TAX_INFO_F Federal tax information for Canada (See page 3–40)
PAY_CA_EMP_PROV_TAX_INFO_F Provincial tax information for Canada (See page 3–42)
PAY_CA_FILE_CREATION_NUMBERS Used in Canadian direct deposit (See page 3–44)
PAY_CA_LEGISLATION_INFO Keeps Canadian legislation specific data (See page 3–45)
PAY_CE_RECONCILED_PAYMENTS Holds reconciliation information for payments processed
through Oracle Cash Management. (See page 3–46)
PAY_COIN_ANAL_ELEMENTS Monetary unit quantities for automatic make–up of cash
payments. (See page 3–47)
PAY_CONSOLIDATION_SETS Consolidation set of results of payroll processing. (See page
3–48)
PAY_COSTS Cost details and values for run results. (See page 3–49)
Oracle Proprietary, Confidential Information––Use Restricted by Contract
High–Level Design 2–43