Search Results oks_bsl_pr_pk

Overview

OKS_BSL_PR is a Service Contracts (OKS) transactional table in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented description states that it is related to a lower-level contract line, such as a coverage level or product. In the OKS data model, the "_PR" suffix denotes a parallel, denormalized structure that mirrors the contract line hierarchy, allowing contract administrators to allocate billed amounts, coverage periods, and pricing attributes down to subordinate service levels without traversing the multi-level OKC hierarchy on every transaction.

Based on the foreign key topology mined from the ETRM metadata, OKS_BSL_PR is a hub-leaning object. It carries its own surrogate primary key, OKS_BSL_PR_PK (ID), and is referenced by at least three downstream tables (OKS_BSD_PR, OKS_BTL_PR), which supports its role as a central anchor for detail and balance records. It also holds outbound references to OKS_BCL_PR, OKC_K_LINES_B, and FND_SECURITY_GROUPS, which act as links to the contract billing, contract line, and security dimensions. From a Data Vault modeling perspective, OKS_BSL_PR would most naturally be modeled as a hub with satellite attributes (averaging, amount, billed dates), and the referencing tables as links or satellites hanging off that hub.

Key Information Stored

The table's 32 documented columns include the following most significant fields:

• ID — The surrogate primary key defined by OKS_BSL_PR_PK and also enforced by the unique index OKS_BSL_PR_U1. This is the only documented business-key candidate; no natural composite unique key is defined in the metadata.
• BCL_ID — Foreign key to OKS_BCL_PR, linking the row to its parent billing contract line.
• CLE_ID — Foreign key to OKC_K_LINES_B, tying the row to the contract line entity in the OKC core line model.
• AVERAGE and AMOUNT — Numeric attributes that store averaged and absolute monetary values for the subordinate line.
• DATE_BILLED_FROM and DATE_BILLED_TO — The billed coverage window for the lower-level line.
• DATE_TO_INTERFACE — The date up to which the row has been interfaced to downstream accounting processes.
• MANUAL_CREDIT — A flag or indicator for manually applied credits on the line.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/data-security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OKS APIs and OA Framework pages.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — The DFF (Descriptive Flexfield) columns for customer-specific extensions.

Common Use Cases and Queries

Typical reporting scenarios include reconciling billed amounts by contract line and identifying credits issued against coverage-level lines. Because the row is anchored to both a billing contract line (BCL_ID) and a contract line (CLE_ID), joins to OKC_K_LINES_B are common to resolve the line number the user actually sees.

• Find all subordinate lines for a given billing contract: SELECT ID, AMOUNT, DATE_BILLED_FROM, DATE_BILLED_TO FROM OKS.OKS_BSL_PR WHERE BCL_ID = :p_bcl_id;
• Join to agreement lines to display the user-visible line number and balance: SELECT b.ID, k.LINE_NUMBER, b.AMOUNT, b.AVERAGE FROM OKS.OKS_BSL_PR b, OKC.OKC_K_LINES_B k WHERE b.CLE_ID = k.ID AND b.BCL_ID = :p_bcl_id;
• Locate rows not yet interfaced to accounting: SELECT ID, DATE_TO_INTERFACE FROM OKS.OKS_BSL_PR WHERE DATE_TO_INTERFACE IS NULL;
• Audit manual credits by security group: SELECT SECURITY_GROUP_ID, SUM(AMOUNT) FROM OKS.OKS_BSL_PR WHERE MANUAL_CREDIT IS NOT NULL GROUP BY SECURITY_GROUP_ID;

These queries are read-only and intended for reporting or troubleshooting. All inserts and updates should flow through the supported OKS Service Contracts APIs, which maintain OBJECT_VERSION_NUMBER and the audit columns, and which also propagate changes to dependent OKS_BSD_PR and OKS_BTL_PR records.

Related Objects

The ETRM metadata documents the following relationship endpoints:

• OKS_BCL_PR — Parent billing contract line; joined via OKS_BSL_PR.BCL_ID.
• OKC_K_LINES_B — Core contract line entity; joined via OKS_BSL_PR.CLE_ID.
• FND_SECURITY_GROUPS — Data security dimension; joined via OKS_BSL_PR.SECURITY_GROUP_ID.
• OKS_BSD_PR — Detail table referencing this table through both BSL_ID and BSL_ID_AVERAGED, used for averaged balance or distribution detail.
• OKS_BTL_PR — Transaction line table referencing this table via BSL_ID, capturing billable transaction activity against the subordinate line.

Collectively these objects form the OKS parallel line family, and OKS_BSL_PR serves as the pivot between the contract hierarchy (OKC) and the billing and transaction detail (OKS_BSD_PR, OKS_BTL_PR).