Search Results update_installation_details

Overview

CS_INST_DETAIL_PUB is a public PL/SQL API package in the Oracle E-Business Suite Applications (APPS) schema that manages installation detail records within the Oracle Service (CS) module. Installation details represent individual instances of a customer product that has been installed at a specific party site, tracked against an order line, quote line shipment, or source installation detail. The package encapsulates the create, read, update, and delete operations for these records, exposing a controlled public interface for external callers while shielding them from the underlying table structures and business rules.

The package defines the Line_Inst_Dtl_Rec_Type record structure, which is the primary payload exchanged between calling programs and the API. This record carries the line installation detail identifier, order line identifier, quote line shipment identifier, source line installation detail identifier, transaction type, system identifier, customer product identifier, type code, quantity, the installed-at party site identifier, expected installation date, active date range, RMA-related fields, and receipt transaction identifier. Most attributes default to the FND_API.G_MISS_* sentinel values, enabling the API to distinguish between attributes the caller intends to leave unchanged and attributes intended to be set to NULL. The package also declares the Line_Inst_Dtl_Tbl_Type PL/SQL table type for bulk operations, and the Rma_Rcpt_Rec_Type record used for RMA receipt processing. Notably, the descriptive flexfield record was deliberately excluded from the line installation detail record type because a PL/SQL table cannot be based on a record type containing a non-scalar field. The header information indicates the package has been in service since at least 2006.

Key Procedures and Functions

• GET_LINE_INST_DETAILS — Retrieves line installation detail information given identifying criteria such as an order line identifier. It returns the full Line_Inst_Dtl_Rec_Type structure, including the line_inst_detail_id, because the same record type is used for both retrieval and maintenance.
• GET_RMA_LINE_INST_DETAILS — Returns installation detail information in the context of RMA processing, supporting the return and receipt flow for installed products.
• CREATE_INSTALLATION_DETAILS — Creates new installation detail records from the supplied record structure, validating inputs and applying defaulting and business rules.
• UPDATE_INSTALLATION_DETAILS — The procedure matched by the search term "update_installation_details." It modifies existing installation detail records, honoring the G_MISS_* sentinel convention so that only explicitly supplied attributes are changed.
• DELETE_INSTALLATION_DETAILS — Removes installation detail records, either physically or through the module's standard logical deletion semantics.
• UPDATE_INST_DETAILS_RMA_RCPT — Updates installation details in conjunction with RMA receipt activity, linking the installation detail to receipt and RMA line information.

Tables Accessed

The package operates against the installation detail base table and its associated entities through APPS synonyms. The line installation detail table stores the per-line installation records keyed by line_inst_detail_id and order_line_id, with foreign references to quote line shipments, customer products, party sites, transaction types, and RMA lines. The fields installed_cp_return_by_date, installed_cp_rma_line_id, new_cp_rma_line_id, and new_cp_return_by_date indicate interaction with customer product return and RMA line tables, while rcv_transaction_id links the detail to receiving transactions. The API reads and writes these tables to persist installation status and to support the return and replacement lifecycle of installed items.

Usage Notes

CS_INST_DETAIL_PUB is classified as a public API and is the supported entry point for programmatic manipulation of installation details. It is typically invoked from Oracle Service forms that display and maintain installation details, from order and RMA processing logic that must record installation events, and from concurrent programs that reconcile installation records in bulk. Custom code should call this package rather than performing direct DML on the underlying tables. Because the package is referenced by one other package, dependencies should be reviewed before applying patches. Callers must observe the G_MISS_* defaulting convention and handle the package's standard API return status when integrating with Oracle EBS 12.1.1 or 12.2.2.