Search Results ece_spso_headers_pk

Overview

ECE_SPSO_HEADERS is an e-Commerce Gateway (EC) schema table that stores supplier schedule header data used to support outbound Planning Schedule (830/DELFOR) and Shipping Schedule (862/DELJIT) transactions in Oracle E-Business Suite 12.1.1 and 12.2.2. The table resides in the EC schema and is classified as VALID in the ETRM repository. It serves as the staging and generation repository for supplier scheduling data exchanged with trading partners through the e-Commerce Gateway, capturing both the transactional schedule information and the trading partner, ship-to organization, and supplier site context required to build ANSI X12 or EDIFACT outbound messages.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as a standalone entity. The metadata does not surface parent-child FK relationships to other tables, so ECE_SPSO_HEADERS is best modeled as a hub-like structure carrying its own descriptive attributes, rather than as a link or satellite dependent on another ECE object. Its 179 documented columns indicate a wide, denormalized staging surface rather than a normalized transactional core.

Key Information Stored

The physical primary key is defined by the constraint ECE_SPSO_HEADERS_PK over the composite columns SCHEDULE_ID and RUN_ID. A unique index, ECE_SPSO_HEADERS_U1, mirrors the same two columns, making (SCHEDULE_ID, RUN_ID) the documented business-key candidate as well. SCHEDULE_ID identifies the logical schedule instance, while RUN_ID ties the record to a specific concurrent program execution that generated it.

• SCHEDULE_ID / RUN_ID — composite surrogate and business key for the header row.
• TRANSACTION_DATE, TRANSACTION_CONTROL1–3, TRANSACTION_RECORD_ID — transactional identifiers embedded in the outbound message.
• SCHEDULE_TYPE, SCHEDULE_SUB_TYPE, SCHEDULE_STATUS, SCHEDULE_NUMBER_REVISION — classify the schedule and track its state.
• SCHEDULE_GENERATION_DATE, FORECAST_HORIZON_START_DATE, FORECAST_HORIZON_END_DATE — time boundaries for the forecast window.
• TP_LOCATION_CODE_EXT, TP_TRANSLATOR_CODE, TP_DESCRIPTION, COMMUNICATION_METHOD — trading partner and translator routing.
• SHIP_TO_ORG_NAME, SHIP_TO_ORG_CODE, SHIP_TO_ORG_CITY, SHIP_TO_ORG_COUNTRY, SHIP_TO_ORG_POSTAL_CODE — ship-to address block.
• SUPPLIER_NAME, SUPPLIER_NUMBER, SUPPLIER_SITE_CODE — supplier identification.
• SUPPLIER_SITE_ADDRESS_LINE_1–3, SUPPLIER_SITE_CITY, SUPPLIER_SITE_STATE, SUPPLIER_SITE_COUNTRY — supplier site address.
• MULTIPLE_SHIP_TO_ORG_FLAG, SHIP_TO_ORG_ENABLE_CUM_FLAG, SHIP_TO_ORG_CUM_START_DATE — cumulative quantity and multi-org indicators.
• DOCUMENT_ID, DOCUMENT_TYPE, DOCUMENT_CODE, DOCUMENT_PURPOSE_CODE, DOCUMENT_STANDARD — EDI document descriptors.
• TEST_FLAG, MAP_ID — test-mode and mapping references.
• Attribute flexfield groups — SCH_HEADER_ATTRIBUTE1–15, VENDOR_ATTRIBUTE1–15, VENDOR_SITE_ATTRIBUTE1–15, SHIP_ORG_ATTRIBUTE1–15, ORG_OPT_ATTRIBUTE1–15, TPH_ATTRIBUTE1–15, and TPD_ATTRIBUTE1–15 plus their category columns.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses center on auditing and troubleshooting outbound supplier schedules generated by e-Commerce Gateway concurrent programs. Analysts frequently join header rows to detail tables to reconstruct the transmission, or query by trading partner and date range to confirm delivery of an 830 or 862 message.

• Identify the most recent run per schedule: SELECT SCHEDULE_ID, MAX(RUN_ID) FROM EC.ECE_SPSO_HEADERS GROUP BY SCHEDULE_ID;
• List all headers for a trading partner: SELECT * FROM EC.ECE_SPSO_HEADERS WHERE TP_LOCATION_CODE_EXT = :tp;
• Reconcile generation output by REQUEST_ID to the concurrent request log.
• Report forecast horizon coverage using FORECAST_HORIZON_START_DATE and FORECAST_HORIZON_END_DATE.
• Filter test transmissions via TEST_FLAG = 'Y'.

Related Objects

The supplied metadata documents no FK parents, so relationships are typically established through shared keys and ECE sibling tables rather than enforced constraints.

• ECE_SPSO_DETAILS — line-level schedule rows joined on SCHEDULE_ID and RUN_ID.
• ECE_TP_HEADERS / ECE_TP_DETAILS — trading partner definitions referenced via TP_LOCATION_CODE_EXT.
• PO_VENDORS, PO_VENDOR_SITES_ALL — supplier and supplier site master data feeding SUPPLIER_NUMBER and SUPPLIER_SITE_CODE.
• HR_OPERATING_UNITS / HR_LOCATIONS_ALL — ship-to organization and address sources.
• FND_CONCURRENT_REQUESTS — concurrent program execution referenced by REQUEST_ID.
• ECX_OUTBOUND_LOG / ECE_OUTBOUND_LOG — outbound transmission history for the generated 830/862 message.