Search Results ozf_sd_batch_lines_int_all_n1

Overview

OZF.OZF_SD_BATCH_LINES_INT_ALL is an interface (staging) table in the Oracle Trade Management module of Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). It receives data transmitted from vendor (supplier) authorization feeds for Supplier Ship and Debit (SD) batch processing. The table is registered as FND Design Data OZF.OZF_SD_BATCH_LINES_INT_ALL, holds VALID status, and is created in the APPS_TS_TX_DATA tablespace with PCTFREE 10. It is a standalone object in terms of referential structure; no foreign keys are mined. Under heuristic Data Vault classification it is modeled as a standalone entity, though its natural role resembles a landing satellite that captures the raw inbound authorization payload before validation and promotion into the transactional SD tables.

Key Information Stored

The physical schema documents 266 columns. The most significant are:

• BATCH_LINE_INT_ID — interface record identifier and the surrogate primary key, enforced by unique index OZF_SD_BATCH_LINES_INT_ALL_U1 (also the heuristic business-key candidate).
• SHIP_FRM_SD_AUTHORIZATION_ID, SHIP_FRM_SD_CLAIM_REQUEST_ID, SHIP_FRM_SD_CLAIM_REQUEST_DATE — link the staged line back to the supplier authorization and Ship-and-Debit claim request.
• BATCH_ID, BATCH_LINE_ID, BATCH_LINE_NUMBER — the batch header, target line, and line sequence (a nonunique index, OZF_SD_BATCH_LINES_INT_ALL_N1, covers SHIP_FRM_SD_CLAIM_REQUEST_ID + BATCH_LINE_NUMBER).
• ORDER_NUMBER, ORDER_LINE_NUMBER, ORDER_DATE, INVOICE_NUMBER, INVOICE_LINE_NUMBER, INVOICE_DATE — commercial references supporting claim matching.
• SHIPPED_QUANTITY, VENDOR_AUTH_QUANTITY, GBL_UOM, SHIP_DATE — quantities and unit of measure for the authorized shipment.
• COST_MONETARY_AMOUNT, AUTH_COST_MONETARY_AMOUNT, RESALE_MONETARY_AMOUNT, VENDOR_AUTH_COST_MONETARY_AMT (with corresponding currency codes) — cost, authorized cost, and resale values.
• VENDOR_PRODUCT_ID, DIST_PRODUCT_ID — vendor and distributor product identifiers.
• GBL_CLAIM_DISPOSITION_CODE, GBL_CLAIM_REJ_CODE1–10, VALIDATION_TXT — claim disposition and rejection diagnostics.
• PROCESSED_FLAG, REQUEST_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrency and concurrent-program audit controls.
• HEADER_ATTRIBUTE1–30 and LINE_ATTRIBUTE1–30 (with matching category columns) — DFF extensibility for header- and line-level data.

Extensive FROM, DIST_BY, SHIP_TO, SOLD_TO, USED_BY, and TO address/contact blocks mirror the RosettaNet-style partner, contact, and location structure of the inbound authorization message.

Common Use Cases and Queries

Typical scenarios include monitoring inbound vendor authorization loads, reconciling staged lines against SD claims, and troubleshooting validation failures before promotion to the base tables.

• Identifying unprocessed lines:
  SELECT BATCH_LINE_INT_ID, BATCH_ID, ORDER_NUMBER, SHIPPED_QUANTITY
FROM OZF.OZF_SD_BATCH_LINES_INT_ALL
WHERE PROCESSED_FLAG = 'N';
• Reviewing validation failures:
  SELECT BATCH_LINE_INT_ID, VALIDATION_TXT, GBL_CLAIM_DISPOSITION_CODE
FROM OZF.OZF_SD_BATCH_LINES_INT_ALL
WHERE VALIDATION_TXT IS NOT NULL;
• Linking to the originating claim request (uses the OZF_SD_BATCH_LINES_INT_ALL_N1 index path):
  SELECT SHIP_FRM_SD_CLAIM_REQUEST_ID, BATCH_LINE_NUMBER, RESALE_MONETARY_AMOUNT
FROM OZF.OZF_SD_BATCH_LINES_INT_ALL
WHERE SHIP_FRM_SD_CLAIM_REQUEST_ID = :p_claim_request_id
ORDER BY BATCH_LINE_NUMBER;

The table supports open-interface reporting, reconciliation of vendor-authorized versus claimed cost, and concurrent-program diagnostics by REQUEST_ID.

Related Objects

• OZF_SD_BATCHES_ALL — parent batch header; joined via BATCH_ID.
• OZF_SD_BATCH_LINES_ALL — target transactional line table; joined via BATCH_LINE_ID / BATCH_LINE_NUMBER.
• OZF_SD_CLAIM_REQUESTS_ALL — Ship-and-Debit claim request; joined via SHIP_FRM_SD_CLAIM_REQUEST_ID.
• OZF_SD_AUTHORIZATIONS_ALL — vendor authorization header; joined via SHIP_FRM_SD_AUTHORIZATION_ID.
• OZF_SD_CLAIMS_ALL — resulting claim records populated during processing.
• FND_CONCURRENT_REQUESTS — correlated through REQUEST_ID for load-program traceability.
• OZF_SD_BATCH_LINES_INT — the non-_ALL interface view/synonym exposing this data to the application layer.

No foreign keys are documented on this object; joins above are inferred from column semantics and the documented unique/nonunique indexes rather than enforced constraints.