Search Results per_form_function_uk

Overview

PER_FORM_FUNCTIONS is a Human Resources (PER) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores navigation and person change information that governs how the Enter Person information screens behave. In practical terms, it acts as a configuration and control repository that determines which functions are available on a given form, what result each function produces, what input it accepts, and what restrictions apply to its availability or execution.

Because the table is documented as a standalone object with no foreign key relationships to other tables, its heuristic Data Vault classification is a standalone hub-like reference structure. In modeling terms, it is best treated as a reference or configuration table rather than a transactional hub, link, or satellite. Its rows are relatively static and are consumed at runtime by the Enter Person forms to drive navigation and validation logic.

Key Information Stored

The table contains six documented columns and is uniquely identified by the UK index PER_FORM_FUNCTION_UK, which spans all six columns: FORM, FUNCTION, RESULT, INPUT, RESTRICTION_CODE, and RESTRICTION_VALUE. This composite unique key serves as the business-key candidate; no separate single-column surrogate primary key is documented.

• FORM — Identifies the Enter Person form or screen to which the function entry applies. This is the anchor that links a configuration row to a specific UI surface.
• FUNCTION — Names the function, action, or navigation capability available on that form, such as a person change operation or navigation step.
• RESULT — Defines the outcome or result produced when the function is invoked, effectively describing the post-action state or target.
• INPUT — Specifies the input required or accepted by the function, defining what the user or calling process must supply.
• RESTRICTION_CODE — Identifies the type of restriction that limits when or whether the function may be used.
• RESTRICTION_VALUE — Supplies the specific value paired with RESTRICTION_CODE, giving the concrete condition that governs the restriction.

Common Use Cases and Queries

Typical use cases include diagnosing unexpected behavior on the Enter Person screens, auditing which functions are enabled for a form, and documenting navigation rules for a specific responsibility or configuration. A common query pattern retrieves all functions and their restrictions for a given form:

• SELECT form, function, result, input, restriction_code, restriction_value FROM hr.per_form_functions WHERE form = :form_name;
• SELECT * FROM hr.per_form_functions WHERE restriction_code = :code AND restriction_value = :value;
• SELECT function, COUNT(*) FROM hr.per_form_functions GROUP BY function ORDER BY 2 DESC;

Because the table is standalone, these queries do not require joins to resolve core meaning. Reporting use cases focus on configuration inventories, restriction audits, and comparison of form behavior across environments or releases.

Related Objects

The metadata documents no foreign key relationships for PER_FORM_FUNCTIONS, so it does not formally reference or depend on other tables through constraints. In operational terms, it is consumed by the Enter Person forms and related PER form infrastructure that read FORM, FUNCTION, and RESTRICTION_CODE at runtime. Related objects to review when analyzing its behavior include PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F for person and assignment context, FND_FORM_FUNCTIONS and FND_FORM_FUNCTION_RULES for form-function and rule configuration, FND_RESPONSIBILITY and FND_USER for access context, and the Enter Person form definitions themselves. Because no join columns are documented, any linkage to these objects is application-level rather than enforced by database constraints.