Results for “okl_svc_pk”

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

Overview

OKL_SERVICES_B is a base table in the OKL (Lease and Finance Management) schema of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It stores header-level information about services that are quoted on a Lease Quote. In the leasing lifecycle, a quote may bundle tangible assets with intangible or value-added services—such as maintenance, insurance, delivery, or installation—and OKL_SERVICES_B captures the descriptive header record for each such service line before it is priced, approved, and ultimately booked into a lease or contract. The table carries a standard Oracle Applications audit and descriptive-flexfield footprint, plus a small set of business-specific columns, which is typical of ETRM transactional entities.

The metadata’s heuristic Data Vault classification describes this object as standalone, meaning it does not exhibit the dependent-child (satellite) or many-to-many junction (link) signatures that the mining routine detects. As a modeling suggestion, OKL_SERVICES_B is therefore best treated as an independent hub-style entity keyed by its own identifier, with related attributes and history handled by downstream or adjacent satellite structures rather than by embedded foreign-key dependencies.

Key Information Stored

The documented physical schema contains 28 columns. The primary key is OKL_SVC_PK, implemented on the ID column (NUMBER). Only ID is a documented unique index (OKL_SVC_UC1), so the surrogate key is the sole strict business-key candidate in the provided metadata—other identifying context is carried by ordinary columns rather than enforced unique constraints.

• ID — surrogate primary key (OKL_SVC_PK) uniquely identifying each service header record.
• OBJECT_VERSION_NUMBER — optimistic-locking column used by the EBS framework to detect concurrent updates.
• INV_ITEM_ID — reference to the inventory item (typically from MTL_SYSTEM_ITEMS_B) that defines the service being quoted.
• SUPPLIER_ID — the supplier or vendor associated with the quoted service, where the service is externally sourced.
• PARENT_OBJECT_CODE and PARENT_OBJECT_ID — polymorphic ownership pair identifying the parent entity (for example, a lease or quote header) to which this service belongs.
• EFFECTIVE_FROM — date from which the service header record is effective.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) segments used for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns used for auditing, change tracking, and incremental extraction.

Common Use Cases and Queries

Typical usage centers on quote-to-lease reporting and integration: extracting quoted services for a given quote, resolving service item descriptions, and reconciling supplier-sourced services. A common pattern joins the parent identifier and the item master:

• List services for a parent quote/lease: SELECT s.id, s.inv_item_id, s.supplier_id, s.effective_from FROM okl.okl_services_b s WHERE s.parent_object_code = :code AND s.parent_object_id = :id;
• Resolve item description: join INV_ITEM_ID to MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID.
• Resolve supplier name: join SUPPLIER_ID to PO_VENDORS.VENDOR_ID (or the supplier master view).
• Incremental loads: filter on LAST_UPDATE_DATE for delta extraction into a reporting or data-vault layer.

Related Objects

The mined relationship data classifies this table as standalone, so no enforced foreign keys are documented. Practical relationships are driven by the columns above:

• MTL_SYSTEM_ITEMS_B — via INV_ITEM_ID = INVENTORY_ITEM_ID, for service item definition.
• PO_VENDORS / POZ_SUPPLIERS — via SUPPLIER_ID = VENDOR_ID, for supplier details.
• OKL parent quote/lease header tables — via PARENT_OBJECT_CODE and PARENT_OBJECT_ID.
• OKL_SERVICES_TL / service line tables — conceptual child rows for the same service.
• FND_DESCR_FLEX_COL_USAGE_VL / FND_FLEX_VALUES_VL — for validating ATTR IBUTE_CATEGORY and DFF segments.
• FND_USER — via CREATED_BY and LAST_UPDATED_BY.