Results for “shipping_method”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_BLKTPRT_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Management (ONT) product. Its purpose is to expose the line-level detail of blanket sales agreements in a flattened, print-ready form. The view name derives from "blanket print lines," indicating that it is intended primarily to drive the blanket sales agreement print program and related reporting. It joins header, line, and line-extension records into a single denormalized result set, and it resolves coded attributes into their descriptive meanings so that a printed or exported document is human-readable.

In both Oracle EBS 12.1.1 and 12.2.2 the object retains a VALID status and is defined as a view rather than a table. Because it is a read-only construct, it is suited to reporting, extracts, and integration lookups rather than to transactional data maintenance. A caller searching on "invoicing_rule" reaches this view because it surfaces the INVOICING_RULE column, which is sourced from RA_RULES. This makes the view useful wherever the invoicing rule attached to a blanket agreement line must be displayed or passed downstream.

Underlying Base Objects

The view is defined over the following documented base objects:

• OE_BLANKET_HEADERS_ALL (synonym) — blanket sales agreement headers; supplies ORG_ID, HEADER_ID, and TRANSACTIONAL_CURR_CODE.
• OE_BLANKET_LINES_ALL (synonym) — blanket agreement lines; the primary source of line identifiers, item information, freight, and shipping attributes.
• OE_BLANKET_LINES_EXT (synonym) — line extension attributes such as start/end dates, quantity and amount limits, and pricing list references.
• OE_LOOKUPS (view) — used for the ITEM_IDENTIFIER_TYPE lookup.
• FND_LOOKUP_VALUES (synonym) — used to resolve freight terms and shipping method codes.
• RA_TERMS_TL (synonym) — payment terms name.
• RA_RULES (synonym) — the invoicing rule name exposed as INVOICING_RULE.
• OE_CONTRACTS_UTIL (package) — used to resolve formatted item and item description values.
• FND_CURRENCY (package) — used to derive a currency format mask for the blanket line amount limits.

The header, line, and line-extension objects are joined on HEADER_ID and LINE_ID, with outer joins to the lookup and terms objects so that lines are not dropped when a code is missing.

Key Columns

• HEADER_ID, LINE_ID, LINE_NUMBER — identifying keys for the agreement and line.
• CUSTOMER_PO_NUMBER — customer purchase order reference.
• SHIP_TO_ORG_ID, DELIVER_TO_ORG_ID, INVOICE_TO_ORG_ID, SOLD_TO_ORG_ID — party and organization identifiers.
• INVENTORY_ITEM_ID, ORDERED_ITEM, ORDERED_ITEM_ID, ITEM_IDENTIFIER, ITEM, ITEM_DESCRIPTION — item identification and descriptive text.
• UOM — order quantity unit of measure.
• ACTIVATION_DATE, EXPIRATION_DATE — line effective dates.
• FREIGHT_TERMS, SHIPPING_METHOD, PAYMENT_TERM — resolved descriptive attributes.
• INVOICING_RULE — the name of the invoicing rule from RA_RULES; the column most relevant to invoicing-rule reporting.
• BLANKET_LINE_MIN_AMOUNT, BLANKET_LINE_MAX_AMOUNT — formatted amount limits.
• BLANKET_MIN_QUANTITY, BLANKET_MAX_QUANTITY — quantity limits.
• PRICE_LIST_ID, QP_LIST_LINE_ID, MODIFIER_LIST_LINE_ID — pricing references.

Common Use Cases and Queries

Typical uses include printing blanket agreement line detail, auditing invoicing rules assigned to blanket lines, and feeding extracts that require human-readable terms. The following query retrieves lines with their invoicing rule:

SELECT header_id, line_number, ordered_item, uom,
       payment_term, invoicing_rule,
       activation_date, expiration_date
FROM   apps.oe_blkTPRt_lines_v
WHERE  invoicing_rule IS NOT NULL
ORDER  BY header_id, line_number;

A second scenario lists all lines for a given header to produce a printable document:

SELECT line_number, item, item_description,
       blanket_min_quantity, blanket_max_quantity,
       blanket_line_min_amount, blanket_line_max_amount
FROM   apps.oe_blkTPRt_lines_v
WHERE  header_id = :p_header_id
ORDER  BY line_number;

Because the view resolves codes into meanings and formats amounts according to the transactional currency, it removes the need for callers to join lookup, terms, and rules tables themselves. Reporting tools and concurrent print programs can therefore consume it directly.