Search Results unit_standard_price

Overview

OZF_X_INVOICE_LINE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OZF - Trade Management product family. It exposes invoice line information sourced from Oracle Receivables, joining transaction headers to their corresponding lines and surfacing both transactional attributes and quantity/price metrics. The view is a public synonym defined over the Receivables base objects RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL.

Its primary role is to provide a denormalized, query-friendly projection of invoice lines for Trade Management reporting and integration purposes, particularly where accrual, settlement, or claim processing must reference billed quantities and amounts. The view filters to completed transactions only, ensuring consumers see finalized invoice data rather than incomplete or unposted records. Because it includes the ORG_ID column on both sides, it supports Multi-Org Access Control (MOAC) filtering so that users see only the operating unit data to which they are authorized.

Underlying Base Objects

The view is defined over two documented base objects:

• RA_CUSTOMER_TRX_ALL — the Receivables transaction header table, referenced by the alias CT. Supplies transaction-level attributes such as TRX_NUMBER and CUSTOMER_TRX_ID.
• RA_CUSTOMER_TRX_LINES_ALL — the Receivables transaction line table, referenced by the alias LINES. Supplies line-level attributes including line identifiers, item references, quantities, and prices.

The join is performed on CUSTOMER_TRX_ID between the two tables. Two additional predicates govern the result set: CT.COMPLETE_FLAG must equal 'Y', restricting output to completed transactions; and the ORG_ID values on both tables must match via NVL comparisons. The view text additionally applies a MOAC client-info predicate, extracting the operating unit identifier from USERENV('CLIENT_INFO') and matching it against the line ORG_ID. This MOAC predicate implements standard EBS multi-org security behavior.

Key Columns

The view exposes thirteen columns:

• TRX_NUMBER — the user-visible Receivables transaction number from the header.
• CUSTOMER_TRX_ID — the transaction header primary key.
• CUSTOMER_TRX_LINE_ID — the transaction line primary key.
• LINE_NUMBER — the line sequence number within the transaction.
• LINE_TYPE — the classification of the line (for example, line, tax, freight, or charges).
• INVENTORY_ITEM_ID — the inventory item associated with the line, where applicable.
• QUANTITY_ORDERED — the quantity originally ordered on the line.
• QUANTITY_CREDITED — the quantity credited against the line, central to credit and return analysis.
• QUANTITY_INVOICED — the quantity actually invoiced on the line.
• UNIT_STANDARD_PRICE — the standard list price per unit.
• UNIT_SELLING_PRICE — the actual selling price per unit.
• EXTENDED_AMOUNT — the extended line amount.
• ORG_ID — the operating unit identifier used for MOAC filtering and multi-org reporting.

Consumers searching for QUANTITY_CREDITED will find it here as a direct line-level quantity, allowing credit volumes to be reported alongside ordered and invoiced quantities without querying RA_CUSTOMER_TRX_LINES_ALL directly.

Common Use Cases and Queries

Typical uses include reconciling billed versus credited quantities, supplying invoice line data to Trade Management accrual and settlement processes, and building multi-org-aware reports over completed Receivables transactions.

A representative query retrieving credited quantities by transaction is:

• SELECT TRX_NUMBER, LINE_NUMBER, INVENTORY_ITEM_ID, QUANTITY_ORDERED, QUANTITY_CREDITED, QUANTITY_INVOICED, EXTENDED_AMOUNT, ORG_ID FROM APPS.OZF_X_INVOICE_LINE_V WHERE QUANTITY_CREDITED > 0 ORDER BY TRX_NUMBER, LINE_NUMBER;

A more targeted query identifying credit activity for a specific item within an operating unit would add predicates on INVENTORY_ITEM_ID and ORG_ID. Because the view already enforces COMPLETE_FLAG = 'Y' and MOAC security through CLIENT_INFO, callers do not need to re-implement those filters, although explicit ORG_ID predicates remain advisable for performance and clarity.