Results for “creator_type_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAYBV_ELEMENT_TYPE is a Business Intelligence System (BIS) view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. Like other objects sharing the "PAYBV_" prefix, it is a reporting-oriented view designed to present decoded, user-friendly representations of Payroll element type data rather than the raw code values stored in the underlying transactional tables. In releases 12.1.1 and 12.2.2, this view provides a denormalized, human-readable projection of the PAY_ELEMENT_TYPES_F entity, allowing report developers, discoverer administrators, and integration specialists to query element type definitions without having to manually translate lookup codes.

The view is validated (Status: VALID) and is intended primarily for read-only consumption by reporting tools, ad hoc SQL, and custom extracts. Selection of the object as a searched target for the term "closed_for_entry_flag" reflects the view's role in exposing that flag in a decoded YES/NO form rather than as a raw system code.

Underlying Base Objects

The view is defined over the following documented base objects:

• PAY_ELEMENT_TYPES_F (referenced via synonym) — the core date-tracked table holding element type definitions, including the various control flags and attributes exposed by the view.
• PAY_ELEMENT_TYPES_F_TL (referenced via synonym) — the translation table supplying language-specific descriptive text, aliased as PETT in the view definition to yield ELEMENT_NAME and REPORTING_NAME.
• HR_BIS (package) — the BIS decode package whose BIS_DECODE_LOOKUP function converts stored lookup codes into their meaning/description values.

The view therefore joins the date-effective element type row to its translated name and wraps each coded flag column in a call to HR_BIS.BIS_DECODE_LOOKUP, producing presentation-ready output. Because it reads from the "_F" date-tracked table without an effective-date filter, callers must apply their own date criteria when only the currently effective definition is required.

Key Columns

The view exposes the identity, currency, and control-flag attributes of an element type:

• ELEMENT_NAME and REPORTING_NAME — from the translation table, giving the display and statutory reporting names.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window of the definition.
• LEGISLATION_CODE, INPUT_CURRENCY_CODE, OUTPUT_CURRENCY_CODE — governing legislation and currencies.
• CLOSED_FOR_ENTRY_FLAG — decoded via BIS_DECODE_LOOKUP on the YES_NO lookup, indicating whether the element is closed to further entry. Because it is decoded, queries should compare against the lookup meaning rather than the underlying 'Y'/'N' code.
• ADDITIONAL_ENTRY_ALLOWED_FLAG, ADJUSTMENT_ONLY_FLAG, INDIRECT_ONLY_FLAG, MULTIPLE_ENTRIES_ALLOWED_FLAG, MULTIPLY_VALUE_FLAG, PROCESS_IN_RUN_FLAG, STANDARD_LINK_FLAG — all YES_NO decoded control flags.
• POST_TERMINATION_RULE, PROCESSING_TYPE, QUALIFYING_UNITS — decoded using their respective lookup types.
• PROCESSING_PRIORITY, QUALIFYING_AGE, QUALIFYING_LENGTH_OF_SERVICE — numeric attributes retained as stored.
• DESCRIPTION, LEGISLATION_SUBGROUP, ELEMENT_INFORMATION_CATEGORY, and ELEMENT_INFORMATION1–7, ATTRIBUTE1–20 — descriptive and descriptive-flexfield (DF) columns; the DF context is fixed at '_DF:PAY:PAY_ELEMENT_TYPES:PET'.

Common Use Cases and Queries

Typical scenarios include building element type reference reports, validating which elements remain open for entry, and driving payroll extracts. A representative query listing currently effective, entry-closed elements follows:

• SELECT element_name, legislation_code, closed_for_entry_flag, effective_start_date, effective_end_date FROM apps.paybv_element_type WHERE closed_for_entry_flag = 'No' AND SYSDATE BETWEEN effective_start_date AND effective_end_date; — note the decoded value is compared as a lookup meaning.
• SELECT element_name, reporting_name, processing_type, post_termination_rule FROM apps.paybv_element_type WHERE legislation_code = 'US'; — element type reference listing by legislation.
• SELECT element_name, adjustment_only_flag, indirect_only_flag, multiple_entries_allowed_flag FROM apps.paybv_element_type ORDER BY element_name; — inventory of control-flag settings for audit.

Because the view returns every date-effective version, always constrain effective dates for point-in-time accuracy.