Results for “pooled_flag”

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

Overview

The CE_UPGA_BA_USES view is a reporting and integration object owned by the APPS schema within the Cash Management (CE) product family of Oracle E-Business Suite. It is classified in the ETRM metadata as a VALID VIEW whose stated purpose is to present a single-organization projection of the underlying multi-organization table CE_UPGA_BA_USES_ALL. In Oracle EBS multi-org architecture, an "_ALL" table stores rows across every operating unit, while a corresponding single-org view applies a runtime filter based on the session's organization context. CE_UPGA_BA_USES performs exactly this role: it exposes bank account usage records relative to the organization currently established in the user's session (typically held in the CLIENT_INFO environment variable for the Multi-Org views). The view therefore serves as the standard, org-secured access path for data describing the assignment of bank accounts to internal and external parties, and it is used by forms, concurrent programs, and custom reporting that must respect operating unit isolation.

Underlying Base Objects

The view is defined over a single referenced object, CE_UPGA_BA_USES_ALL, accessed via its synonym in the APPS schema. The "_ALL" suffix denotes the multi-org master table that physically holds bank account usage rows for all operating units. The view text is a straightforward projection of all columns from that base table, with a WHERE clause that enforces the organization filter. The filter logic uses NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99). This decodes the first ten characters of CLIENT_INFO (the current org ID) and matches it against the row's ORG_ID, defaulting both sides to -99 when no org context is available. Because no joins or aggregations are applied, the view is a one-to-one pass-through of qualifying rows.

Key Columns

The view exposes approximately forty-six columns. Central to account-usage identity are CE_BANK_ACCT_USE_ID, the primary key for a bank account use record; CE_UPGRADE_ID and PARENT_UPGRADE_ID, which support the upgrade conversion of bank account data; and UPGRADE_STATUS. The multi-org context is captured by ORG_ID and ORG_PARTY_ID; the latter, the subject of the user's search, identifies the party associated with the organization owning the account use, and is frequently joined to party-related tables (such as HZ_PARTIES) in integration and reconciliation queries. Usage flags include PRIMARY_FLAG, PRIMARY_ACCT_USE_FLAG, SECONDARY_ACCT_USE_FLAG, and the application-specific enable flags AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG, XTR_USE_ENABLE_FLAG, and PAY_USE_ENABLE_FLAG. Transaction defaults are held in EDISC_RECEIVABLES_TRX_ID, UNEDISC_RECEIVABLES_TRX_ID, and BR_STD_RECEIVABLES_TRX_ID. Operational attributes include POOLED_FLAG, END_DATE, DIRECT_DEBIT_AUTH_FLAG, and GROUP_ID. Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), the fifteen ATTRIBUTE flexfields and ATTRIBUTE_CATEGORY, plus concurrent request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), complete the structure.

Common Use Cases and Queries

Typical usage centers on org-scoped reporting of bank account assignments. A representative query retrieving account uses for the current organization and their associated party is:

SELECT CE_BANK_ACCT_USE_ID, ORG_ID, ORG_PARTY_ID,
       PRIMARY_FLAG, AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG,
       PAY_USE_ENABLE_FLAG, END_DATE
FROM   APPS.CE_UPGA_BA_USES
WHERE  ORG_PARTY_ID = :p_party_id
AND    NVL(END_DATE, SYSDATE) >= SYSDATE;

Because the view auto-filters by CLIENT_INFO, developers should initialize the org context through FND_CLIENT_INFO.SET_ORG_CONTEXT before querying, particularly in concurrent programs and OAF pages. The view is valuable when reconciling payments and receivables transaction defaults against bank accounts, when auditing which applications (AP, AR, XTR, PAY) may use a given bank account, and when migrating upgrade data tied to CE_UPGRADE_ID. Querying ORG_PARTY_ID directly supports integrations that must map bank account usage to Trading Community Architecture parties without traversing the full multi-org table.