Search Results cse_utility_grp
Overview
APPS.CSE_UTILITY_GRP is a utility package belonging to the Oracle E-Business Suite CSE (Enterprise Asset Management / eAM) product family. It is classified in the ETRM metadata as a GRP (group) package, a designation reserved for modules that aggregate shared helper routines rather than exposing business object APIs. In Oracle EBS 12.1.1 and 12.2.2, packages of this type provide lightweight, cross-cutting services consumed by other packages and forms within the same product schema.
The specific business function served by CSE_UTILITY_GRP is the detection of whether the Electronic Interface BoM (EIB) integration mechanism is currently active within the CSE application environment. EIB is the inbound interface used to load asset, work order, and maintenance data from external systems. Rather than allowing each consumer to inspect configuration flags independently, this package centralizes that determination behind a stable programmatic entry point. The package is declared with AUTHID CURRENT_USER, meaning that at runtime its SQL executes under the privileges of the invoking session rather than as the definer, a pattern consistent with utility packages that must respect the caller's security context.
Key Procedures and Functions
The ETRM metadata documents a single program unit in this package:
- IS_EIB_ACTIVE — A function returning BOOLEAN that reports whether the EIB (Electronic Interface BoM) facility is enabled and active. Consumers use the returned value to branch logic: when the function evaluates true, EIB-dependent processing paths are permitted; when false, callers bypass or suppress that functionality. The BOOLEAN return type is characteristic of PL/SQL-internal utility APIs that are invoked from other server-side code rather than from forms or concurrent program definitions, which cannot directly consume PL/SQL BOOLEAN values. No parameter list is documented for this function.
No other procedures or functions are recorded in the 12.2.2 documentation set for this package. The header comment indicates a revision level of 120.0 dated 2006, suggesting the unit has been stable across the 11i through 12.2 release lines with minimal change.
Tables Accessed
The documented metadata lists no tables referenced via APPS synonyms. This is consistent with the package's role as a pure decision utility: IS_EIB_ACTIVE most plausibly resolves its answer from profile option values, package state, or system parameters retrieved through helper calls rather than by directly querying application tables. Because no base tables are documented, implementers should not assume any dependency on CSE asset, work order, or interface staging tables. Any database access performed indirectly occurs through other called packages or through profile option retrieval, neither of which surfaces as a direct table reference in the ETRM catalog.
Usage Notes
CSE_UTILITY_GRP is not exposed as a form-level API or a concurrent program executable. It is an internal support package intended for invocation from other PL/SQL units and, occasionally, from custom code extending CSE functionality. The metadata confirms that it is referenced by one other package, which is the primary consumer of IS_EIB_ACTIVE.
- Forms: Not directly invoked. CSE forms that trigger EIB-aware behavior call the referencing package, which in turn calls this utility.
- Concurrent programs: Not registered as a concurrent executable. EIB-related concurrent programs may indirectly depend on its result through their PL/SQL logic.
- Custom code: Developers extending CSE can call APPS.CSE_UTILITY_GRP.IS_EIB_ACTIVE to align custom logic with standard EIB enablement behavior. Because the function returns BOOLEAN, it must be consumed within PL/SQL; custom code that needs a SQL-visible or form-visible result should wrap the call accordingly.
Given the AUTHID CURRENT_USER declaration, callers must ensure their session has whatever privileges the underlying determination requires. Because documentation is limited to a single function, any behavior beyond EIB activity detection should not be attributed to this package.
-
PACKAGE: APPS.CSE_UTILITY_GRP
12.2.2
-
PACKAGE BODY: APPS.CSE_UTILITY_GRP
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSE_UTILITY_GRP, status:VALID,
-
PACKAGE: APPS.CSE_UTILITY_GRP
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSE_UTILITY_GRP, status:VALID,
-
PACKAGE: APPS.CSE_UTILITY_GRP
12.1.1
-
PACKAGE: APPS.CSE_UTILITY_GRP
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSE_UTILITY_GRP, status:VALID,
-
PACKAGE BODY: APPS.CSE_UTILITY_GRP
12.1.1
-
PACKAGE BODY: APPS.CSE_UTILITY_GRP
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSE_UTILITY_GRP, status:VALID,
-
PACKAGE BODY: APPS.CSE_UTILITY_GRP
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.PA_NL_INSTALLED
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PA_NL_INSTALLED, status:VALID,
-
PACKAGE BODY: APPS.PA_NL_INSTALLED
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PA_NL_INSTALLED, status:VALID,
-
PACKAGE BODY: APPS.PA_NL_INSTALLED
12.2.2
-
PACKAGE BODY: APPS.PA_NL_INSTALLED
12.1.1
-
APPS.PA_NL_INSTALLED dependencies on CSE_UTILITY_GRP
12.1.1
-
APPS.CSE_UTILITY_GRP dependencies on CSE_UTILITY_GRP
12.2.2
-
APPS.CSE_UTILITY_GRP dependencies on CSE_UTILITY_GRP
12.1.1
-
APPS.PA_NL_INSTALLED dependencies on CSE_UTILITY_GRP
12.2.2
-
PACKAGE: APPS.FND_PROFILE
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FND_PROFILE, status:VALID,
-
PACKAGE: APPS.FND_PROFILE
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_PROFILE, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,