Search Results production_complete

Overview

APPS.PMIFV_SALES_DETAILS_V is a reporting and integration view within the Oracle E-Business Suite Process Manufacturing Intelligence (PMI) and Enterprise Territory/Revenue Management (ETRM) layer. It consolidates order-line level sales detail from the Process Manufacturing Order Management tables (the OP_ORDR_HDR and OP_ORDR_DTL synonyms) together with corresponding Oracle Order Management (OE) header and line records, customer master data, item master data, warehouse and organization references, and currency conversion logic. The consolidated result set is exposed as a single, denormalized row per sales order line, which is the form most commonly consumed by downstream analytics, extracts, and interface programs.

The view plays a central role in PMI sales reporting: it joins transactional order data to descriptive master data, resolves billing and shipping customer attributes, and computes derived monetary values such as the converted extended price and a package-derived charge amount. The presence of the constant literal 'OPSO' as ORDER_SOURCE_SYSTEM identifies the process-manufacturing operational source of the records.

Underlying Base Objects

The documented metadata lists the base objects referenced by the view. Order transaction data originates from the OP_ORDR_HDR and OP_ORDR_DTL synonyms, aliased in the view text as orderhdr and orderdetail respectively; these are joined with the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL synonyms to marry process order lines to the standard OE order model. Item and warehouse context is supplied by IC_ITEM_MST, IC_WHSE_MST, MTL_SYSTEM_ITEMS, and SY_ORGN_MST. Customer and address data come from OP_CUST_MST, SY_ADDR_MST, and the PMI_HZ_PARTY_V view, with sales representative information from OP_SLSR_MST and RA_SALESREPS_ALL.

Operational and organizational context is drawn from HR_OPERATING_UNITS, SY_ORGN_MST, GL_SETS_OF_BOOKS, GL_PLCY_MST, GL_PERIODS, and the PMI_GL_CALENDAR_V view. Conversion and business logic are provided by the GMICUOM package (unit-of-measure conversion via i2uom_cv), PMI_SALES_PKG (the pmisa_get_charge charge calculation), PMI_COMMON_PKG, PMI_SECURITY_PKG, and FND_PROFILE. OE_SYSTEM_PARAMETERS_ALL contributes order-management system parameter behavior.

Key Columns

Ordering and status attributes include ORDER_ID, ORDER_NO, ORDER_DATE, ORDER_STATUS, LINE_ID, LINE_NO, and LINE_STATUS. Item attributes are ITEM_ID, ITEM_NO, ITEM_DESC1, ITEM_UM, and SALES_CLASS. Quantity and UOM fields include ORDER_QTY1, ORDER_UM1, and a package-converted quantity derived through gmicuom.i2uom_cv. Pricing and currency columns include BASE_PRICE, NET_PRICE, EXTENDED_PRICE, LIST_PRICE, PRICE_UM, BILLING_CURRENCY, BASE_CURRENCY, and EXCHANGE_RATE, with converted extended price computed via a DECODE on mul_div_sign and a charge amount returned by pmi_sales_pkg.pmisa_get_charge.

Customer columns include BILLCUST_ID, CUST_NO, CUST_NAME, CUST_CLASS, addr_id, ADDR4, STATE_CODE, and COUNTRY_CODE, supplied for both billing and shipping parties. Shipping and logistics columns include SHIPPER_CODE, SHIP_MTHD, TO_WHSE, FROM_WHSE, SHIP_STATUS, and organizational fields ORGN_CODE, ORGN_NAME, and CO_CODE. Date columns include REQUESTED_SHIPDATE, PROMISED_SHIPDATE, SCHED_SHIPDATE, ACTUAL_SHIPDATE, REQUIRED_DLVDATE, and ACTUAL_DLVDATE.

Common Use Cases and Queries

Typical uses include sales-line extraction for territory and revenue reporting, reconciliation of process orders to OE order lines, and currency-normalized revenue analysis. The ORDER_SOURCE_SYSTEM literal allows the view to be unioned with other source systems in consolidated sales extracts.

• Sales by billing customer and period: select CUST_NAME, ORDER_DATE, EXTENDED_PRICE from APPS.PMIFV_SALES_DETAILS_V where ORDER_STATUS = 'Closed'.
• Shipped revenue by organization: select ORGN_CODE, SUM(EXTENDED_PRICE) from APPS.PMIFV_SALES_DETAILS_V where ACTUAL_SHIPDATE is not null group by ORGN_CODE.
• Currency-converted pipeline by warehouse: select ORDER_NO, LINE_NO, FROM_WHSE, BILLING_CURRENCY, BASE_CURRENCY, EXCHANGE_RATE from APPS.PMIFV_SALES_DETAILS_V where PRICE_SELECTED_IND = 'Y'.

Note that the view text references a column such as production_complete only in truncated documentation; the fully documented column list should be verified against the deployed view definition before production use.