Search Results pricing_method_code

Overview

PJM_UEFF_SO_LINES_V is an APPS-owned view in Oracle E-Business Suite, catalogued under the Project Manufacturing (PJM) product family. Its name reflects its function: it exposes sales order line data organized for the User Exit / User Extensible Foreign Function (UEFF) integration layer used by Project Manufacturing to synchronize order information with external planning or execution systems. The view presents a wide, denormalized projection of sales order line attributes rather than narrowly scoped engineering data, making it suitable for extract, reporting, and interface processes that must carry the full commercial context of an order line into downstream manufacturing or project-driven flows.

Because it is a view, it introduces no independent storage and reflects the state of its underlying base object at query time. In 12.1.1 and 12.2.2 the documented definition is a single-source projection over the SO_LINES_ALL synonym, which resolves to the Order Management sales order lines table.

Underlying Base Objects

The ETRM metadata documents exactly one referenced base object: SO_LINES_ALL, exposed through a synonym in the APPS schema. There is no documented join to OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, or any Project Manufacturing table; the view is a column-level selection from the order line entity itself. Practically, this means:

• Row grain matches SO_LINES_ALL: one row per sales order line.
• Filtering, sorting, and joins against header-level data must be performed by the calling process.
• No aggregation, transformation, or business-rule filtering is documented, so values are passed through essentially as stored.
• Because it is a synonym-based projection, the view is sensitive to SO_LINES_ALL grants and to any editioning or synonym resolution changes between 12.1.1 and 12.2.2.

Key Columns

The projection is broad and includes identifiers, flags, quantities, pricing attributes, and a large set of surrogate identifier (SVRID) columns used by the UEFF/synchronization mechanism. Significant columns include:

• LINE_ID, HEADER_ID, LINE_NUMBER — the primary O2C identifiers; HEADER_ID links a line to its order header.
• PARENT_LINE_ID and LINK_TO_LINE_ID — model/option and configuration hierarchy relationships. These are the columns most closely related to the user's search term "service_parent_line_id"; service-oriented parent linkage is expressed here through the parent/link line identifiers rather than a dedicated service parent column.
• COMPONENT_SEQUENCE_ID, COMPONENT_CODE, COMPONENT_SORT_CODE, ATO_FLAG, ATO_LINE_ID, OPTION_FLAG — configure-to-order and bill-of-material structure.
• ORDERED_QUANTITY, CANCELLED_QUANTITY, INVOICED_QUANTITY, OPEN_FLAG — fulfillment and billing state.
• LIST_PRICE, LIST_PERCENT, PERCENT_BASE_PRICE, PRICE_LIST_ID, INVOICING_RULE_ID, ACCOUNTING_RULE_ID — pricing and revenue scheduling.
• INVENTORY_ITEM_ID, CUSTOMER_ITEM_ID, ITEM_TYPE_CODE, DEMAND_CLASS_CODE, ORG_ID — item and organization context.
• CP_SERVICE_ID and numerous SVRID columns — surrogate keys supporting the UEFF synchronization between systems.
• ATTRIBUTE1–15 and PRICING_ATTRIBUTE1–15 — extensibility placeholders for customer-specific integration data.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage is extraction of order lines for Project Manufacturing planning, service-order investigation, and reconciliation of parent/child line structures.

• Locating child lines by parent, which is the closest direct answer to the "service_parent_line_id" search:

SELECT line_id, parent_line_id, line_number, ordered_quantity
FROM   apps.pjm_ueff_so_lines_v
WHERE  parent_line_id IS NOT NULL;

• Retrieving all lines for a given order and inspecting status:

SELECT line_id, line_number, item_type_code, ordered_quantity, open_flag
FROM   apps.pjm_ueff_so_lines_v
WHERE  header_id = :p_header_id
ORDER  BY line_number;

• Extracting surrogate identifiers for an interface run:

SELECT line_id, number_svrid, item_svrid, ordered_quantity_svrid
FROM   apps.pjm_ueff_so_lines_v
WHERE  last_update_date >= :p_since;

Because the view is a thin projection over SO_LINES_ALL, performance depends almost entirely on the base table's indexes; predicates on LINE_ID, HEADER_ID, and ORGANIZATION-adjacent columns should be pushed down accordingly.