Search Results expire_item_instance_post

Overview

APPS.CSI_ITEM_INSTANCE_CUHK is a PL/SQL customization hook package within the Oracle E-Business Suite Install Base (CSI) module. In Oracle EBS 12.1.1 and 12.2.2, the Install Base application manages the lifecycle of item instances — the discrete, serialized, or tracked occurrences of items that an enterprise owns, deploys, services, or sells. The CSI_ITEM_INSTANCE_CUHK package provides customer hook entry points that surround the core Create, Update, and Expire operations performed against item instances through the public APIs exposed by CSI_ITEM_INSTANCE_PUB.

The "_CUHK" suffix denotes a customer hook pattern, under which Oracle delivers a stub package whose procedure bodies are intentionally empty. Customers, system integrators, or Oracle development teams may populate these procedures with site-specific logic — validation, defaulting, integration calls, or data enrichment — without modifying the seeded public API packages. This preserves the integrity of the standard code during patching and upgrades, since custom logic is isolated in a separate, upgrade-safe object. The package is classified as API type OTHER in the ETRM metadata, reflecting its hook/extension nature rather than a callable business API. The signature conventions it follows (p_api_version, p_commit, p_init_msg_list, p_validation_level, and x_return_status/x_msg_count/x_msg_data out parameters) are those of the Oracle Application Object Library (FND_API) standard API framework, ensuring consistent error handling and transaction control semantics.

Key Procedures and Functions

The ETRM documentation records six procedures, organized as pre- and post-hooks around three user-visible operations:

• CREATE_ITEM_INSTANCE_PRE — Executed before the standard item instance creation logic. It receives the full set of inbound creation parameters — the instance record, extended attribute values, party and account tables, pricing attributes, organization assignments, asset assignment details, and transaction record — allowing the customer to validate, default, or transform these values prior to the core processing. This is the procedure associated with the search term "create_item_instance_pre."
• CREATE_ITEM_INSTANCE_POST — Executed after the standard creation logic completes, with an identical parameter profile, enabling follow-on actions such as downstream integration, notification, or derived data population once the instance exists.
• UPDATE_ITEM_INSTANCE_PRE — Executed before standard update processing of an existing item instance, supporting pre-update validation and value adjustment.
• UPDATE_ITEM_INSTANCE_POST — Executed after standard update processing, supporting post-update side effects.
• EXPIRE_ITEM_INSTANCE_PRE — Executed before an item instance is expired (end-dated), permitting validation of business rules that govern expiration.
• EXPIRE_ITEM_INSTANCE_POST — Executed after expiration processing, enabling cleanup or notification activities.

Tables Accessed

The provided metadata does not enumerate direct table references via APPS synonyms; the package operates primarily through the strongly typed record and table structures defined in csi_datastructures_pub, which abstract the underlying Install Base schema objects. In practice, the underlying public API operations affect core Install Base entities including item instance definitions, instance ownership and party relationships, party account assignments, pricing attributes, organization unit assignments, and instance asset assignments. Because the hook procedures are invoked within the same transaction as the public API, any direct table manipulation added by a customer must respect the transactional boundaries of the calling API and avoid committing independently unless p_commit semantics are deliberately managed.

Usage Notes

CSI_ITEM_INSTANCE_CUHK is not invoked directly by end users. It is called by the CSI_ITEM_INSTANCE_PUB public API layer, which itself is surfaced through Install Base forms, Oracle Service, Oracle Order Management, and other product flows that create, update, or expire item instances. The ETRM metadata notes that the package is referenced by two other packages, consistent with the hook contract whereby the public API packages call into the hook stubs at defined points. Custom code requiring item instance creation should call the public CSI_ITEM_INSTANCE_PUB API rather than this hook package; site-specific extensions are placed inside the hook bodies. Because Oracle may replace the empty stub bodies during patch application, any customization must be documented and reapplied after upgrades, and changes should be validated against the FND_API error-handling conventions used by the out parameters x_return_status, x_msg_count, and x_msg_data.