Search Results csi_instance_parties_vld_pvt




Overview
Explore in AI Chat

Overview

CSI_INSTANCE_PARTIES_VLD_PVT is a private validation package within the Oracle EBS Installed Base (CSI) module. It provides the internal business rules that govern the relationship between item instances and the parties (customers, contacts, and accounts) associated with them. The package encapsulates the validation logic used to confirm that instance identifiers, party identifiers, relationship types, contact records, and effective dates are consistent before an instance-party association is created, updated, or queried. It is classified as a private (PVT) API, meaning it is not exposed for direct customer invocation and is instead consumed by the public Installed Base APIs and concurrent programs that maintain the CSI_I_PARTIES and CSI_IP_ACCOUNTS data structures. The declarative AUTHID CURRENT_USER clause indicates the package executes with the privileges of the calling user, relying on APPS synonyms for its table access. The user search term "is_party_valid" maps directly to IS_PARTY_VALID, one of the twenty documented routines in this package.

Key Procedures and Functions

The package defines fifty-three documented procedures and functions. The primary validation utilities include CHECK_REQD_PARAM_NUM, CHECK_REQD_PARAM_CHAR, and CHECK_REQD_PARAM_DATE, which enforce that mandatory numeric, character, and date parameters have been supplied by the caller. IS_PARTY_VALID, IS_PTY_SOURCE_TAB_VALID, IS_INSTANCEID_VALID, IS_PTY_REL_TYPE_VALID, IS_CONTACT_VALID, IS_STARTDATE_VALID, and IS_ENDDATE_VALID collectively verify that each attribute entering an instance-party record is well formed and references legitimate data.

Existence checks are handled by IS_PARTY_REL_COMB_EXISTS, which determines whether a given instance, party source table, party identifier, relationship type, and contact combination already exists, and by IS_INST_PARTYID_EXISTS, IS_INST_PARTYID_EXPIRED, IS_INST_OWNER_EXISTS, IS_PTY_ACCT_COMB_EXISTS, IS_IP_ACCOUNT_EXISTS, and IS_INST_PARTYID_VALID, which confirm the state of existing instance-party and account associations. Generation routines GEN_INST_PARTY_ID and GEN_INST_PARTY_HIST_ID allocate surrogate keys for new party and history records. IS_INST_CREATION_COMPLETE provides a completion gate for instance creation processing. As a private package, none of these routines are supported for direct external calls; they exist to service the public Installed Base APIs.

Tables Accessed

The package reads and writes the core Installed Base tables through APPS synonyms. CSI_I_PARTIES, CSI_I_PARTIES_S, CSI_I_PARTIES_H, and CSI_I_PARTIES_H_S store current, translated, and historical instance-party associations. CSI_IP_ACCOUNTS, CSI_IP_ACCOUNTS_S, CSI_IP_ACCOUNTS_H, and CSI_IP_ACCOUNTS_H_S hold the account relationships attached to those parties. CSI_ITEM_INSTANCES supplies the parent instance records, while CSI_I_ASSETS, CSI_I_ASSETS_H_S, and CSI_I_ASSETS_S provide asset context. CSI_IPA_RELATION_TYPES defines the permitted party relationship types, and CSI_A_LOCATIONS and CSI_I_VERSION_LABELS supply location and version reference data used during validation.

Usage Notes

CSI_INSTANCE_PARTIES_VLD_PVT is invoked indirectly. Forms and concurrent programs in the Installed Base module, and the public CSI APIs they call, use this package to validate data before committing instance-party and account records. The package is referenced by four other packages, reflecting its role as a shared internal validation service. Custom code should not call these private routines directly, because no upward compatibility is guaranteed; instead, developers should use the corresponding public Installed Base APIs. Both Oracle EBS 12.1.1 and 12.2.2 ship this package, and the validation semantics have remained stable across those releases.