Search Results csi_asset_vld_pvt




Overview
Explore in AI Chat

Overview

CSI_ASSET_VLD_PVT is a private validation package body in the Oracle E-Business Suite CSI (Customer Service Intelligence / Installed Base) module. As a private (PVT) package, it is not exposed for direct invocation by external callers; instead, it provides the internal validation logic that backs the public installed-base asset APIs and related processing routines. Its central responsibility is to confirm that the data submitted to the asset and instance-asset APIs is well-formed before that data is committed to the CSI tables.

The package combines two categories of validation: mandatory-parameter checking and business-rule validation of identifiers, dates, quantities, locations, and asset combinations. The header line references a version dated 2003, indicating this is long-standing core code that ships with both 12.1.1 and 12.2.2 and is largely unchanged across those releases.

Key Procedures and Functions

  • CHECK_REQD_PARAM — An overloaded procedure that verifies a required parameter has been supplied. Separate versions handle NUMBER, VARCHAR2, and DATE inputs, comparing each against the corresponding FND_API missing-value sentinel (G_MISS_NUM, G_MISS_CHAR, G_MISS_DATE). On failure it raises FND_API.G_EXC_ERROR after populating the CSI_API_REQD_PARAM_MISSING message with the API name and missing parameter tokens.
  • GEN_INST_ASSET_ID — Generates the installed-base asset identifier used when creating new instance-asset records. This is the routine referenced by the search term gen_inst_asset_id, and it is the primary key-generation hook for the CSI_I_ASSETS insert path.
  • GEN_INST_ASSET_HIST_ID — Generates the surrogate key for the asset history record, used when a historical row is written to CSI_I_ASSETS_H.
  • IS_INSTANCEID_VALID — Confirms that a supplied instance identifier exists and is valid within the installed-base instance tables.
  • IS_INST_ASSETID_EXISTS and IS_INST_ASSET_ID_VALID — Determine whether an instance-asset identifier already exists and whether a given one is valid for the operation underway.
  • IS_UPDATE_STATUS_EXISTS — Validates that the status value being applied to an asset update is a legitimate existing status.
  • IS_QUANTITY_VALID — Checks that a submitted quantity value is acceptable for the asset transaction.
  • IS_ASSET_COMB_VALID — Validates the combination of asset attributes that together must form a permitted configuration.
  • IS_ASSET_LOCATION_VALID — Confirms the asset location resolves to a valid entry in the CSI locations table.
  • IS_STARTDATE_VALID and IS_ENDDATE_VALID — Verify that the effective start and end dates fall within acceptable ranges and are internally consistent.

Tables Accessed

The package reads and writes the core installed-base tables, accessed through APPS synonyms:

  • CSI_I_ASSETS, CSI_I_ASSETS_S, CSI_I_ASSETS_H, CSI_I_ASSETS_H_S — the instance-asset base, security, history, and history-security tables where generated asset IDs and history IDs are used and validated.
  • CSI_ITEM_INSTANCES — the item instance table, read for instance-ID validation.
  • CSI_A_LOCATIONS — the asset location table, read by the location validation routine.
  • CSI_TRANSACTIONS — the installed-base transaction table, consulted during asset transaction validation.
  • FA_BOOKS — the Fixed Assets book table, referenced when validating asset/accounting context for installed-base assets linked to fixed assets.

Usage Notes

CSI_ASSET_VLD_PVT is invoked indirectly. It is called from the public CSI installed-base asset APIs, which in turn are driven by the Installed Base forms, concurrent programs that process asset transaction interfaces, and custom integrations that call the public CSI API layer. Because the package is a private PVT body, custom code should never call it directly; instead, callers should use the corresponding public API, which will invoke these validators as part of its standard processing. The package is referenced by one other package in the ETRM metadata, consistent with its role as a shared internal validation library.