Search Results ozf_sd_batch_headers_all

Overview

OZF_SD_BATCH_HEADERS_ALL is a transactional table in the Oracle Trade Management (OZF) module of Oracle E-Business Suite. It stores the header-level information for Supplier Ship and Debit (S&D) batches, which are the containers through which distributors and suppliers process ship-and-debit claims against vendor purchase rebate agreements. In EBS 12.1.1 and 12.2.2 the table is owned by the OZF schema and holds 69 documented columns, making it one of the principal header entities in the S&D settlement flow. Each row represents one batch, identified by a surrogate primary key and a user-facing batch number, and is linked to a claim, a vendor, and the operating unit context in which the batch was created.

From a dimensional modeling perspective, the mined foreign-key structure supports classifying this object as a hub under a Data Vault heuristic: it is a standalone entity keyed by a single surrogate identifier with no dependent-child table feeding it, and it carries references outward to other hubs rather than resolving relationships between two or more hubs. Practically, it behaves as a header/satellite combination, since much of the row width consists of descriptive and flexfield attributes (for example the thirty ATTRIBUTE columns and the numerous vendor contact fields).

Key Information Stored

The table’s columns divide into identifying keys, business keys, foreign key references, and descriptive attributes. The most significant columns are:

• BATCH_ID — the surrogate primary key, enforced by OZF_SD_BATCH_HEADERS_ALL_PK and also covered by the unique index OZF_SD_BATCH_HEADERS_ALL_U1.
• BATCH_NUMBER — the user-visible batch identifier and a business-key candidate, enforced through unique index OZF_SD_BATCH_HEADERS_ALL_U2.
• CLAIM_ID — foreign key to OZF_CLAIMS_ALL, tying the batch to the claim it services. CLAIM_NUMBER and CLAIM_MINOR_VERSION carry the denormalized claim reference.
• VENDOR_ID, VENDOR_SITE_ID, and VENDOR_CONTACT_ID — supplier, supplier site, and contact associated with the batch or credit request.
• VENDOR_EMAIL, VENDOR_PHONE, VENDOR_FAX, and VENDOR_CONTACT_NAME — contact details used for supplier correspondence.
• STATUS_CODE and BATCH_TYPE — the lifecycle state and the classification of the batch (for example credit request versus ship-and-debit batch).
• CURRENCY_CODE, CREDIT_CODE, and VENDOR_CREDIT_REF — monetary context and the vendor’s reference for the resulting credit.
• BATCH_AMOUNT_THRESHOLD and BATCH_LINE_AMOUNT_THRESHOLD — the value limits applied when consolidating claim lines into a batch.
• PARENT_BATCH_ID and CHILD_BATCH_ID — self-referencing hierarchy for batch consolidation or splitting.
• ORG_ID — the operating unit, essential for Multi-Org security and reporting.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting the security-group filtering model.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and CREATED_FROM — concurrent-program and provenance metadata.
• OWNER_ID and IMD_CLAIM_FLAG — ownership reference and the flag indicating interaction with the IMD claim process.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF-based S&D user interface.
• The standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Reporting on S&D batches typically begins at the header and joins outward. A common query lists pending batches for a given operating unit:

• SELECT batch_id, batch_number, status_code, batch_submission_date, vendor_id FROM ozf_sd_batch_headers_all WHERE org_id = :p_org AND status_code = :p_status ORDER BY batch_submission_date;
• Linking to claims for reconciliation: SELECT h.batch_number, c.claim_number, h.vendor_credit_ref FROM ozf_sd_batch_headers_all h, ozf_claims_all c WHERE h.claim_id = c.claim_id;
• Locating a batch by its business key: SELECT * FROM ozf_sd_batch_headers_all WHERE batch_number = :p_batch_number;
• Isolating consolidated or split batches via the self-reference: SELECT batch_id, parent_batch_id, child_batch_id FROM ozf_sd_batch_headers_all WHERE parent_batch_id IS NOT NULL;

These queries support vendor settlement analytics, outstanding credit tracking, security-group-filtered reporting, and operational monitoring of submission and threshold parameters. Because the table is partitioned conceptually by ORG_ID and filtered by SECURITY_GROUP_ID, reports should always constrain on operating unit and security group to avoid cross-organization leakage.

Related Objects

The most significant related objects are derived from the documented foreign keys and the S&D batch structure:

• OZF_CLAIMS_ALL — referenced by CLAIM_ID; the claim that drives the batch and its settlement.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs record-level security filtering.
• OZF_SD_BATCH_LINES_ALL — the likely line-level child table keyed to BATCH_ID; stores the individual claim lines consolidated into the batch.
• OZF_SD_BATCH_HEADERS_ALL — self-referencing through PARENT_BATCH_ID and CHILD_BATCH_ID for batch hierarchy.
• PO_VENDORS / AP_SUPPLIERS and PO_VENDOR_SITES_ALL — the supplier and site referenced by VENDOR_ID and VENDOR_SITE_ID.
• FND_CONCURRENT_REQUESTS — related via REQUEST_ID, identifying the concurrent program that created or updated the batch.
• Trade Management S&D batch APIs and OAF pages — the application layer that creates and maintains these headers, including the object-version-number locking semantics.