Search Results interface_offset

Overview

OKS_BILLING_PROFILES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined within the Service Contracts (OKS) product family. Its documented purpose is to expose billing profile information maintained in the Service Contracts module, presenting a denormalized, read-oriented projection of the billing profile base table together with its translated descriptive attributes. In Oracle EBS 12.1.1 and 12.2.2 the view is marked VALID and is used primarily for reporting, concurrent program output, and integration interfaces that need to retrieve billing profile definitions without accessing the underlying transactional tables directly.

Billing profiles in Service Contracts govern how contract and subscription lines are invoiced — the frequency and offset rules applied to billing schedules, the parties and addresses involved in the billing relationship, and the summarization behavior of generated invoices. Exposing this data through a single view allows reports and external systems to resolve billing behavior per profile using a stable, supportable interface.

Underlying Base Objects

The view is defined over two documented base objects:

• OKS_BILLING_PROFILES_B — the billing profile base (non-translated) table, which holds the operational and foreign-key attributes of each profile, including identifiers for owned parties, dependent customer accounts, bill-to addresses, billing frequency codes, offset codes, and the invoice offset defaults. Every non-translated column in the view (aliased as BPEB.*) originates from this table.
• OKS_BILLING_PROFILES_TL — the translation table, which stores language-dependent descriptive text keyed to the base profile. Columns aliased as BPET.* are drawn from this table, including SFWT_FLAG, MESSAGE, DESCRIPTION, and INSTRUCTIONS.

Both objects are referenced in the view text through APPS synonyms. The join is a one-to-many pattern typical of the _B/_TL convention: for each base row, the translation row matching the current session language is returned, ensuring the profile name, description, and instructions appear in the appropriate language.

Key Columns

• ID / OBJECT_VERSION_NUMBER — primary identifier and optimistic locking column for the billing profile.
• MDA_CODE — the code identifying the profile definition within the billing profile framework.
• OWNED_PARTY_ID1/2, DEPENDENT_CUST_ACCT_ID1/2 — party and customer account relationships defining who is billed.
• BILL_TO_ADDRESS_ID1/2 — bill-to address references for the profile.
• UOM_CODE_FREQUENCY / TCE_CODE_FREQUENCY — frequency values expressed in unit of measure and time-code equivalents.
• UOM_CODE_SEC_OFFSET / TCE_CODE_SEC_OFFSET — offset values applied to the secondary billing period, expressed in UOM and time-code forms.
• UOM_CODE_PRI_OFFSET / TCE_CODE_PRI_OFFSET — offset values for the primary billing period.
• REG_INVOICE_PRI_OFFSET / REG_INVOICE_SEC_OFFSET — regular invoice offsets for primary and secondary periods.
• SUMMARISED_YN — indicates whether invoices generated for the profile are summarized.
• PROFILE_NUMBER — the user-facing profile identifier.
• FIRST_BILLTO_DATE / FIRST_INVOICE_DATE — dates anchoring the initial billing and invoicing cycles.
• MESSAGE, DESCRIPTION, INSTRUCTIONS, SFWT_FLAG — translated descriptive attributes from OKS_BILLING_PROFILES_TL.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard extensibility (DDF) columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• INVOICE_OBJECT1_ID1/2, INVOICE_JTOT_OBJECT1_CODE — references to the invoice object used by the profile.

The requested search term uom_code_sec_offset corresponds directly to the view column UOM_CODE_SEC_OFFSET, which records the secondary billing offset in unit-of-measure terms and is paired with TCE_CODE_SEC_OFFSET for the time-code representation.

Common Use Cases and Queries

The view is most often queried to report billing behavior by profile, to validate offset and frequency configuration, and to feed integrations that create or interpret billing schedules. A typical query retrieves the profile identifier, description, and its offset configuration:

• Reporting all billing profiles and their primary/secondary offset codes for configuration review.
• Identifying profiles with a specific UOM_CODE_SEC_OFFSET value during data validation or migration.
• Resolving the bill-to and party relationships for a given profile before generating invoices.
• Joining to OKS contract and subscription tables to explain how a given billing line was scheduled.

Sample SQL:

SELECT profile_number, description, uom_code_frequency, uom_code_sec_offset, uom_code_pri_offset, summarised_yn
FROM apps.oks_billing_profiles_v
WHERE uom_code_sec_offset IS NOT NULL
ORDER BY profile_number;

Because the view is a straight projection with translation, it can be treated as a stable read interface; developers should not depend on the ROW_ID pseudo-column for DML, as the view is intended for query access rather than update.