Search Results ozf_rule_based_log

Overview

OZF_RULE_BASED_LOG is a Trade Management (OZF) transactional table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It records rule-based claim data generated by the Trade Management rule engine, capturing the outcome of processing events that match configured accrual or claim rules. The table is owned by the OZF schema and is marked VALID in the ETRM data dictionary. Physically it is defined with 13 columns.

Because the table holds one record per rule-processing event and is keyed by a surrogate identifier, a Data Vault heuristic modeling exercise classifies it as a satellite—an insert-mostly log of descriptive attributes and outcomes attached to parent business entities. It is not a hub or link in the strict sense, since its natural business key (the claim context) is carried as a foreign key rather than as the table's own identity. This classification is a suggestion for analytical modeling only; the operational table itself is a conventional Oracle EBS transaction log.

Key Information Stored

The surrogate primary key is LOG_ID, enforced by the constraint OZF_RULE_BASED_LOG_PK. It is a system-generated sequence value with no business meaning. The most significant columns are:

• LOG_ID – surrogate primary key; unique identifier for each rule-based log entry.
• CLAIM_ID – foreign key to OZF_CLAIMS_ALL; links the log record to the parent claim. This is the primary business-key candidate for joining to claim data.
• QP_LIST_HEADER_ID – references the Advanced Pricing price list header (QP_LIST_HEADERS) associated with the claim or rule evaluation.
• CUSTOMER_TRX_ID – references the AR transaction (RA_CUSTOMER_TRX_ALL) tied to the claim, enabling linkage between Trade Management claims and receivables.
• PROCESSED_MATCH_TYPE – indicates the match type applied during rule processing, a key analytic dimension for rule effectiveness reporting.
• CREATED_FROM – records the source of the record's creation, supporting audit and diagnostic analysis of rule execution paths.
• REQUEST_ID – concurrent request identifier that generated or processed the record, useful for tracing batch rule runs.
• PROGRAM_APPLICATION_ID – identifies the application that owns the concurrent program which produced the row.
• CREATION_DATE / CREATED_BY – standard WHO audit columns recording record creation.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN – standard WHO audit columns tracking the last modification.

No unique business-key index is documented beyond the primary key, so CLAIM_ID plus the audit columns are the practical composite used for entity resolution.

Common Use Cases and Queries

Typical scenarios include auditing rule processing for a claim, diagnosing why a claim matched or failed to match a rule, and reconciling rule-based claims with pricing and receivables data. A representative query pattern joining the log to the parent claim is:

• Trace all rule events for a claim: SELECT l.LOG_ID, l.CLAIM_ID, l.PROCESSED_MATCH_TYPE, l.CREATION_DATE FROM OZF_RULE_BASED_LOG l WHERE l.CLAIM_ID = :claim_id ORDER BY l.CREATION_DATE;
• Reconcile claims to receivables: join CUSTOMER_TRX_ID to RA_CUSTOMER_TRX_ALL to verify that rule-generated claims produced the expected invoice transactions.
• Batch diagnostics: group by REQUEST_ID and PROGRAM_APPLICATION_ID to measure which concurrent program produced rule results and when.
• Pricing analysis: join QP_LIST_HEADER_ID to QP_LIST_HEADERS to confirm which price lists drove rule outcomes.

Because the table grows as a log, reporting queries should restrict by CREATION_DATE or CLAIM_ID to avoid full scans.

Related Objects

The following objects are the most significant dependencies and reference points:

• OZF_CLAIMS_ALL – parent claim table; joined on OZF_RULE_BASED_LOG.CLAIM_ID = OZF_CLAIMS_ALL.CLAIM_ID. This is the only documented foreign key relationship.
• OZF_CLAIMS_VL – view layer over claims, commonly joined for reporting claim attributes alongside log entries.
• QP_LIST_HEADERS – Advanced Pricing price list headers; joined on QP_LIST_HEADER_ID.
• RA_CUSTOMER_TRX_ALL – AR transactions; joined on CUSTOMER_TRX_ID.
• FND_CONCURRENT_REQUESTS – concurrent request metadata; joined on REQUEST_ID for batch traceability.
• OZF_RULE_BASED_PROCESS (or equivalent Trade Management rule processing program/logic) – the consumer that populates this table during claim rule evaluation.

Together these associations make OZF_RULE_BASED_LOG the audit trail connecting Trade Management claims, pricing rules, and receivables transactions. All observations above are grounded in the documented schema; supplemental relationships should be validated against the target instance's data dictionary.