Search Results process_webadi_batch

Overview

CSI_MASS_EDIT_PUB is the public application programming interface for the mass maintenance of install base records in Oracle E-Business Suite. It belongs to the Customer Service Intelligence (CSI) product family, which stores the enterprise install base — item instances, systems, configurations, parties, and their associated attributes. The package provides the procedural entry points through which Oracle EBS forms, concurrent programs, and external integrations create, validate, and execute bulk updates against those records without requiring direct DML against the underlying CSI tables.

The package is classified as a PUB (public) API, indicating that it is intended for supported external invocation and that its signatures are treated as a stable interface. It sits above the private implementation package CSI_MASS_EDIT_PVT and the underlying worker packages CSI_MASS_EDIT_PUB_W, delegating validation and persistence logic while exposing a controlled, user-oriented contract. The dependency metadata confirms that CSI_MASS_EDIT_PUB references CSI_DATASTRUCTURES_PUB, CSI_T_DATASTRUCTURES_GRP, FND_API, and FND_GLOBAL, and that it is itself referenced by CSI_MASS_EDIT_PVT, CSI_MASS_EDIT_PUB_W, and CSI_T_GEN_UTILITY_PVT. The latter reference is directly relevant to the originating search: CSI_T_GEN_UTILITY_PVT, the install base generic utility package, invokes CSI_MASS_EDIT_PUB as part of its own processing.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions. They divide naturally into batch lifecycle management, update execution, and WebADI integration.

• INITIATE_MASS_EDIT — Establishes the mass edit context and prepares the session for a subsequent mass update operation.
• CREATE_MASS_EDIT_BATCH — Creates a new mass edit batch header, the container against which entries are processed.
• UPDATE_MASS_EDIT_BATCH — Modifies attributes of an existing mass edit batch.
• DELETE_MASS_EDIT_BATCH — Removes a single mass edit batch.
• DELETE_MASS_EDIT_BATCHES — Removes multiple mass edit batches in one call.
• GET_MASS_EDIT_DETAILS — Retrieves the detail rows associated with a mass edit batch for display or downstream processing.
• PROCESS_MASS_EDIT_BATCH — Executes a mass edit batch, applying the staged changes to the install base.
• IDENTIFY_SYSTEM_FOR_UPDATE — Determines which systems are eligible for a system-level mass update.
• VALIDATE_SYSTEM_BATCH — Validates a system batch prior to execution, returning errors for rejected entries.
• PROCESS_SYSTEM_MASS_UPDATE — Performs the system-oriented mass update once validation succeeds.
• PROCESS_WEBADI_BATCH — Processes a batch originating from a WebADI spreadsheet upload.
• PROCESS_WEBADI_CREATE — Handles the create portion of a WebADI mass edit upload.
• PROCESS_WEBADI_UPDATE — Handles the update portion of a WebADI mass edit upload.
• CREATE_REUPLOAD_BATCH — Builds a reupload batch, typically to present rejected or corrected rows back to the user.
• POPULATE_WEBADI_IDS — Populates the internal identifiers required to tie WebADI spreadsheet rows to install base records.

Tables Accessed

The package reads and writes through APPS synonyms across the core install base schema. CSI_ITEM_INSTANCES, CSI_SYSTEMS_B, and CSI_SYSTEMS_TL hold the item instance and system definition data being edited, including translated system names. CSI_II_RELATIONSHIPS and CSI_I_VERSION_LABELS capture instance-to-instance relationships and version labeling affected by system updates. CSI_IEA_VALUES, CSI_I_PRICING_ATTRIBS, and CSI_INSTALL_PARAMETERS store extensible attribute values, pricing attributes, and installation parameters that mass edit frequently targets. Party and account data are handled through CSI_I_PARTIES, CSI_T_PARTY_ACCOUNTS, and CSI_T_PARTY_DETAILS. The mass edit batch structures are CSI_MASS_EDIT_ENTRIES_B and CSI_MU_REUPLOAD_S, the latter supporting the reupload workflow. CSI_T_TRANSACTION_LINES records install base transaction activity generated by the update. Taken together, these tables represent both the batch staging area and the production install base records the batch ultimately modifies.

Usage Notes

CSI_MASS_EDIT_PUB is invoked from the install base mass edit user interface, from concurrent programs that process batches asynchronously, and from WebADI-based spreadsheet integrations where users maintain install base data offline. Custom code should call this public package rather than the private CSI_MASS_EDIT_PVT or the worker package CSI_MASS_EDIT_PUB_W, and should initialize the FND globals and callers via FND_GLOBAL in the standard EBS manner before invocation. Because the package raises errors through FND_API, callers should check the returned FND_API.G_RET_STS status rather than relying on exceptions alone. Bulk operations should be committed explicitly by the caller at the appropriate transaction boundary. In 12.2.2 the API signatures are unchanged from 12.1.1 for the documented entry points, and the persistent references from CSI_T_GEN_UTILITY_PVT confirm that the package remains an active dependency within the install base processing chain.