Search Results chargeback_int_id




Overview

The OZF_CHARGEBACK_INT_ALL table is a core interface table within the Oracle Trade Management (OZF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the primary staging area for importing and processing chargeback transactions. Chargebacks are financial claims made by a trading partner, such as a distributor or retailer, against a supplier for various promotional or pricing adjustments. This table acts as the intermediary data store where raw chargeback data is loaded, typically via a custom interface program or data import, before being validated and processed into the main transactional tables of the Trade Management system. Its role is critical for ensuring data integrity and facilitating the automated reconciliation of high-volume chargeback claims.

Key Information Stored

The table stores a record for each chargeback line item being interfaced. While the full column list is not detailed in the provided metadata, the foreign key relationships indicate it holds essential identifiers for the transaction and the involved trading partners. The primary key is the CHARGEBACK_INT_ID column. Critical foreign key columns include BILL_TO_CUST_ACCOUNT_ID and BILL_TO_SITE_USE_ID, which link to the HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL tables to identify the customer account and specific billing site. Similarly, SHIP_TO_CUST_ACCOUNT_ID and SHIP_TO_SITE_USE_ID identify the shipping customer and site. The BATCH_ID column links to the OZF_BATCHES_ALL table, allowing chargebacks to be grouped and processed in logical sets. The table likely also contains columns for chargeback amount, reason code, reference document numbers (like invoice numbers), product identifiers, and status flags to track the interface record's processing state.

Common Use Cases and Queries

The primary use case is the batch import and validation of chargeback data from external systems or spreadsheets. A typical process involves inserting records into this table, running a validation and import concurrent program, and then reviewing errors in the related log table. Common queries include identifying pending interface records for a specific batch or customer, and troubleshooting failed imports. Sample SQL patterns include:

  • Selecting unprocessed records: SELECT * FROM ozf_chargeback_int_all WHERE batch_id = :p_batch_id AND process_status IS NULL;
  • Joining with customer data for validation reports: SELECT int.*, cust.account_number FROM ozf_chargeback_int_all int, hz_cust_accounts cust WHERE int.bill_to_cust_account_id = cust.cust_account_id;
  • Investigating errors by joining with the log table: SELECT int.*, log.error_message FROM ozf_chargeback_int_all int, ozf_chargeback_int_log log WHERE int.chargeback_int_id = log.chargeback_int_id;

Related Objects

The table has defined relationships with several key EBS objects, primarily within the Trade Management and Trading Community Architecture modules. The documented foreign key relationships are as follows:

  • Primary Key: CHARGEBACK_INT_ID_PK on column CHARGEBACK_INT_ID.
  • Foreign Keys (Referencing Parent Tables):
    • OZF_CHARGEBACK_INT_ALL.BILL_TO_CUST_ACCOUNT_ID references HZ_CUST_ACCOUNTS.
    • OZF_CHARGEBACK_INT_ALL.BILL_TO_SITE_USE_ID references HZ_CUST_SITE_USES_ALL.
    • OZF_CHARGEBACK_INT_ALL.SHIP_TO_CUST_ACCOUNT_ID references HZ_CUST_ACCOUNTS.
    • OZF_CHARGEBACK_INT_ALL.SHIP_TO_SITE_USE_ID references HZ_CUST_SITE_USES_ALL.
    • OZF_CHARGEBACK_INT_ALL.BATCH_ID references OZF_BATCHES_ALL.
  • Foreign Keys (Referenced by Child Tables):