Search Results ozf_sd_batch_lines_int_all_pk

Overview

OZF_SD_BATCH_LINES_INT_ALL is an interface (staging) table owned by the OZF schema within the Oracle Trade Management module of Oracle E-Business Suite. Its documented purpose is to receive data transmitted during vendor authorization processing of Supplier Ship and Debit (SD) batches. In the Supplier Ship and Debit flow, a distributor submits claims against a supplier for ship-and-debit arrangements, and the supplier responds with an authorization transmission. This interface table captures the inbound vendor authorization payload at the batch-line level before it is validated and loaded into the permanent Trade Management transaction tables.

The table contains 266 documented columns, reflecting the broad scope of the vendor authorization document, which carries ship-from, distribute-by, ship-to, sold-to, and used-by party blocks, along with order, invoice, and cost details. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This is consistent with an interface table: it does not participate in enforced parent/child relationships but instead acts as a landing zone whose identifiers (such as BATCH_ID and BATCH_LINE_ID) are correlated to core entities during the subsequent import and validation process.

Key Information Stored

The primary key of the table is OZF_SD_BATCH_LINES_INT_ALL_PK, defined on the surrogate column BATCH_LINE_INT_ID. A unique index, OZF_SD_BATCH_LINES_INT_ALL_U1, is also defined on BATCH_LINE_INT_ID, making it both the surrogate key and the documented business-key candidate at the interface level. The most operationally significant columns include:

• BATCH_LINE_INT_ID — surrogate primary key for each staging record.
• BATCH_ID and BATCH_LINE_ID — foreign references to the parent Supplier Ship and Debit batch and its line in the permanent tables.
• SHIP_FRM_SD_AUTHORIZATION_ID, SHIP_FRM_SD_CLAIM_REQUEST_ID, and SHIP_FRM_SD_CLAIM_REQUEST_DATE — identify the supplier authorization and linked claim request.
• BATCH_LINE_NUMBER, ORDER_NUMBER, ORDER_LINE_NUMBER, INVOICE_NUMBER, and INVOICE_LINE_NUMBER — the transaction document references that tie the claim to actual sales activity.
• SHIPPED_QUANTITY, VENDOR_AUTH_QUANTITY, COST_MONETARY_AMOUNT, AUTH_COST_MONETARY_AMOUNT, and VENDOR_AUTH_COST_MONETARY_AMT — the quantities and cost values submitted or authorized.
• GBL_CLAIM_DISPOSITION_CODE and the GBL_CLAIM_REJ_CODE1 through GBL_CLAIM_REJ_CODE10 columns — capture claim disposition and up to ten rejection reasons returned by the vendor.
• PROCESSED_FLAG — controls whether the staging line has been consumed by the import program.
• VALIDATION_TXT — holds validation error messages generated during processing.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and REQUEST_ID, plus the HEADER_ATTRIBUTE1–30 and LINE_ATTRIBUTE1–30 descriptive flexfield columns.

Common Use Cases and Queries

The principal use case is monitoring and troubleshooting the Supplier Ship and Debit vendor authorization import. Typical queries check unprocessed lines and validation failures before rerunning the import:

• Pending records: SELECT BATCH_LINE_INT_ID, BATCH_ID, ORDER_NUMBER, INVOICE_NUMBER, PROCESSED_FLAG, VALIDATION_TXT FROM OZF.OZF_SD_BATCH_LINES_INT_ALL WHERE PROCESSED_FLAG = 'N';
• Rejected lines: query rows where GBL_CLAIM_REJ_CODE1 is populated to analyze vendor rejection patterns by disposition code.
• Reconciliation: compare VENDOR_AUTH_QUANTITY and VENDOR_AUTH_COST_MONETARY_AMT against the corresponding claim amounts to detect short-pays.
• Batch-level audit: group records by BATCH_ID and REQUEST_ID to trace which concurrent request loaded each batch.
• Reporting: join to the SD batch and claim tables on BATCH_ID or SHIP_FRM_SD_CLAIM_REQUEST_ID to build authorization and claim-status reports for the supplier recovery process.

Related Objects

As an interface table, OZF_SD_BATCH_LINES_INT_ALL is populated by the vendor authorization transmission process and consumed by the Supplier Ship and Debit import concurrent program, which writes into the base SD batch tables. The most significant related objects, joined on the columns documented above, include:

• OZF_SD_BATCHES_ALL — parent Supplier Ship and Debit batch; join on BATCH_ID.
• OZF_SD_BATCH_LINES_ALL — permanent batch lines; join on BATCH_LINE_ID and BATCH_ID.
• OZF_SD_CLAIMS_ALL — claim records linked through SHIP_FRM_SD_CLAIM_REQUEST_ID.
• OZF_SD_AUTHORIZATIONS_ALL — vendor authorization records linked by SHIP_FRM_SD_AUTHORIZATION_ID.
• OZF_CLAIMS_ALL — the underlying Trade Management claim header referenced by the claim request ID.
• Concurrent programs for Supplier Ship and Debit interface import and purge, which read and clear rows from this table.
• FND_REQUEST / FND_CONCURRENT_REQUESTS, joined on REQUEST_ID, for tracing the loading process.