Search Results per_assignment_extra_info_s




Overview

PAY_CONTACT_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, validated in both 12.1.1 and 12.2.2. Its documented classification is OTHER, indicating that it is not part of the public, customer-callable Oracle HRMS or Payroll API set, but rather an internal utility package used to maintain contact-related assignment data. The package derives its functional identity from the combination of tables it references: PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENT_EXTRA_INFO, and PER_ASSIGNMENT_EXTRA_INFO_S. These objects belong to the Core HR assignment model, and the assignment extra information table is the standard repository for date-tracked, descriptive attributes attached to an assignment, frequently configured as EIT (Extra Information Type) segments. PAY_CONTACT_PKG therefore exists to consolidate or refresh contact details held against an assignment record — for example emergency contacts, next-of-kin, or address and telephone information stored in an EIT — into a form that downstream Payroll or HR processes can consume. The body depends on HR_UTILITY, the HRMS utility package that supplies reusable date and business-group helper logic, confirming that the code follows standard HRMS development conventions. Only one procedure is documented, and the package is not referenced by any other database object, marking it as a terminal consumer in the dependency graph rather than a shared library.

Key Procedures and Functions

The ETRM metadata documents a single procedure: POPULATE_PAY_CONTACT_DETAILS.

  • POPULATE_PAY_CONTACT_DETAILS — The sole documented entry point. As its name implies, the procedure populates payload contact detail records. Given the tables in scope, the routine reads assignment and assignment extra information rows and materialises the corresponding contact attributes for use by a calling process. The procedure is intended as an internal building block rather than a general-purpose API, and no parameter list is published in the available metadata; consumers should therefore treat its signature as private and access it only through the application modules that already depend on it.

No functions or additional procedures are recorded in the ETRM extract for this package body.

Tables Accessed

The dependency list identifies the following tables, referenced through APPS synonyms:

  • PER_ALL_ASSIGNMENTS_F — The date-tracked core assignment table. It supplies the assignment context, business group, person, and effective dates used to scope the contact detail extraction.
  • PER_ASSIGNMENT_EXTRA_INFO — The base table holding assignment-level extra information entries, which is where contact data such as emergency contact names and telephone numbers is typically stored when configured as EIT segments.
  • PER_ASSIGNMENT_EXTRA_INFO_S — The corresponding date-tracked/translated sibling table associated with the extra information records. Because the searched object is PER_ASSIGNMENT_EXTRA_INFO_S, this table is central to the package's read path; the procedure joins these rows to the assignment to resolve the current effective contact values.
  • DUAL — Referenced from the PUBLIC schema, indicating simple scalar selection or validation logic within the body.

Usage Notes

PAY_CONTACT_PKG is an internal APPS package. The metadata records that it is referenced by zero other database objects and that it is referenced by no other packages, which means it is normally invoked from outside the database dependency chain — most plausibly from an Oracle Forms trigger, a concurrent program wrapper, or bespoke PL/SQL that calls POPULATE_PAY_CONTACT_DETAILS directly. Because Oracle does not publish this package as a supported API, extensions should treat it as subject to change between releases and should not build critical interfaces on it. Where contact information must be read independently, the underlying PER_ASSIGNMENT_EXTRA_INFO and PER_ASSIGNMENT_EXTRA_INFO_S tables are the recommended source; the public HRMS extra information APIs provide the supported route for reading and writing that data.