Results for “adjustment_minimum”

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

Overview

OKS_BILL_SUB_LINE_DTLS is a Service Contracts (OKS) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the detail-level quantities and monetary amounts associated with billing sub-lines, covering both regular (non-adjustment) and adjustment records. In the contracts billing model, the hierarchy descends from a billing line to a billing sub-line (OKS_BILL_SUB_LINES) and then to this detail table, which holds the granular values that ultimately drive invoice generation and revenue recognition. The table resides in the OKS schema and is documented with 43 columns; it is the lowest level of the contract billing decomposition structure.

From a modeling perspective, the FK topology and the presence of a surrogate primary key (ID) combined with multiple foreign keys to other tables, including self-references, suggests a satellite-leaning classification. Under a Data Vault interpretation, this table behaves as a satellite attached to the OKS_BILL_SUB_LINES hub, carrying descriptive and measurable attributes rather than acting as an independent hub or pure link.

Key Information Stored

The primary key is OKS_BILL_SUB_LINE_DTLS_PK, enforced on the ID column, which is also the sole documented unique index candidate (OKS_BILL_SUB_LINE_DTLS_U1). The table's most significant columns include:

• ID — Surrogate primary key uniquely identifying each detail record.
• BSL_ID — Foreign key to OKS_BILL_SUB_LINES, anchoring the detail to its parent billing sub-line.
• BSL_ID_AVERAGED — Reference to an averaged sub-line, used when quantity or amount values are averaged across periods.
• BSD_ID and BSD_ID_APPLIED — Self-referencing keys linking a detail record to another detail record, typically to associate an adjustment with the base line it applies against.
• AMOUNT — Monetary value held on the detail record.
• RESULT — Outcome or computed value produced by the billing calculation for this detail.
• UNIT_OF_MEASURE, START_READING, END_READING, BASE_READING, ESTIMATED_QUANTITY — Counter-based and usage quantities, supporting meter-style contracts.
• FIXED, ACTUAL, DEFAULT_DEFAULT, AMCV_YN — Flags controlling pricing behavior and default handling.
• ADJUSTMENT_LEVEL, ADJUSTMENT_MINIMUM — Parameters describing tiered or threshold-based adjustments.
• CCR_ID, CGR_ID — References to vendor/party and grouping contexts associated with the billing detail.
• SECURITY_GROUP_ID — Access control reference to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard concurrency control and audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Extensible descriptive flexfield storage.

Common Use Cases and Queries

Typical uses include reconciliation of contract billing amounts against invoice lines, analysis of usage and meter readings for quantity-based contracts, and auditing of adjustments applied to prior billing details. Reporting queries frequently join this table to OKS_BILL_SUB_LINES to reconstruct the billing hierarchy.

• Retrieve detail for a sub-line: SELECT d.* FROM oks_bill_sub_line_dtls d WHERE d.bsl_id = :p_bsl_id ORDER BY d.id;
• Identify adjustments and their base lines: SELECT d.id, d.bsd_id_applied, d.amount, d.adjustment_level FROM oks_bill_sub_line_dtls d WHERE d.bsd_id_applied IS NOT NULL;
• Aggregate amounts by sub-line: SELECT d.bsl_id, SUM(d.amount) total_amount FROM oks_bill_sub_line_dtls d GROUP BY d.bsl_id;
• Summarize usage-based details: SELECT d.bsl_id, d.unit_of_measure, d.start_reading, d.end_reading, d.estimated_quantity FROM oks_bill_sub_line_dtls d;

These patterns are useful for contract billing extracts, revenue subledger feeds, and operational dashboards of contract usage.

Related Objects

• OKS_BILL_SUB_LINES — Parent sub-line table; joined via BSL_ID and BSL_ID_AVERAGED.
• OKS_BILL_SUB_LINE_DTLS — Self-reference via BSD_ID and BSD_ID_APPLIED for adjustment-to-base relationships.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for row-level security.
• FV_CCR_VENDORS — Referenced through CCR_ID for vendor and party context.
• OKS_BILL_LINES / OKS_BILL_HEADERS — Higher billing hierarchy objects reached by traversing from the parent sub-line.

Because no public PL/SQL APIs are documented for this table in the metadata excerpt, integration is generally performed through the Service Contracts billing APIs that manage the parent sub-line records. The tables below are the principal dependencies and join targets.