Search Results check_object_function

Overview

IEU_DIAGNOSTICS_PVT is a private PL/SQL package in the APPS schema that supplies the application programming interfaces underpinning the Universal Work Queue (UWQ) Diagnostic Framework in Oracle E-Business Suite. Its declared purpose, recorded in the package header, is "to provide easy to use apis for UQW Diagnostic Framework," and the original source header ($Header: IEUVDFS.pls 115.11, dated 23-Apr-2004) confirms its lineage as a long-standing component of the interaction-center (IEU) product family. The package is classified as PVT, meaning it is not intended for direct invocation by external integrations; it is a supporting layer called by UWQ diagnostic forms, concurrent processing, and other framework code that must validate the environment before UWQ functionality can operate.

Functionally, the package answers a set of environment-verification questions: does the logged-in user map to a valid resource, does that user hold the correct responsibility with the correct application context, is the media type enabled, is the current server a valid UWQ server, and are the routing nodes correctly enumerated and refreshed? These checks collectively constitute the diagnostic surface for UWQ and are the reason the package appears in troubleshooting and health-check contexts in 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions. Their purposes are as follows. IS_RESOURCEID_EXIST verifies whether a resource identifier exists for a supplied user name. CHECK_USER_RESP validates that a named user holds a given responsibility and returns the associated user, responsibility, and application identifiers. CHECK_OBJECT_RESP performs the analogous validation for a responsibility against a specific object. DETERMINE_MEDIA_ENABLED establishes whether the configured UWQ media type is active. DETERMINE_VALID_SERVER and GET_VALID_NODES determine whether the current server and its nodes qualify as valid UWQ targets. CHECK_PROFILE_OPTIONS inspects the relevant profile option settings, and CHECK_NODE_ENUMERATION and GET_VALID_RT_NODES inspect routing-node enumerators and valid runtime nodes. CHECK_REFRESH_NODE_COUNTS and REFRESH_NODE are the node-refresh pair: the former assesses whether node counts require refreshing, and REFRESH_NODE performs the refresh operation — this is the procedure most directly associated with the "refresh_node" search term. CHECK_VIEW, CHECK_TASK_LAUNCHING, and CHECK_OBJECT_FUNCTION complete the set, covering view availability, task-launching configuration, and object-function checks respectively. Parameter lists are intentionally not restated here; the documented signatures use the standard x_return_status, x_msg_count, and x_msg_data OUT parameters for error propagation.

Tables Accessed

The package reads and writes a defined set of FND and IEU tables through APPS synonyms. FND_USER, FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL, and FND_APPLICATION_TL support the user, responsibility, and application validation routines. FND_PROFILE_OPTIONS supplies the profile values inspected by CHECK_PROFILE_OPTIONS, while FND_LOOKUP_VALUES provides lookup-driven configuration. Server-side definitions come from IEO_SVR_GROUPS and IEO_SVR_SERVERS. The UWQ-specific tables — IEU_UWQ_MEDIA_TYPES_B and _TL, IEU_UWQ_RES_CATS_B, IEU_UWQ_RTNODE_BIND_VALS, IEU_UWQ_SEL_ENUMERATORS, IEU_UWQ_SEL_RT_NODES, and IEU_UWQ_SVR_MPS_MMAPS — hold media types, resource categories, routing-node bindings, enumerators, selected runtime nodes, and server-to-media-type mappings that the diagnostic and refresh routines evaluate and update.

Usage Notes

IEU_DIAGNOSTICS_PVT is referenced by zero other packages in the ETRM dependency data, confirming that it is invoked directly from UWQ diagnostic forms and administrative flows rather than from a shared call chain. The REFRESH_NODE and CHECK_REFRESH_NODE_COUNTS procedures are typically triggered when UWQ nodes appear stale or missing after configuration changes to responsibilities, media types, or server mappings. Because the package is AUTHID CURRENT_USER and classified PVT, custom code should not call it directly; administrators should use the supported UWQ diagnostic screens instead. The package is unchanged in intent between 12.1.1 and 12.2.2.