Results for “create_orders”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CSP_PARTS_REPAIR is a PL/SQL package belonging to the Oracle E-Business Suite Service (CSP) module. Its stated purpose, per the package header comment, is to contain procedures that create internal orders and repair orders for repair notifications. In the EBS 12.1.1 and 12.2.2 code lines, this places the package inside the depot repair and parts-requirement flow: when a repair notification identifies components or assemblies that must be sourced, repaired, or replenished, the package translates that business demand into the transactional documents (internal orders and repair orders) needed by downstream order management and procurement processing. The package declares AUTHID CURRENT_USER and is owned by APPS, so it executes with the privileges of the invoking user, consistent with standard EBS API coding practice and the FND_API error-handling model visible in its parameter signatures.

Key Procedures and Functions

• CREATE_ORDERS — the single documented procedure in the package (the header comment dates the original creation to 2003). Its purpose is to create the internal orders and repair orders associated with repair notifications. The signature reveals the standard EBS API conventions rather than the internal business logic: an API version parameter, an initialization flag for the message list, and a commit flag, all following FND_API constants; an IN OUT NOCOPY header record typed against csp_parts_requirement.Header_rec_type; an IN OUT NOCOPY line table typed against csp_parts_requirement.Line_Tbl_type; an input repair supplier identifier; and the standard three OUT NOCOPY return values (return status, message count, message data). The record and table types are defined in the companion CSP_PARTS_REQUIREMENT package, indicating that CREATE_ORDERS consumes an already-populated parts-requirement structure and converts it into orders.

Tables Accessed

The documented table reference is PO_REQUISITION_HEADERS_S, reached through an APPS synonym. This is the base table for purchasing requisition headers. Its presence confirms that at least one of the order-creation paths produces a requisition—consistent with the internal-order concept, where a requisition is the vehicle that drives an internal sales order between inventory organizations. The parts-requirement header and line data passed in through the CSP_PARTS_REQUIREMENT types supplies the item, quantity, and source information that populates the requisition and any resulting repair order. The ETRM excerpt lists a single referenced table, so any additional order-management or repair-order tables touched by the implementation are not surfaced by this metadata and should be confirmed by reviewing the packaged body rather than assumed.

Usage Notes

The package is referenced by three other packages in the ETRM repository, which indicates it is an internal service layer rather than a user-facing entry point. It is most likely invoked from the depot repair / parts requirement processing logic—typically triggered from the Service (Depot Repair) forms or from a concurrent program that processes repair notifications in batch—whenever a part requirement must be converted into an actual order. Because CREATE_ORDERS follows the FND_API contract, callers should always check x_return_status for FND_API.G_RET_STS_SUCCESS before proceeding, honor the p_commit flag to control transaction boundaries, and initialize the message list when p_Init_Msg_List is set so that messages accumulate correctly. Custom code should treat this as an unsupported internal API: Oracle's ETRM classification for the object is OTHER, not a public or certified API, so direct invocation carries upgrade risk and should be avoided where a documented public interface exists. The 2003 header revision and the low version number (115.1) suggest the package has been stable for many releases, and it should be validated in a test instance before use in any customization.