Search Results create_orders

Overview

CSP_PLANNED_ORDERS_W is a public wrapper package in the Oracle E-Business Suite Applications (APPS) schema, owned by APPS and classified under the OTHER API category. It belongs to the CSP (Supply Chain Planning / Collaborative Planning) product family and provides the published PL/SQL entry point through which planned orders are converted into executable order documents. The package is implemented as an AUTHID CURRENT_USER unit, meaning its SQL statements execute under the privileges of the calling schema rather than the definer of the package. This is characteristic of EBS interface wrappers that are invoked from multiple product schemas and from Java-based or forms-based clients.

From a business standpoint, the package supports the transition from planning output to execution. Supply chain planning processes generate planned orders as recommendations; this package receives that data and calls the underlying business logic that generates the corresponding orders in the execution system. In the 12.1.1 and 12.2.2 releases the object remains essentially unchanged from the version documented in the source header (cspwppos.pls 120.0, dated 12 July 2005), which reflects its stability as a legacy interface layer maintained for backward compatibility.

Key Procedures and Functions

• CREATE_ORDERS — The primary public procedure and the object of the user's search. It accepts the API version, message-list initialization flag, commit flag, and organization context, then consumes a set of parallel PL/SQL table (JTF_TABLE) parameters representing the planned-order lines to be processed. It returns the standard EBS API return status (x_return_status), message count (x_msg_count), and message data (x_msg_data) so callers can evaluate success or failure through the conventional FND message stack.
• ROSETTA_TABLE_COPY_IN_P1 — A generated (Rosetta/BC4J-style) helper that converts generic JTF scalar-typed tables supplied by the caller into the strongly typed csp_planned_orders.line_tbl_type record table used internally by the package.
• ROSETTA_TABLE_COPY_OUT_P1 — The inverse of the above, converting the internal typed line table back into the generic JTF_NUMBER, JTF_VARCHAR2_100, and JTF_DATE table structures for return to the caller.

The presence of paired Rosetta copy procedures indicates this package is exposed to Java-based middleware or the Oracle Applications Framework, which pass PL/SQL collections across the JDBC boundary as generic JTF tables rather than as product-specific record types.

Tables Accessed

The documented table referenced through APPS synonyms is PLITBLM, the standard EBS multi-lingual temporary table used to carry API message text and error rows between the API layer and the calling form or program. The package reads and writes PLITBLM to stage messages generated during order creation processing, enabling callers to retrieve localized message strings using the message count and message data returned by CREATE_ORDERS. No other base tables are documented as directly referenced, because the actual planned-order and order table manipulation is performed by subordinate APIs invoked from this wrapper.

Usage Notes

CSP_PLANNED_ORDERS_W is typically invoked as a subordinate interface called by planning-related concurrent programs, by the Collaborative Planning and Advanced Supply Chain Planning order-release flows, or by custom integration code that releases planned orders into a target instance. Callers must supply a valid organization and inventory item context, populate the parallel JTF tables with the planned-order line attributes (quantities, dates, and descriptive columns), and set p_commit according to the transaction scope demanded by the surrounding process — FND_API.G_TRUE for a self-contained release, or FND_API.G_FALSE when the call participates in a larger unit of work. Because the package is a wrapper, business validation, defaulting, and actual order insertion are delegated to underlying CSP and order-management APIs; customizations should therefore avoid modifying this package directly and instead call it as published, respecting the standard EBS API return-status conventions. Given that it is referenced by no other packages, its invocation surface is limited to forms, concurrent programs, and external integration clients.