Results for “markup_percent”

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

Overview

OKS_K_ORDER_DETAILS is a Service Contracts (OKS) table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to capture service contract details at the point a service is ordered through Order Management. When a service-enabled item is entered on a sales order and subsequently flows into the contracts schema, this table stores the resulting contract line-level and header-level references, renewal attributes, and pricing configuration that govern how the service is contracted and renewed.

The table carries 34 documented columns and resides in the OKS schema. It has two unique indexes: OKS_K_ORDER_DETAILS_PK on ID (also the primary key) and OKS_K_ORDER_DETAILS_U1 on ID, with OKS_K_ORDER_DETAILS_U2 representing a business-key candidate on (ORDER_LINE_ID1, ORDER_LINE_ID2). The FK topology — heavy outbound references to OKC_K_HEADERS_B and OKC_K_LINES_B, a self-referencing COD_ID, and a SECURITY_GROUP_ID to FND_SECURITY_GROUPS — suggests a satellite-leaning structure in Data Vault terms, holding descriptive and transactional attributes keyed to the contract header/line hubs.

Key Information Stored

The table distinguishes a surrogate primary key from its documented business-key candidates, and separates contract linkage from renewal and pricing attributes.

• ID — surrogate primary key (OKS_K_ORDER_DETAILS_PK, unique index U1); the internal row identifier.
• ORDER_LINE_ID1 / ORDER_LINE_ID2 — the documented business-key candidate (unique index U2), tying the record to the originating order line.
• CHR_ID — foreign key to OKC_K_HEADERS_B, the contract header this detail belongs to.
• CLE_ID — foreign key to OKC_K_LINES_B, the contract line associated with this detail.
• LINK_CHR_ID / LINK_CLE_ID — secondary references to a linked contract header and line (for example, a covering or parent contract).
• COD_ID — self-referencing FK to OKS_K_ORDER_DETAILS, supporting hierarchical or parent-child ordering of details.
• COD_TYPE — classifies the type of order detail record.
• LINK_ORDER_HEADER_ID / LINK_ORD_LINE_ID1 / LINK_ORD_LINE_ID2 — references back to the originating order header and line.
• RENEWAL_TYPE / LINE_RENEWAL_TYPE — renewal behavior at the contract and line level.
• RENEWAL_PRICING_TYPE / MARKUP_PERCENT / PRICE_LIST_ID1 / PRICE_LIST_ID2 — pricing basis used when the service renews.
• END_DATE — the termination or renewal end date of the detail.
• PO_REQUIRED_YN / APPLY_ALL_YN / RENEWAL_APPROVAL_FLAG — control flags for purchase orders, blanket application, and renewal approval.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing multi-org / group access.
• CONTACT_ID, SITE_ID, EMAIL_ID, PHONE_ID, FAX_ID, BILLING_PROFILE_ID — contact and billing identifiers associated with the detail.

Common Use Cases and Queries

Typical usage centers on reconciliation between Order Management and Service Contracts, renewal reporting, and contract-line tracing. A common pattern joins the detail to its contract header and line:

• Locate the contract context for an order line:

  SELECT d.id, d.order_line_id1, d.chr_id, h.contract_number
  FROM oks_k_order_details d, okc_k_headers_b h
  WHERE d.chr_id = h.id
  AND d.order_line_id1 = :order_line_id;

• Resolve the associated contract line:

  SELECT d.id, d.cle_id, l.line_number
  FROM oks_k_order_details d, okc_k_lines_b l
  WHERE d.cle_id = l.id
  AND d.chr_id = :chr_id;

• List renewal configuration for reporting:

  SELECT id, renewal_type, line_renewal_type, renewal_pricing_type,
  markup_percent, end_date
  FROM oks_k_order_details
  WHERE order_line_id1 = :order_line_id;

• Traverse self-referenced hierarchies using COD_ID and identify contact linkage via OKS_K_ORDER_CONTACTS.COD_ID.

Related Objects

• OKC_K_HEADERS_B — parent contract header, joined on CHR_ID (and LINK_CHR_ID for linked contracts).
• OKC_K_LINES_B — contract line, joined on CLE_ID (and LINK_CLE_ID).
• OKS_K_ORDER_CONTACTS — child contact table referencing OKS_K_ORDER_DETAILS.COD_ID.
• OKS_K_ORDER_DETAILS — self-referencing via COD_ID for hierarchical details.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for access control.

These relationships make OKS_K_ORDER_DETAILS the bridge between Order Management order lines and the OKC contract header/line model, and the anchor for renewal, pricing, and contact configuration within Service Contracts.