Results for “returned_amount”

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

Overview

OE_BLANKET_HEADERS_V is an APPS-owned reporting view in the Oracle Order Management (ONT) module, validated as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents blanket sales agreement header information in a denormalized, user-facing form. Blanket sales agreements are long-term ordering vehicles in which a customer commits to purchasing goods or services under pre-negotiated terms over a defined validity period. While OE_BLANKET_HEADERS stores the transactional core of these agreements, OE_BLANKET_HEADERS_V enriches that data with descriptive values drawn from Oracle Receivables, Oracle Pricing, Oracle Human Resources, and the Trading Community Architecture (HZ) model. The view therefore serves as a convenient read-only interface for reports, concurrent programs, OBIEE/BI Publisher extracts, and custom integrations that need customer, currency, salesrep, order type, price list, payment term, and invoicing rule descriptions without performing multiple joins manually. Users frequently query this view when investigating pricing, expiration, or order-release questions on blanket agreements, including searches related to released_amount, which is derived from the agreement lines and releases associated with a blanket header rather than stored directly on the header record.

Underlying Base Objects

The view is defined over the OE_BLANKET_HEADERS synonym, which is the primary driving table, and is extended by OE_BLANKET_HEADERS_EXT, the descriptive flexfield (DFF) extension table, supplying the GLOBAL_ATTRIBUTE and ATTRIBUTE columns. Foreign-key style lookups resolve codes into meaningful names via AR_LOOKUPS, OE_LOOKUPS, OE_TRANSACTION_TYPES_TL, QP_LIST_HEADERS_TL, RA_RULES, RA_TERMS_TL, and FND_CURRENCIES. Customer and address context is resolved through the HZ tables — HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES, and HZ_RELATIONSHIPS — which supply sold-to, ship-to, invoice-to, and deliver-to party and site descriptions. RA_SALESREPS and MTL_PARAMETERS provide salesperson and inventory organization details respectively. Because it is a view, no data is stored within it; all values are resolved at query time, and the ROWID column reflects the underlying OE_BLANKET_HEADERS row for update-safe identification.

Key Columns

• HEADER_ID, ORDER_NUMBER, VERSION_NUMBER — unique identifier and human-readable agreement reference.
• ORG_ID — operating unit, critical for multi-org security (MOAC) filtering.
• ORDER_TYPE_ID — transaction type, joined to OE_TRANSACTION_TYPES_TL for the type name.
• EXPIRATION_DATE, ORDERED_DATE, REQUEST_DATE, PRICING_DATE — validity and date-basis fields governing the agreement.
• SOLD_TO_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID — party and site references resolved against HZ tables.
• PRICE_LIST_ID, AGREEMENT_ID, PAYMENT_TERM_ID, INVOICING_RULE_ID, ACCOUNTING_RULE_ID — commercial terms linked to Pricing and Receivables.
• TRANSACTIONAL_CURR_CODE, CONVERSION_RATE, CONVERSION_TYPE_CODE — currency and conversion context.
• ATTRIBUTE1–20, GLOBAL_ATTRIBUTE1–20, GLOBAL_ATTRIBUTE_CATEGORY, CONTEXT — descriptive flexfield segments from OE_BLANKET_HEADERS_EXT.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Note that a column literally named RELEASED_AMOUNT is not exposed on this header-level view; released quantities and amounts against a blanket are held on the associated order release and line tables.

Common Use Cases and Queries

Typical uses include listing active blanket agreements per customer, auditing expiring agreements, and joining to release tables to compute released versus authorized amounts. A representative query is:

SELECT bh.order_number, bh.expiration_date, bh.transactional_curr_code,
hp.party_name sold_to, bh.cust_po_number
FROM oe_blanket_headers_v bh, hz_parties hp
WHERE bh.sold_to_org_id = hp.party_id
AND bh.org_id = :p_org_id
AND bh.expiration_date >= SYSDATE;

To investigate released_amount per blanket, join the view to OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL on AGREEMENT_ID, restricting to release order types, and aggregate ORDERED_QUANTITY or the line amount. Filtering by ORG_ID is mandatory in multi-org environments, and the DFF columns should be referenced when reporting on client-specific agreement attributes.