Results for “source_end_date”

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

Overview

PAY_ELEMENT_ENTRIES is a date-effective (DATE_EFFECTIVE) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PAY — Payroll product. It presents element entry records that are valid for the current session's effective date, drawing from the underlying date-effective table. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the reporting and integration surface for element entries — the assignment-level instances of an element that carry pay values, costing information, and processing attributes used during payroll runs.

Because it filters on the session effective date, the view reflects only the version of each element entry applicable to the querying session's effective date context, isolating the current row from the historical, date-tracked versions.

Underlying Base Objects

The view is defined over two documented objects:

• PAY_ELEMENT_ENTRIES_F (SYNONYM) — the date-effective base table holding the element entry rows, including effective start and end dates. The view reads the current version by comparing EFFECTIVE_START_DATE and EFFECTIVE_END_DATE against the session effective date.
• FND_SESSIONS (SYNONYM) — the Oracle Application Object Library table that stores session context. The WHERE clause obtains the effective date via FND_SESSIONS.EFFECTIVE_DATE for the row matching USERENV('SESSIONID').

The view's SELECT projects the base table columns and applies the predicate:

WHERE EFFECTIVE_START_DATE <= (SESSION EFFECTIVE_DATE) AND EFFECTIVE_END_DATE >= (SESSION EFFECTIVE_DATE)

No joins or aggregation are performed; the view is a filtered projection of the "_F" table.

Key Columns

• ELEMENT_ENTRY_ID — primary surrogate key identifying each element entry.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range defining the entry's validity window; the driving columns for the view's filter.
• ASSIGNMENT_ID — the assignment to which the entry applies.
• ELEMENT_LINK_ID / ELEMENT_TYPE_ID — the element link and element type used by the entry.
• ORIGINAL_ENTRY_ID / TARGET_ENTRY_ID — linkage between source and target entries (e.g., adjustment relationships).
• ENTRY_TYPE / CREATOR_TYPE / CREATOR_ID — classification of the entry and its originator.
• COST_ALLOCATION_KEYFLEX_ID — the costing keyflex reference for the entry.
• ENTRY_INFORMATION1 … ENTRY_INFORMATION30 — element-defined input values (entry information) captured for the entry.
• ATTRIBUTE1 … ATTRIBUTE20 — the standard EBS descriptive attribute flexfield columns.
• BALANCE_ADJ_COST_FLAG, DATE_EARNED, PERSONAL_PAYMENT_METHOD_ID — balance adjustment, earning, and payment attributes.
• SOURCE_ASG_ACTION_ID, SOURCE_LINK_ID, SOURCE_PERIOD, SOURCE_RUN_TYPE, SOURCE_START_DATE, SOURCE_END_DATE — origin details when the entry was generated by another process or run.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY — audit columns.

Common Use Cases and Queries

The view is used in payroll reporting, reconciliation, and integration interfaces requiring the currently effective element entry for an assignment, and for retrieving entry information used by payroll processing.

List entries for a specific assignment:

SELECT element_entry_id, element_link_id, element_type_id, entry_type, date_earned
FROM apps.pay_element_entries
WHERE assignment_id = :p_assignment_id;

Retrieve element input values (entry information):

SELECT element_entry_id, entry_information1, entry_information2
FROM apps.pay_element_entries
WHERE element_link_id = :p_link_id;

Trace entries created from a payroll run type:

SELECT element_entry_id, source_run_type, source_period, date_earned
FROM apps.pay_element_entries
WHERE source_run_type = :p_run_type;

Because results depend on the session effective date maintained in FND_SESSIONS, callers should ensure the session context is initialized when the view is queried directly outside standard EBS application flows.