Search Results one_time




Overview
Explore in AI Chat

Overview

XNC_ITEM_TYPE_CHARGES_V is a reporting view within the Oracle E-Business Suite XNC product family, "Sales for Communications." The XNC module is documented as obsolete, meaning it is retained only for backward compatibility in existing installations and receives no further development or support. In EBS 12.1.1 and 12.2.2, this view is not registered as an implemented database object; the ETRM metadata explicitly records "Not implemented in this database," so it exists as a documented, deployment-dependent object rather than a guaranteed schema element in every environment.

The view aggregates order line amounts at the order header level, producing two consolidated figures for each order: total one-time (non-recurring) charges and total recurring charges. This mirrors the standard telecommunications and subscription revenue distinction, where upfront activation or installation charges are recognized once and subscription, usage, or maintenance fees recur over a billing period. Its columns are limited to HEADER_ID, ONE_TIME, and RECURRING, making it a compact header-level summary rather than a line-level detail set.

Underlying Base Objects

The view text is defined over two objects. The first is ASO_I_OE_ORDER_LINES_V, an order-line integration view in the ASO (Order Capture) schema that exposes order header identity, inventory item, ordered quantity, unit selling price, and organization. The second is XNC_ITEM_TYPE_V, which classifies an inventory item as 'NON-RECURRING' or 'RECURRING' per organization. The two are joined by INVENTORY_ITEM_ID and, notably, by ORGANIZATION_ID against AIOV.ORG_ID. The metadata lists no other referenced base objects, consistent with the view's narrow purpose.

The join is an outer join on XNC_ITEM_TYPE_V (indicated by the (+) syntax on the ORG_ID and INVENTORY_ITEM_ID predicates). Items without a matching item-type row are therefore retained from the order side, but DECODE returns NULL for them, so their amounts contribute to neither aggregate. The rule is a text match on the two literal item-type values; any other classification value silently drops out of both sums.

Key Columns

  • HEADER_ID — The order header identifier, used as the single GROUP BY key. Each output row represents one order.
  • ONE_TIME — SUM of UNIT_SELLING_PRICE multiplied by ORDERED_QUANTITY for lines whose item type is 'NON-RECURRING'. Non-matching lines contribute NULL and are excluded from the sum.
  • RECURRING — SUM of the same extended-price expression restricted to lines whose item type is 'RECURRING'.

Because both measures are built from DECODE-based conditional sums, no explicit item-type column is returned; the classification is absorbed into the two aggregate expressions. No currency, status, or date dimension is exposed, so filtering or contextual enrichment must come from the consuming query.

Common Use Cases and Queries

Typical use is to profile an order by its upfront versus recurring revenue split, supporting pricing review, commission or revenue-recognition preparation, and subscription reporting. A user searching "one_time" is most likely retrieving the ONE_TIME column for such reporting.

Representative query:

  • SELECT HEADER_ID, ONE_TIME, RECURRING FROM XNC_ITEM_TYPE_CHARGES_V WHERE HEADER_ID = :p_header_id;
  • SELECT HEADER_ID, NVL(ONE_TIME,0) ONE_TIME, NVL(RECURRING,0) RECURRING FROM XNC_ITEM_TYPE_CHARGES_V WHERE ONE_TIME IS NOT NULL OR RECURRING IS NOT NULL;
  • SELECT NVL(ONE_TIME,0) + NVL(RECURRING,0) TOTAL_CHARGES FROM XNC_ITEM_TYPE_CHARGES_V WHERE HEADER_ID = :p_header_id;

Deployment caution: since the object is documented as not implemented, verify existence with ALL_VIEWS before relying on it, and confirm that XNC_ITEM_TYPE_V is populated for the relevant organizations, otherwise all aggregates map to NULL.