Search Results csi_ii_forward_sync_temp_s
Overview
APPS.CSI_DIAGNOSTICS_PKG is a diagnostic and data-remediation package body in the Oracle E-Business Suite Enterprise Asset Management / Complex Maintenance, Repair, and Overhaul (EAM/CMRO) schema family, built on the CSI (Customer Service Intelligence / Installed Base) data model. Its business purpose is to detect, report, and repair inconsistencies in installed base instance, transaction, relationship, account, and party data that arise from partial failures, concurrent processing, duplicate records, or orphaned rows. The package is classified as OTHER (not a published integration API), confirming that it is an internal utility rather than a supported public interface.
The package is heavily dependency-rich, invoking PL/SQL APIs such as CSI_ITEM_INSTANCE_PUB, CSI_ITEM_INSTANCE_PVT, CSI_ITEM_INSTANCE_VLD_PVT, CSI_TRANSACTIONS_PVT, CSI_II_RELATIONSHIPS_PUB, CSI_PROCESS_TXN_PVT, CSI_RESUBMIT_PUB, and CSI_INV_TRXS_PKG, along with generic concurrent-processing utilities (FND_CONCURRENT, FND_FILE, AD_CONC_UTILS_PKG, AD_PARALLEL_UPDATES_PKG). This indicates that it both diagnoses and performs corrective write operations through the standard installed base APIs.
Key Procedures and Functions
The 47 documented procedures are organized around five diagnostic themes:
- Data dumps and staging: INSERT_FULL_DUMP, UPDATE_FULL_DUMP_FLAG, and STAGE_SOISHIP_INSTANCES extract or stage installed base and shipping-related records into temporary structures for offline analysis.
- Duplicate detection and removal: DELETE_DUP_RELATIONSHIP, DELETE_DUP_SRL_INV_INSTANCE, DEL_API_DUP_SRL_INSTANCE, UPDATE_DUP_SRL_INSTANCE, and DELETE_DUP_ORG_ASSIGNMENTS identify and purge duplicate relationship, serial-numbered instance, and organization assignment rows.
- Attribute correction: UPDATE_INSTANCE_USAGE, UPDATE_REVISION, UPDATE_VLD_ORGANIZATION, UPDATE_MASTER_ORGANIZATION_ID, and UPDATE_INSTANCE_PARTY_SOURCE repair incorrectly maintained instance attributes.
- Party and account repair: GET_RMA_OWNER, DELETE_DUP_ACCOUNT, UPDATE_CONTACT_PARTY_RECORD, and REVERT_PARTY_REL_TYPE_UPDATE correct party-source, account, and RMA ownership data.
- Transaction integrity: MISSING_MTL_TXN_ID_IN_CSI and FORWARD_SYNC reconcile installed base transactions with inventory transaction identifiers and propagate changes forward; GET_NEXT_LEVEL supports hierarchical traversal of instance relationships.
Tables Accessed
The package operates across the install base core and its history tables. It reads and writes CSI_ITEM_INSTANCES (with its _H and _S history/shadow counterparts) to maintain the master instance record. CSI_II_RELATIONSHIPS and its _H/_S siblings store instance-to-instance relationships. CSI_IP_ACCOUNTS and _H/_S hold instance party account data, while CSI_I_ORG_ASSIGNMENTS, CSI_I_ASSETS, CSI_I_PARTIES, CSI_I_PRICING_ATTRIBS_H, and CSI_I_VERSION_LABELS (with history and shadow tables) carry organizational, asset, party, pricing, and version attributes. CSI_TRANSACTIONS, CSI_TRANSACTIONS_S, CSI_TXN_ERRORS, CSI_T_TXN_DETAILS, CSI_T_TRANSACTION_LINES, and CSI_T_TXN_LINE_DETAILS support transaction and error diagnosis. CSI_DIAGNOSTICS_TEMP, CSI_EXPIRE_INSTANCES_TEMP, CSI_XNP_MSGS_TEMP, and notably CSI_II_FORWARD_SYNC_TEMP (and its _S shadow) serve as working and staging areas — the object the user searched for, CSI_II_FORWARD_SYNC_TEMP_S, is the shadow table backing forward-sync diagnostics. CSI_LOOKUPS, CSI_TXN_TYPES, CSI_TXN_SUB_TYPES, CSI_INSTANCE_STATUSES, and CSI_INST_TRANSACTIONS_V provide reference and view data.
Usage Notes
CSI_DIAGNOSTICS_PKG is normally invoked from EAM/Installed Base diagnostic concurrent programs, from administrative utilities, and from correction scripts executed by Oracle Support or advanced implementation teams. Because it performs direct DML on base and history tables and drives standard install base APIs, it should be invoked during controlled maintenance windows with prior backups. The README documentation in the CSI_*_PUB and CSI_*_PVT packages referenced here should be consulted before execution, since these APIs enforce validation rules that the diagnostic routines depend on.
-
SEQUENCE: CSI.CSI_II_FORWARD_SYNC_TEMP_S
12.2.2
owner:CSI, object_type:SEQUENCE, object_name:CSI_II_FORWARD_SYNC_TEMP_S, status:VALID,
-
SYNONYM: APPS.CSI_II_FORWARD_SYNC_TEMP_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:CSI_II_FORWARD_SYNC_TEMP_S, status:VALID,
-
SYNONYM: APPS.CSI_II_FORWARD_SYNC_TEMP_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:CSI_II_FORWARD_SYNC_TEMP_S, status:VALID,
-
SEQUENCE: CSI.CSI_II_FORWARD_SYNC_TEMP_S
12.1.1
owner:CSI, object_type:SEQUENCE, object_name:CSI_II_FORWARD_SYNC_TEMP_S, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.CSI_DIAGNOSTICS_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_DIAGNOSTICS_PKG, status:VALID,
-
PACKAGE BODY: APPS.CSI_DIAGNOSTICS_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_DIAGNOSTICS_PKG, status:VALID,
-
PACKAGE BODY: APPS.CSI_ITEM_INSTANCE_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ITEM_INSTANCE_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ITEM_INSTANCE_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ITEM_INSTANCE_PVT, status:VALID,
-
APPS.CSI_DIAGNOSTICS_PKG dependencies on CSI_II_FORWARD_SYNC_TEMP_S
12.2.2
-
APPS.CSI_ITEM_INSTANCE_PVT dependencies on CSI_II_FORWARD_SYNC_TEMP_S
12.2.2
-
APPS.CSI_DIAGNOSTICS_PKG dependencies on CSI_II_FORWARD_SYNC_TEMP_S
12.1.1
-
APPS.CSI_ITEM_INSTANCE_PVT dependencies on CSI_II_FORWARD_SYNC_TEMP_S
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1