Search Results ozf_sd_batch_headers_all_u1

Overview

OZF.OZF_SD_BATCH_HEADERS_ALL is the master header table for Supplier Ship and Debit (SD) batches in Oracle Trade Management, part of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 application stacks. A Supplier Ship and Debit batch is a container that groups supplier-facing claims — typically volume-incentive, rebate, or accrual-style claims — so that they can be submitted to a supplier for credit. This table stores one row per batch, capturing supplier identification, batch-level thresholds, submission status, and the WHO audit columns required by EBS multi-org and audit conventions.

The table is owned by the OZF schema and resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, typical of high-volume transactional data. The heuristic Data Vault classification of this object is standalone, which suggests it functions as an independent hub-like entity rather than a dependent link or satellite in a Data Vault model. Its two foreign keys — CLAIM_ID to OZF_CLAIMS_ALL and SECURITY_GROUP_ID to FND_SECURITY_GROUPS — indicate that although it is not formally a pure hub in the source schema, it plays a referential anchor role for claims and security grouping. The primary key is BATCH_ID, defined by the OZF_SD_BATCH_HEADERS_ALL_PK constraint.

Key Information Stored

The most operationally significant columns in this table include the surrogate primary key BATCH_ID, which uniquely identifies each batch, and the business-key candidate BATCH_NUMBER, enforced by the unique index OZF_SD_BATCH_HEADERS_ALL_U2. BATCH_NUMBER is a system-generated, VARCHAR2(30) value produced by the sequence OZF_SD_BATCH_HEADERS_ALL_S. A parallel unique index, OZF_SD_BATCH_HEADERS_ALL_U1, enforces uniqueness on BATCH_ID itself.

• BATCH_ID — surrogate primary key; the internal identifier referenced by all child batch lines.
• BATCH_NUMBER — user-visible unique batch identifier, generated by sequence.
• CLAIM_ID — foreign key to OZF_CLAIMS_ALL, linking the batch to its governing claim.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — supplier, supplier site, and supplier contact references; indexed by OZF_SD_BATCH_HEADERS_ALL_N1 to support supplier-centric lookups.
• VENDOR_EMAIL, VENDOR_PHONE, VENDOR_FAX — contact channels used when the batch is submitted to the supplier.
• CURRENCY_CODE, CREDIT_CODE, STATUS_CODE — batch currency, credit/debit indicator, and lifecycle status.
• BATCH_LINE_AMOUNT_THRESHOLD and BATCH_AMOUNT_THRESHOLD — thresholds inherited from the supplier trade profile at batch creation, controlling eligibility.
• BATCH_SUBMISSION_DATE — the date the batch was most recently submitted.
• ORG_ID and SECURITY_GROUP_ID — multi-org operating unit and security grouping; ORG_ID is indexed by OZF_SD_BATCH_HEADERS_ALL_N2.
• OBJECT_VERSION_NUMBER — optimistic locking control for HTML-based user interfaces.
• BATCH_TYPE, PARENT_BATCH_ID, CHILD_BATCH_ID, IMD_CLAIM_FLAG, CLAIM_MINOR_VERSION — batch hierarchy and claim-versioning attributes.
• WHO / audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, LAST_UPDATE_LOGIN) — standard EBS audit and concurrent-program traceability.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all batches for a supplier, identifying unsubmitted or failed batches, reconciling batch totals against claim amounts, and monitoring batch status progression for supplier settlement.

Sample query to retrieve all batches for a given supplier site, ordered by submission date:

• SELECT b.batch_id, b.batch_number, b.status_code, b.currency_code, b.batch_submission_date
FROM ozf.ozf_sd_batch_headers_all b
WHERE b.vendor_id = :vendor_id
  AND b.vendor_site_id = :vendor_site_id
ORDER BY b.batch_submission_date DESC;

Sample query to identify batches awaiting submission or in error status within an operating unit:

• SELECT batch_number, status_code, org_id
FROM ozf.ozf_sd_batch_headers_all
WHERE status_code IN ('NEW','ERROR')
  AND org_id = :org_id;

These queries benefit from the unique index on BATCH_NUMBER for single-batch lookups, the vendor index (VENDOR_ID, VENDOR_SITE_ID) for supplier-driven reports, and the ORG_ID index for multi-org filtered extracts.

Related Objects

The following objects are the most significant participants in this table's relationship network:

• OZF.OZF_CLAIMS_ALL — referenced by OZF_SD_BATCH_HEADERS_ALL.CLAIM_ID; the parent claim entity whose eligible lines are aggregated into a batch.
• FND_SECURITY_GROUPS — referenced by OZF_SD_BATCH_HEADERS_ALL.SECURITY_GROUP_ID; governs row-level security and data visibility.
• OZF.OZF_SD_BATCH_LINES_ALL — presumed child table keyed by BATCH_ID, holding the individual claim lines or transaction details within a batch.
• OZF.OZF_SD_BATCH_HEADERS_ALL_S — the sequence that generates BATCH_NUMBER values.
• OZF.OZF_SD_BATCH_HEADERS_ALL_PK / _U1 / _U2 — primary key and unique constraints enforcing the BATCH_ID and BATCH_NUMBER business keys.
• Supplier and vendor master tables (e.g., PO_VENDORS, PO_VENDOR_SITES_ALL, AP_SUPPLIERS) — logically referenced via VENDOR_ID and VENDOR_SITE_ID for supplier identification and contact detail.

Where the metadata lists only BATCH_ID and BATCH_NUMBER as unique business keys, developers should treat BATCH_ID as the immutable technical key and BATCH_NUMBER as the external-facing identifier used in supplier correspondence and reconciliation workflows.