Results for “okl_billing_charges_v”

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

Overview

OKL_BILLING_CHARGES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL – Lease and Finance Management product family. It exposes billing charge records that have been loaded through the OKL billing import mechanism, which provides the ability to read third-party files containing billing charges. Rather than representing a single physical entity, the view is a denormalized projection that combines the header-level charge data stored in OKL_BILLING_CHARGES_B with the translatable descriptive data held in OKL_BILLING_CHARGES_TL. Because the view is valid and available in both EBS 12.1.1 and 12.2.2, it can be relied upon for concurrent-program imports, interface validation, and ad hoc reporting across release upgrades.

The view's principal design goal is to present each imported billing charge as a single flattened row, combining charge classification, monetary values, customer and contract references, and the standard Oracle EBS who-columns used for audit and multi-org security.

Underlying Base Objects

According to the documented ETRM metadata, OKL_BILLING_CHARGES_V is defined over two base objects, both presented through synonyms:

• OKL_BILLING_CHARGES_B – the base (non-translatable) table holding the operational columns: identifiers, contract and asset references, charge dates, amounts, currency, customer data, the ATTRIBUTE1–15 flex columns, INTERFACE_ATTRIBUTE1–7 interface columns, ORG_ID, and the audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).
• OKL_BILLING_CHARGES_TL – the translatable table supplying language-dependent fields such as CHARGE_TYPE, DESCRIPTION, and the SFWT_FLAG.

The join is performed on the charge record's primary key (BCHB.ID = BCHT.ID), with the view projecting BCHB.ROWID as ROW_ID and BCHB.OBJECT_VERSION_NUMBER for optimistic-locking consistency. Because CHARGE_TYPE and DESCRIPTION originate from the TL table, multilingual installations return the value appropriate to the current session language.

Key Columns

• ID / ROW_ID / OBJECT_VERSION_NUMBER – surrogate key and row identity used by the import and update logic.
• CHARGE_TYPE – sourced from OKL_BILLING_CHARGES_TL; classifies the nature of the billing charge, which is the attribute most commonly searched by integrators and report developers.
• CONTRACT_ID, ASSET_ID, BGH_ID, STY_ID – foreign references to the contract, leased asset, billing group header, and stream type that own the charge.
• CHARGE_DATE, AMOUNT, CURRENCY_CODE – the financial substance of the record: when the charge applies and its monetary value.
• CUSTOMER_ID, CUSTOMER_REF, CUSTOMER_ADDRESS_ID, CUSTOMER_ADDRESS_REF – customer identification and alternate reference keys for reconciliation against third-party source files.
• SEQUENCE_NUMBER – ordering attribute within the imported batch.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15, INTERFACE_ATTRIBUTE1–7 – descriptor flexfields and interface-specific placeholders used to carry source-system data.
• ORG_ID and audit columns – support multi-org partitioning and standard EBS auditing and concurrent request traceability.

Common Use Cases and Queries

The view is typically queried during billing import reconciliation, charge-type validation, and interface troubleshooting. A representative query filters by the search term of interest:

• Retrieve all charges of a given type for a contract:
  SELECT contract_id, charge_date, amount, currency_code, charge_type
FROM okL_billing_charges_v
WHERE charge_type = 'LATE_FEE';
• Audit the most recent imported batch by concurrent request:
  SELECT id, contract_id, charge_type, amount, request_id, creation_date
FROM okL_billing_charges_v
WHERE request_id = :request_id
ORDER BY sequence_number;
• Reconcile customer charges against a private-label spreadsheets source using CUSTOMER_REF and INTERFACE_ATTRIBUTE columns.

Because the view is a read-only projection, all data maintenance must be performed against the underlying base and translation tables through the supported OKL APIs or concurrent programs; direct DML against the view is not advised.