Search Results ece_spso_trans2




Overview
Explore in AI Chat

Overview

APPS.ECE_SPSO_TRANS2 is a valid PL/SQL package body in the Oracle E-Business Suite APPS schema that supports supplier scheduling and supply-plan collaboration flows. Its name follows the ECE (e-Commerce Gateway / EDI) naming convention, and the metadata classifies it as an "OTHER" API rather than a public interface. Business-wise, the package belongs to the Supplier Scheduling (SPSO) area: it translates supplier schedules, releases, and shipment information exchanged between a buying organization and its suppliers through Oracle's collaborative planning modules into the ECE staging structures consumed by downstream outbound processes.

The package acts as a transformation and population layer. It reads purchasing and scheduling data from the CHV and PO table families and writes the results into ECE_SPSO_ITEM_DET, ECE_SPSO_SHIP_DET, and their corresponding _S staging tables. This data movement underpins the supplier schedule and shipment notification documents that trading partners receive.

Key Procedures and Functions

The documented package metadata lists a single callable program unit:

  • POPULATE_SUPPLIER_SCHED_API2 — the principal entry point of the package. This procedure populates the supplier schedule API structures, gathering the source data and loading it into the ECE_SPSO_* detail and staging tables. It is the successor to an earlier version of the supplier schedule population routine, and it is invoked by one other package according to the dependency metadata.

No additional procedures or functions are documented for this body. Parameter lists are not published in the ETRM metadata and are therefore not enumerated here.

Tables Accessed

The package reads and writes a defined set of tables, all resolved through APPS synonyms:

Usage Notes

ECE_SPSO_TRANS2 is an internal technical package rather than a documented public API. It is expected to be invoked indirectly — typically from supplier scheduling concurrent programs or from wrapper logic that builds the outbound supplier schedule and shipment notification messages. It relies on several supporting packages, including APP_EXCEPTION for error handling, FND_FILE for concurrent program output and logging, FND_PROFILE for profile option lookups, and EC_DEBUG for diagnostic tracing. Because it depends on these FND and debug utilities, the package is most likely executed in a concurrent program or batch context rather than from a form.

Because the metadata records no parameters and no public interface contract, custom code should not call POPULATE_SUPPLIER_SCHED_API2 directly. Any extension or troubleshooting should instead work through the officially supported supplier scheduling APIs. The presence of the _S staging tables indicates a two-step load: data is first staged, then validated and moved to the final detail tables during the ECE outbound processing cycle. The package is not referenced by any database object according to the dependency report, confirming it is an upper-layer routine invoked at runtime rather than a foundational library.