Search Results ozf_chargeback_headers_all

Overview

The OZF_CHARGEBACK_HEADERS_ALL table is a core transactional entity within the Oracle Trade Management (OZF) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master record for a chargeback transaction, which is a financial claim typically issued by a supplier (manufacturer) to a customer (distributor or retailer) to recover funds related to trade promotions, pricing discrepancies, or other deductions. The table stores high-level administrative and customer information for the chargeback, establishing the foundational context for the detailed line items stored in its child table. Its multi-org structure, indicated by the "_ALL" suffix, supports implementations operating in a multi-organization environment.

Key Information Stored

While the provided metadata does not list all columns, the documented foreign key relationships and primary key define its critical structure. The primary identifier is the CHARGEBACK_HEADER_ID (synonymous with OZF_CHARGEBACK_HEADERS_ID). This unique key is populated from a sequence and is the primary reference for the chargeback document. The table centrally manages customer and site relationships through foreign keys: BILL_TO_CUST_ACCOUNT_ID and SHIP_TO_CUST_ACCOUNT_ID link to HZ_CUST_ACCOUNTS, while BILL_TO_SITE_USE_ID and SHIP_TO_SITE_USE_ID link to HZ_CUST_SITE_USES_ALL. This structure separates the legal billing entity from the physical shipment destination. Other typical columns in such a header table, inferred from standard practice, would include status, currency, chargeback number, creation date, and terms.

Common Use Cases and Queries

This table is central to chargeback lifecycle management and reporting. Common operational use cases include generating a summary of all chargebacks for a specific customer account, tracking chargebacks by status, and auditing creation data. For reporting, it is frequently joined to its lines and customer tables to analyze chargeback volume and value by customer, site, or time period. A fundamental query pattern retrieves header information with customer details:

• SELECT h.chargeback_header_id, h.chargeback_number, ca.account_name, h.status_code, h.creation_date FROM ozf_chargeback_headers_all h, hz_cust_accounts ca WHERE h.bill_to_cust_account_id = ca.cust_account_id AND ca.account_number = :p_cust_num;

Another critical pattern joins the header to its child lines to aggregate total chargeback amounts: SELECT h.chargeback_header_id, h.chargeback_number, SUM(l.chargeback_amount) FROM ozf_chargeback_headers_all h, ozf_chargeback_lines_all l WHERE h.chargeback_header_id = l.chargeback_header_id GROUP BY h.chargeback_header_id, h.chargeback_number;

Related Objects

The table exists within a defined relational schema, as per the provided metadata. Its primary relationship is a one-to-many parent link to the OZF_CHARGEBACK_LINES_ALL table via the CHARGEBACK_HEADER_ID foreign key. All transactional line details for a chargeback are stored in this child table. To resolve customer information, OZF_CHARGEBACK_HEADERS_ALL references two foundational Trading Community Architecture (TCA) tables: HZ_CUST_ACCOUNTS (for the customer account) and HZ_CUST_SITE_USES_ALL (for the specific bill-to and ship-to addresses). There are four documented foreign key relationships from this table:

• BILL_TO_CUST_ACCOUNT_ID → HZ_CUST_ACCOUNTS
• SHIP_TO_CUST_ACCOUNT_ID → HZ_CUST_ACCOUNTS
• BILL_TO_SITE_USE_ID → HZ_CUST_SITE_USES_ALL
• SHIP_TO_SITE_USE_ID → HZ_CUST_SITE_USES_ALL

Conversely, the table is referenced by one foreign key:

• OZF_CHARGEBACK_LINES_ALL.CHARGEBACK_HEADER_ID → OZF_CHARGEBACK_HEADERS_ALL