Results for “approved_by”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.HXC_NOTIFICATION_PROCESS_PKG is a PL/SQL package body in the Oracle E-Business Suite Applications schema that supports the Oracle Time and Labor (OTL) approval and notification infrastructure. Its principal business function is to evaluate, prepare, and dispatch workflow-based notifications associated with timecard approval routing. The package determines which approvers, timecard owners, and compensation-related parties receive notifications, evaluates approval-time preferences, governs timeout behavior, and controls the restart of approval workflow processes when approval state changes. It sits alongside companion packages such as HXC_APPROVAL_WF_PKG, HXC_APPROVAL_WF_HELPER, HXC_APPROVAL_WF_UTIL, and HXC_NOTIFICATION_HELPER, operating as a processing layer that translates approval business rules into Oracle Workflow notification activity.

In Oracle EBS 12.1.1 and 12.2.2, this package is classified under the OTHER API classification rather than as an open, externally supported interface. It is therefore treated as internal infrastructure for the Time and Labor approval framework rather than a documented integration point for customer extension.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within this package body:

• APPROVED_BY — Resolves or evaluates the approver identity associated with a timecard approval, supporting the determination of who approved or must approve submitted time.
• TIMEOUTS_ENABLED — Determines whether notification timeout processing is enabled for the applicable approval configuration, gating whether escalation or timeout handling should proceed.
• RESET_FOR_NEXT_TIMEOUT — Resets notification state so that the next timeout interval can be processed, supporting recurring timeout evaluation for pending approvals.
• RESTART_WORKFLOW — Reinitiates the approval workflow for a timecard or approval item when processing must be resumed after a state change.
• IS_TRANSFER — Evaluates whether the processing context represents a transfer, distinguishing transfer-related approval notifications from standard timecard notifications.
• EXCLUDE_TOTAL_HOURS — Determines whether total hours should be excluded from notification content, honoring preference or configuration settings for the delivered message.
• EVALUATE_ABS_PREF — Evaluates the absence preference settings that influence how absence and time-off data participate in approval notifications.
• IS_TCOWNER_SAMEAS_APPROVER — Establishes whether the timecard owner is the same person as the approver, a check that suppresses or alters self-notification behavior.

Tables Accessed

The package operates across Time and Labor approval, time attribute, and Oracle Workflow tables accessed through APPS synonyms:

• FND_USER and PER_ALL_PEOPLE_F — Supply user and person identity for approver and owner resolution.
• HXC_APPROVAL_COMPS, HXC_APPROVAL_ITEM_KEY_S, and HXC_APPROVAL_STYLES — Define approval components, approval item identifiers, and approval styles.
• HXC_APP_COMP_NOTIFICATIONS and HXC_APP_COMP_NOTIF_USAGES — Drive which notifications apply to which approval components.
• HXC_APP_PERIOD_SUMMARY — Provides period-level timecard summary data used in notification content.
• HXC_TIME_ATTRIBUTES, HXC_TIME_ATTRIBUTE_USAGES, HXC_TIME_BUILDING_BLOCKS, and HXC_TIME_CATEGORIES — Supply the time attribute, building block, and category definitions reflected in approval processing.
• WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_LOCAL_ROLES — Provide Oracle Workflow item, activity status, and role resolution required to create and manage notifications.

Usage Notes

HXC_NOTIFICATION_PROCESS_PKG is invoked indirectly by the Time and Labor approval workflow and by companion packages rather than through a user-facing form or dedicated concurrent program. It is referenced by one other package and does not itself reference any database object beyond the dependencies listed. Because it depends on Oracle Workflow APIs (WF_CORE, WF_ENGINE, WF_PROCESS_ACTIVITIES) and FND messaging, it executes within workflow notification processing contexts, including background workflow agents. Customers should not call this package directly from custom code; notification and approval extensions should be implemented through supported Time and Labor configuration and workflow customization rather than by modifying or invoking this internal package body.