Search Results ece_spso_item_det




Overview
Explore in AI Chat

Overview

ECE_SPSO_ITEM_DET is a table in the EC (e-Commerce Gateway) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It contains the supplier schedule item detail data required to support outbound Planning Schedule (830/DELFOR) and Shipping Schedule (862/DELJIT) transactions. In practice, this table functions as a staging and detail repository that the e-Commerce Gateway populates when it extracts scheduling agreement information from the planning and procurement modules, then flattens and formats that data prior to generating the outbound EDI/XML message.

From a Data Vault modeling perspective, the documented schema is classified heuristically as standalone, meaning it is not joined to other EC tables through foreign keys. This is a modeling suggestion rather than a physical constraint. The table's composite primary key includes RUN_ID alongside the schedule identifiers, which indicates it behaves more like a detail satellite capturing a snapshot of schedule lines for a specific outbound processing run than a conventional hub or link.

Key Information Stored

The table is documented with 26 columns. The most operationally significant are the identifiers and quantity fields:

Common Use Cases and Queries

Typical use is diagnostic: when an outbound planning or shipping schedule fails validation or contains unexpected quantities, support analysts query this table by RUN_ID or SCHEDULE_ID to inspect the extracted detail before transmission. A common pattern is:

  • SELECT schedule_item_detail_sequence, detail_category, starting_date, forecast_quantity, release_quantity, total_quantity FROM ec.ece_spso_item_det WHERE schedule_id = :schedule_id AND run_id = :run_id ORDER BY starting_date;
  • Reconciling extracted totals against source planning data by summing TOTAL_QUANTITY grouped by SCHEDULE_ITEM_ID.
  • Auditing a specific concurrent request via WHERE request_id = :req_id to confirm which schedule rows were processed.
  • Reporting forecast visibility windows by joining on DOCUMENT_NUMBER to order headers for supplier collaboration reviews.

Related Objects

The documented relationship data classifies this object as standalone, so no foreign keys are formally declared. In practice it participates in the e-Commerce Gateway supplier-scheduling family alongside ECE_SPSO_HEADER_DET (parent schedule header detail) and associated item-level tables sharing SCHEDULE_ID, SCHEDULE_ITEM_ID, and RUN_ID join columns. It is populated by the Planning and Shipping Schedule extraction concurrent programs (traceable through PROGRAM_ID and REQUEST_ID) and consumed by the gateway outbound processing that reads TRANSACTION_RECORD_ID. Downstream, the generated EDI 830 and 862 messages reference these rows before delivery to the supplier.