Search Results invoicing_date

Overview

OE_BIS_BILLINGS_V is an APPS-owned reporting view in the Oracle E-Business Suite Order Entry (OE) module. The name follows the OE_BIS naming convention, indicating a Business Intelligence System / operational reporting view designed for downstream analytics, and it is registered in ETRM with a status of VALID across 12.1.1 and 12.2.2. The view consolidates order header, order line, item, cost, warehouse, and accounting flexfield data into a single denormalized result set for billing, revenue, discount, and margin analysis. It is read-only and exposes no maintenance path; consumers query it directly or use it as a source for extracts, Discoverer workbooks, and BI Publisher reports.

The view is significant to users searching on invoicing_date because it exposes that attribute under the alias INVOICING_DATE, mapped from SO_LINES_ALL.S5_DATE. This makes it a convenient way to analyze invoiced order lines without joining SO_LINES_ALL manually.

Underlying Base Objects

The documented SQL is defined over the following objects, all referenced as APPS synonyms or views:

• SO_HEADERS_ALL — order header, aliased H (HEADER_ID, CUSTOMER_ID, CURRENCY_CODE, ORG_ID).
• SO_LINES_ALL — order line, aliased L (LINE_ID, prices, quantities, S1/S5 workflow flags, WAREHOUSE_ID).
• SO_ORDER_TYPES_ALL and SO_CYCLE_ACTIONS — used to restrict to the Receivables Interface cycle (ACTION_ID = 7).
• MTL_SYSTEM_ITEMS, MTL_PARAMETERS, MTL_ITEM_CATEGORIES, MTL_CATEGORIES, MTL_DEFAULT_CATEGORY_SETS, MTL_UOM_CONVERSIONS — item master, warehouse, category, and UOM conversion data.
• CST_ITEM_COSTS — item cost used in cost and margin computations.
• GL_SETS_OF_BOOKS — set of books currency for the cost currency column.
• HR_ORGANIZATION_INFORMATION — additional operating unit resolution.
• SO_LOOKUPS — lookup meanings for product group and sales channel.

Joins are inner except for the UOM conversion rates, which are outer-joined on ITEM_ID = 0 and the line UOM code, with a TRUNC(SYSDATE) validity test.

Key Columns

• INVOICING_DATE — sourced from SO_LINES_ALL.S5_DATE; the required date filter for many billing reports.
• HEADER_ID, LINE_ID, CUSTOMER_ID, OU_ID — primary identifiers and operating unit.
• INVOICED_QUANTITY, INVOICED_LIST_PRICE, INVOICED_SELLING_PRICE, INVOICED_DISCOUNTS, INVOICED_MARGIN — billing and margin metrics.
• UNIT_LIST_PRICE, UNIT_SELLING_PRICE, LINE_COST, LINE_COST_CURRENCY, LINE_CURRENCY — price and cost bases.
• INVENTORY_ITEM_ID, WAREHOUSE_ID — item and shipping warehouse.
• PRODUCT_GROUP, SALES_CHANNEL — category and lookup descriptors.

Common Use Cases and Queries

Typical uses include period revenue reporting, discount and margin analysis by product group or channel, and reconciliation of order lines to the Receivables interface.

Example: invoiced value by day and product group.

• SELECT TRUNC(INVOICING_DATE) INV_DATE, PRODUCT_GROUP, SUM(INVOICED_SELLING_PRICE) REVENUE FROM OE_BIS_BILLINGS_V WHERE INVOICING_DATE >= :p_from AND INVOICING_DATE < :p_to GROUP BY TRUNC(INVOICING_DATE), PRODUCT_GROUP ORDER BY 1, 2;

Example: margin by channel for a given operating unit.

• SELECT SALES_CHANNEL, SUM(INVOICED_MARGIN) MARGIN FROM OE_BIS_BILLINGS_V WHERE OU_ID = :p_org AND INVOICING_DATE BETWEEN :p_start AND :p_end GROUP BY SALES_CHANNEL;

Because the view scans SO_LINES_ALL and multiple MTL objects, restrict queries by INVOICING_DATE and OU_ID where possible, and confirm the SO_CYCLE_ACTIONS Receivables Interface filter satisfies the intended audit scope.