Search Results add_attribute

Overview

APPS.HXC_SECURITY is a server-side PL/SQL package body that implements the security and attribute-governance layer for Oracle E-Business Suite timecard and time-building-block functionality. Its central business purpose is to determine which security attributes apply to a given timecard block configuration and to enforce the rules that govern those attributes. In releases 12.1.1 and 12.2.2, the HXC schema family underpins Oracle Time and Labor (OTL), where timecard layouts are assembled from building blocks and each block may carry attribute usages that must be validated against the security model. HXC_SECURITY provides the programmatic entry point for attaching, or "adding," such a security attribute to a block context.

The package references the internal header string hxcaddsec.pkb (version 120.7), indicating that it is the "add security" component of the HXC family. It operates primarily against time attribute metadata rather than transactional timecard data, which makes it a configuration-time rather than a runtime data-entry package.

Key Procedures and Functions

The ETRM documentation identifies a single documented procedure or function in the package:

• ADD_SECURITY_ATTRIBUTE — The documented entry point, corresponding to the user search term "add_attribute," is the routine that adds a security attribute to the package's working attribute collection. It is the interface through which callers register an attribute so that subsequent security evaluation can consider it. Per ETRM conventions, no parameter list is reproduced here; the procedure's role is the addition and registration of a security attribute within the HXC attribute framework.

The package body additionally contains private helper logic, including a function that determines whether a given application set includes the "Projects" time recipient (effectively testing whether a timecard is Projects-related), and a validation function that checks whether an organization ID is required when a Projects-based timecard block is in use. These helpers raise the predefined message identifier HXC_366546_NO_ORG_ID when an organization ID is absent but required. A further internal routine derives a list of building blocks from a supplied attribute table. These routines are not separately exposed in the ETRM procedure listing but illustrate the package's supporting validation behavior.

Tables Accessed

The package reads and writes configuration metadata through APPS synonyms, including:

• HXC_TIME_ATTRIBUTES and HXC_TIME_ATTRIBUTE_USAGES — the store of time attribute definitions and where each attribute is used, central to ADD_SECURITY_ATTRIBUTE.
• HXC_TIME_BUILDING_BLOCKS and HXC_BLD_BLK_INFO_TYPES — the building-block definitions and information types that attributes are attached to.
• HXC_ENTITY_GROUP_COMPS and HXC_TIME_RECIPIENTS — used by the Projects-detection helper to resolve application sets to time recipients.
• FND_PROFILE_OPTION_VALUES — profile option resolution for security-relevant settings.
• PLITBLM — the standard EBS PL/SQL table-index-by utility used for in-memory list handling.

Usage Notes

HXC_SECURITY is invoked through dependent code rather than directly by end users. The ETRM metadata records that it is referenced by three other packages in the HXC family, indicating it functions as a shared service consumed by higher-level timecard configuration and validation routines, including those driven from Oracle Time and Labor setup forms and concurrent configuration processes. Customizations should call ADD_SECURITY_ATTRIBUTE only within a supported attribute-registration context and should not depend on the private helper routines, whose behavior may change between patch levels. Because the package manipulates shared attribute metadata, changes should be tested against referenced packages and profile option settings before deployment.