Search Results get_root_id

Overview

CSICUMPI_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PUB (public) API. Its name derives from the Customer Service (CS) module and the concept of a "customer product" or installed base configuration item, and the PUB suffix indicates that its subprograms are intended for external invocation by other application code. The package provides utility accessors for navigating the configuration hierarchy that Oracle's Customer Service and Depot Repair functionality maintains against installed base records. In EBS, configured items — such as a server assembled from a chassis, cards, and drives, or a piece of equipment tracked as a customer product — are stored as item instances related through relationship records. CSICUMPI_PUB allows callers to interrogate those structures without directly querying the underlying CSI and HZ tables. It exposes only functions in the documented interface; the sole procedure, Get_Configuration, is commented out in the source header and is not part of the shipped public interface. The package also declares the Config_Rec_Type record and Config_Tbl_Type collection types, reflecting its heritage as a configuration retrieval API.

Key Procedures and Functions

The documented public interface comprises five functions. None are accompanied by published parameter lists in this metadata beyond the source excerpt, so parameter details are not reproduced here.

• GET_ROOT_INFORMATION — Returns descriptive information about the root (top-level) configuration item associated with a given customer product. This is the function matching the user's search term and is the primary entry point for walking from a component instance up to the configuration to which it belongs.
• GET_ROOT_ID — Returns the numeric identifier of the root customer product for a supplied customer product ID. It is the lighter-weight companion to GET_ROOT_INFORMATION, useful when only the key is required.
• GET_PART_INFORMATION — Returns information about the inventory part associated with a given customer product, resolving the instance to its defining item.
• GET_CHILDREN_FLAG — Indicates whether a given customer product has child components in the configuration hierarchy, allowing callers to determine whether further traversal (for example, in a tree or picker UI) is warranted.
• GET_NON_PRIMARY_PARTY_LIST — Returns a list of parties associated with an account and operating unit who are not the primary party, supporting party-selection and contact logic for installed base records.

Tables Accessed

The package reads through APPS synonyms rather than owning any tables. CSI_ITEM_INSTANCES and CSI_II_RELATIONSHIPS provide the installed base instances and the parent-child links that define configuration structure; the root-navigation and children-flag functions depend on these. MTL_SYSTEM_ITEMS_KFV is the key-flexfield view over inventory items, used by GET_PART_INFORMATION to resolve item descriptions and identifiers. HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_PARTIES support GET_NON_PRIMARY_PARTY_LIST by supplying account, role, and party data from the Trading Community Architecture model. All access is read-only in the documented interface.

Usage Notes

Because the package is classified PUB, it is a supported extension point for customer and partner code. It is referenced by 25 other packages within the EBS code base, which indicates heavy internal reuse by Customer Service, Depot Repair, and installed base processing logic. Typical invocations include Oracle Forms and OAF pages that display configuration hierarchies, concurrent programs that report on installed base structure, and custom PL/SQL that must locate a root configuration or test for component children. Developers should call the packaged functions rather than querying CSI_ITEM_INSTANCES and CSI_II_RELATIONSHIPS directly, since the functions encapsulate the relationship semantics. Note that the header comment carries no-ship status history and the Get_Configuration procedure is commented out; callers should rely only on the five documented functions.