Search Results update_flow_status

Overview

CSD_FLOW_STATUSES_PVT is a private PL/SQL package in the APPS schema that manages the lifecycle of Flow Status records within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Flow Statuses are used by the Oracle Service (CSD) and related supply chain modules to track the processing state of a business flow or document through its various stages. Because it is classified as a PVT package, it is not part of the public API surface; instead, it provides the underlying create, update, delete, and lock mechanics consumed by other components such as forms, concurrent programs, and higher-level public APIs.

The package body is stored in source file csdvflsb.pls, and the header shows a version of 120.3 dated 2005/07/29. It follows the standard Oracle Applications API coding conventions: an API version constant, a compatible API call check via FND_API.Compatible_API_Call, message list initialization through FND_MSG_PUB, savepoint management, and the NOCOPY OUT parameters used for return status, message count, and message data.

Key Procedures and Functions

Four documented procedures comprise the package's public interface:

• CREATE_FLOW_STATUS — Inserts a new Flow Status record. It accepts an API version, commit flag, message-list initialization flag, validation level, and a flow status record structure, returning the status, message details, and the newly generated flow status identifier. The body traps the UNIQUE_CONSTRAINT_VIOLATED exception (SQLCODE -00001) to handle duplicate inserts.
• UPDATE_FLOW_STATUS — Modifies an existing Flow Status record. This is the procedure most commonly targeted when users search for update_flow_status, since it is the documented entry point for changing flow status attributes.
• DELETE_FLOW_STATUS — Removes a Flow Status record, typically invoked when a flow is purged or cancelled and the status row is no longer required.
• LOCK_FLOW_STATUS — Acquires a lock on a Flow Status row to prevent concurrent modification, supporting the standard check-out semantics used by the EBS forms layer.

Each procedure follows the same defensive pattern: a savepoint for rollback control, version compatibility verification, conditional message initialization, and structured error propagation through the FND message stack.

Tables Accessed

The provided ETRM metadata does not enumerate the underlying tables referenced through APPS synonyms. Given the package's function and naming, the primary object is the CSD_FLOW_STATUSES base table, with inserts performed by CREATE_FLOW_STATUS, DML updates by UPDATE_FLOW_STATUS, row deletions by DELETE_FLOW_STATUS, and SELECT ... FOR UPDATE locking by LOCK_FLOW_STATUS. Related lookup or reference tables may also be touched for validation, but the metadata does not confirm specific names, and no additional tables should be assumed.

Usage Notes

CSD_FLOW_STATUSES_PVT is referenced by zero other packages according to the documented metadata, which indicates it is called directly rather than through a published wrapper. Typical invocation points include the service or flow-status maintenance forms, concurrent programs that bulk-process flow state transitions, and custom extensions that require programmatic control over flow status lifecycle events. Callers must supply a valid p_api_version (1.0 for CREATE_FLOW_STATUS) and should respect the commit flag and message-list conventions to integrate correctly with the FND error stack. Because the package is private, Oracle does not guarantee backward compatibility, and direct calls should be reviewed during upgrades between 12.1.1 and 12.2.2.