Search Results validate_new_owner




Overview

OKS_IBINT_PUB is a public PL/SQL package in the Oracle E-Business Suite service contracts and install base modules, owned by the APPS schema and declared with AUTHID CURRENT_USER. It serves as the integration bridge between Oracle Installed Base (CSI) item instances, Oracle Service (OKS) contract structures, and Oracle Order Management and Receivables entities. The package coordinates the creation, validation, and propagation of installed base and covered-level records that arise when service agreements, subscriptions, and item instances must remain synchronized. It is classified as a PUB package, meaning its procedures are intended for consumption by other application modules and by external integration code, rather than being strictly internal to a single module.

Key Procedures and Functions

The metadata documents ten entry points. Their purposes are as follows:

  • IB_INTERFACE — the principal integration routine that drives Installed Base transactions, typically processing records staged for the CSI interface tables and reconciling them with contract data.
  • DELETE_BATCH — removes a previously created batch of instance or interface records, supporting rollback and cleanup of failed or superseded processing runs.
  • CREATE_BATCH_RULES — establishes the rule sets that govern how a batch of instances is generated or validated.
  • CREATE_K_COVERED_LEVELS_WEBADI — creates contract covered-level records through the Web ADI interface, enabling bulk maintenance of coverage hierarchies tied to contract lines.
  • CHECK_SUBSCR_INSTANCE — validates whether a subscription instance satisfies the conditions required for contract processing.
  • POPULATE_CHILD_INSTANCES — derives and inserts child instance records from a parent instance, supporting hierarchical instance structures.
  • CHECK_CONTRACTS_IMPACTED — determines which contracts are affected by an instance-level change, a prerequisite for downstream validation.
  • GET_CONTRACTS — retrieves the contracts associated with a given instance or owner context.
  • CREATE_ITEM_INSTANCE — creates an Installed Base item instance record, including the associated organization and account assignments.
  • VALIDATE_NEW_OWNER — validates a prospective new owner for an item instance, verifying that the target customer account, account relationship, and party meet the eligibility rules before ownership is transferred. This is the routine most directly associated with the user's search term.

Tables Accessed

The package reads and writes across several module boundaries. On the Installed Base side it touches CSI_ITEM_INSTANCES, CSI_INSTANCE_STATUSES, CSI_I_ORG_ASSIGNMENTS and CSI_COUNTER_ASSOCIATIONS to maintain instance attributes, status history, organization assignments and counter linkages. Contract data is held in OKC_K_HEADERS_ALL_B, OKC_K_LINES_B, OKC_K_ITEMS and OKC_CLASS_OPERATIONS. Customer and party validation for ownership checks relies on HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_RELATE_ALL, while product and unit definitions come from MTL_SYSTEM_ITEMS_TL and MTL_UNITS_OF_MEASURE_TL. Order context is supplied by OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL and OE_SYSTEM_PARAMETERS_ALL.

Usage Notes

OKS_IBINT_PUB is typically invoked from service contract and Installed Base forms, from concurrent programs that process Installed Base interface batches, and from custom integration code that must create or validate instances and contracts programmatically. Because it is referenced by sixteen other packages, changes to its behavior can propagate widely across service, order and receivables flows. The package exposes global message constants inherited from OKC_API and a G_EXCEPTION_HALT_VALIDATION exception, allowing callers to surface validation failures consistently. Debug output is controlled by the OKS_DEBUG profile option.