Search Results cp_cust




Overview
Explore in AI Chat

Overview

VIEW APPS.CE_AR_FC_INVOICES_V is a receivables reporting view used within Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes open Accounts Receivable transactions together with their associated customer profile class information, combining invoice-level payment schedule data with the Customer Relationship Management profile hierarchy. The view is designed to supply the data set required by customer profile ("FC") collection logic, whereby open invoices and debit memos are matched to the profile class that governs collections, credit, and dunning behavior.

Because the view filters on payment schedule status and excludes specific transaction classes, it returns only currently open, collectible receivables. Its role is primarily reporting and integration: it is consumed by collections and credit modules, by customer-facing inquiries, and by external extract processes that require open invoice detail keyed by customer profile class.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms and the AR public utility package:

  • AR_PAYMENT_SCHEDULES_ALL — the primary table, aliased APS, supplying invoice number, amounts, currency, due date, transaction identifiers, and organization identifiers. Only rows with STATUS = 'OP' and CLASS not in ('PMT','GUAR') qualify.
  • HZ_CUSTOMER_PROFILES — aliased CP_CUST and CP_SITE, providing the customer or site-level profile assignment.
  • HZ_CUST_PROFILE_CLASSES — aliased CP_CLASS, supplying the profile class identifier and class name.
  • AR_PUBLIC_UTILS — a PL/SQL package whose Check_Prepay_Transaction function is invoked to exclude prepayment transactions.

The view body is a UNION of two branches. The first joins on CUSTOMER_SITE_USE_ID to resolve site-level profiles. The second joins on CUST_ACCOUNT_ID and requires that the customer-level profile row have a null SITE_USE_ID, guaranteeing that a site-level profile does not already exist for the transaction. The second branch additionally applies a NOT EXISTS subquery that suppresses duplicate rows where a site-level profile already matches the same transaction and due date.

Key Columns

Common Use Cases and Queries

This view is typically queried to retrieve open receivables grouped by profile class, or to reconcile collection activity against customer profile assignments. A representative query follows:

  • SELECT trx_number, amount_due_remaining, invoice_currency_code, due_date, name FROM apps.ce_ar_fc_invoices_v WHERE org_id = :p_org_id ORDER BY due_date;
  • Filtering by profile_class_id or name to isolate invoices under a specific collection class.
  • Aggregating amount_due_remaining by customer or profile class to produce exposure and aging summaries.

The user search term "cp_cust" corresponds to the CP_CUST alias used in the second UNION branch, which resolves customer-level (account-level) profiles for transactions lacking a site-level profile. Queries joining to HZ_CUSTOMER_PROFILES through account-level identifiers should account for this alias behavior to avoid duplication across the two branches.