Results for “oke_k_billing_methods_h”

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

Overview

OKE_K_BILLING_METHODS_H is a history table in the OKE (Project Contracts) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the historical, versioned associations between a contract header and the billing methods defined for that contract. In Oracle Project Contracts, the term "K" refers to the contract (the "K" contract object), so this table records which billing method codes were attached to a given contract header at each major version of that contract. The "(History)" suffix in the object description indicates that rows are retained across versions rather than being overwritten, allowing the full audit trail of billing method assignment to be reconstructed.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link table. It sits between two hubs — the contract header (OKE_K_HEADERS_H) and the billing method definition (OKE_BILLING_METHODS_B) — and records the relationship between them across versions. The presence of MAJOR_VERSION in both the primary key and the foreign key reinforces its role as a versioned association (link) rather than a descriptive satellite.

Key Information Stored

The documented physical schema contains 25 columns. The most significant are:

• K_HEADER_ID — Foreign key to the contract header (OKE_K_HEADERS_H). Identifies the parent contract for which the billing method applies.
• BILLING_METHOD_CODE — Foreign key to OKE_BILLING_METHODS_B. Identifies the specific billing method (for example, a rate-based, milestone, or labor-based method) associated with the contract.
• MAJOR_VERSION — The contract major version at which this billing method association was captured. It is part of the primary key and appears in the foreign key to OKE_K_HEADERS_H, tying each history row to a specific contract version.
• DEFAULT_FLAG — Indicates whether the billing method is the default method for the contract version.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, allowing customer-specific extensions to be stored against each billing method history row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "who columns" providing the audit trail of row creation and modification.

Two key constraints are documented. The surrogate primary key is OKE_K_BILLING_METHODS_H_PK, defined on MAJOR_VERSION per the metadata. The business-key candidate is the unique index OKE_K_BILLING_METHODS_H_U1, defined on the composite of K_HEADER_ID, MAJOR_VERSION, and BILLING_METHOD_CODE. This unique index confirms that a billing method may appear only once per contract header per major version, which is the natural business identifier for the row. Note that a second unique index, OKE_K_BILLING_METHODS_H_UK01, is also referenced in the source metadata, reinforcing the same business key.

Common Use Cases and Queries

Typical reporting and diagnostics center on reconstructing which billing methods were active on a contract at a given version, and on auditing changes between versions. A common query pattern retrieves the current billing methods for a contract by filtering on the header and selecting the maximum major version:

• Retrieve billing methods for a contract: SELECT billing_method_code, default_flag FROM oke_k_billing_methods_h WHERE k_header_id = :p_header_id ORDER BY major_version, billing_method_code;
• Compare methods across versions: select the same header at two major versions and diff the BILLING_METHOD_CODE sets to detect additions or removals.
• Audit who changed billing method assignment, using CREATED_BY and LAST_UPDATED_BY joined to FND_USER.
• Identify contracts using a specific billing method by joining on BILLING_METHOD_CODE to OKE_BILLING_METHODS_B and OKE_K_HEADERS_H for contract context.

Because the table is history-bearing, reports must always constrain by MAJOR_VERSION to avoid double-counting the same billing method across versions.

Related Objects

• OKE_K_HEADERS_H — Parent contract header history table. Join on K_HEADER_ID and MAJOR_VERSION.
• OKE_BILLING_METHODS_B — Base billing methods definition table. Join on BILLING_METHOD_CODE to resolve the method name and attributes.
• OKE_BILLING_METHODS_TL — Translation table typically paired with the _B table for language-specific method descriptions.
• OKE_K_BILLING_METHODS — The corresponding non-history (current) billing methods interface, where present.
• OKE_K_HEADERS — Current contract header table providing the active contract context.

The primary key constraint OKE_K_BILLING_METHODS_H_PK and the unique index OKE_K_BILLING_METHODS_H_U1 should be considered when designing joins, as they guarantee at most one row per header/version/method combination.