Search Results rosetta_table_copy_in_p8




Overview

CSD_SOO_PVT_W is a public wrapper package within the Oracle E-Business Suite service and depot repair module (CSD). It is deployed under the APPS schema with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the package owner. The package functions as the externally callable interface to the SOO (Sales Order Orchestration) private processing logic encapsulated in CSD_SOO_PVT, and provides the entry point through which callers request a refresh of service order orchestration data.

In the depot repair and service fulfillment flows, the orchestration process synchronizes repair order attributes — status, repair type, priority, age, and due dates — with the underlying order orchestration tables. CSD_SOO_PVT_W exposes this synchronization as a single well-defined call, shielding callers from the internal PL/SQL table types defined in the private package. The "_W" suffix follows the standard Oracle EBS naming convention for a wrapper layer that publishes a private API to external consumers and additional modules.

The package header is at version 120.0.12020000.3 (dated 2013/05/08), consistent with use in both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package documents three public procedures:

  • ROSETTA_TABLE_COPY_IN_P8 — Converts a JTF_NUMBER_TABLE (the generic numeric table type used across the EBS JTF framework) into the strongly typed CSD_SOO_PVT.SO_ORCHESTRATION_KEY_TBL_TYPE consumed by the private package. It exists because the wrapper deliberately accepts generic collections from external callers, decoupling them from the internal type definition.
  • ROSETTA_TABLE_COPY_OUT_P8 — Performs the inverse conversion, translating the private SO_ORCHESTRATION_KEY_TBL_TYPE back into a JTF_NUMBER_TABLE for return to external callers. Together, the two "Rosetta" procedures act as a serialization boundary between generic and private collection types, a pattern used extensively where table types cannot be published directly.
  • REFRESH — The principal business procedure. It accepts an orchestration key collection plus a set of repair-order context attributes (repair line, document type, operating unit, inventory organization, repair owner, repair status, repair type, priority code, repair order age, and due-date age) and standard API control and result parameters, including API version, commit and message-list flags, validation level, and return status, message count, and message data outputs. Its purpose is to recompute and persist the orchestration state for the identified repair orders, returning standard EBS API diagnostics to the caller.

Tables Accessed

The documented table reference is PLITBLM, accessed via an APPS synonym. PLITBLM is the standard Oracle EBS temporary/PL-SQL table storage object used by the table-handler infrastructure to marshal collection data between the database and calling environments, including Oracle Forms. Its presence confirms that CSD_SOO_PVT_W supports collection-based invocation, where the orchestration key table is passed through the table-handler mechanism rather than as an inline array.

No other base tables are documented at the wrapper level; the substantive read and write activity against service order and depot repair tables occurs inside CSD_SOO_PVT, which this package delegates to.

Usage Notes

CSD_SOO_PVT_W is intended for programmatic invocation rather than direct end-user interaction. Typical callers include depot repair Oracle Forms that pass orchestration keys through the table handler, concurrent programs that batch-refresh orchestration data across large repair order populations, and custom extensions or integrations that need to trigger orchestration refresh without accessing the private package.

Callers should supply the API version, commit, message-list, and validation-level arguments in accordance with standard EBS API conventions, and must inspect X_RETURN_STATUS plus the message outputs to determine success or failure. Because the package is AUTHID CURRENT_USER, the invoking schema requires the appropriate privileges on CSD_SOO_PVT and its underlying objects. ETRM records no other packages referencing CSD_SOO_PVT_W, indicating that it is a leaf-level public API consumed by forms, concurrent managers, or custom code rather than by other PL/SQL packages. As with any wrapper whose private implementation may change between patch levels, callers should rely only on the documented signatures and avoid depending on internal type definitions.