Search Results is_asset_comb_valid

Overview

APPS.CSI_ASSET_VLD_PVT is a private validation package within the Oracle E-Business Suite Install Base (CSI) module. The _PVT suffix indicates that the package is classified as a private (internal) API, meaning it is intended for use by other CSI packages and product code rather than being exposed as a supported public interface for customer extensions. Numerous CSI packages follow this naming convention, in which a public API delegates reusable field-level and record-level validation to a private helper package.

The business function of CSI_ASSET_VLD_PVT is to centralize the validation logic applied when instance assets, instance asset histories, and related Install Base transactions are created or updated. It answers questions such as whether an instance identifier is valid and unexpired, whether a generated instance asset identifier already exists, whether an asset combination or asset location is acceptable, and whether the effective start and end dates supplied by a caller are internally consistent. The header source references a script version dated 2003, but the package remains documented in ETRM for 12.2.2, indicating that it has been carried forward with minimal structural change.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions in the package. The fourteen include three overloaded signatures of CHECK_REQD_PARAM, two variants of the instance asset identifier existence check, and several dedicated date and quantity validators.

• CHECK_REQD_PARAM — Overloaded routine that verifies a mandatory parameter has actually been passed by the caller. Separate overloads exist for numeric, varchar2, and date inputs, each accepting the parameter name and the calling API name so that a descriptive error can be raised.
• IS_INSTANCEID_VALID — Function that checks whether a supplied instance identifier exists. A parameter allows the caller to also request a check for instance expiry, and an error-handling flag controls whether messages are pushed onto the stack.
• IS_INST_ASSETID_EXISTS — Function that determines whether an instance asset identifier is already present, typically used to prevent duplicate asset creation.
• IS_INST_ASSET_ID_VALID — Function that validates the instance asset identifier itself, confirming that the referenced asset record is legitimate.
• GEN_INST_ASSET_ID — Function that generates a new instance asset identifier from the underlying database sequence.
• GEN_INST_ASSET_HIST_ID — Function that generates a new instance asset history identifier, used when writing audit rows to the history tables.
• IS_UPDATE_STATUS_EXISTS — Function that checks whether an update-status condition applies to the record under validation.
• IS_QUANTITY_VALID — Function that validates the quantity value supplied on an asset transaction or instance record.
• IS_ASSET_COMB_VALID — Function that validates the asset combination, confirming that the combination of asset-defining attributes is permitted.
• IS_ASSET_LOCATION_VALID — Function that validates the asset location, ensuring the location reference is acceptable for the asset.
• IS_STARTDATE_VALID — Function that validates the start date supplied for the asset or transaction. This is the routine most closely associated with the search term is_startdate_valid, and it is typically used to confirm that the proposed effective start date is present, correctly formatted, and consistent with the asset's existing date range.
• IS_ENDDATE_VALID — Function that validates the end date, applying the complementary logic to IS_STARTDATE_VALID, including the rule that an end date may not precede the corresponding start date.

Tables Accessed

The package reads and writes Install Base and Fixed Assets data through APPS synonyms. CSI_ITEM_INSTANCES holds the item instance records that anchor asset validity checks; CSI_I_ASSETS, CSI_I_ASSETS_S, CSI_I_ASSETS_H, and CSI_I_ASSETS_H_S store instance asset rows and their history and audit variants. CSI_A_LOCATIONS supplies asset location data for the location validator, while CSI_TRANSACTIONS records the Install Base transactions that drive many of the validation paths. FA_BOOKS is referenced for depreciation book context when asset combinations or dates are validated against Fixed Assets conventions.

Usage Notes

Because CSI_ASSET_VLD_PVT is a private API, it is not called directly from Oracle Forms or concurrent programs. Instead, it is invoked from within other CSI packages, and ETRM reports that it is referenced by one other package. Typical invocation occurs during Install Base asset creation and update flows, instance asset identifier generation, and history record insertion, where the public API performs field validation by delegating to these private functions. For the search term is_startdate_valid, the relevant entry point is the IS_STARTDATE_VALID function, which a calling CSI API uses to confirm that a supplied effective start date is acceptable before the asset row is committed. Custom code should not call this package directly; developers should instead use the corresponding public CSI application programming interfaces, which invoke these private validators on the caller's behalf and translate failures into standard API error messages.