Search Results notify_preparer_approved

Overview

APPS.HXC_APPROVAL_STYLES_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Time and Labor / OTL approval framework, exposed under the APPS schema in both release 12.1.1 and 12.2.2. It presents the configuration of approval styles defined in the HXC_APPROVAL_STYLES table while enriching each row with runtime behavioral attributes resolved through calls to the HXC_NOTIFICATION_HELPER package. The view decouples consumers from the internal notification-builder logic: rather than invoking helper functions directly, report writers, integrations, and diagnostic queries can read precomputed flags such as whether timeouts are enabled, how many retries are configured, and which notification events are active for a given approval style. The presence of AUDIT-style maintenance columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) makes the view suitable for data-extraction and change-tracking scenarios. Because the notification helper functions are invoked per row, the view is intended for targeted queries rather than full-table scans in high-volume batch processes.

Underlying Base Objects

The view is defined over two documented base objects:

• HXC_APPROVAL_STYLES (referenced as a synonym) — the base table holding approval style definitions, including BUSINESS_GROUP_ID, LEGISLATION_CODE, APPROVAL_STYLE_ID, NAME, DESCRIPTION, OBJECT_VERSION_NUMBER, RUN_RECIPIENT_EXTENSIONS, ADMIN_ROLE, and ERROR_ADMIN_ROLE.
• HXC_NOTIFICATION_HELPER — a PL/SQL package supplying scalar functions that compute per-style notification behavior, including HAS_TIMEOUT_NOTIFICATIONS, NUMBER_TIMEOUT_RETRIES_ANY, APPROVER_TIMEOUT_VALUE, PREPARER_TIMEOUT_VALUE, ADMIN_TIMEOUT_VALUE, NOTIFY_SUP_FOR_APPROVAL, NOTIFY_WORKER_SUBMISSION, NOTIFY_WORKER_AUTO_APPROVE, NOTIFY_PREPARER_APPROVE, NOTIFY_PREPARER_REJECT, and NOTIFY_PREPARER_TRANSFER.

Each helper function is passed APS.APPROVAL_STYLE_ID, so every row reflects the resolved configuration for that specific style. RUN_RECIPIENT_EXTENSIONS is defaulted to 'Y' via NVL, indicating that recipient extension logic is enabled unless explicitly disabled on the base record.

Key Columns

• APPROVAL_STYLE_ID / NAME / DESCRIPTION — identity and descriptive attributes of the approval style.
• BUSINESS_GROUP_ID / LEGISLATION_CODE — organizational and legislative scoping keys.
• TIMEOUTS_ENABLED — derived flag indicating whether any timeout notifications apply.
• NUMBER_RETRIES, APPROVER_TIMEOUT, PREPARER_TIMEOUT, ADMIN_TIMEOUT — retry count and timeout thresholds for approvers, preparers, and administrators.
• NOTIFY_SUPERVISOR, NOTIFY_WORKER_ON_SUBMIT, NOTIFY_WORKER_ON_AA — flags controlling supervisor and worker notifications on submission and auto-approval.
• NOTIFY_PREPARER_APPROVED — the column mapped from HXC_NOTIFICATION_HELPER.NOTIFY_PREPARER_APPROVE(APS.APPROVAL_STYLE_ID). This is the attribute directly relevant to notify_preparer_approved: it indicates whether the preparer is notified when the timecard or document is approved.
• NOTIFY_PREPARER_REJECTED / NOTIFY_PREPARER_TRANSFER — parallel flags for rejection and transfer-notification behavior.
• RUN_RECIPIENT_EXTENSIONS, ADMIN_ROLE, ERROR_ADMIN_ROLE, OBJECT_VERSION_NUMBER — configuration and error-handling governance attributes.

Common Use Cases and Queries

Typical scenarios include auditing notification configuration across approval styles, verifying that preparers are notified on approval, and investigating timeout/retry behavior. A query to confirm the preparer-approved setting is:

• SELECT approval_style_id, name, notify_preparer_approved, notify_preparer_rejected, notif_num_retries FROM apps.hxc_approval_styles_v WHERE notify_preparer_approved = 'Y'; (substitute the exact column names as exposed).
• Reviewing timeout configuration: SELECT approval_style_id, name, timeouts_enabled, number_retries, approver_timeout, preparer_timeout, admin_timeout FROM apps.hxc_approval_styles_v WHERE timeouts_enabled = 'Y';
• Scoping to a business group or legislation: add WHERE business_group_id = :p_bg_id to filter results for extraction or reconciliation reports.

Because each notification column is computed by a package function, queries should filter by APPROVAL_STYLE_ID or BUSINESS_GROUP_ID wherever possible to avoid unnecessary function executions. The view is best regarded as a configuration-diagnostic and integration surface rather than a high-volume extraction source.