Search Results add_security_attribute




Overview

HXC_SECURITY is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Time and Labor (HXC) module's attribute-level security model for timecards. The package encapsulates the logic required to attach security-related attributes to the timecard building blocks used during time entry and processing. It is classified as OTHER under the Oracle ETRM API taxonomy, indicating it is an internal, helper-style package rather than a published, customer-facing API. The package was authored with AUTHID CURRENT_USER and carries a source header dated 2006 (hxcaddsec.pkh 120.2), suggesting a long-lived and stable code line that has survived the transition between Oracle EBS 12.1.1 and 12.2.2 without major structural change. Its role is to cooperate with the Time and Labor timecard layout engine, ensuring that the attributes assembled into a timecard carry the appropriate security context before they are presented to, or validated against, the user.

Key Procedures and Functions

  • ADD_SECURITY_ATTRIBUTE — The single documented procedure in this package. Its purpose is to augment a collection of timecard building blocks and their associated attributes with the security attributes required for the time entry operation. It operates on block, attribute, timecard property, and message table types, allowing it to contribute to the in-memory structures that the timecard layout engine assembles and, where necessary, to return diagnostic messages to the caller. The procedure participates in the internal pipeline that prepares a timecard payload, so it is invoked during layout or attribute resolution rather than as a standalone transaction processor.

Tables Accessed

Through APPS synonyms, the package reads configuration and metadata that drive its attribute injection logic:

Usage Notes

HXC_SECURITY is an internal dependency invoked by other Time and Labor packages rather than a directly callable user API. The ETRM metadata records that it is referenced by three other packages, which confirms its position as a subordinate component in the attribute-resolution and timecard-assembly flow. Typical invocation occurs when the Time and Labor timecard layout is being built — for example, during self-service time entry or when a timecard structure is validated — and the caller requires security attributes to be attached to the attributes already collected. Because it is not exposed through a concurrent program or an Oracle Forms trigger directly, customizations should not rely on it as a stable interface. Any extension should instead operate through the supported Time and Labor APIs, since the signature and internal behaviour of ADD_SECURITY_ATTRIBUTE are subject to change without notice in future patches or upgrades.