Results for “billing_type”

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

Overview

The view OKX_TXN_BILLING_TYPES_V is an APPS-owned, VALID database view that belongs to the OKX - Contracts Integration product family within Oracle E-Business Suite. It publishes transaction billing type definitions for reporting and integration consumption, presenting a flattened, language-aware projection of the configuration that links transaction types to the billing types available for them. The object is documented in ETRM for both EBS 12.1.1 and 12.2.2, and its structure is stable across these releases.

Functionally, the view answers a recurring reporting question: for a given transaction type in the Contracts (OKX/CS) integration model, which billing types are permitted, what are their effective dates, and are they currently active? Because billing type configuration is held in the CS core tables, direct access is normally discouraged; this view provides a supported, denormalized interface suitable for concurrent programs, Oracle Reports, OAF/ADF pages, and inter-module integrations. Applications searching on the identifier Billing_type resolve to the single exposed column of the same name, which carries the billing type code stored in CS_TXN_BILLING_TYPES.BILLING_TYPE.

Underlying Base Objects

The view is defined as an inner join across three synonym-referenced base objects:

• CS_TXN_BILLING_TYPES (aliased TBT) - the primary source of billing type configuration, supplying the transaction billing type identifier, billing type code, transaction type identifier, and active date range.
• CS_TRANSACTION_TYPES_B (aliased B) - the transaction type base table, joined on TRANSACTION_TYPE_ID.
• CS_TRANSACTION_TYPES_TL (aliased TL) - the translation table for transaction types, joined on TRANSACTION_TYPE_ID to both the base table and the billing types table, and restricted to the session language via TL.LANGUAGE = USERENV('LANG').

The join is therefore transaction-type centric: a row is returned only where a billing type configuration exists for a transaction type that has a base record and a translation in the run-time session language. No outer joins are used, so transaction types lacking a billing type setup do not appear.

Key Columns

• BILLING_TYPE - the billing type code associated with the transaction type; the primary search target for users querying on "billing_type".
• TRANSACTION_TYPE_ID - foreign key to the owning transaction type in CS.
• STATUS - derived value computed at query time by decoding the current system date against START_DATE_ACTIVE and END_DATE_ACTIVE; returns A for active and I for inactive.
• NAME and DESCRIPTION - the transaction type name and description, resolved in the user's language from the _TL table.
• START_DATE_ACTIVE / END_DATE_ACTIVE - the effective date window for the billing type configuration.
• ID1 / ID2 - surrogate and placeholder key columns, with ID2 hard-coded to '#', used to satisfy generic Flexfield-style key expectations.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, PRIMARY_UOM_CODE - exposed as NULL placeholders so the view conforms to a common interface shape; they carry no data.

Common Use Cases and Queries

Typical uses include validating billing type setup during Contracts-to-billing integration, feeding billing type values into order or invoice interfaces, and producing active/inactive configuration reports.

List active billing types for every transaction type:

• SELECT TRANSACTION_TYPE_ID, NAME, BILLING_TYPE, STATUS, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OKX_TXN_BILLING_TYPES_V WHERE STATUS = 'A' ORDER BY TRANSACTION_TYPE_ID;

Find the billing types configured for a specific transaction type:

• SELECT BILLING_TYPE, NAME, DESCRIPTION FROM OKX_TXN_BILLING_TYPES_V WHERE TRANSACTION_TYPE_ID = :p_transaction_type_id;

Resolve the transaction type name for a billing type code:

• SELECT NAME, TRANSACTION_TYPE_ID FROM OKX_TXN_BILLING_TYPES_V WHERE BILLING_TYPE = :p_billing_type;

Detect expired configurations that may require maintenance:

• SELECT TRANSACTION_TYPE_ID, BILLING_TYPE, END_DATE_ACTIVE FROM OKX_TXN_BILLING_TYPES_V WHERE STATUS = 'I' AND END_DATE_ACTIVE IS NOT NULL;

Because STATUS is derived from SYSDATE and NAME depends on USERENV('LANG'), results vary by session language and by the date the query executes; reports should be scheduled with this in mind.