Search Results g_log_prefix
Overview
APPS.AHL_WARRANTY_GRP is a Group (GRP) layer PL/SQL package in the Oracle E-Business Suite Advanced Service (AHL) application. Its documented purpose, as stated in the package header comments, is to provide a stable set of APIs that may be invoked by other EBS products, most notably Depot Repair. The package therefore acts as a thin public façade over the private warranty-handling business logic implemented in the AHL_WARRANTY_CONTRACTS_PVT package.
The package body carries the source control header AHLGSWCB.pls 120.0 2011/01/27 and defines three file-scope constants: G_PKG_NAME ('AHL_WARRANTY_GRP'), G_APP_NAME ('AHL'), and G_LOG_PREFIX. The logging prefix is constructed at load time as 'ahl.plsql.'||G_PKG_NAME||'.', producing the string ahl.plsql.AHL_WARRANTY_GRP.. This value is the anchor for every debug key emitted by the package and is the identifier most commonly searched for when tracing runtime diagnostics.
Key Procedures and Functions
- IS_INSTANCE_WARRANTY_AVAILABLE — A public function that determines whether a given warranty instance has at least one active contract available, returning 'Y' or 'N'. It accepts a single required input, the warranty instance identifier, initialises the return value to 'N', and delegates the actual determination to the private routine
AHL_WARRANTY_CONTRACTS_PVT.Is_Instance_Warranty_Available. The wrapper itself performs no business validation; it exists to expose the private API across product boundaries.
No other procedures or functions are documented in the package body. The body terminates immediately after IS_INSTANCE_WARRANTY_AVAILABLE, confirming that the package is a single-entry-point façade rather than a general warranty service library.
Tables Accessed
The ETRM metadata records no direct table references for AHL_WARRANTY_GRP. This is consistent with its design: the group layer issues no DML and no direct SQL against APPS synonyms. All data access is performed downstream by AHL_WARRANTY_CONTRACTS_PVT, which resolves warranty instance records against the AHL warranty and service contract tables. Because the group package performs no I/O of its own, it introduces no additional row-level locking, no commit boundaries, and no dependency on table privileges beyond those already granted to the private package.
Usage Notes
The package is classified as GRP, meaning it is a public API surface intended for consumption by other EBS modules and by customer extensions. It is typically invoked from Depot Repair flows and from any custom code that needs a lightweight, product-independent warranty availability check without binding directly to the private PVT layer.
Diagnostics follow the standard EBS FND_LOG pattern. Each call constructs a debug key by concatenating G_LOG_PREFIX with the local API name (is_instance_warranty_available) and then emits begin and end messages at FND_LOG.LEVEL_PROCEDURE when that level is enabled. Administrators tracing a warranty check should therefore enable FND logging at the PROCEDURE level and filter on the prefix ahl.plsql.AHL_WARRANTY_GRP. to capture entry and exit records, including the inbound warranty instance identifier and the returned 'Y'/'N' value.
Because the package is documented as referenced by zero other packages, it holds no internal callers in the shipped codebase; its consumers are external to the indexed dependency graph, which reinforces its role as a published integration point rather than an internal utility.
-
PACKAGE BODY: APPS.AHL_WARRANTY_GRP
12.2.2
-
APPS.AHL_UMP_SR_GRP SQL Statements
12.1.1
-
APPS.AHL_UMP_SR_GRP SQL Statements
12.2.2
-
APPS.AHL_UC_UTILIZATION_PVT SQL Statements
12.2.2
-
APPS.AHL_UC_UTILIZATION_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AHL_UMP_SR_GRP
12.2.2
-
PACKAGE BODY: APPS.AHL_UMP_SR_GRP
12.1.1
-
APPS.AHL_OSP_PO_REQ_PVT SQL Statements
12.2.2
-
APPS.AHL_OSP_PO_REQ_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_ORDERS_PVT
12.2.2
-
APPS.AHL_OSP_ORDERS_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.AHL_PRD_DISP_UTIL_PVT
12.2.2
-
APPS.AHL_OSP_PO_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AHL_PRD_DISP_UTIL_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_ORDERS_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_PRD_DISP_MTL_TXN_PVT
12.2.2
-
APPS.AHL_OSP_PO_PVT SQL Statements
12.2.2
-
APPS.AHL_APPR_DEPT_SHIFTS_PUB SQL Statements
12.1.1
-
APPS.AHL_UMP_SR_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.AHL_PRD_DISPOSITION_PVT
12.1.1
-
APPS.AHL_UMP_SR_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AHL_PRD_DISP_MTL_TXN_PVT
12.1.1
-
APPS.AHL_OSP_ORDERS_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AHL_PRD_DISPOSITION_PVT
12.2.2
-
APPS.AHL_APPR_DEPT_SHIFTS_PUB SQL Statements
12.2.2
-
PACKAGE BODY: APPS.AHL_UMP_SR_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_PO_REQ_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_PO_REQ_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_APPR_DEPT_SHIFTS_PUB
12.1.1
-
PACKAGE BODY: APPS.AHL_APPR_DEPT_SHIFTS_PUB
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_PO_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_UMP_SR_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_ACCOMP_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_PO_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_LTP_MTL_REQ_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_UC_UTILIZATION_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_MATERIALS_GRP
12.2.2
-
PACKAGE BODY: APPS.AHL_UC_UTILIZATION_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_COST_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_COST_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_LTP_MTL_REQ_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_QUERIES_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_QUERIES_PVT
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_UTIL_PKG
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_UTIL_PKG
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_SHIPMENT_PUB
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_SHIPMENT_PUB
12.2.2
-
PACKAGE BODY: APPS.AHL_WORKORDER_SEARCH_PUB
12.2.2
-
PACKAGE BODY: APPS.AHL_WORKORDER_SEARCH_PUB
12.1.1
-
APPS.AHL_PRD_DISP_MTL_TXN_PVT dependencies on FND_LOG
12.2.2