Results for “bic_contract_headers_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIC_CONTRACT_HEADERS_V is a reporting view in the Oracle E-Business Suite Customer Intelligence (BIC) product family. It presents a denormalized, read-only projection of service contract header information sourced from the Oracle Service Contracts (OKS) module, enriched with descriptive names resolved from accounting rules, invoicing rules, price lists, payment terms, and agreements. The view is classified as obsolete in release 12.1.1 and 12.2.2 and is not implemented in the current database instance, meaning it exists only as documented metadata rather than as a deployed database object. Its historical purpose was to support Customer Intelligence analytics and downstream reporting by exposing contract attributes in a single flattened structure that avoids repeated joins at query time.
The view is particularly relevant to users searching on the term "accounting_rule," since ACCOUNTING_RULE is one of the joined descriptive columns it exposes. The view surfaces both the foreign key ACCOUNTING_RULE_ID and the resolved ACCOUNTING_RULE name, allowing reports to display the human-readable rule designation without additional joins to RA_RULES.
Underlying Base Objects
The view is defined over one primary driving object and five lookup or reference sources, all joined with outer joins to preserve contract rows even where reference data is absent:
- OKS_ENT_HEADERS_V — the driving source, aliased as C, providing contract header attributes such as contract ID, number, amount, status, and type.
- RA_RULES — joined twice (aliases R1 and R2) to resolve ACCOUNTING_RULE_ID and INVOICING_RULE_ID into descriptive rule names.
- RA_TERMS — aliased T, resolving TERMS_ID into the payment terms name.
- ASO_I_PRICE_LISTS_V — aliased P, resolving PRICE_LIST_ID into a price list name.
- ASO_I_AGREEMENTS_V — aliased A, resolving AGREEMENT_ID into an agreement name.
No base tables are separately documented for this view beyond these referenced objects. The outer-join construction ensures that a contract missing an accounting rule, price list, or agreement still returns a row, with the corresponding descriptive column set to null.
Key Columns
The view exposes 41 columns. The principal identifiers and attributes include ORG_ID, CONTRACT_ID, CONTRACT_NUMBER, SHORT_DESCRIPTION, CONTRACT_AMOUNT, CONTRACT_STATUS_CODE, CONTRACT_TYPE_CODE, and PARTY_ID. Lifecycle and scheduling attributes include DURATION, PERIOD_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE, FIRST_BILL_TO, FIRST_BILL_ON, AUTO_RENEW_BEFORE_DAYS, BILLING_FREQUENCY, and BILLING_METHOD. Billing and financial references include ACCOUNTING_RULE_ID, INVOICING_RULE_ID, TERMS_ID, PRICE_LIST_ID, CURRENCY_CODE, MODIFIER, and CONVERSION_TYPE.
The resolved descriptive columns are ACCOUNTING_RULE, INVOICING_RULE, PRICE_LIST, PAYMENT_TERMS, and AGREEMENT. For users focused on accounting rule analysis, ACCOUNTING_RULE_ID provides the operational foreign key to RA_RULES, while ACCOUNTING_RULE supplies the display name, making the view suitable for grouping contracts by revenue recognition or billing rule.
Common Use Cases and Queries
Typical scenarios include contract portfolio reporting, billing configuration audits, and reconciliation of contracts to their assigned accounting and invoicing rules. Because the view is obsolete and not implemented in the database, the following query illustrates the intended access pattern rather than a guaranteed live execution:
- Listing contracts by accounting rule:
SELECT contract_number, accounting_rule, contract_amount FROM bic_contract_headers_v WHERE accounting_rule IS NOT NULL; - Auditing contracts lacking an accounting rule:
SELECT contract_id, contract_number FROM bic_contract_headers_v WHERE accounting_rule_id IS NULL; - Grouping contract value by rule:
SELECT accounting_rule, SUM(contract_amount) FROM bic_contract_headers_v GROUP BY accounting_rule;
For current implementations, equivalent reporting should be reconstructed directly from OKS_ENT_HEADERS_V and RA_RULES, since the obsolete BIC view is not available for deployment.
-
View: BIC_CONTRACT_HEADERS_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_CONTRACT_HEADERS_V 12.1.1
Not implemented in this database·Explore BIC module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2