Results for “error_message”

4 results




Overview
Explore in AI Chat

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

Overview

OZF_CHARGEBACK_INT_LOG is a table in the OZF (Trade Management) product schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to serve as the log table for the chargeback interface table. Chargebacks in Trade Management represent supplier or distributor claims generated when a customer purchases at a promotional price and the difference is later reclaimed through the interface pipeline. The interface table moves chargeback records into the transactional chargeback structures; OZF_CHARGEBACK_INT_LOG records the outcome of each attempt to process or load those records, capturing both successful diagnostics and error conditions.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. This is a modeling suggestion rather than an EBS implementation detail: the table is an attribute-bearing child of an interface record, carrying descriptive outcome data keyed to a parent business entity rather than acting as a standalone hub or as a pure associative link between two hubs.

Key Information Stored

The table is documented with nine physical columns. The surrogate primary key is CHARGEBACK_INT_LOG_ID, enforced by the unique index CHARGEBACK_INT_LOG_ID_PK. A second unique index, OZF_CHARGEBACK_INT_LOG_U1, also runs on CHARGEBACK_INT_LOG_ID, confirming it as the sole documented business-key candidate; there is no separate natural key column in the metadata.

  • CHARGEBACK_INT_LOG_ID — surrogate primary key, generated per log entry.
  • CHARGEBACK_INT_ID — foreign key to OZF_CHARGEBACK_INT_ALL, tying the log row to the interface record it describes.
  • ERROR_CODE — code identifying the failure or validation exception encountered during processing.
  • ERROR_MESSAGE — human-readable description of the error condition.
  • ERROR_TABLE_NAME — identifies the destination or target table in which the error occurred.
  • COLUMN_NAME — the specific attribute that failed validation, where applicable.
  • COLUMN_VALUE — the rejected value recorded for that attribute.
  • ORG_ID — the operating unit context of the interface record.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data segregation.

Common Use Cases and Queries

The principal use case is chargeback interface error diagnosis. Support and integration teams query the log to determine why a chargeback interface row did not load, and reporting teams summarize failure frequency by code or by operating unit.

  • Retrieve all errors for a given interface record:
    SELECT l.error_code, l.error_message, l.column_name, l.column_value FROM ozf.ozf_chargeback_int_log l WHERE l.chargeback_int_id = :p_int_id ORDER BY l.chargeback_int_log_id;
  • Aggregate failure counts for a period by operating unit:
    SELECT org_id, error_code, COUNT(*) FROM ozf.ozf_chargeback_int_log GROUP BY org_id, error_code;
  • Join to the parent interface table to correlate errors with payload data:
    SELECT a.chargeback_int_id, a.*, l.error_message FROM ozf.ozf_chargeback_int_all a, ozf.ozf_chargeback_int_log l WHERE a.chargeback_int_id = l.chargeback_int_id AND l.error_code IS NOT NULL;

Because the table is append-oriented, purge routines typically delete log rows for interface records that have successfully loaded, keeping only unresolved diagnostics.

Related Objects

  • OZF_CHARGEBACK_INT_ALL — the parent interface table; joined on OZF_CHARGEBACK_INT_LOG.CHARGEBACK_INT_ID = OZF_CHARGEBACK_INT_ALL.CHARGEBACK_INT_ID via the documented foreign key.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security group resolution.
  • OZF_CHARGEBACK_INT_LOG_PK / OZF_CHARGEBACK_INT_LOG_U1 — the primary and unique indexes enforcing uniqueness on CHARGEBACK_INT_LOG_ID.

The chargeback interface and its log support the broader Trade Management chargeback processing flow, in which populated interface rows are validated and transferred into the transactional chargeback tables, with any diagnostics written back to this log.