Search Results ce_fc_xtr_disc_v




Overview
Explore in AI Chat

Overview

CE_FC_XTR_DISC_V is a Cash Management (CE) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a discovery (DISC) view designed to expose external cash flow transaction data sourced from the Treasury module, filtered by the legal entity access controls defined in the user's security profile. The view is a thin projection over CE_XTR_CASHFLOWS_V, applying Oracle's multi-org and function security model so that users see only cash flows belonging to legal entities they are authorized to access.

Its role in Oracle EBS reporting and integration is to provide a pre-joined, security-aware data source for external reporting tools, ad-hoc queries, custom concurrent programs, and integration extracts that need deal-level cash flow information without embedding their own access-control logic. Because the security filtering is encapsulated within the view definition, downstream reports automatically inherit legal entity restrictions, reducing the risk of data leakage across organizations.

Underlying Base Objects

The documented base object for CE_FC_XTR_DISC_V is CE_XTR_CASHFLOWS_V, itself a view over Treasury cash flow data. The view's WHERE clause enforces access control through a correlated EXISTS subquery against CE_SECURITY_PROFILES_V, testing the source organization identifier and a legal entity organization type.

Supporting objects and packages referenced by the underlying stack include:

  • CE_SECURITY_PROFILES_V — supplies the authorized organization and organization-type combinations for the current user.
  • CE_XTR_CASHFLOWS_V — the primary cash flow source supplying all displayed columns.
  • FND_ACCESS_CONTROL_UTIL — utility package used by the security views to resolve accessible data sets.
  • FND_GLOBAL and FND_PROFILE — supply session context such as user, responsibility, and organization profile values.
  • MO_GLOBAL — supports multi-org initialization and operating unit context.
  • XTR_USER_ACCESS — Treasury user access package underpinning visibility rules for Treasury instruments.

The relationship is therefore one of composition: CE_FC_XTR_DISC_V adds a security predicate and a column projection to CE_XTR_CASHFLOWS_V, which in turn resolves deal, counterparty, and amount attributes from Treasury data structures.

Key Columns

  • REFERENCE_ID — the source reference identifier, converted to character with TO_CHAR. Used for joining back to the originating Treasury transaction.
  • DEAL_NUMBER — the Treasury deal number associated with the cash flow.
  • TRX_AMOUNT — the transaction amount; mapped from SRC.AMOUNT in the view text.
  • BANK_ACCOUNT_AMOUNT — the amount reflected at the bank account level; also mapped from SRC.AMOUNT.
  • DEAL_TYPE — the deal type name (DDA_DEAL_TYPE_NAME), for example the instrument category.
  • DEAL_SUBTYPE — the deal subtype name (DDA_DEAL_SUBTYPE_NAME), providing finer classification.
  • COUNTERPARTY — the counterparty associated with the deal.
  • AMOUNT_TYPE — the amount type name, distinguishing principal, interest, and similar components.
  • TRANSACTION_NUMBER — the transaction number for reconciliation and traceability.

Common Use Cases and Queries

Typical scenarios include legal-entity-scoped cash flow reporting, Treasury deal reconciliation against bank statements, and feeds into custom cash forecasting extracts.

  • Listing all cash flows visible to the current user: 
    SELECT reference_id, deal_number, trx_amount, counterparty
FROM   apps.ce_fc_xtr_disc_v;
  • Filtering by deal type and amount threshold: 
    SELECT deal_number, deal_type, deal_subtype, trx_amount
FROM   apps.ce_fc_xtr_disc_v
WHERE  deal_type = 'CURRENCY'
AND    trx_amount > 1000000;
  • Joining to a Treasury detail table on the reference identifier: 
    SELECT d.deal_number, d.counterparty, d.trx_amount
FROM   apps.ce_fc_xtr_disc_v d
WHERE  d.reference_id = :reference_id;
  • Aggregating exposure by counterparty: 
    SELECT counterparty, SUM(trx_amount) total_amt
FROM   apps.ce_fc_xtr_disc_v
GROUP  BY counterparty;

Because access control is embedded, no additional organization predicate is usually required; multi-org session initialization through MO_GLOBAL and the relevant profile options must still be established before querying.