Search Results po_hxc_interface_pvt




Overview
Explore in AI Chat

Overview

PO_HXC_INTERFACE_PVT is a private PL/SQL package in the APPS schema that bridges Oracle Purchasing and Oracle Time and Labor (the HXC application). Its central business purpose is to support the interaction between purchase order lines and timecards, allowing purchasing documents that represent contingent worker or service-based commitments to be validated against, and enriched with, time and labor data. In this way the package enables the requisition-to-pay cycle to account for labor that has actually been recorded in OTL.

The package is constructed in the standard Oracle EBS private API pattern: it carries the _PVT suffix, indicating it is an internal implementation layer rather than a public, supported entry point. It is exposed to, and consumed by, the public Purchasing APIs and validation utilities rather than being called directly by external integrations. Its status is VALID in the APPS schema, and its object metadata is consistent across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

  • FIELD_PO_HEADER_ID — Returns or derives the purchase order header identifier associated with the time-related context being processed, enabling the interface to link OTL activity back to the correct purchasing document header.
  • FIELD_PO_LINE_ID — Corresponds to the line-level equivalent, resolving the purchase order line identifier so that timecard data can be mapped to a specific committed line.
  • CHECK_TIMECARD_EXISTS — Determines whether a timecard record exists for the purchase order or line under evaluation, supporting validation logic that prevents processing where required labor records are absent.
  • GET_TIMECARD_AMOUNT — Retrieves the monetary amount associated with a timecard, supplying the value used for matching or reconciliation against the purchasing commitment.
  • GET_PA_TIMECARD_AMOUNT — Retrieves the corresponding timecard amount from a Projects (PA) perspective, reflecting the integrated treatment of labor costs recorded through Oracle Projects.

The six documented program units (the five above plus the package-level entries) are all utility-oriented: they field identifiers, test existence, and return amounts. None of the documented procedures are exposed as public callable APIs, consistent with the PVT classification.

Tables Accessed

Usage Notes

PO_HXC_INTERFACE_PVT is referenced by PO_DOCUMENT_CONTROL_PVT, PO_DOCUMENT_UPDATE_PVT, PO_VALIDATION_HELPER, and PO_VAL_LINES. These are internal Purchasing packages that drive document validation, document control, and document update processing. This reference chain confirms that the package is invoked indirectly whenever a Purchasing document involving OTL timecard data is validated or updated.

Typical invocation therefore occurs through Purchasing forms and concurrent processes that call the public document-control and validation APIs, not through direct custom calls. Customizations and integrations should avoid calling this package directly; instead they should use the supported public Purchasing APIs, which delegate to this private layer. Direct dependency on a PVT package risks breakage across patching and upgrades, since Oracle does not guarantee the stability of private interfaces. Dependency tracing in ETRM is the appropriate method for identifying impact when this package changes.