Search Results delete_installation_details




Overview

ASO_INSTBASE_INT is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Order Capture / Advanced Pricing product family (the ASO application short name) and is classified in the ETRM repository under the API classification type OTHER. The package provides an integration-layer API surface for maintaining installation base details associated with quote and order lines. Its source header (asoicsis.pls 120.1, dated June 2005) confirms it was authored as a controlled interface rather than an internal utility, and it declares AUTHID CURRENT_USER so that execution privileges are resolved against the calling schema.

The core business purpose of the package is to allow callers — typically other ASO packages, forms, or external integration code — to remove obsolete installation detail records and to re-sequence installation detail lines after insert, update, or delete operations. The package also exposes a helper to resolve the top model line identifier for a given configuration, which is required when installation details must be attributed to the correct top-level model rather than to an option or component line.

Key Procedures and Functions

ETRM documents three callable units in this package:

  • DELETE_INSTALLATION_DETAIL — the procedure matched by the user's search term "delete_installation_details" (the documented name in the header comment is Delete_Installation_Details; the declared symbol is the singular Delete_Installation_Detail). Its documented function is to delete installation detail records. It accepts the standard Oracle API parameters — p_api_version_number (required), p_init_msg_list (defaulting to FND_API.G_FALSE), and p_commit — and returns the standard x_return_status, x_msg_count, and x_msg_data outputs. The single business parameter is p_line_inst_dtl_id, a required numeric identifier of the installation detail line to be removed. The API is documented as having no pre-requisites and version 1.0 as its initial release.
  • UPDATE_INST_DETAILS_ORDER — re-sequences installation detail records, typically invoked after a deletion or insertion so that line ordering remains contiguous and consistent for downstream display and processing.
  • GET_TOP_MODEL_LINE_ID — resolves the top model line identifier associated with an installation detail or configuration context, enabling the delete and reorder logic to locate the correct parent model line.

Tables Accessed

The package operates against four documented base tables through APPS synonyms:

  • ASO_LINE_RELATIONSHIPS — stores the parent/child relationships between quote lines; used to identify the structure to which an installation detail belongs.
  • ASO_QUOTE_LINES_ALL — the primary quote line table; the delete and reorder logic must keep installation detail records aligned with their owning quote line.
  • ASO_SHIPMENTS — shipment records associated with quote lines, relevant when installation details are tied to shipped configurations.
  • CSI_TRANSACTION_LINES — the installation/instance transaction interface table, which is the source of the installation base detail rows being deleted or reordered.

Usage Notes

ASO_INSTBASE_INT is an integration package, so it is intended to be invoked programmatically rather than through direct end-user navigation. The standard API signature (p_api_version_number, p_init_msg_list, p_commit, x_return_status, x_msg_count, x_msg_data) shows that it follows the Oracle Application Object Library error-handling and message-stack conventions. Callers should check x_return_status for FND_API.G_RET_STS_SUCCESS and, when it is not returned, drain the message stack using FND_MSG_PUB routines against x_msg_count and x_msg_data.

The package is referenced by two other packages in the ETRM repository, confirming it is a dependency in the ASO installation base flow rather than a standalone utility. Typical invocation points are quote maintenance forms, concurrent programs that reconcile installation details after shipment confirmation, and custom PL/SQL integration code that synchronizes installation base records between Oracle EBS and external order or asset systems. Because the package is AUTHID CURRENT_USER, the invoking schema must be granted execute privilege on the package and appropriate DML privileges on the underlying ASO and CSI tables through the APPS synonyms.