Search Results bind_group_id

Overview

ISC_MAINT_RPT_UTIL_PKG (header revision iscmaintrptutils.pls 120.1, dated 13-SEP-2005) is an Oracle E-Business Suite utility package owned by APPS and classified under the ETRM API taxonomy as OTHER. It supports the Enterprise Asset Management (eAM) maintenance reporting infrastructure by providing reusable PL/SQL building blocks that maintenance analytics reports invoke at runtime. The package centralizes the definition of pseudo dimension-level identifiers used by the maintenance reporting engine: constants such as G_ORGANIZATION, G_CURRENCY, G_DEPARTMENT, G_ASSET_GROUP, G_ASSET_NUMBER, G_ACTIVITY, G_COST_CATEGORY, G_COST_ELEMENT, G_WORK_ORDER_TYPE, G_LATE_CMPL_AGING, G_PAST_DUE_AGING, G_ASSET_CATEGORY, G_ASSET_CRITICALITY, G_REQUEST_TYPE, G_REQ_CMPL_AGING, G_WORK_ORDER_STATUS, and G_RESOURCE each encode a physical dimension plus a specific dimension level (for example, 'BIV_MAINT_ASSET+BIV_MAINT_ASSET_GROUP_LVL'). The header comments explicitly instruct developers to reference these constants rather than hard-coding dimension strings, ensuring consistency between report definitions and the underlying report metadata. Beyond constants, the package supplies runtime services for parameter processing, dynamic SQL construction, detail column management, view-by/drill-down handling, and row-level security.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. REGISTER_DIMENSION_LEVELS and ADD_VIEW_BY participate in declaring report dimensions and configuring the "view by" axes available to a report. PROCESS_PARAMETERS, GET_PARAMETER_VALUE, GET_PARAMETER_ID, and DUMP_PARAMETERS handle report parameters: binding them, resolving a parameter's identifier or current value, and emitting parameter state for diagnostics. ADD_DETAIL_COLUMN, GET_DETAIL_COLUMN, CHANGE_COLUMN, RATE_COLUMN, GET_INNER_SELECT_COL, and ADD_ASSET_GROUP_COLUMN manage the column set of a report — adding, retrieving, transforming, or computing columns, including the inner SELECT projection used to assemble detail SQL. DETAIL_SQL and GET_DRILL_DETAIL generate the SQL text for the main report and its drill-down detail view respectively. GET_SEC_WHERE_CLAUSE builds the row-level security predicate appended to report queries. BIND_GROUP_ID — the object associated with the search term "bind_group_id" — is the routine responsible for establishing the bind group identifier used to associate runtime bind variables with a report execution, so that dynamically constructed SQL can be parsed and executed consistently within the report framework.

Tables Accessed

Per the documented metadata, the package references only the APPS synonyms DBMS_SQL and PLITBLM. DBMS_SQL is Oracle's built-in dynamic SQL package, consistent with the package's role in constructing and executing report SQL at runtime (DETAIL_SQL, GET_INNER_SELECT_COL, GET_SEC_WHERE_CLAUSE). PLITBLM is the PL/SQL internal table (associative array) support package, used here for passing and manipulating collections of parameter or column values. No application data tables are documented as direct references; eAM reporting data reaches the package indirectly through the SQL fragments it assembles against the BIV_MAINT_* reporting views and dimensions named in the constants (for example, BIV_MAINT_ASSET, BIV_MAINT_ACTIVITY, BIV_MAINT_CST_CATEGORY, BIV_MAINT_AGING, BIV_MAINT_WK_ORDER_STATUS).

Usage Notes

The package is a supporting utility rather than an end-user API: it is invoked by the eAM maintenance reporting framework and by six other documented packages that depend on it. It therefore executes in the context of report generation — typically triggered from Oracle Forms-based report launch pages, from concurrent programs that produce maintenance reports, or from custom code that reuses the standard report engine. Because its procedures manipulate dynamic SQL and bind state (notably BIND_GROUP_ID), callers should follow the same invocation sequence as the seeded reporting framework rather than calling individual routines in isolation. The package is marked NOSHIP in its header, indicating it is not a standalone shipped deliverable but part of the internal reporting stack; it exists in both 12.1.1 and 12.2.2 environments. Customizations should prefer the exposed constants and routines over direct references to dimension names or report metadata, and any modification should be treated as an upgrade-sensitive change to the APPS schema.