Search Results chk_approval_req

Overview

APPS.HXC_APPROVAL_WF_PKG is the core approvals engine within the Oracle E-Business Suite Time and Labor (OTL) module. It governs whether a submitted timecard, time entry, or self-service time deposit must pass through an approval workflow, identifies the applicable approval rules and routing, and drives the Oracle Workflow (WF) process that carries the transaction through to final approval or rejection. In effect, the package bridges the transactional time data held in the HXC tables with the generic Oracle Workflow engine (WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ATTRIBUTE_VALUES), translating Time and Labor business rules — approval styles, approval periods, approval components and conditions — into workflow activity transitions.

The package is classified as OTHER rather than a public API, meaning it is primarily an internal engine invoked by other OTL components rather than being documented for direct customer extension. It is delivered VALID under the APPS schema and is present in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions. Their responsibilities cluster into four areas:

• Workflow initiation: START_APPROVAL_WF_PROCESS launches the approval workflow for a given time transaction, and IS_APPR_REQUIRED determines whether approval is needed at all before a process is started.
• Approval rule evaluation: CHK_APPR_RULES, FIND_APPROVAL_RULE, EXECUTE_APPR_RULE, and CHK_APPROVAL_REQ evaluate the approval rule set configured for the transaction and decide which rule fires and whether its conditions are satisfied. GET_APPROVAL_STYLE_ID resolves the approval style (and therefore the routing pattern) to be applied.
• Approval period processing: CREATE_APPL_PERIOD_INFO, PROCESS_APPL_PERIODS, UPDATE_APP_PERIOD, and CREATE_NEXT_PERIOD manage the approval period construct — the segmented time windows over which approvals are grouped — including creating, updating, and rolling periods forward.
• Routing and detail maintenance: FIND_MYSTERIOUS_APPROVER (locating a default or fallback approver), UPD_APR_DETAILS, GET_OVERRIDE (handling override approvers), CODE_CHK, IS_DIFFERENT_TIME_CATEGORY (category-change detection), and ITEM_ATTRIBUTE_EXISTS (workflow item attribute existence check used before reading or writing WF item attributes).

None of these are documented public APIs; parameter lists are intentionally omitted here in line with ETRM's treatment of the package as internal.

Tables Accessed

Through APPS synonyms the package reads and writes a mix of Workflow and Time and Labor tables. The Workflow tables — WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_ITEM_ATTRIBUTE_VALUES — are used to create items, track their activity status, and store item attributes that carry approval context. The HXC approval configuration tables, HXC_APPROVAL_COMPS, HXC_APPROVAL_PERIOD_COMPS, HXC_APPROVAL_PERIOD_SETS, HXC_APPROVAL_STYLES, HXC_APPROVAL_ITEM_KEY_S, and HXC_APP_PERIOD_SUMMARY, hold the approval rules, components, styles, period sets, and per-transaction approval summaries. HXC_AP_DETAIL_LINKS and HXC_ARCHIVE_TEMP support detail linkage and archival staging. FND_USER and FND_PROFILE_OPTION_VALUES supply approver identity and profile-driven behavior; FF_FORMULAS_F and HXC_BLD_BLK_INFO_TYPES/FF_FORMULAS_F are referenced for formula-based conditions and build information types. HXC_SELF_SERVICE_TIME_DEPOSIT is read and updated as the primary transaction of record for self-service time.

Usage Notes

HXC_APPROVAL_WF_PKG is not intended for direct invocation by customers. It is called by OTL's own components: HXC_FIND_NOTIFY_APRS_PKG (approver notification), HXC_NOTIFICATION_PROCESS_PKG (notification processing), HXC_SELF_SERVICE_TIME_DEPOSIT (self-service timecard submission), HXC_TIMECARD_APPROVAL (the timecard approval flow), and HXC_INTEGRATION_LAYER_V1_GRP (integration-layer group). These callers are triggered from the Time and Labor self-service pages and from the OTL approval concurrent programs that periodically scan submitted timecards for approval routing. Customizations that require modified approval behavior should be implemented through the supported configuration (approval styles, rules, components, and period sets) rather than by modifying this package, since it is an internal dependency of multiple OTL flows and changes to it risk breaking workflow integration across releases.