Results for “rate_type_code”

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

Overview

The OKX_RATE_SCHEDULES_V view belongs to the OKX – Contracts Integration product within Oracle E-Business Suite, and is owned by the APPS schema. Its documented purpose is to expose the billing rates applied to service coverage, presenting records drawn from the coverage billing rates table in a denormalized, report-friendly form. Because OKX handles contracts integration, this view is typically consumed by contract and service modules that need to reference billable coverage rates without querying the underlying transactional table directly.

The view is a single-table wrapper over CS_COV_BILL_RATES, exposing rate type, unit of measure, flat and percentage rate values, along with synthesized display attributes such as NAME, STATUS, DESCRIPTION, and effective-date placeholders. As a VIEW object type with VALID status, it carries no independent storage and is regenerated from the base table definition. In both 12.1.1 and 12.2.2 environments, the definition is delivered as an APPS-owned view referencing the CS_COV_BILL_RATES synonym.

Underlying Base Objects

The documented base object is CS_COV_BILL_RATES, accessed through a synonym. The view performs a straightforward SELECT against this table with no joins, unions, or aggregations. Each row in CS_COV_BILL_RATES corresponds to one row in OKX_RATE_SCHEDULES_V. Because the view passes through the base table's primary key COVERAGE_BILL_RATE_ID as ID1, row identity is preserved for downstream consumers.

The columns RATE_TYPE_CODE, UNIT_OF_MEASURE_CODE, FLAT_RATE, and PERCENT_RATE are passed through unmodified. The remaining columns are constructed inline: a literal '#' for ID2, RATE_TYPE_CODE reused as NAME, a constant 'A' for STATUS, a concatenation of FLAT_RATE, PERCENT_RATE, and UNIT_OF_MEASURE_CODE for DESCRIPTION, SYSDATE for START_DATE_ACTIVE, and NULL for END_DATE_ACTIVE. This means the value-oriented columns reflect real persisted data, while the descriptive and status columns are presentation-only constructs.

Key Columns

• RATE_TYPE_CODE — The rate classification used to distinguish billing rate behavior. It is also aliased as NAME, making it the principal descriptive key in the view.
• UNIT_OF_MEASURE_CODE — The unit against which the rate is expressed, also appended into the DESCRIPTION field.
• FLAT_RATE — The fixed monetary component of the billing rate.
• PERCENT_RATE — The percentage-based component of the billing rate.
• DESCRIPTION — A concatenated string combining flat rate, percent rate, and unit of measure for display purposes.
• STATUS — Constant 'A', indicating an active presentation state regardless of underlying record state.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Derived date fields populated with SYSDATE and NULL respectively; these do not reflect true date-tracked effectivity.

Common Use Cases and Queries

The view is most often used in reporting and integration contexts where rate values must be presented alongside display-friendly labels. A common scenario is retrieving all defined rate types for coverage billing, or filtering to a specific rate type via the RATE_TYPE_CODE column.

To list all rate schedules:

• SELECT rate_type_code, unit_of_measure_code, flat_rate, percent_rate FROM okx_rate_schedules_v;

To isolate a specific rate classification:

• SELECT name, description FROM okx_rate_schedules_v WHERE rate_type_code = :p_rate_type;

Because STATUS and date columns are synthesized, consumers should not rely on them for effectivity logic; the underlying CS_COV_BILL_RATES table should be queried directly when true dated or status-driven behavior is required.