Results for “ap_default_settlement_flag”

34 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_BANK_ACCT_USES_LE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Cash Management (CE) product family. It exposes bank account use assignments that are specifically tied to legal entities, providing a filtered perspective over the transactional CE_BANK_ACCT_USES_ALL table. The view is documented as VALID in ETRM 12.1.1 and 12.2.2 and is intended for reporting and integration scenarios where only active, legal-entity-scoped bank account uses with external transaction (XTR) processing enabled are relevant.

Because the view enforces legal entity and date-range predicates internally, it is a convenient data source for settlement, treasury, and reconciliation reporting that must respect legal entity boundaries without requiring every query to re-implement the same filters.

Underlying Base Objects

The view is defined over two primary sources: CE_BANK_ACCT_USES_ALL (synonym) aliased as BAU, and CE_SECURITY_PROFILES_V (a view) aliased as LE. The join links BAU.LEGAL_ENTITY_ID to LE.ORGANIZATION_ID, with LE.ORGANIZATION_TYPE restricted to 'LEGAL_ENTITY'. In addition, an EXISTS subquery against CE_BANK_ACCOUNTS (synonym) ensures that the parent bank account is currently effective based on START_DATE and END_DATE.

Supporting infrastructure objects include FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS packages, which underpin security profile evaluation and multi-org context. Effectively, the view merges the bank account use record with legal entity security visibility and current-date validity.

Key Columns

  • BANK_ACCT_USE_ID / BANK_ACCOUNT_ID – Primary identifiers linking the use assignment to its parent bank account.
  • LEGAL_ENTITY_ID / ORG_ID / ORG_PARTY_ID – Legal entity and operating unit context for the assignment.
  • AP_USE_ENABLE_FLAG – Indicates whether the account is enabled for Payables.
  • AP_DEFAULT_SETTLEMENT_FLAG – Flags the account as the default settlement account for Payables, the column most commonly referenced by users searching this view.
  • XTR_USE_ENABLE_FLAG – Must equal 'Y' for a row to appear in the view; enables treasury use.
  • XTR_DEFAULT_SETTLEMENT_FLAG – Default settlement indicator for treasury transactions.
  • AR_USE_ENABLE_FLAG / PAY_USE_ENABLE_FLAG – Receivables and Payroll enablement indicators.
  • PRIMARY_FLAG – Identifies the primary use record for the account.
  • END_DATE – Effective end date of the use assignment; rows are only returned when SYSDATE is within the effective window.
  • Attribute1–15, REQUEST_ID, PROGRAM_ID – Descriptive flexfield and concurrent program audit columns inherited from the base table.

Common Use Cases and Queries

The view is frequently queried to identify default Payables settlement accounts per legal entity, to validate treasury-enabled bank accounts, and to drive reconciliation or cash positioning reports.

Locating default Payables settlement accounts for a legal entity:

  • SELECT bank_account_id, legal_entity_id, ap_default_settlement_flag FROM ce_bank_acct_uses_le_v WHERE ap_default_settlement_flag = 'Y';

Listing all active treasury-enabled accounts with their legal entity names:

  • SELECT b.bank_account_name, u.ap_default_settlement_flag, u.xtr_default_settlement_flag FROM ce_bank_acct_uses_le_v u, ce_bank_accounts b WHERE u.bank_account_id = b.bank_account_id;

Confirming whether a specific account is the default settlement account in Payables before configuring payment documents or treasury transactions.

Because the view already applies security profile and effective-date filtering, it is preferred over CE_BANK_ACCT_USES_ALL for legal-entity-oriented reporting. Note that rows require XTR_USE_ENABLE_FLAG = 'Y', so AP-only use assignments without treasury enablement will not be returned.