Search Results csi_iea_values_h_s

Overview

CSI_EXTEND_ATTRIB_VLD_PVT is the private validation package body within the Oracle E-Business Suite (EBS) Extended Territory and Asset Management schema (CSI). In the 12.1.1 and 12.2.2 releases it provides the internal validation and lookup logic used to enforce the integrity of extended attribute data stored against item instances and their history. Extended attributes are the customer-defined, flexfield-style characteristics that enterprises attach to tracked assets, equipment instances, and transactions; these values are held in the CSI_IEA_VALUES family of tables and their "_H", "_H_S", and "_S" counterparts. The package is classified as a PVT object, meaning it is intended for consumption only by other packages in the same product family (notably the companion public package CSI_EXTEND_ATTRIB_PUB and item-instance processing routines) and should not be called directly by customer code. Its central role is to answer the procedural question "is this instance, attribute, value, or date combination valid, and if so, what is its identifier?" — returning the surrogate primary keys used in the IEA value tables while verifying object-version numbers, effective dates, and attribute-level content before any insert or update proceeds.

Key Procedures and Functions

The package body exposes sixteen documented routines that fall into three groups. The first group validates entity and instance identity: IS_VALID_INSTANCE_ID confirms that a supplied instance identifier is genuine, VAL_INST_ID_FOR_UPDATE performs the same check under an update context (typically bypassing certain checks or applying locking semantics), IS_VALID_ATTRIBUTE_ID confirms the extended attribute definition exists, and VAL_AND_GET_EXT_ATT_ID validates and then returns the extended-attribute identifier. The second group handles value identifiers and history: IS_VALID_ATTRIBUTE_VALUE_ID validates a value row, GET_ATTRIBUTE_VALUE_ID returns the value-table key, GET_ATTRIBUTE_VALUE_H_ID returns the corresponding historical key, and IS_VALID_ATTRIB_LEVEL_CONTENT confirms the supplied content is appropriate for the designated attribute level. The third group governs lifecycle, concurrency, and temporal rules: IS_EXPIRE_OP identifies expiration operations, IS_UPDATABLE determines whether a record may be modified, IS_STARTDATE_VALID and IS_ENDDATE_VALID enforce effective-date boundaries, ALTERNATE_PK_EXISTS checks for an alternate primary-key match, GET_OBJECT_VERSION_NUMBER retrieves the current optimistic-locking version, IS_VALID_OBJ_VER_NUM confirms a caller's version is current, and GET_FULL_DUMP_FREQUENCY returns the configured full-dump cadence used when extended-attribute data is propagated to the "_S" staging tables. No parameter lists are asserted here; signatures are established by the published package specification.

Tables Accessed

The documented dependencies show reads and writes against CSI_IEA_VALUES (current attribute values), CSI_IEA_VALUES_H (history), CSI_IEA_VALUES_H_S and CSI_IEA_VALUES_S (staging/snapshot copies used by the territory and instance synchronization processes), CSI_ITEM_INSTANCES (the instance master being validated), CSI_I_EXTENDED_ATTRIBS (attribute definitions and levels), CSI_TRANSACTIONS (transaction context), and MTL_ITEM_CATEGORIES (item/category verification). DUAL is referenced for trivial PL/SQL expressions. The package also calls CSI_DATASTRUCTURES_PUB, CSI_GEN_UTILITY_PVT, FND_API, FND_MESSAGE, and FND_MSG_PUB for data structures, generic utilities, and the standard error-stack API.

Usage Notes

This package is invoked internally by the CSI extended-attribute public APIs and by Oracle Forms that maintain item-instance extended attributes. Because it is a PVT package and is not referenced by any database object outside the CSI family, customizations should never call it directly; instead, use the corresponding public API. The presence of the "_H_S" and "_S" tables in the dependency list indicates it participates in the ETRM synchronization and full-dump process, so its validation logic directly governs which attribute rows are eligible for replication. Its optimistic-locking routines (GET_OBJECT_VERSION_NUMBER and IS_VALID_OBJ_VER_NUM) mean callers must always pass the version retrieved on read in order for updates to succeed, and its date-validation routines enforce the effective-dating model required for auditability of tracked assets.