Results for “oks_billing_profiles_b_pk”

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

Overview

OKS_BILLING_PROFILES_B is a Service Contracts (OKS) module table in Oracle E-Business Suite releases 12.1.1 and 12.2.2 that stores billing profile information for a customer. A billing profile defines how contract lines associated with a given owned party or dependent customer account are grouped, priced in time, and invoiced — including bill-to addresses, billing frequency offsets, and summarization rules. The table is the base (or "_B") table in the standard EBS pattern, holding the canonical row data identified by the surrogate primary key OKS_BILLING_PROFILES_B_PK on the ID column. The "_B" suffix indicates that a corresponding translation or interface table (typically OKS_BILLING_PROFILES_TL) may carry language-specific display attributes, while OKS_BILLING_PROFILES_B carries the operational columns.

The metadata extracts a heuristic Data Vault classification of standalone, meaning that based strictly on the mined foreign-key structure, no parent-child hub or link relationship is strongly implied. As a modeling suggestion, this table is best treated as a satellite-style reference table: it holds descriptive, time-stamped attributes (Created_By, Creation_Date, Last_Updated_By, Last_Update_Date) around a natural business key, with the SECURITY_GROUP_ID FK to FND_SECURITY_GROUPS providing multi-tenant or security partitioning. The presence of OBJECT_VERSION_NUMBER confirms it participates in EBS optimistic-locking conventions used by the Oracle Forms/ADF stack.

Key Information Stored

The 54 documented columns describe three broad categories of information: identity, billing timing, and accounting/invoice references. The most significant columns are:

• ID — surrogate primary key; a system-generated unique identifier (also a unique index, OKS_BILLING_PROFILES_B_U1).
• PROFILE_NUMBER — the user-facing business key used to identify the billing profile in the UI.
• OWNED_PARTY_ID1 / OWNED_PARTY_ID2 — the party (customer) that owns the profile and whose contracts are governed by it.
• DEPENDENT_CUST_ACCT_ID1 / DEPENDENT_CUST_ACCT_ID2 — dependent customer account identifiers for which the profile is applied.
• BILL_TO_ADDRESS_ID1 / BILL_TO_ADDRESS_ID2 — the bill-to address used when invoices are generated.
• MDA_CODE, UOM_CODE_FREQUENCY, TCE_CODE_FREQUENCY — frequency and unit-of-measure definitions controlling how often billing occurs.
• UOM_CODE_PRI_OFFSET, UOM_CODE_SEC_OFFSET, REG_INVOICE_PRI_OFFSET, REG_INVOICE_SEC_OFFSET — primary and secondary offset units/values applied before invoice generation.
• FIRST_BILLTO_DATE, FIRST_INVOICE_DATE — the first billing and first invoicing dates for the profile.
• SUMMARISED_YN — indicates whether contract lines are summarized onto a single invoice.
• BILLING_LEVEL, BILLING_TYPE, INTERVAL — classification attributes controlling the granularity and cadence of billing.
• INVOICE_OBJECT1_ID1/ID2, INVOICE_JTOT_OBJECT1_CODE, ACCOUNT_OBJECT1_ID1/ID2, ACCOUNT_JTOT_OBJECT1_CODE — journal total object references linking billing profiles to invoice and accounting distributions.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS for security partitioning.

Common Use Cases and Queries

Typical use cases include retrieving the billing profile for a customer, validating frequency and offset configuration before contract invoicing, and generating billing-profile reports. A representative query joins the profile to the party and address:

• Locate a profile by number: SELECT * FROM oks_billing_profiles_b WHERE profile_number = :p;
• Retrieve bill-to address context: SELECT p.profile_number, p.owned_party_id1, p.bill_to_address_id1 FROM oks_billing_profiles_b p WHERE p.owned_party_id1 = :party_id;
• Reporting frequency setup: filter on UOM_CODE_FREQUENCY and REG_INVOICE_PRI_OFFSET for audit of invoicing cadence.
• Full text UI extraction: join to OKS_BILLING_PROFILES_TL on ID to obtain translated display names.

The vast majority of production access is performed through the Service Contracts concurrent programs and the Contracts/Billing Profile forms, which enforce the OBJECT_VERSION_NUMBER and audit columns.

Related Objects

Because the mined FK structure identifies only one external reference, related objects are inferred from OKS module conventions and the documented schema:

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID (documented FK).
• OKS_BILLING_PROFILES_TL — translation table joined via ID for language-specific columns.
• HZ_PARTIES / HZ_CUST_ACCOUNTS — source of OWNED_PARTY_ID1 and DEPENDENT_CUST_ACCT_ID1.
• HZ_LOCATIONS / HZ_CUST_SITE_USES_ALL — source of BILL_TO_ADDRESS_ID1.
• OKS_CONTRACTS_B — contracts reference the billing profile for invoicing behavior.
• RA_CUSTOMER_TRX_ALL — downstream invoices generated according to profile timing.

The table is a configuration/reference entity; it is read by billing and invoicing processes rather than updated by transactional flows.