Search Results log_mu_error

Overview

CSI_MASS_EDIT_PVT is the private implementation package body for the Oracle E-Business Suite Mass Edit feature within the Enterprise Command Center / CSI (Complex Systems and Installations) module. It provides the underlying API logic that supports bulk updates to item instances, ownership, locations, and related transaction data maintained in the CSI schema. The package operates as a companion to the public package CSI_MASS_EDIT_PUB, which exposes the user-facing API signatures while CSI_MASS_EDIT_PVT contains the actual business validation and persistence routines. The header comment indicates this is release 120.10.12010000.2, making it relevant to Oracle EBS 12.1.1 and 12.2.2 installations that maintain the CSI module at the 12.0.10 level or higher.

Key Procedures and Functions

The package exposes 21 documented procedures and functions organized around batch lifecycle management, validation, and error logging.

• CREATE_MASS_EDIT_BATCH — Creates a new mass edit batch, accepting mass edit header, transaction line, instance, party, and extended attribute data, and returning an error table plus standard FND_API return status, message count, and message data.
• UPDATE_MASS_EDIT_BATCH — Modifies an existing mass edit batch's header and detail data.
• DELETE_MASS_EDIT_BATCH — Removes a mass edit batch and its associated entries.
• GET_MASS_EDIT_DETAILS — Retrieves batch detail information for downstream processing or display.
• IS_VALID_BATCH — Determines whether a given batch identifier is valid.
• VALIDATE_BATCH_NAME, VALIDATE_BATCH_TYPE, VALIDATE_BATCH_STATUS, VALIDATE_BATCH — Perform discrete and composite validation of batch attributes.
• LOG_MU_ERROR — Records mass update errors into the error collection surfaced to callers and the UI.
• VLD_ITEM_INSTANCE_ACTIVE — Confirms the item instance is in an active state.
• VLD_BATCH_INST_SAME_OWNER / VLD_BATCH_INST_CURR_OWNER — Verify ownership consistency between the batch and the instance.
• VLD_CHILD_INST_LOCATION / VLD_ITEM_INST_LOCATION — Validate location assignments for child and parent instances.
• CHECK_ITEM_INST_LOC_CHANGED — Detects whether an instance's location has actually changed.
• VLD_XFER_DATE / VLD_TERM_DATE — Validate transfer and termination effective dates.
• VLD_SYSTEM_ACTIVE / VLD_SYSTEM_CURRENT_OWNER — Validate system-level active status and current ownership.

Tables Accessed

The package reads and writes through APPS synonyms into the CSI data model. Batch headers and their translated descriptions reside in CSI_MASS_EDIT_ENTRIES_B and CSI_MASS_EDIT_ENTRIES_TL. Instance and system data are drawn from CSI_ITEM_INSTANCES and CSI_SYSTEMS_B, with status reference values from CSI_INSTANCE_STATUSES. Ownership and account information are sourced from CSI_I_PARTIES, CSI_IP_ACCOUNTS, CSI_T_PARTY_ACCOUNTS, and CSI_T_PARTY_DETAILS. Interface and staging data are held in CSI_T_TRANSACTION_LINES and CSI_T_TXN_LINE_DETAILS. PLITBLM is used as the standard PL/SQL index-by table buffer for message handling in the FND message stack.

Usage Notes

CSI_MASS_EDIT_PVT is not intended to be called directly by end users or customization code; the public wrapper CSI_MASS_EDIT_PUB is the supported entry point. In practice the package is invoked from the Mass Edit Oracle Forms UI, from concurrent programs that process queued mass edit batches, and from a small number of dependent PL/SQL packages (one package is documented as referencing it). The log_mu_error routine specifically maps to the Mass Update error logging pathway, so any troubleshooting of "log_mu_error" typically begins here — errors captured by LOG_MU_ERROR are propagated through x_mass_edit_error_tbl for display in the Mass Edit form or for downstream notification. Because the package body is marked PVT, Oracle does not guarantee backward compatibility of its signatures across patches, and direct calls should be replaced with the public API.