Results for “oke_billing_methods_vl”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKE_BILLING_METHODS_VL is a multi-lingual (VL) validation view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OKE – Project Contracts product family and exposes the set of billing methods that govern how contract and project invoices are assembled. In Oracle EBS, billing methods determine which charge components — price, cost, and fee — are included when a contract line is billed and invoiced downstream in Oracle Projects and Oracle Receivables.
As a VL view, OKE_BILLING_METHODS_VL presents the translatable descriptive attributes (billing method name and description) alongside the non-translatable, installation-specific attributes held in the base table. The view automatically filters the translation table to the session language via T.LANGUAGE = USERENV('LANG'), so a user or concurrent program sees the billing method descriptions in their own language without custom WHERE clauses. This makes the view the natural read interface for reports, listings, and integrations that require billing method definitions in the reporting user's language.
The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its structure is stable across these releases.
Underlying Base Objects
The view is defined over two synonyms that resolve to the OKE base tables:
- OKE_BILLING_METHODS_B — the base table holding the billing method code, the include flags, activation dates, WHO audit columns, and the 15 descriptive flexfield (DFF) attribute columns.
- OKE_BILLING_METHODS_TL — the translation table holding BILLING_METHOD_NAME and DESCRIPTION for each installed language.
The join is performed on BILLING_METHOD_CODE, with the language restriction applied to the TL side. Because both underlying objects are accessed through APPS-owned synonyms, the view is usable by any responsibility whose data access grants read privileges on these objects, without the caller needing to know the physical table names.
Key Columns
- ROW_ID — the ROWID of the base table row, exposed for row-level addressing.
- BILLING_METHOD_CODE — the primary business key that uniquely identifies each billing method and links the B and TL rows.
- BILLING_METHOD_NAME and DESCRIPTION — translatable descriptive fields sourced from OKE_BILLING_METHODS_TL and returned in the session language.
- INCLUDE_PRICE_FLAG, INCLUDE_COST_FLAG, INCLUDE_FEE_FLAG — flags defining whether price, cost, and fee components are included when the method is used for billing.
- START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the billing method is active.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns for customer-defined extensions.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
Common Use Cases and Queries
The view is typically used for reporting on available billing methods, validating a billing method code before assigning it to a contract or project, and feeding interface programs that must resolve a method name for display. A listing of active methods in the user's language can be produced as follows:
SELECT billing_method_code, billing_method_name, include_price_flag, include_cost_flag, include_fee_flag FROM oke_billing_methods_vl WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY billing_method_name;SELECT billing_method_name FROM oke_billing_methods_vl WHERE billing_method_code = :p_code;— resolves a code to its translated name for a single lookup.SELECT billing_method_code, billing_method_name, attribute_category, attribute1 FROM oke_billing_methods_vl WHERE attribute_category IS NOT NULL;— identifies methods with populated DFF attributes.
Because the view enforces the session-language join, it should always be preferred over querying OKE_BILLING_METHODS_TL directly, which would require an explicit LANGUAGE predicate and risks returning rows in multiple languages.
-
View: OKE_BILLING_METHODS_VL 12.1.1
Contract billing methods multi-lingual view
APPS.OKE_BILLING_METHODS_VL·↳ OKE_BILLING_METHODS_B·↳ OKE_BILLING_METHODS_TL·Explore OKE module →
-
View: OKE_BILLING_METHODS_VL 12.2.2
Contract billing methods multi-lingual view
APPS.OKE_BILLING_METHODS_VL·↳ OKE_BILLING_METHODS_B·↳ OKE_BILLING_METHODS_TL·Explore OKE module →
-
Contract billing method assignments view
APPS.OKE_K_BILLING_METHODS_V·↳ OKE_BILLING_METHODS_VL·↳ OKE_K_BILLING_METHODS·Explore OKE module →
-
Contract billing method assignments view
APPS.OKE_K_BILLING_METHODS_V·↳ OKE_BILLING_METHODS_VL·↳ OKE_K_BILLING_METHODS·Explore OKE module →
-
Contract billing method assignments history view
APPS.OKE_K_BILLING_METHODS_HV·↳ OKE_BILLING_METHODS_VL·↳ OKE_K_BILLING_METHODS_H·Explore OKE module →
-
Contract billing method assignments history view
APPS.OKE_K_BILLING_METHODS_HV·↳ OKE_BILLING_METHODS_VL·↳ OKE_K_BILLING_METHODS_H·Explore OKE module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - OKE Tables and Views 12.2.2
This table stores the version comparison results.
-
eTRM - OKE Tables and Views 12.1.1
This table stores the version comparison results.
-
eTRM - OKE Tables and Views 12.1.1
This table stores the version comparison results.
-
12.2.2 DBA Data 12.2.2
-
eTRM - OKE Tables and Views 12.2.2
This table stores the version comparison results.
-
12.1.1 DBA Data 12.1.1