Search Results stage_soiship_instances

Overview

APPS.CSI_DIAGNOSTICS_PKG is a diagnostic and maintenance utility package within the Oracle E-Business Suite Install Base (CSI) module. Its primary business function is to identify, report, and remediate data inconsistencies, duplicates, and orphaned records that accumulate in the Install Base instance and relationship tables as a result of normal transactional processing, data conversions, or integration errors. The package operates under the APPS schema and is classified as an OTHER API rather than a public application programming interface, meaning it is intended for internal diagnostics and corrective use rather than for direct invocation by external integrations.

The package carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. It exposes 47 documented procedures and functions, and it depends upon APPS.CSI_DATASTRUCTURES_PUB and FND_API, leveraging the standard EBS API error-handling and data-structure conventions. It is also referenced by CSI_ML_UTIL_PVT, indicating that the multi-language utility layer calls into this package for instance-related maintenance routines.

Key Procedures and Functions

The documented routines fall into several functional groups:

• Full dump and diagnostic reporting: INSERT_FULL_DUMP and UPDATE_FULL_DUMP_FLAG populate and flag diagnostic output used to capture the state of Install Base data for troubleshooting.
• Synchronization routines: FORWARD_SYNC and STAGE_SOISHIP_INSTANCES stage and synchronize instance data, including information originating from Order Management shipment and SOI/ASN flows, into Install Base staging tables.
• Duplicate elimination: DELETE_DUP_RELATIONSHIP, DELETE_DUP_SRL_INV_INSTANCE, DEL_API_DUP_SRL_INSTANCE, UPDATE_DUP_SRL_INSTANCE, and DELETE_DUP_ACCOUNT identify and resolve duplicate relationship, serial-number, instance, and account records.
• Instance and attribute maintenance: UPDATE_INSTANCE_USAGE, UPDATE_REVISION, UPDATE_MASTER_ORGANIZATION_ID, UPDATE_VLD_ORGANIZATION, and UPDATE_INSTANCE_PARTY_SOURCE correct attribute values on existing instance records.
• Party and contact correction: UPDATE_CONTACT_PARTY_RECORD, REVERT_PARTY_REL_TYPE_UPDATE, and related routines repair party source and relationship-type inconsistencies on instance and contact records.
• Organization assignment cleanup: DELETE_DUP_ORG_ASSIGNMENTS removes duplicate organization assignments linked to instances.
• Cross-reference and hierarchy helpers: GET_RMA_OWNER resolves ownership for return material authorization processing, while GET_NEXT_LEVEL supports hierarchical traversal of instance or relationship structures.
• Transaction validation: MISSING_MTL_TXN_ID_IN_CSI detects instance records that lack a corresponding inventory transaction identifier.

Tables Accessed

The package reads and writes the core Install Base entity tables CSI_ITEM_INSTANCES and its history counterpart CSI_ITEM_INSTANCES_H, along with CSI_II_RELATIONSHIPS and CSI_II_RELATIONSHIPS_H/H_S for relationship and hierarchy diagnostics. Account-level data is corrected through CSI_IP_ACCOUNTS and its history tables CSI_IP_ACCOUNTS_H and CSI_IP_ACCOUNTS_H_S. Instance attribute and value-set records are examined via CSI_IEA_VALUES_H and CSI_IEA_VALUES_H_S, and instance status checks use CSI_INSTANCE_STATUSES. Working and staging data is held in CSI_DIAGNOSTICS_TEMP, CSI_EXPIRE_INSTANCES_TEMP, CSI_II_FORWARD_SYNC_TEMP, and CSI_II_FORWARD_SYNC_TEMP_S, which serve as scratch areas for batch reconciliation and forward synchronization. All tables are addressed through APPS synonyms.

Usage Notes

CSI_DIAGNOSTICS_PKG is typically invoked from concurrent programs, diagnostic scripts, or oracle-supplied maintenance routines rather than from end-user forms. It supports post-implementation data cleansing, reconciliation after conversion or interface failures, and resolution of duplicates surfaced by Install Base diagnostic reports. Because it performs destructive operations such as duplicate deletion and organization reassignment, it should be executed only under the guidance of Oracle Support or by experienced Install Base administrators, with a validated backup and audit trail in place. Custom code should reference the package sparingly, as its routines are not part of the committed public API surface.