Search Results xtr_user




Overview
Explore in AI Chat

Overview

CE_OA_UTIL is a small utility package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name associates it with the Cash Management (CE) product family, while the "OA" component and the presence of the XTR_USER function indicate that it was created to support Oracle Treasury (XTR) integration points within the E-Business Suite desktop and web-based forms. The package does not implement an application programming interface in the transactional sense; rather, it provides lightweight, reusable helper logic that other Cash Management or Treasury components can call to answer two recurring questions: whether a given application user is registered as a Treasury dealer, and whether a specific product is installed and available.

The header comment records a single source revision, ceoautlb.pls 120.0, dated 2004, which reflects the longevity and stability of the utility. The package contains only two functions and no procedures, making it one of the more compact utility units in the CE schema. Its low coupling — it is referenced by zero other packages according to the ETRM metadata — suggests it is consumed directly by forms-level or ad hoc code rather than forming part of a larger dependency graph.

Key Procedures and Functions

  • XTR_USER — Accepts a user identifier and returns a single-character flag indicating whether that user exists in the Treasury dealer codes table. The function counts matching rows; a count of zero yields 'N', and any non-zero count yields 'Y'. This allows calling code to gate Treasury-related functionality on whether the session user is an authorized dealer.
  • IS_INSTALLED — Accepts a product identifier and returns 'Y' or 'N' based on the product's installation status. It delegates to FND_INSTALLATION.get and treats the statuses 'I' (installed) and 'S' (shared) as installed, returning 'N' for any other status. This provides a convenient wrapper around the standard Oracle Application Object Library installation check.

No parameter lists beyond the identifiers shown in the source excerpt are invented here; the documented signatures are a numeric user ID and a numeric product ID respectively.

Tables Accessed

The only documented table reference is XTR_DEALER_CODES, accessed through an APPS synonym. The XTR_USER function issues a SELECT COUNT(1) against this table filtered by USER_ID. The table stores the mapping between E-Business Suite application users and Treasury dealer records, so querying it is the authoritative way to determine dealer eligibility. No INSERT, UPDATE, or DELETE operations are documented, confirming that CE_OA_UTIL is strictly a read-only utility. IS_INSTALLED does not query a table directly; it relies on the FND_INSTALLATION API, which resolves installation state from the applications system tables.

Usage Notes

CE_OA_UTIL is typically invoked from Oracle Forms and Oracle Application Framework pages within Cash Management and Treasury flows where a conditional decision about the current user or the availability of a product is required. A form might call XTR_USER during initialization to enable or disable dealer-specific fields, while IS_INSTALLED may be used to conditionally display functionality that depends on another product being licensed and installed. Because the package is not referenced by other PL/SQL packages, customizations and extensions should call it directly, using the APPS synonym, rather than relying on indirect invocation. Developers extending Treasury or Cash Management should treat these functions as stable, low-overhead helpers; they can be safely reused in custom concurrent programs, triggers, or personalization logic. As with any APPS-owned object, modifications should be avoided in favor of wrapping the documented calls in custom code.