Search Results check_district_filter

Overview

The PL/SQL package body APPS.ISC_FS_RPT_UTIL_PKG is a reporting utility package in Oracle E-Business Suite, owned by the APPS schema and validated in both 12.1.1 and 12.2.2. It belongs to the ETRM/ISC (Enterprise Territory and Resource Management, formerly Incentive Compensation and field service reporting) reporting framework, and is classified as an OTHER API rather than a public, concurrency-safe interface. Its purpose is to provide shared helper routines to the ISC reporting suite: constructing dynamic SQL, registering dimension and level metadata, resolving report parameters, binding drill-down context, and generating the WHERE-clause fragments that drive the ISC_FS_002_MV materialized view and its related report pages. The package exposes 28 documented procedures and functions, and it is referenced by 10 other database objects, indicating that it functions as a common library for the ISC reporting stack rather than as a standalone entry point.

Key Procedures and Functions

The documented program units group into several functional clusters:

• Parameter handling: REGISTER_DIMENSION_LEVELS, PROCESS_PARAMETERS, GET_PARAMETER_VALUE, GET_PARAMETER_ID, and DUMP_PARAMETERS register, resolve, and diagnose report parameters and dimension level definitions.
• Column and SQL construction: ADD_DETAIL_COLUMN, GET_DETAIL_COLUMN, DETAIL_SQL, CHANGE_COLUMN, RATE_COLUMN, and GET_INNER_SELECT_COL build and inspect the dynamic select lists used by the reporting engine.
• Grouping and view-by: BIND_GROUP_ID, ADD_VIEW_BY, and BIND_LOW_HIGH associate the report with grouping identifiers and view-by ranges.
• Security and filtering: GET_SEC_WHERE_CLAUSE generates the security predicate applied to report data, while CHECK_DISTRICT_FILTER validates district-level filtering.
• Drill-down navigation: GET_CATEGORY_DRILL_DOWN, GET_DISTRICT_DRILL_DOWN, and GET_SR_DETAIL_PAGE_FUNCTION resolve the drill-down targets and page functions for category, district, and service-request detail views.
• Bind parameters: ADD_CUSTOM_BIND_PARAMETER extends the bind variable set for dynamic SQL generated by DBMS_SQL.

Tables Accessed

The package does not maintain application data tables of its own. Its documented table references are DBMS_SQL and PLITBLM, accessed through APPS synonyms; the latter is the PL/SQL table/index-by table utility used for bind and parameter collections, and the former underpins dynamic SQL parsing, binding, and execution. In addition, the package depends on ISC_FS_002_MV, the materialized view supplying the report's underlying data. Reporting metadata and parameter structures are supplied by the BIS layer: BIS_BUCKET_PUB, BIS_PMV_PARAMETERS_PUB, BIS_PMV_PAGE_PARAMETER_REC/TBL, BIS_QUERY_ATTRIBUTES(_TBL), and BIS_UTILITIES_PUB. Formatting and messaging rely on FND_DATE and FND_MESSAGE, while territory/incentive reporting is served via JTF_RS_DBI_CONC_PUB, POA_DBI_TEMPLATE_PKG, and POA_DBI_UTIL_PKG. The package itself is not referenced by any database object, but it references itself internally.

Usage Notes

ISC_FS_RPT_UTIL_PKG is not intended for direct invocation by end users. It is called from within the ISC reporting layer—typically the concurrent programs, OAF pages, or packaged report drivers that render ISC field service and dashboard reports—and from the 10 dependent database objects that consume its utility routines. Because it manipulates dynamic SQL through DBMS_SQL and relies on BIS parameter tables, callers must initialize the BIS report parameter context and any bucket definitions before invoking the SQL-building routines. The GET_SEC_WHERE_CLAUSE, CHECK_DISTRICT_FILTER, and drill-down functions are the standard hooks used to enforce responsibility-level data security and to wire drill-down navigation. Customizations should avoid modifying this package directly; the supported extension points are the custom bind parameter and detail column routines, which allow additional columns or binds to be introduced without altering the core reporting logic.