Search Results upd_contact_info




Overview

APPS.PAY_KR_ENTRIES_PKG is a Korean localization package within the Oracle EBS Payroll (PAY) module. Its source header (pykretr.pkh, version 120.7) and its ownership under the APPS schema identify it as a server-side PL/SQL package that supports the entry, validation, and maintenance of element entry data in the Korean payroll legislative environment. The package is classified under ETRM as API classification OTHER, meaning it is intended primarily for internal consumption by Oracle forms, concurrent programs, and dependent packages rather than as a formal public API for customer extensions.

The package encapsulates business logic specific to Korean statutory requirements, including the derivation of a person's age from the national identifier, the derivation of input value attributes and format masks, and the management of localized contact information records. It also implements the standard insert, update, and delete (INS/UPD/DEL) operations against element entry structures, together with lookups, locking, and data-derivation helper routines. The header declares a large set of PL/SQL record and collection types (ev_rec, elm_rec, iv_rec and their table variants) that are used to cache element, input value, and entry value information for the Forms layer.

Key Procedures and Functions

The package exposes sixteen documented program units:

  • CALC_AGE — Computes a person's age from a national identifier, a date of birth, and an effective date, returning a number.
  • DERIVE_ATTRIBUTES — Populates element and input value attributes used by the entry screens.
  • DERIVE_FORMAT_MASK — Derives the display format mask (and related maximum length) applied to an input value entry.
  • DERIVE_DEFAULT_VALUES — Determines default values applied to element entry input values.
  • CHK_ENTRY — Validates an element entry as a whole before it is committed.
  • CHK_ENTRY_VALUE — Validates a single entry value against its associated input value definition.
  • FIND_DT_UPD_MODES — Determines the date update modes applicable to an entry during maintenance.
  • FIND_DT_DEL_MODES — Determines the date delete modes applicable to an entry during maintenance.
  • INS_LCK — Performs an insert preceded by the appropriate locking step.
  • LCK — Locks the relevant element entry rows to protect against concurrent modification.
  • INS — Inserts a new element entry record.
  • UPD — Updates an existing element entry record.
  • DEL — Deletes an element entry record.
  • UPD_CONTACT_INFO — Updates localized contact information associated with the payroll record; this is the routine that matches the user search term "upd_contact_info".
  • UPD_CONTACT_EXTRA_INFO — Updates supplementary contact information beyond the primary contact set.
  • CREATE_CONTACT_EXTRA_INFO — Creates new supplementary contact information records.

Tables Accessed

The package reads and writes the core Korean payroll element entry tables through APPS synonyms. PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F store the entry header and its individual input values; PAY_ELEMENT_TYPES_F and PAY_INPUT_VALUES_F (with its translation table PAY_INPUT_VALUES_F_TL) provide the element and input value definitions, display sequences, mandatory flags, units of measure, and format information. PAY_ELEMENT_LINKS_F and PAY_LINK_INPUT_VALUES_F supply link-level input value definitions used during validation and default derivation. FF_FDI_USAGES_F supports derived input value processing, and PLITBLM is the standard Oracle Forms PL/SQL table used for caching. HR_LOOKUPS provides the meaning values returned for entry values.

Usage Notes

PAY_KR_ENTRIES_PKG is invoked primarily from the Korean payroll element entry forms during data capture and maintenance. The DERIVE_* routines populate the form's item attributes and defaults, CHK_ENTRY and CHK_ENTRY_VALUE enforce validation, and the INS/INS_LCK/UPD/DEL group commits changes. Its contact information routines (UPD_CONTACT_INFO, UPD_CONTACT_EXTRA_INFO, CREATE_CONTACT_EXTRA_INFO) are called when contact details attached to the payroll record are maintained. Because the package is referenced by three other packages and ETRM classifies it as OTHER, integrators should treat it as an internal object: prefer documented APIs where available and validate any direct call against the target EBS release (12.1.1 or 12.2.2) before deployment.