Search Results update_repair_actual_lines




Overview
Explore in AI Chat

Overview

CSD_REPAIR_ACTUAL_LINES_PVT is a private PL/SQL package body in the APPS schema that implements the business logic supporting actual repair line processing within Oracle Depot Repair, part of the Enterprise Asset Management / Service family in Oracle E-Business Suite. The package is classified as a PVT (private) API, meaning it is intended to be consumed internally by other CSD packages rather than called directly by external integrations. It provides the core create, update, delete, and locking primitives for repair actual lines, which record the labor, material, and charge detail captured against a repair order after work has been performed.

In ETRM, the search term lock_repair_actual_lines corresponds to the LOCK_REPAIR_ACTUAL_LINES procedure, which manages concurrency control over repair actual line records so that simultaneous edits by multiple Depot Repair users do not corrupt data. The package header date of 2008 and version 120.6 indicate a mature, stable implementation carried forward through EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package body exposes four documented procedures:

  • CREATE_REPAIR_ACTUAL_LINES — Creates repair actual lines. It accepts the standard API version, commit, initialization of message list, and validation level parameters, together with in/out records for the actual line (CSD_ACTUAL_LINES_REC_TYPE) and associated charge details (CS_CHARGE_DETAILS_PUB.CHARGES_REC_TYPE), returning standard return status, message count, and message data outputs. It is invoked from the Depot Repair Actuals UI.
  • UPDATE_REPAIR_ACTUAL_LINES — Modifies existing repair actual line records, applying the same API convention and charge record handling used by the create procedure.
  • DELETE_REPAIR_ACTUAL_LINES — Removes repair actual line records, including the corresponding charge detail, and returns the standard API response payload.
  • LOCK_REPAIR_ACTUAL_LINES — Acquires a lock on a repair actual line so that it may be safely amended without concurrent modification. This is the entry point associated with the user's search term and is the concurrency-control gateway for the create, update, and delete operations.

All procedures follow a uniform API signature pattern: an API version, a commit flag, a message-list initialization flag, an optional validation level, the record(s) being processed, and the x_return_status, x_msg_count, x_msg_data outputs. This consistency allows callers to chain operations and inspect failures uniformly.

Tables Accessed

The package reads and writes the core Depot Repair and Service tables through APPS synonyms:

  • CSD_REPAIR_ACTUAL_LINES — the primary table holding the individual actual line records created, updated, deleted, or locked by the package.
  • CSD_REPAIR_ACTUALS — the parent header for a repair's actuals; used to associate lines with their repair actual document.
  • CSD_REPAIRS — the repair order header; supplies the repair context and validated repair identity.
  • CSD_PRODUCT_TRANSACTIONS — product transaction history; used to link actual lines to the transactions they represent.
  • CS_ESTIMATE_DETAILS — estimate line details, referenced for pricing and charge validation.
  • CS_INCIDENTS_ALL_B — the incident/service request base table, providing the originating service request context.
  • CS_TRANSACTION_TYPES_B — transaction type definitions, used to classify the actual line transaction.
  • OE_ORDER_HEADERS_ALL and OE_PRICE_LISTS — Order Management header and price list tables, consulted to derive order association and pricing for charges captured on actual lines.

Usage Notes

CSD_REPAIR_ACTUAL_LINES_PVT is invoked from the Depot Repair Actuals user interface and from other CSD packages that manage repair transactions; ETRM records two dependent packages that reference it. Because it is a PVT API, custom code should not call it directly. Instead, developers should use the public API layer exposed by Depot Repair. Typical invocations occur when a technician records labor or material against a repair, when charges must be recalculated or revalidated, or when a line must be locked for editing. All operations follow the EBS API convention of validating inputs, accumulating messages on the stack, and honoring the p_commit and p_init_msg_list flags. Callers are expected to pass a properly initialized record and to inspect x_return_status before proceeding.