Search Results ozf_sd_request_hdrs_all_b_u2

Overview

OZF.OZF_SD_REQUEST_HEADERS_ALL_B is the foundational header table for Oracle E-Business Suite's Trade Management (formerly Oracle Sales and Marketing) Ship and Debit (S&D) functionality. It stores the header-level information for every ship and debit request submitted by suppliers, customers, or internal users to claim or request accrual-backed promotional offer funding. In the Oracle EBS 12.1.1 / 12.2.2 footprint, this table acts as the operational anchor for the S&D request lifecycle, capturing request identity, offer linkage, counterparty references, approval workflow timestamps, and financial budget figures.

The object carries an FND Design Data registration (OZF.OZF_SD_REQUEST_HEADERS_ALL_B) and is stored in the APPS_TS_TX_DATA tablespace with PCT Free of 10, reflecting its transactional nature. Its 69 documented columns include the standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, and similar), confirm columns, and business-specific attributes. In Data Vault modeling terms, the metadata classification suggests a hub-leaning structure: REQUEST_HEADER_ID behaves as a durable business key, while the surrounding descriptive and foreign-key columns represent contextual relationships to offers, customers, and suppliers.

Key Information Stored

The table's primary key is REQUEST_HEADER_ID (OZF_SD_REQUEST_HDRS_ALL_B_PK), which serves as the surrogate unique identifier for each S&D request header. Two unique indexes represent documented business-key candidates: OZF_SD_REQUEST_HDRS_ALL_B_U1 on REQUEST_HEADER_ID and OZF_SD_REQUEST_HDRS_ALL_B_U2 on OFFER_ID — the latter being precisely the index referenced in the user's search term "ozf_sd_request_hdrs_all_b_u2".

• REQUEST_NUMBER — the auto-generated or manually entered request number displayed on the SD Request Summary page.
• OFFER_ID — foreign key to OZF_OFFERS, tying the request to its promotional offer.
• OFFER_TYPE — the type of offer submitted to the Trade Management module.
• REQUEST_START_DATE / REQUEST_END_DATE — the S&D request validity window captured on the request header creation page.
• REQUEST_OUTCOME — outcome code with documented values IN PROGRESS, REJECTED, or ACCEPTED.
• DECLINE_REASON_CODE / RETURN_REASON_CODE — lookup-derived reason codes explaining rejection or return.
• REQUESTED_BUDGET_AMOUNT / APPROVED_BUDGET_AMOUNT — requested versus approved funding values.
• REQUEST_CURRENCY_CODE — currency of the budget amounts.
• SUPPLIER_ID, SUPPLIER_SITE_ID, SUPPLIER_CONTACT_ID — supplier party references; a non-unique index (OZF_SD_REQUEST_HDRS_ALL_B_N1) supports lookups by SUPPLIER_ID and SUPPLIER_SITE_ID.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS identifying the customer account.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS controlling row-level access.
• ORG_ID — multi-org operating unit identifier.
• ASIGNEE_RESOURCE_ID, ASIGNEE_RESPONSE_BY_DATE, ASIGNEE_RESPONSE_DATE — assignee and response tracking for the approval workflow.

A full set of ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 columns provides descriptive flexfield extensibility.

Common Use Cases and Queries

Typical reporting scenarios include tracking open S&D requests, measuring approval cycle times, and reconciling requested against approved budgets. A standard query joins the header to the multi-language translation table on REQUEST_HEADER_ID to retrieve translated request names, and to OZF_OFFERS via OFFER_ID to resolve offer descriptions.

• Status dashboards grouping by REQUEST_OUTCOME to count in-progress, accepted, and rejected requests.
• Supplier scorecards aggregating REQUESTED_BUDGET_AMOUNT and APPROVED_BUDGET_AMOUNT by SUPPLIER_ID and REQUEST_CURRENCY_CODE.
• Cycle-time analysis comparing INTERNAL_SUBMISSION_DATE, SUPPLIER_RESPONSE_DATE, and ASIGNEE_RESPONSE_DATE.
• Multi-org reporting filtered by ORG_ID and SECURITY_GROUP_ID to respect operating unit and security policies.
• Duplicate-offer checks leveraging the unique index OZF_SD_REQUEST_HDRS_ALL_B_U2 on OFFER_ID, which enforces one active request header per offer at the base-table level and is the object most likely returned when troubleshooting that specific index name.

Related Objects

This table integrates tightly with several core EBS and Trade Management objects. The most significant relationships, documented through the schema metadata, are:

• OZF.OZF_SD_REQUEST_HEADERS_ALL_TL — the translation (multi-language) table referencing this table on REQUEST_HEADER_ID; required for any UI or report needing translated content.
• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID to resolve customer account details.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID to enforce security group access.
• OZF_OFFERS — the promotional offer master referenced by OFFER_ID (documented as the foreign key target for the offer identifier).
• OZF_SD_REQUEST_LINES_ALL — the S&D request line detail table, which links back to this header through REQUEST_HEADER_ID, providing the line-level claim detail.
• POZ_SUPPLIERS / POZ_SUPPLIER_SITES_ALL — supplier master references joined on SUPPLIER_ID and SUPPLIER_SITE_ID.

Together these relationships make OZF_SD_REQUEST_HEADERS_ALL_B the central hub of the Ship and Debit request model, with downstream line tables, translation tables, and supplier/customer masters depending upon it.