Search Results validate_batch_type

Overview

CSI_MASS_EDIT_PVT is the private helper package within the Oracle E-Business Suite Enterprise Asset Management / Inventory instance-tracking architecture that supports mass maintenance of item instance records stored in the CSI schema. It belongs to the CSI (Complex Maintenance, Repair, and Overhaul / Instance Tracking) product family and carries the standard API classification of PVT, indicating that it is a private implementation package not intended for direct third-party invocation.

The package provides the procedural engine behind the public API surface exposed by CSI_MASS_EDIT_PUB, which is the sole documented external reference to this package. In Oracle EBS 12.1.1 and 12.2.2, mass edit operations allow maintenance and inventory personnel to update attributes across large populations of item instances—locations, owners, transfer dates, termination dates, and system associations—without editing each instance individually. CSI_MASS_EDIT_PVT encapsulates the validation logic, batch persistence, and transaction-line handling required to make those bulk updates atomic, auditable, and consistent with instance-tracking business rules.

The package is documented as VALID in the APPS schema and depends on FND_API for the standard Oracle Application Object Library error-handling and savepoint stack, on CSI_T_DATASTRUCTURES_GRP for shared instance data structures, and on the STANDARD SYS package.

Key Procedures and Functions

The documented interface comprises twenty-one procedures and functions, which fall into four functional groups.

• Batch lifecycle management: CREATE_MASS_EDIT_BATCH, UPDATE_MASS_EDIT_BATCH, and DELETE_MASS_EDIT_BATCH create, amend, and remove mass edit batch headers and their entries. GET_MASS_EDIT_DETAILS retrieves batch and entry detail for display or downstream processing.
• Batch validation: IS_VALID_BATCH, VALIDATE_BATCH, VALIDATE_BATCH_NAME, VALIDATE_BATCH_TYPE, and VALIDATE_BATCH_STATUS enforce uniqueness, referential integrity, and enumerated-value correctness on batch metadata before persistence.
• Instance-level validation: VLD_ITEM_INSTANCE_ACTIVE, VLD_SYSTEM_ACTIVE, VLD_BATCH_INST_SAME_OWNER, VLD_BATCH_INST_CURR_OWNER, VLD_SYSTEM_CURRENT_OWNER, VLD_ITEM_INST_LOCATION, VLD_CHILD_INST_LOCATION, and CHECK_ITEM_INST_LOC_CHANGED verify that the instances targeted by a batch are active, share owner and current-owner relationships, and are being moved to permitted locations.
• Date and error validation: VLD_XFER_DATE and VLD_TERM_DATE confirm that transfer and termination dates fall within allowable ranges, while LOG_MU_ERROR records validation failures against the FND_API message stack.

Tables Accessed

The package reads and writes the core instance-tracking tables. CSI_MASS_EDIT_ENTRIES_B and CSI_MASS_EDIT_ENTRIES_TL hold the batch entry records and their translated descriptions; CSI_ITEM_INSTANCES is the primary instance record queried and updated; CSI_SYSTEMS_B maintains system-level groupings. CSI_INSTANCE_STATUSES and CSI_IP_ACCOUNTS support status and account validation. Ownership validation relies on CSI_I_PARTIES, CSI_T_PARTY_ACCOUNTS, and CSI_T_PARTY_DETAILS. Transaction-line generation during mass edit uses CSI_T_TRANSACTION_LINES and CSI_T_TXN_LINE_DETAILS. PLITBLM is the standard Oracle PL/SQL table used as an in-memory collection buffer.

Usage Notes

CSI_MASS_EDIT_PVT is invoked indirectly. The Instance Tracking mass edit forms and any concurrent program that processes mass edit batches call CSI_MASS_EDIT_PUB, which in turn delegates to this private package. Custom code should never call CSI_MASS_EDIT_PVT directly, because its contract is subject to change between point releases; integrators should use CSI_MASS_EDIT_PUB instead. Within the API stack, this package raises errors through FND_API so that the calling public API can roll back a batch atomically and surface a consistent message to the user.