Search Results available_services




Overview
Explore in AI Chat

Overview

ASO_SERVICE_CONTRACTS_INT_W is an internal PL/SQL package in the Oracle E-Business Suite Order-to-Cash (ASO) module, owned by the APPS schema and classified under the ETRM registry as an OTHER API. It serves as the integration and wrapper layer between the Oracle Service Contracts and Service/Quote functionality and the underlying quoting and order data model. Its primary business function is to determine the set of services, warranties, and warranty-related coverage that are available for a given product, organization, or item instance, and to expose those results through standardized FND_API-style interfaces that support message list initialization, message count, message data, and return status conventions.

The package predates and is closely associated with the legacy Service Contracts integration flow in Release 12.1.1 and 12.2.2. Because it is a wrapper (the "_W" suffix), it abstracts the underlying ASO_SERVICE_CONTRACTS_INT package and provides the "Rosetta" table-copy routines that convert between strongly typed PL/SQL record collections and the generic JTF_* table types used by the Oracle Applications Framework and the Order Capture / Quoting engine.

Key Procedures and Functions

  • ROSETTA_TABLE_COPY_IN_P2 / ROSETTA_TABLE_COPY_OUT_P2 — Convert in and out of aso_service_contracts_int.order_service_tbl_type using JTF_NUMBER_TABLE collections. These are plumbing procedures used to marshal scalar numeric attributes across the Rosetta boundary.
  • ROSETTA_TABLE_COPY_IN_P4 / ROSETTA_TABLE_COPY_OUT_P4 — Convert in and out of aso_service_contracts_int.war_tbl_type (warranty table type). These carry multiple parallel JTF collections: numbers, VARCHAR2(2000), VARCHAR2(300), VARCHAR2(100), and DATE tables to represent warranty attributes in bulk.
  • AVAILABLE_SERVICES — Returns the set of services available for a given context. It follows the FND_API signature pattern with p_api_version_number, p_init_msg_list, x_msg_count, x_msg_data, and x_return_status, and outputs a JTF_NUMBER_TABLE of available service identifiers. Default parameters indicate optional organization, date, and text filters.
  • GET_WARRANTY — Retrieves warranty coverage for a specified operating unit (p_org_id), inventory organization (p_organization_id), and product item (p_product_item_id). It returns the warranty set as parallel JTF collections mirroring the WAR_TBL_TYPE structure.
  • GET_SERVICES — Returns services associated with the calling context, using the same FND_API message and return-status convention.
  • IS_SERVICE_AVAILABLE — The function corresponding to the user search term "is_service_available". It evaluates whether a specific service is available for a given product or item-instance context and returns a boolean-style indicator. It is the predicate form of AVAILABLE_SERVICES and is the entry point most commonly referenced by quoting and order-capture customizations that need a simple yes/no availability check.

Tables Accessed

  • ASO_QUOTE_LINES_ALL — Source of quote header/line context for service lines being configured or validated.
  • ASO_QUOTE_LINE_DETAILS — Line-level detail attributes used to determine service and warranty applicability.
  • CSI_ITEM_INSTANCES — Installed base item instances that drive service and warranty eligibility.
  • OE_ORDER_LINES_ALL — Order lines referenced when services are validated against the sales order model.
  • OE_SYSTEM_PARAMETERS — Operating unit defaults and system-level behavior parameters.
  • PLITBLM — The PL/SQL integer table used to materialize and pass numeric ID collections, particularly for available-service and warranty lists.

Usage Notes

ASO_SERVICE_CONTRACTS_INT_W is an internal API, not a published public interface, and is not referenced by any other documented package (referenced-by count of zero in ETRM). It is typically invoked from the Oracle Service Contracts and Order Capture forms, quoting engine, and Advanced Pricing flows, and from custom extensions or concurrent programs that require programmatic service/warranty availability checks. Because it relies on FND_API conventions, callers should initialize the message list, check x_return_status on return, and inspect x_msg_count/x_msg_data for error handling. Custom code calling IS_SERVICE_AVAILABLE should treat it as a read-only validation routine and avoid DML dependencies on the returned collections.