Results for “draft_submitted_flag”

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

Overview

OE_AK_BLANKET_HEADERS_V is an Oracle E-Business Suite view owned by the APPS schema and registered as VALID in the Order Management (ONT) product. It is a denormalized, reporting-oriented projection that consolidates blanket sales agreement header data drawn from the transactional blanket header table and its revision-controlled extension table. Oracle Order Management stores blanket sales agreements as a header record plus one or more revision rows; the view joins those two structures so that a single row presents both the agreement-level attributes and the currently effective revision attributes.

The "AK" prefix reflects the Oracle Application Framework / AK-style attribute layer historically used by Order Management to expose business object attributes for descriptive flexfields, region-based UI, and external interfaces. In practice, OE_AK_BLANKET_HEADERS_V is consumed by concurrent programs, BI Publisher reports, and custom integrations that need a stable, read-only representation of blanket agreements without navigating the revision model manually. Because it is a view rather than a table, it carries no storage of its own and always reflects the underlying base rows at query time.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed in the view definition through APPS synonyms:

• OE_BLANKET_HEADERS_ALL — the core blanket agreement header table, aliased OEBHDR in the view text. It holds agreement identity, customer and site references, pricing and payment terms, currency, sales representative, shipping and packing instructions, order type, operating unit (ORG_ID), document numbering, signature capture fields, and workflow/flow status columns.
• OE_BLANKET_HEADERS_EXT — the revision extension table, aliased OEBHDRX. It holds effective-dating and revision attributes: START_DATE_ACTIVE, END_DATE_ACTIVE, revision change date, reason code and comments, the ENFORCE_* enforcement flags, minimum and maximum blanket amounts, override amount and hold flags, and the NEW_* pricing/modifier list columns.

The view joins these two objects on the blanket header identifier, exposing OEBHDR columns alongside OEBHDRX columns as a single flat row set. Multi-org security is preserved through ORG_ID, so queries must be constrained to the correct operating unit, consistent with the underlying _ALL table.

Key Columns

• HEADER_ID — primary identifier of the blanket agreement; the join key to both base objects.
• ORDER_NUMBER, ORDER_TYPE_ID — the agreement document number and its order type classification.
• USER_STATUS_CODE — the user-defined status on the header, controlling the agreement's lifecycle state (for example active, cancelled, on hold). Because the column originates from OE_BLANKET_HEADERS_ALL, it is not revision-specific.
• FLOW_STATUS_CODE, TRANSACTION_PHASE_CODE — Oracle Flow Manufacturing / order flow status and transaction phase indicators.
• SOLD_TO_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID, SHIP_FROM_ORG_ID — party and organization role references.
• ON_HOLD_FLAG, OVERRIDE_AMOUNT_FLAG, BLANKET_MIN_AMOUNT, BLANKET_MAX_AMOUNT — commercial controls governing releases against the agreement.
• ENFORCE_* — flags enforcing ship-to, freight terms, shipping method, price list, payment terms, invoice-to, invoicing rule, and accounting rule on release orders.
• START_DATE_ACTIVE, END_DATE_ACTIVE, VERSION_NUMBER — revision validity window and version identity.
• DRAFT_SUBMITTED_FLAG, SUPPLIER_SIGNATURE, CUSTOMER_SIGNATURE — signature and draft workflow state.

Common Use Cases and Queries

Typical scenarios include validating blanket agreement status before allowing releases, reporting effective vs. expired agreements, auditing enforcement-flag configuration, and feeding downstream pricing or contract systems. A representative query filters by operating unit and user status:

• SELECT header_id, order_number, user_status_code, sold_to_org_id, transactional_curr_code, start_date_active, end_date_active, on_hold_flag FROM oe_ak_blanket_headers_v WHERE org_id = :p_org_id AND user_status_code = :p_status AND sysdate BETWEEN NVL(start_date_active, sysdate) AND NVL(end_date_active, sysdate) ORDER BY order_number;
• Identify agreements missing effective dates: SELECT header_id, order_number FROM oe_ak_blanket_headers_v WHERE org_id = :p_org_id AND end_date_active IS NULL;
• Audit enforcement configuration: SELECT order_number, enforce_price_list_flag, enforce_payment_term_flag, enforce_ship_to_flag FROM oe_ak_blanket_headers_v WHERE org_id = :p_org_id;

Because the view exposes revision-extension columns without a revision discriminator, consumers requiring a specific amendment history should join to OE_BLANKET_HEADERS_EXT directly. Use the view for current-state reporting and integration where a single flattened row per agreement is sufficient.