Results for “oke_k_billing_methods”

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

Overview

OKE.K_BILLING_METHODS is a table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Project Contracts (OKE) module. It stores the association between a contract header and the billing methods eligible or assigned to that contract, forming part of the contract setup configuration used by Oracle Projects and Project Contracts billing processes.

In Data Vault modeling terms, the heuristic classification derived from the foreign key structure is a link table. This classification is a modeling suggestion rather than a physical implementation detail: the table resolves a many-to-many relationship between contract headers and the underlying billing method definitions, and does not itself carry descriptive descriptive attributes beyond audit columns and a default indicator.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 24 columns. The primary key is named OKE_K_BILLING_METHODS_PK and is composed of K_HEADER_ID and BILLING_METHOD_CODE, which are also the columns of the unique index OKE_K_BILLING_METHODS_U1. This composite key is the business-key candidate, since both columns together uniquely identify each row.

• K_HEADER_ID — Foreign key to OKE_K_HEADERS; identifies the contract header to which the billing method assignment belongs.
• BILLING_METHOD_CODE — Foreign key to OKE_BILLING_METHODS_B; identifies the billing method being associated with the contract.
• DEFAULT_FLAG — Indicates whether the associated billing method is the default for the contract header.
• CREATION_DATE, CREATED_BY — Standard audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle Applications descriptive flexfield (DFF) columns, available for customer-defined extension of the table.

The audit and attribute columns follow the conventional Oracle Applications pattern and should not be treated as business keys.

Common Use Cases and Queries

Typical reporting scenarios include listing the billing methods enabled for a given contract and identifying the default billing method. A representative query joining the link to its parent header and lookup definition is:

• SELECT kbm.k_header_id, kbm.billing_method_code, kbm.default_flag FROM oke.oke_k_billing_methods kbm WHERE kbm.k_header_id = :header_id;
• Joining to OKE_K_HEADERS on K_HEADER_ID to retrieve contract number, name, and status for billing-method reporting.
• Joining to OKE_BILLING_METHODS_B on BILLING_METHOD_CODE to obtain descriptive billing method text from the base table.
• Filtering on DEFAULT_FLAG = 'Y' to isolate the default billing method assigned to each contract header.
• Audit queries using CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY to trace configuration changes over time.
• Querying the DFF columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15) where customer-specific flexfield segments have been enabled.

Related Objects

The following objects are the most significant dependents or references based on the documented foreign key structure:

• OKE_K_HEADERS — Parent table referenced by K_HEADER_ID; holds the contract header definition.
• OKE_BILLING_METHODS_B — Base table referenced by BILLING_METHOD_CODE; holds billing method definitions.
• OKE_K_BILLING_METHODS_PK — Primary key constraint on (K_HEADER_ID, BILLING_METHOD_CODE).
• OKE_K_BILLING_METHODS_U1 — Unique index supporting the business key.
• OKE_BILLING_METHODS_TL — Translation table conventionally paired with the _B table for multilingual billing method descriptions, where installed.

Because this table is a link between contracts and billing methods, changes to it should be made through the supported Project Contracts setup and API paths rather than direct DML.