Search Results operational_status_code

Overview

CSIUPOPS is a concurrent program delivered within the Oracle E-Business Suite Install Base module (CSI). Its documented purpose is to update the operational status (operational_status_code) of install base instances. The program is registered with the user-facing name Install Base - Update operational status and carries the internal description "Install Base - Update operational_status_code." It is enabled in the ETRM 12.2.2 repository, and the same registration metadata applies to the 12.1.1 code line, where the Install Base module is functionally consistent.

The operational status of an instance reflects its current lifecycle condition within the install base — for example, whether an item is active, in repair, or otherwise flagged through the operational status lookup. Maintaining accurate values in operational_status_code is essential for downstream service, depot repair, and field service processes that rely on the true state of a customer asset. CSIUPOPS provides a batch, set-based mechanism for applying operational status updates across large populations of instances rather than requiring users to edit each record manually.

The program belongs to the CSI - Install Base product family, and all documented metadata originates from the Oracle-proprietary ETRM repository for release 12.2.2.

Execution Details

The documented execution attributes for CSIUPOPS are as follows:

• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: CSIUPOPS
• Execution File: csi_diagnostics_pkg.create_oper_upd_worker
• User Name (Executable): CSIUPOPS
• Enabled: Yes

The execution file reference points to the CSI_DIAGNOSTICS_PKG package, specifically the create_oper_upd_worker procedure. This confirms that CSIUPOPS operates as a multi-process worker-based program: the top-level executable spawns worker processes that perform the actual operational status updates in parallel batches. This design is consistent with other Oracle diagnostics and Install Base bulk maintenance programs, which use worker creation to avoid long-running single-threaded transactions over large instance volumes.

Because the program is registered with the Standard argument method, parameters are passed as positional arguments at submission time, in the order defined by the concurrent program's parameter form.

How to Run

Users submit CSIUPOPS through the standard Oracle EBS Submission Request flow: navigate to Requests > Run, select Install Base - Update operational status, and choose the applicable parameters. The concurrent program is also commonly invoked from the Install Base responsibility menus and, where implemented, from diagnostics dashboards that trigger the worker-generated update.

General guidance on parameter usage:

• Instance selection: Scope the update to a specific instance, instance set, or range so that only intended records are affected.
• Operational status value: Supply the target operational_status_code to be applied; this must be a valid value from the operational status lookup.
• Operational unit or organization: Restrict the run to the owning organization to align with multi-org security.
• Batch/parallelism: Because the executable creates worker processes, larger selections benefit from tuning the number of workers or the batch size parameter.

Because the update changes persistent instance data, it should be run during a low-activity window and be preceded by a validation run where available. The concurrent request log will report the number of records updated and any records skipped due to validation failures.

Related Objects

CSIUPOPS interacts with or depends on the following Install Base objects:

• CSI_ITEM_INSTANCES: The primary table holding instance records, including operational_status_code.
• CSI_DIAGNOSTICS_PKG: The executing PL/SQL package containing create_oper_upd_worker.
• Operational status lookup (CSI_OPERATIONAL_STATUS): The valid-values source for status codes.
• CSI_INSTANCE_PUB / CSI_ITEM_INSTANCE_PUB: Public APIs commonly used for instance updates; CSIUPOPS provides a batch alternative for operational status specifically.
• Install Base diagnostics reports: Programs that surface instance inconsistencies prior to a status update run.

DBAs should review concurrent manager worker capacity before running CSIUPOPS at scale, since its child workers consume additional process slots while executing.