Search Results populate_supplier_sched_api2

Overview

ECE_SPSO_TRANS2 is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ECE (E-Commerce Gateway) module family. Its name reflects its role in the Supplier Scheduling / Planning and Shipping Schedule Outbound (SPSO) processing stream, where it supports the transformation and staging of supplier schedule data for EDI transmission between a buying organization and its suppliers. The package operates as a supporting driver inside the supplier scheduling workflow, taking planning and shipping schedule information held in the Oracle Purchasing supplier scheduling tables and preparing it for outbound interchange processing.

The header comment in the package spec records a performance-related change introduced under Bug 2064311, in which the batch_id parameter was added to the main procedure. This addition signals that the package is intended to process supplier schedule data in bounded batches rather than in a single monolithic pass, which matters for large suppliers with many schedules, releases, and line items.

Key Procedures and Functions

The package exposes a single documented procedure, POPULATE_SUPPLIER_SCHED_API2. Only the procedure name and purpose are fixed by the metadata; the parameter list is not reproduced here. Based on the package specification excerpt, the procedure is designed to accept a communication method (for example EDI), a transaction type distinguishing planning schedules (SPSO) from shipping schedules (SSSO), a document type (SPS versus SSS), a run identifier, an optional schedule identifier, and a batch identifier. Its function is to populate the outbound supplier schedule interface structures for a given run, optionally narrowed to a specific schedule and further segmented by batch.

The procedure does not exist in isolation. It is invoked as part of a larger outbound processing sequence, and the package is referenced by one other package in the APPS schema, indicating that it sits downstream of an orchestrating program rather than being the top-level entry point. No public functions are documented.

Tables Accessed

The procedure reads from and writes to a set of supplier scheduling and Purchasing document tables, all accessed through APPS synonyms. On the source side, it works with CHV_SCHEDULE_HEADERS, CHV_SCHEDULE_ITEMS, CHV_HORIZONTAL_SCHEDULES, and CHV_ITEM_ORDERS, which together hold the master schedule agreements, their scheduled items, horizontal schedule buckets, and item order references. Purchasing document context is obtained from PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and PO_RELEASES. Unit of measure conversion uses MTL_UNITS_OF_MEASURE.

On the staging side, the procedure populates the outbound interface tables ECE_SPSO_ITEM_DET and ECE_SPSO_ITEM_DET_S for planning schedule item detail, and ECE_SPSO_SHIP_DET and ECE_SPSO_SHIP_DET_S for shipping schedule detail. ECE_TP_DETAILS supplies trading partner detail used to identify the EDI destination. DUAL is referenced for single-row lookups and defaulting logic.

Usage Notes

ECE_SPSO_TRANS2 is normally invoked from the ECE outbound processing programs that generate supplier schedule EDI transactions, rather than being called directly from a form. In a typical EBS 12.1.1 or 12.2.2 environment, the concurrent program responsible for outbound supplier scheduling processing calls POPULATE_SUPPLIER_SCHED_API2 with the appropriate transaction and document types, passing the run and batch identifiers to control scope and throughput. Custom code should mirror this pattern: supply a nonzero batch identifier, set the schedule identifier when a single schedule must be processed, and rely on the procedure to stage rows in the ECE_SPSO_ITEM_DET and ECE_SPSO_SHIP_DET families before the EDI translation and delivery steps run.