Search Results get_ib_trackable_lines

Overview

CSI_DEBUG_PKG is a diagnostic utility package owned by the APPS schema in Oracle E-Business Suite. It resides within the Oracle Installed Base (CSI) product family and serves a purely investigative role rather than a transactional or business-processing one. Its classification in the ETRM metadata is "OTHER," reflecting that it is not part of the public application programming interface and is not intended to be called by external integration code. Instead, the package provides a collection of debugging and status-inspection routines that allow support engineers, developers, and technical consultants to interrogate the state of Installed Base entities—orders, jobs, serials, transactions, RMAs, and instance records—and to dump installation-related metadata for troubleshooting.

The package is exceptionally self-contained. According to the dependency information, it references only SYS.STANDARD among other packages and is referenced by no other packages (0 reverse dependencies). This isolation confirms its role as a leaf-level diagnostic tool that does not participate in the standard call graph of Installed Base processing. It remains VALID across both 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The ETRM metadata documents twelve callable units within CSI_DEBUG_PKG. Their names indicate a consistent diagnostic intent:

• ORDER_STATUS, JOB_STATUS, SERIAL_STATUS, TXN_STATUS, RMA_STATUS, INSTANCE_STATUS — status-inspection routines that report the current state of an order, a job, a serial-numbered item, a transaction, an RMA, and an installed base instance respectively. These are typically used to confirm what the application believes the status of a given record to be.
• DIAGNOSE — a general-purpose diagnostic entry point that aggregates checks across Installed Base data.
• DUMP_INSTALLATION_DETAILS — outputs installation detail information for inspection, drawing on the CSI_INSTALL_PARAMETERS and related tables.
• GET_ORDER_LINES — retrieves order line information, likely correlating sales order lines with Installed Base trackable entities.
• GET_IB_TRACKABLE_LINES — returns lines representing trackable Installed Base items.
• DUMP_FILE_VERSION and DUMP_FILE_VERSIONS — utilities that report file and file-version information from the AD_FILES and AD_FILE_VERSIONS repositories, useful for confirming patch and file-level details in a support context.

Tables Accessed

The documented table references fall into two groups. The first is Installed Base core data: CSI_ITEM_INSTANCES and its history table CSI_ITEM_INSTANCES_H, CSI_TRANSACTIONS, CSI_TXN_ERRORS, CSI_TXN_TYPES, CSI_II_RELATIONSHIPS and CSI_T_II_RELATIONSHIPS (the interface and denormalized relationship tables), CSI_INSTALL_PARAMETERS, and CSI_T_PARTY_ACCOUNTS. These support the status, diagnose, order-line, and instance routines.

The second group supports order and patch/file diagnostics: BOM_CTO_ORDER_LINES (configured-to-order lines), and the Applications DBA tables AD_BUGS, AD_FILES, AD_FILE_VERSIONS, AD_PATCH_RUN_BUGS, and AD_PATCH_RUN_BUG_ACTIONS. The AD tables underpin the DUMP_FILE_VERSION routines, tying the package into patch-level troubleshooting. Notably, the package reads these tables through APPS synonyms and performs no documented write operations, consistent with a read-only debugging mandate.

Usage Notes

CSI_DEBUG_PKG is not exposed through standard concurrent programs or forms menus. It is ordinarily invoked interactively from SQL*Plus or another PL/SQL client by Oracle Support, development, or senior technical staff while investigating a specific Installed Base issue—for example, tracing why a transaction failed (CSI_TXN_ERRORS) or confirming the status of a serialized instance. Because it is classified as OTHER and has no reverse dependencies, it must not be called from custom production code or integration interfaces; Oracle may change or remove it without notice. Its greatest value is in root-cause analysis, where the status and dump routines provide an authoritative view of Installed Base and file-version data on demand.