Search Results upd_contact_extra_info




Overview
Explore in AI Chat

Overview

APPS.PAY_KR_ENTRIES_PKG is a Korean localization package within the Oracle Payroll (PAY) module. It supports the creation, validation, and maintenance of element entries — the payroll records that link an assignment to an element and its input values. In the Korean legislative context this includes statutory deductions such as income tax and the two premium elements referenced by the package's constants: TAX, HI_PREM (health insurance premium), and NP_PREM (national pension premium). The package encapsulates the date-tracked insert, update, and delete logic required by the element entries datetrack model, plus validation and derivation routines that populate entry attributes and input values. The header comment identifies the source file as pykretr.pkb, version 120.7, dated 2008/01/08, indicating a long-lived component that has been patched under multiple bug fixes (for example Bug 2734338, which changed how national identifier digits 5–8 are decoded to identify foreign nationals).

Key Procedures and Functions

  • CALC_AGE — Derives an age in years from a national identifier, date of birth, and effective date. It interprets the seventh digit of the Korean national identifier to determine the century of birth and then uses MONTHS_BETWEEN to compute the age.
  • DERIVE_ATTRIBUTES — Populates the descriptive attributes of an element entry based on element type and link configuration.
  • DERIVE_FORMAT_MASK — Establishes the display or validation format mask applicable to an entry value.
  • DERIVE_DEFAULT_VALUES — Resolves default input values for an entry from the element link and input value definitions.
  • CHK_ENTRY / CHK_ENTRY_VALUE — Validation routines that verify the entry as a whole and individual entry values against element and input value rules before the record is saved.
  • FIND_DT_UPD_MODES / FIND_DT_DEL_MODES — Determine the datetrack update and delete modes required for a given change, driving correct effective-date behaviour.
  • INS_LCK / LCK — Locking helpers used to serialize access to entry rows before insert or update.
  • INS / UPD / DEL — The core datetracked insert, update, and delete operations for element entries; these wrap the underlying table writes with validation and locking.
  • UPD_CONTACT_INFO / UPD_CONTACT_EXTRA_INFO / CREATE_CONTACT_EXTRA_INFO — Maintain contact and contact-extra information associated with Korean element entries, supporting localized reporting and statutory requirements.

Tables Accessed

The package operates on the core payroll datetrack tables through APPS synonyms. PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F store the entry header and its input values, and are the primary targets of INS, UPD, and DEL. PAY_ELEMENT_TYPES_F and PAY_INPUT_VALUES_F (with its translation table PAY_INPUT_VALUES_F_TL) provide element and input value metadata used during validation and attribute derivation. PAY_ELEMENT_LINKS_F and PAY_LINK_INPUT_VALUES_F supply the link-level defaults that DERIVE_DEFAULT_VALUES applies. FF_FDI_USAGES_F defines which Fast Formula database items are available to the element. PLITBLM serves as a PL/SQL index-by table buffer used internally when accumulating and processing entry rows.

Usage Notes

PAY_KR_ENTRIES_PKG is normally invoked indirectly. Oracle Payroll forms such as the Element Entries window call the datetracked INS, UPD, and DEL entry points, and the validation routines CHK_ENTRY and CHK_ENTRY_VALUE are invoked implicitly during save. Derivations run when a user selects or changes an element, populating attributes and defaults before the record is committed. The package is also referenced by three other packages, so custom code should prefer those documented entry points rather than issuing direct DML against the underlying _F tables. Because the routines assume the standard datetrack mode resolution performed by FIND_DT_UPD_MODES and FIND_DT_DEL_MODES, any custom invocation must supply a valid effective date and business group context. Site-specific extensions should be limited to wrapped calls or hooks, since the source file header indicates the object is shipped and patched by Oracle.