Search Results oks_billing_profiles_b_u1

Overview

The OKS.OKS_BILLING_PROFILES_B table is a core Service Contracts (OKS) entity that stores billing profile definitions used to drive contract invoicing behavior in Oracle E-Business Suite. Billing profiles capture customer account assignments, bill-to addresses, invoicing rules, accounting rules, billing levels and types, billing intervals, and interface/invoice offsets. Records are created through the Billing Profile setup UI and are subsequently applied during contract authoring via the Cascade Attributes form to override existing line-level billing schedules. On renewal, profile information can be defaulted onto a contract by associating a billing profile template to a customer in the Global Contract Defaults form. In 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10, and its indexes reside in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the heuristic mined from the foreign key structure classifies this object as standalone, suggesting it behaves principally as a reference or hub-like entity rather than a transaction link, with a single documented outbound relationship to FND_SECURITY_GROUPS via SECURITY_GROUP_ID.

Key Information Stored

The documented physical schema comprises 54 columns. The most significant are:

• ID — surrogate primary key, defined by index OKS_BILLING_PROFILES_B_PK and enforced as unique by OKS_BILLING_PROFILES_B_U1. This index is the object returned when searching for the business-key candidate.
• PROFILE_NUMBER — user-entered billing profile number; the primary business-facing identifier.
• OWNED_PARTY_ID1 — unique identifier of the profile-owning party; indexed by nonunique index OKS_BILLING_PROFILES_B_N1.
• BILL_TO_ADDRESS_ID1 — bill-to address of the party.
• BILLING_LEVEL, BILLING_TYPE — control how invoices are grouped and generated.
• INTERVAL — billing interval for recurring invoicing.
• INTERFACE_OFFSET, INVOICE_OFFSET, REG_INVOICE_PRI_OFFSET, REG_INVOICE_SEC_OFFSET — timing offsets applied to interface and invoice generation dates.
• FIRST_BILLTO_DATE, FIRST_INVOICE_DATE — anchor dates for the initial billing and invoicing cycle.
• INVOICE_OBJECT1_ID1, ACCOUNT_OBJECT1_ID1, and their JTOT object codes — invoice and account object references.
• OBJECT_VERSION_NUMBER and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for concurrency control and audit.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — DFF extensibility.
• SECURITY_GROUP_ID — the only documented foreign key target, referencing FND_SECURITY_GROUPS.

Several legacy columns (MDA_CODE, OWNED_PARTY_ID2, DEPENDENT_CUST_ACCT_ID1/2, BILL_TO_ADDRESS_ID2, and the UOM_CODE_/TCE_CODE_ offset pairs) are documented as not being used.

Common Use Cases and Queries

Typical reporting scenarios include retrieving the billing profile applied to a contract, auditing invoice and accounting rule configuration, and reconciling billing intervals with actual invoicing. A basic lookup by business key:

• SELECT id, profile_number, owned_party_id1, billing_level, billing_type FROM oks.oks_billing_profiles_b WHERE profile_number = :p_number;
• SELECT b.id, b.profile_number, b.bill_to_address_id1, b.interval, b.first_invoice_date FROM oks.oks_billing_profiles_b b WHERE b.owned_party_id1 = :party_id; — leverages index OKS_BILLING_PROFILES_B_N1.
• SELECT b.* FROM oks.oks_billing_profiles_b b, fnd_security_groups g WHERE b.security_group_id = g.security_group_id; — joins the sole documented FK target.

Analysts commonly extend these patterns to expose active (non-obsolete) profiles, to compare FIRST_INVOICE_DATE against generated invoice dates, and to surface DFF attributes through ATTRIBUTE_CATEGORY joins.

Related Objects

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, the single documented foreign key.
• OKS_BILLING_PROFILES_TL — translation table for profile descriptive fields.
• OKS_BILLING_SCHEDULES and related schedule tables — consume profile settings during contract authoring.
• OKS_CONTRACTS / OKS contract lines — the Cascade Attributes form applies profile values to line-level billing schedules.
• OKS_BILLING_PROFILE_TEMPLATES — used by Global Contract Defaults to default profiles onto customers at renewal.
• OKS_BILLING_PROFILES_B_U1 and OKS_BILLING_PROFILES_B_N1 — the unique ID index and the OWNED_PARTY_ID1 lookup index.
• OKS_BILLING_PROFILES_B_PK — primary key constraint on ID.