Search Results get_events_full_refresh_flag

Overview

HRI_BPL_CONC_ADMIN is an Oracle EBS Applications (APPS) package classified under the "OTHER" API category. Its name — Business Process Library Concurrent Administration — indicates that it functions as a centralized administrative and control utility for the concurrent processing and data-refresh infrastructure associated with Oracle HR Intelligence (HRI) and related Business Intelligence/HR analytics components. Rather than exposing business transactions to end users, this package supplies internal services that govern how refresh operations, request sets, and event-processing jobs are configured and retrieved.

The package belongs to the HRI_BPL (Business Process Library) family and is referenced by three other packages, confirming its role as a shared, low-level dependency rather than a top-level entry point. It combines refresh-flag lookups, global date retrieval, and request-set metadata resolution into a single administrative interface. The documented header carries a version stamp of 120.5 (2006), reflecting a long-standing, stable internal component that predates later 12.1.1/12.2.2 releases and has been carried forward largely unchanged.

Key Procedures and Functions

• get_full_refresh_flag — Returns a VARCHAR2 indicator describing whether a full refresh is required for a given table. Accepts a table name as input and resolves the corresponding refresh directive.
• get_full_refresh_code — Returns a VARCHAR2 code value for the full-refresh state of a specified table, providing a coded counterpart to the flag function above.
• get_events_full_refresh_flag — Returns a VARCHAR2 flag indicating whether a full refresh is required for the events processing stream. Unlike the table-specific functions, it applies globally to events.
• get_hri_global_start_date — Returns a DATE representing the global start date used across HRI refresh or processing logic, anchoring operations to a common baseline.
• get_request_set_details — The procedure matching the user's search term. It is an OUT-parameter procedure that retrieves the details of a request set, returning the request set identifier, the application identifier, the refresh mode, and a page list collection (page_list_tab_type, built from page_list_rec_type records containing page owner, page name, and page type). This is the primary extraction routine for request-set configuration data.

Tables Accessed

The documented dependencies explain how these routines obtain their results:

• BIS_REQUEST_SET_OBJECTS and BIS_REQUEST_SET_OPTIONS — Source the request-set membership and option data used by get_request_set_details.
• FND_CONCURRENT_REQUESTS — Provides concurrent request context, associating refresh operations with their submitted jobs.
• FND_LOOKUP_VALUES — Supplies lookup-based validation, most likely for refresh mode or code resolution.
• HRI_CL_WKR_SUP_STATUS_CT, HRI_CS_SUPH, and HRI_MB_ASGN_EVENTS_CT — HRI-specific summary and event-change tables linked to the worker/supervisor and assignment event refresh streams referenced by the events refresh and global start-date functions.

Usage Notes

Because this is an internal administrative package, it is typically invoked by other HRI packages, concurrent programs, and refresh-processing routines rather than from standard forms. Custom code should treat it as read-oriented: the functions return refresh flags, codes, and global dates, while get_request_set_details populates caller-declared OUT variables and a page list collection. Developers integrating with it must declare the page_list_tab_type collection to receive the page list output. The three referencing packages indicate the standard consumption pattern is orchestration of HRI refresh activity, where this package supplies configuration metadata to drive downstream processing decisions.