Search Results ce_security_profiles_gt




Overview
Explore in AI Chat

Overview

APPS.CE_STATEMENT_RECON_GT_V is a security-filtered reporting view over the Cash Management statement reconciliation data model in Oracle E-Business Suite. In release 12.1.1 and 12.2.2, it presents a subset of rows from CE_STATEMENT_RECONCILS_ALL, restricted to those bank statement reconciliation records that the currently connected application user is entitled to see based on their Cash Management security profile. The view is the principal mechanism by which statement reconciliation data is exposed through Oracle Forms, OAF pages, and concurrent programs without granting unrestricted access to the full reconciliation table.

The "_GT_V" naming convention reflects its dependency on a global temporary table, CE_SECURITY_PROFILES_GT, which is populated at runtime with the organization identifiers permitted for the active user session. The view therefore returns different row sets depending on the security context established when the session begins, making it a session-sensitive rather than fully deterministic object. Sub-ledger accounting, bank reconciliation, and cash positioning reports routinely reference this view to enforce organizational data isolation.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS-owned synonyms:

  • CE_STATEMENT_RECONCILS_ALL — the primary reconciliation table aliased as CSR, supplying statement line identifiers, reference information, status flags, amounts, and audit columns for every reconciliation record across all organizations.
  • CE_SECURITY_PROFILES_GT — the global temporary table aliased as OU and LE, containing the ORGANIZATION_ID values and ORGANIZATION_TYPE classifications that the current user is authorized to access.

The join establishes three alternative access paths combined with OR predicates: rows whose ORG_ID matches an authorized BUSINESS_GROUP or OPERATING_UNIT organization, rows whose LEGAL_ENTITY_ID matches an authorized LEGAL_ENTITY organization, and rows whose REFERENCE_TYPE is one of JE_LINE, ROI_LINE, or STATEMENT. The third path means journal line, reconciliation open interface line, and statement-level records are unconditionally visible, irrespective of the security profile contents, which is a deliberate design choice allowing users to review cross-organizational statement detail where the record type is inherently shared.

Key Columns

Common Use Cases and Queries

The dominant use case is enforcing Cash Management security in reconciliation inquiry screens and reports. A concurrent program submitting a reconciliation extract during a user session automatically inherits the profile restrictions placed on the global temporary table. Typical queries include:

  • Secure reconciliation listing: SELECT STATEMENT_LINE_ID, REFERENCE_TYPE, REFERENCE_ID, AMOUNT, STATUS_FLAG FROM CE_STATEMENT_RECONCIL_GT_V WHERE ORG_ID = :org_id;
  • Unreconciled or pending items for a legal entity: SELECT * FROM CE_STATEMENT_RECONCIL_GT_V WHERE LEGAL_ENTITY_ID = :le_id AND CURRENT_RECORD_FLAG = 'Y';
  • Audit of auto-reconciliation: SELECT JE_HEADER_ID, AMOUNT, AUTO_RECONCILED_FLAG FROM CE_STATEMENT_RECONCIL_GT_V WHERE AUTO_RECONCILED_FLAG = 'Y' AND CREATION_DATE > SYSDATE - 7;
  • Concurrent request traceability: SELECT REQUEST_ID, COUNT(*) FROM CE_STATEMENT_RECONCIL_GT_V GROUP BY REQUEST_ID;

Because the view relies on a populated CE_SECURITY_PROFILES_GT, direct SQL execution from tools such as SQL*Plus returns no rows unless the session has been initialised by the Cash Management security profile initialisation routine. Developers diagnosing missing rows should first verify that the global temporary table contains entries for the intended organization identifiers.