Search Results add_datetrack_event_to_entry

Overview

PAY_INTERPRETER_PKG is a core Oracle Payroll PL/SQL package (source file pyinterp.pkh) owned by the APPS schema and defined with AUTHID DEFINER rights. Its principal business function is to interpret the events, dated tables, and element entries that Oracle Payroll generates during the payroll run and during datetracked (date-effective) maintenance of assignment and element information. Rather than performing payroll calculation itself, the package acts as the interpretive layer that determines which assignment actions, element entries, and event groups are "affected" by a given datetrack change, resolving effective dates, process modes, and event qualifiers so that downstream payroll processes and notifications (including "penserver"/pension server integration, period allocation, and RetroNotification processing) receive correctly qualified data.

The package has evolved through many versions, with changelog entries addressing penserver dependency removal, global variables for penserver dates, internal cache handling, and performance tuning for RetroNotification and Period Allocation. It is referenced by 24 other packages, confirming its role as a shared, foundational interpreter within the Oracle Payroll event model rather than a leaf-level utility.

Key Procedures and Functions

The package exposes 25 documented procedures and functions. The search term generic_data_validation corresponds to the documented GENERIC_DATA_VALIDATION routine, which performs generic validation of data passed into the interpreter layer, ensuring that entry and event records conform to expected formats and rules before further interpretation occurs.

• INITIALISE_GLOBAL — Initializes package-level global variables and state at the start of interpreter processing.
• ADD_DATETRACK_EVENT_TO_ENTRY / CLEAR_DT_EVENT_FOR_ENTRY — Associate or remove a datetrack event against a specific entry.
• EVENT_GROUP_TABLES — Identifies the dated tables relevant to an event group.
• GET_PRORATED_DATES / PRORATE_START_DATE — Compute prorated date boundaries for period allocation.
• ENTRY_AFFECTED / ENTRIES_AFFECTED — Determine whether one or many entries are affected by a change, using process mode and creation date in the detailed output.
• TIME_FN — Time-related utility used within interpreter logic.
• ASG_ACTION_AFFECTED / ASG_ACTION_EVENT / VALID_GROUP_EVENT_FOR_ASG — Evaluate assignment-action impacts and prequalify events for an assignment.
• EVENT_GROUP_TABLES_AFFECTED — Apply the affected-table determination across an event group.
• GENERIC_DATA_VALIDATION — Perform generic data validation of interpreter input.
• GET_OBJECT_KEY / GET_PARENT_KEY — Return key values used to resolve object and parent relationships.
• GET_EFFECTIVE_DATE / GET_ASSIGNMENT_ID / GET_ELEMENT_ENTRY_ID — Retrieval helpers for effective date and primary identifiers.
• GET_SUBSET_GIVEN_NEW_EVG — Derive a subset given a new event group value.

Tables Accessed

The package reads and writes through APPS synonyms. Payroll dated and datetrack infrastructure tables — PAY_DATED_TABLES, PAY_DATETRACKED_EVENTS, and PAY_EVENT_UPDATES — define which tables and events are subject to date-effective interpretation. PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F provide the entry and value records being interpreted, while PAY_ELEMENT_LINKS_F supplies link context. PAY_EVENT_PROCEDURES, PAY_EVENT_QUALIFIERS_F, PAY_EVENT_VALUE_CHANGES_F, and PAY_PROCESS_EVENTS drive event qualification and processing. PAY_ASSIGNMENT_ACTIONS records the assignment actions evaluated. The BEN_EXT_* tables (BEN_EXT_CRIT_TYP, BEN_EXT_CRIT_VAL, BEN_EXT_DFN, BEN_EXT_RSLT) support extended criteria definition and results used in qualifier resolution.

Usage Notes

PAY_INTERPRETER_PKG is invoked indirectly by payroll forms, concurrent programs, and datetrack processing rather than by end users directly. When an element entry, assignment, or event is modified, the interpreter is called to determine affected entries and events, resolve prorated dates, and validate data via GENERIC_DATA_VALIDATION. Custom code should call the package only through its documented interface and never modify its globals. Because it is referenced by 24 packages and marked AUTHID DEFINER, changes should be regression-tested across payroll, benefits, and pension server integrations in both 12.1.1 and 12.2.2.