Results for “ar_cons_inv_draft_v”

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

Overview

The AR_CONS_INV_DRAFT_V view is a consolidated billing draft inquiry object owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It exposes a filtered, denormalized presentation of consolidated invoice draft records held in the AR_CONS_INV table, joined to customer name and party information so that consumers receive human-readable output without having to perform the joins themselves.

Consolidated billing (also referred to as consolidated invoicing) allows a single billing transaction to aggregate multiple transactions across a customer account hierarchy or related bill-to sites. Records in the base consolidated invoice table progress through statuses such as new, draft, and finalized. This view isolates only the rows whose STATUS equals 'DRAFT', making it a purpose-built window onto consolidated billing numbers that have been created but not yet finalized.

In EBS 12.1.1 and 12.2.2, the object is documented as a VALID VIEW in the ETRM repository, with the owner recorded as APPS. It is intended primarily for reporting, inquiry, and integration scenarios where downstream consumers — custom concurrent programs, BI Publisher reports, OAF extensions, or external system extracts — need a lightweight, pre-joined projection of draft consolidated invoices rather than the full base table.

Underlying Base Objects

The documented base objects referenced by the view are AR_CONS_INV, HZ_CUST_ACCOUNTS, and HZ_PARTIES, all accessed through public synonyms in the APPS schema. The relationship is a straightforward three-table join:

• AR_CONS_INV (aliased CV) is the driving table. It holds the consolidated billing number, the operating unit identifier, the customer identifier, the site use identifier, and the status that determines whether a row qualifies as a draft.
• HZ_CUST_ACCOUNTS (aliased C) is joined on C.CUST_ACCOUNT_ID = CV.CUSTOMER_ID, resolving the customer identifier to the Trading Community Architecture (TCA) customer account record.
• HZ_PARTIES (aliased PARTY) is joined on C.PARTY_ID = PARTY.PARTY_ID, supplying the party name used as the customer name attribute.

The view therefore inherits the partitioning and multi-org characteristics of its base objects, and returns only records where the base row status is 'DRAFT'.

Key Columns

• CONS_BILLING_NUMBER — the consolidated billing number from AR_CONS_INV, the primary business identifier for the draft consolidated invoice.
• ORG_ID — the operating unit identifier, essential for multi-org security and for filtering results to the appropriate business unit.
• CUSTOMER_NAME — derived via SUBSTRB(PARTY.PARTY_NAME, 1, 30), truncating the TCA party name to thirty bytes. Consumers should note this truncation when comparing against the untruncated party name elsewhere.
• SITE_USE_ID — the site use identifier associated with the consolidated invoice record, indicating the bill-to or relevant customer site.
• CUSTOMER_ID — the customer account identifier from AR_CONS_INV, which corresponds to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.

Common Use Cases and Queries

The view is typically used to list draft consolidated invoices with customer names for operational review, to reconcile consolidated billing activity against transactions, or to feed extracts that must exclude finalized documents.

A basic listing filtered by operating unit:

• SELECT cons_billing_number, customer_name, site_use_id FROM ar_cons_inv_draft_v WHERE org_id = :p_org_id ORDER BY cons_billing_number;

Joining to the base table for additional consolidated invoice attributes not exposed by the view:

• SELECT v.cons_billing_number, v.customer_name, cv.status, cv.creation_date FROM ar_cons_inv_draft_v v, ar_cons_inv cv WHERE cv.cons_billing_number = v.cons_billing_number AND cv.org_id = v.org_id;

Count of draft consolidated invoices per customer:

• SELECT customer_id, customer_name, COUNT(*) draft_count FROM ar_cons_inv_draft_v GROUP BY customer_id, customer_name;

Because the view filters on STATUS = 'DRAFT' internally, callers do not need to apply that predicate themselves; adding it again is redundant but harmless. Multi-org filtering on ORG_ID, however, must be applied explicitly where operating unit isolation is required.