Search Results csd_ro_status_bevent_key_s1

Overview

APPS.CSD_REPAIRS_PVT is the private implementation package body for the Oracle E-Business Suite Depot Repair repair-order API stack. In EBS 12.1.1 and 12.2.2, this package encapsulates the business logic that creates, maintains, and transitions repair orders (ROs) recorded in the CSD_REPAIRS table. It sits beneath the public API layer, APPS.CSD_REPAIRS_PUB, which exposes the supported entry points to callers, while CSD_REPAIRS_PVT performs the actual validation, data manipulation, and workflow coordination.

The package belongs to the CSD (Depot Repair) product family and is classified as a PVT (private) API. Its documented status is VALID, and it is not referenced by any other database object, confirming its role as a top-level implementation unit invoked only through its public wrapper or directly by product forms and concurrent programs.

Key Procedures and Functions

ETRM documents sixteen procedures and functions within this package. The core transaction routines are:

• CREATE_REPAIR_ORDER — inserts a new repair order and its associated repair lines into CSD_REPAIRS.
• UPDATE_REPAIR_ORDER — modifies attributes of an existing repair order.
• DELETE_REPAIR_ORDER — removes a repair order and dependent records.
• VALIDATE_REPAIRS — applies business-rule validation over the repair records prior to persistence.

Attachment handling is provided by COPY_ATTACHMENTS and DELETE_ATTACHMENTS, which manipulate the FND_DOCUMENTS and FND_ATTACHED_DOCUMENTS framework on behalf of a repair order.

Status and repair-type maintenance is handled by UPDATE_RO_STATUS, UPDATE_RO_STATUS_WEBSRVC, and UPDATE_REPAIR_TYPE, together with the guard functions IS_RT_UPDATE_ALLOWED and IS_FLWSTS_UPDATE_ALLOWED that determine whether a repair type or flow status may be changed given current state.

Workflow integration is delivered by UPDATE_FLOW_STATUS, LAUNCH_FLWSTS_WF, RAISE_RO_STATUS_BEVENT, UPDATE_RO_STATUS_WF, and LAUNCH_WFEXCEPTION_BEVENT. These routines raise Oracle Workflow business events and launch flow-status and exception workflows that drive repair processing.

Tables Accessed

The package reads and writes the primary repair entities CSD_REPAIRS, CSD_REPAIR_ORDER_GROUPS, CSD_REPAIR_TYPES_B, CSD_RT_TRANS_B, and CSD_RT_TRAN_RESPS, which store repair order, grouping, repair-type, and repair-type transition data. Flow-status data is held in CSD_FLOW_STATUSES_B, CSD_FLWSTS_TRANS_B, CSD_FLWSTS_TRAN_MILES, and CSD_FLWSTS_TRAN_RESPS. Sequences CSD_REPAIRS_S1, CSD_REPAIRS_S2, CSD_RO_STATUS_BEVENT_KEY_S1, and CSD_WF_EXCEPTIONS_BEVENT_S1 supply surrogate keys. CSI_INSTALL_PARAMETERS and CSI_ITEM_INSTANCES link the repair to installed-base items, while CSD_WF_ITEM_KEY_S stores workflow item keys.

Usage Notes

CSD_REPAIRS_PVT is typically invoked indirectly through APPS.CSD_REPAIRS_PUB, which is the supported public interface. Depot Repair forms and concurrent programs call the public layer, which delegates to this private body. Custom integrations and web-service calls, including the WebSvc-specific wrapper UPDATE_RO_STATUS_WEBSRVC, may reach CSD_REPAIRS_PVT through the public API. Because the package raises workflow events and launches flows, it must be executed within a properly initialized EBS session where FND_GLOBAL, FND_MSG_PUB, and WF_ENGINE contexts are available. Direct calls to the PVT body are unsupported and should be avoided in favour of CSD_REPAIRS_PUB.