Search Results stmt_cyc

Overview

OKL_CS_CUST_ACCT_OVERVIEW_UV is an Oracle E-Business Suite 12.1.1 and 12.2.2 reporting view owned by the APPS schema. It presents a consolidated, user-facing picture of customer accounts as used within the Oracle Lease and Finance Management (OLFM) and Oracle Contracts Service modules, built on top of the Trading Community Architecture (TCA) customer model.

The view joins the customer account registry in HZ_CUST_ACCOUNTS to the customer profile in HZ_CUSTOMER_PROFILES, enriching the result with decoded lookup descriptions, payment term names, and statement cycle names. Because it is a read-only view rather than a base table, it is intended for inquiry, reporting, and integration consumption rather than transactional data manipulation. Downstream leases, contracts, invoices, and collections processes reference the account attributes exposed here — status, payment terms, statement cycle, balances, and lifecycle dates — making the view a convenient single source for account-level context in ETRM (Oracle Lease Management) reporting.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

• HZ_CUST_ACCOUNTS (SYNONYM) — The primary source for account identity, numbering, status, type, class, tax attributes, balance, and lifecycle dates.
• HZ_CUSTOMER_PROFILES (SYNONYM) — Supplies the profile-level attributes, most notably STATEMENT_CYCLE_ID, which links the account to its billing statement cycle.
• AR_STATEMENT_CYCLES (SYNONYM) — The Receivables statement cycle definition table, joined to resolve the statement cycle name. This is the table addressed by the user's search term stmt_cyc.
• AR_LOOKUPS (VIEW) — Used to decode the account status code into a descriptive value (ACCOUNT_STATUS_DESCRIPTION).
• RA_TERMS_TL (SYNONYM) — Provides the translated payment term name (PAYMENT_TERM_NAME) matching the account's PAYMENT_TERM_ID.

The view is a denormalized projection: for each customer account it returns one row (keyed on ROWID and CUST_ACCOUNT_ID) with the associated profile, term, and cycle descriptors resolved by outer joins.

Key Columns

• CUST_ACCOUNT_ID / ACCOUNT_NUMBER — Primary identifier and the human-readable account number.
• PARTY_ID / ORG_ID — TCA party reference and operating unit.
• STATUS / ACCOUNT_STATUS_DESCRIPTION — Status code and its AR_LOOKUPS description.
• CUSTOMER_TYPE / CUSTOMER_CLASS_CODE / SUBCATEGORY_CODE — Classification attributes. CATEGORY_CODE, THIRD_PARTY_FLAG, and COMPETITOR_FLAG are returned as NULL, retained for legacy interface compatibility.
• PAYMENT_TERM_ID / PAYMENT_TERM_NAME — Payment term identifier and its translated name from RA_TERMS_TL.
• STATEMENT_CYCLE_ID / STATEMENT_CYCLE_NAME — The profile statement cycle and its name from AR_STATEMENT_CYCLES; this is the column pair referenced by the stmt_cyc search.
• CURRENT_BALANCE — Account balance at the time of query.
• ACCOUNT_ESTABLISHED_DATE / ACCOUNT_ACTIVATION_DATE / ACCOUNT_TERMINATION_DATE / SUSPENSION_DATE — Lifecycle dates used for aging and status reporting.
• WRITE_OFF_AMOUNT / WRITE_OFF_PAYMENT_AMOUNT / WRITE_OFF_ADJUSTMENT_AMOUNT — Write-off values for collection analysis.
• ATTRIBUTE_CATEGORY through ATTRIBUTE20, plus WHO columns — Descriptive flexfield segments and audit columns.

Common Use Cases and Queries

Typical uses include statement-cycle-driven billing audits, payment-term reconciliation, and account status reporting for leasing portfolios.

List accounts grouped by statement cycle (the stmt_cyc scenario):

SELECT statement_cycle_name,
       COUNT(*) accounts,
       SUM(current_balance) total_balance
  FROM apps.okl_cs_cust_acct_overview_uv
 GROUP BY statement_cycle_name
 ORDER BY statement_cycle_name;

Retrieve accounts on a specific cycle with payment terms and status:

SELECT cust_account_id, account_number, account_name,
       statement_cycle_name, payment_term_name,
       account_status_description, current_balance
  FROM apps.okl_cs_cust_acct_overview_uv
 WHERE statement_cycle_id = :p_cycle_id;

Because the view is externalized across five base objects, confirm that the APPS synonyms and grants are valid in the target environment; performance is best when filtering on CUST_ACCOUNT_ID, ORG_ID, or STATEMENT_CYCLE_ID, which align with indexed base-table keys.