Search Results check_ba_security

Overview

APPS.CEP_STANDARD is a foundational utility package within the Oracle E-Business Suite Cash Management (CE/CEP) module. Its primary responsibility is to provide shared, reusable services that other Cash Management packages depend upon, most notably diagnostic debugging infrastructure, session-title construction, effective-date derivation for bank transactions, and security initialization logic for the Cash Management user interface. The package header carries the patch-level constant G_patch_level, historically stamped '11.5.CE.J', reflecting its long lineage from earlier EBS releases through 12.1.1 and 12.2.2. Because it is referenced by approximately 85 other packages, CEP_STANDARD functions as a cross-cutting utility layer rather than a transaction-processing routine. The search term init_security_baui maps directly to INIT_SECURITY_BAUI, a procedure that establishes security context for the Bank Account User Interface (BAUI), indicating the package plays a role in enforcing Cash Management security profiles at the point of user interaction.

Key Procedures and Functions

• RETURN_PATCH_LEVEL — Returns the current patch level string for the package, used for version verification and diagnostics.
• DEBUG — Emits a line of text to DBMS_OUTPUT or to a file when debug mode is enabled, supporting client-side logging.
• ENABLE_DEBUG — Activates run-time debugging, optionally directing output to a specified path and file name.
• DISABLE_DEBUG — Deactivates debugging and optionally displays collected debug information.
• GET_WINDOW_SESSION_TITLE — Constructs a window session title, accepting organization and legal entity identifiers, for display in the application UI.
• GET_EFFECTIVE_DATE — Derives an effective date from bank account, transaction code, and receipt date inputs, supporting bank account transaction validation.
• DEBUG_MSG_STACK — Displays debug messages held on the message stack, using message count and message data parameters.
• SQL_ERROR — Provides standardized SQL error handling and reporting.
• GET_UMX_PREDICATE — Builds a UMX (User Management) predicate, likely for security-based row filtering.
• CHECK_BA_SECURITY — Validates bank account security, checking user access against configured security profiles.
• GET_CONVERSION_RATE — Retrieves currency conversion rates, supporting multi-currency Cash Management processing.
• INIT_SECURITY — Initializes the general security context for Cash Management operations.
• INIT_SECURITY_BAUI — Initializes security specifically for the Bank Account User Interface, establishing the profile-based access context before account data is presented or modified.

Tables Accessed

• CE_SECURITY_PROFILES_GT — Global temporary table holding security profile data used during access checks.
• CE_SYSTEM_PARAMETERS — Provides Cash Management system-level setup values.
• CE_TRANSACTION_CODES — Supplies transaction code definitions referenced by effective-date and rate lookups.
• FND_APPLICATION and FND_PRODUCT_GROUPS — Used to resolve application and product group context.
• HR_ALL_ORGANIZATION_UNITS and HR_ORGANIZATION_INFORMATION — Supply organizational and legal entity details for session titles and security resolution.
• XLE_ENTITY_PROFILES — Provides legal entity profile data supporting security and effective-date logic.
• DBMS_SQL — Used for dynamic SQL execution supporting flexible predicate and security queries.

Usage Notes

CEP_STANDARD is invoked indirectly by Cash Management forms, concurrent programs, and the roughly 85 dependent packages rather than being called directly by end users. The security initialization routines, particularly INIT_SECURITY_BAUI, are typically called during form initialization or bank account query processing to establish row-level access based on security profiles. The debug procedures are used throughout development, diagnostics, and support scenarios, allowing tracing without code changes. Custom code extending Cash Management should reuse these utilities rather than reimplementing effective-date, security, or conversion-rate logic, ensuring consistency with standard EBS behavior across 12.1.1 and 12.2.2.