Search Results is_enddate_valid

Overview

The APPS.CSI_PRICING_ATTRIB_VLD_PVT package is a private validation utility within the Oracle E-Business Suite Advanced Pricing and Installed Base (CSI) integration layer. Its core business function is to enforce the integrity of pricing attribute records that are attached to item instances. Pricing attributes in EBS describe the billable or rating characteristics associated with an installed asset, service, or transaction line, and each such record must reference a valid instance and must observe consistent date-effectivity rules. The _PVT suffix indicates that this is a private (internal) API: it is not intended to be called directly by customers or third-party developers, but rather is invoked by the public CSI and pricing APIs that govern the pricing attribute lifecycle.

The package is declared AUTHID CURRENT_USER, meaning that it executes with the privileges of the calling schema rather than the defining schema. This design ensures that validation queries against installed-base and pricing tables respect the security context of the invoking session. The header identifies the package as shipped under version 120.0.12010000.1, consistent with the 12.1.1 and 12.2.2 release lines referenced by ETRM.

Key Procedures and Functions

The package exposes thirteen documented functions, all of which return a BOOLEAN result indicating whether the supplied data satisfies the relevant validation rule.

• IS_VALID_INSTANCE_ID — The function highlighted by the user's search. It verifies that a given instance identifier refers to a legitimate item instance, returning TRUE when the instance exists and is valid for the supplied event context. It is the primary guard against orphaned pricing attribute rows.
• VAL_INST_ID_FOR_UPDATE — Determines whether an existing instance identifier may be updated to a new value, comparing the new and old identifiers to prevent illegal re-association of pricing attributes.
• IS_STARTDATE_VALID and IS_ENDDATE_VALID — Validate the effective date range of a pricing attribute, checking that the start date precedes the end date and does not overlap conflicting records for the same instance.
• IS_VALID_PRICING_ATTRIB_ID — Confirms that a pricing attribute identifier corresponds to an existing record.
• VAL_AND_GET_PRI_ATT_ID — Performs validation and additionally retrieves the resolved pricing attribute identifier.
• IS_EXPIRE_OP — Determines whether the current operation is an expiration (end-dating) action, allowing the caller to branch validation logic accordingly.
• IS_UPDATABLE — Checks whether a pricing attribute record is in a state that permits modification.
• GET_PRICING_ATTRIB_ID and GET_PRICING_ATTRIB_H_ID — Retrieve the base and history (audit) identifiers respectively.
• GET_OBJECT_VERSION_NUMBER and IS_VALID_OBJ_VER_NUM — Support optimistic locking by returning and validating the object version number, preventing lost updates in concurrent sessions.
• GET_FULL_DUMP_FREQUENCY — Returns the configured frequency for full diagnostic dumps, used for debugging and trace purposes.

Tables Accessed

The package operates against the core Installed Base and pricing attribute tables, all referenced through APPS synonyms:

• CSI_ITEM_INSTANCES — The master instance table; queried to confirm instance existence and validity in IS_VALID_INSTANCE_ID and related functions.
• CSI_I_PRICING_ATTRIBS — The primary pricing attribute entity, read to resolve identifiers and validated for date and update eligibility.
• CSI_I_PRICING_ATTRIBS_H and CSI_I_PRICING_ATTRIBS_H_S — The history and history-sequence tables, accessed by GET_PRICING_ATTRIB_H_ID.
• CSI_I_PRICING_ATTRIBS_S — The primary key sequence source used during identifier generation and validation.
• CSI_TRANSACTIONS — Consulted to confirm that a pricing attribute is associated with a valid transaction context.
• DUAL — Used for scalar queries and function evaluation.

Usage Notes

Because this is a private package, it is not documented for direct customer invocation and should never be called from custom code where a public API exists. It is invoked internally by the public CSI pricing attribute APIs during insert, update, and expiration operations, and indirectly through the Advanced Pricing and Installed Base forms when users maintain pricing attribute data. It is also referenced by one other package within the CSI schema, which delegates validation to these routines before committing changes. In Oracle EBS 12.1.1 and 12.2.2, the package participates in the standard concurrent processing and OAF-based form flows that manage item instance pricing attributes. Developers troubleshooting integrity errors should trace calls into IS_VALID_INSTANCE_ID and the date-validation functions rather than altering the package, since modifications would be overwritten by patching.