Search Results ship_pr

Overview

PJM_PROJECT_SO_V is a Project Manufacturing (PJM) inquiry view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supplies project-related sales order information to the Web Inquiry component of Project Manufacturing, allowing users to review order, customer, item, and shipment details associated with a specific project and task without navigating the full Order Management transaction windows. The view consolidates header-level and line-level order data into a single denormalized result set keyed by PROJECT_ID and TASK_ID, making it suitable for embedded inquiry screens, ad hoc reporting, and lightweight integration extracts. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying Order Management tables at query time. Its status is VALID in the documented environments.

Underlying Base Objects

The documented base objects for the 12.2.2 metadata are OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, joined on HEADER_ID, together with OE_TRANSACTION_TYPES_TL (order type name), RA_TERMS_TL (payment terms), OE_SOLD_TO_ORGS_V (sold-to customer), and MTL_SYSTEM_ITEMS_KFV (item description and number). Supporting lookups come from OE_LOOKUPS for freight terms and shipment priority, and FND_CURRENCY_CACHE is used to derive the currency format mask for the order total. Two PL/SQL packages, PJM_INQUIRY and PJM_INQUIRY.OE_ORDER_TOTAL, provide the formatted ship-to and bill-to addresses and the order total value. In the 12.1.1 text the item source is MTL_ITEM_FLEXFIELDS rather than MTL_SYSTEM_ITEMS_KFV, a difference worth noting when porting queries between releases. Most joins to terms, sold-to, freight terms, and shipment priority are outer joins, so orders with missing reference data still appear.

Key Columns

• PROJECT_ID / TASK_ID — the project and task context that scopes the inquiry; these are the primary filtering columns.
• HEADER_ID / ORDER_NUMBER — Order Management header identifier and the user-visible sales order number.
• CUST_PO_NUMBER — the customer purchase order reference captured on the order header.
• ORDER_CATEGORY_CODE / ORDER_TYPE — order category and the transaction type name from OE_TRANSACTION_TYPES_TL.
• ITEM_NUMBER / DESCRIPTION / END_ITEM_UNIT_NUMBER — item identity and the end item unit number, central to project manufacturing traceability.
• SOLDTO.CUSTOMER_ID / CUSTOMER_NUMBER / NAME — sold-to customer identification.
• ORDERED_DATE / REQUEST_DATE — order entry date and requested (schedule) date.
• ORDERED_QUANTITY (DECODE) — flags whether the ordered quantity is zero ('Y'/'N').
• Ship-to / Bill-to columns — org IDs plus formatted addresses produced by PJM_INQUIRY.OE_ORG_ADDRESS; ship-to falls back from line to header via NVL.
• SHIPPING_METHOD_CODE / SHIP_PR.MEANING — shipping method and shipment priority meaning.
• FRTRM.MEANING / OTERM.NAME — freight terms and payment terms.
• Order total (TO_CHAR) and TRANSACTIONAL_CURR_CODE — PJM_INQUIRY.OE_ORDER_TOTAL formatted using the currency mask from FND_CURRENCY_CACHE. This is the column most often sought under the term "order_amount."
• TAX_EXEMPT_FLAG / PARTIAL_SHIPMENTS_ALLOWED — order attributes resolved from line then header.

Common Use Cases and Queries

The principal use case is the PJM Web Inquiry, which filters this view by project and task to display open and booked sales orders against a project. Reporting users also query it directly to reconcile project demand with Order Management, and developers reference it when building custom inquiry pages.

SELECT order_number,
       po_number,
       customer_number,
       item_number,
       ordered_date,
       order_total,
       transactional_curr_code
FROM   apps.pjm_project_so_v
WHERE  project_id = :p_project_id
AND    task_id    = :p_task_id;

To locate a specific customer purchase order, filter on PO_NUMBER or CUST_PO_NUMBER. To extract order value by project for analysis, aggregate the currency-formatted order total column, taking care that formatting is string-based. Because the view text embeds a call to PJM_INQUIRY.OE_ORDER_TOTAL per row and joins MTL_SYSTEM_ITEMS_KFV against the SO_ORGANIZATION_ID profile, performance depends heavily on selective PROJECT_ID/TASK_ID predicates; unfiltered queries can be expensive. All access is through the APPS schema, so grants and synonyms must be in place before use by custom code.