Results for “check_soln_in_progress”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The PL/SQL package body APPS.CS_KB_SOLN_IN_PROGRESS_PKG belongs to the Oracle E-Business Suite Service (CS) knowledge base schema and supports the Solutions authoring workflow. Its purpose is to identify knowledge base Solutions that are locked by a user who no longer holds sufficient visibility privileges over the complete Solution, and to release those locks so that other authors or reviewers can continue working on the record. In effect, the package functions as a housekeeping and lock-recovery utility for the Solutions life cycle, preventing "orphaned" locks that would otherwise block progress on incomplete knowledge articles.
The package is classified as OTHER within the ETRM registry under owner APPS, and the $Header comment indicates an original shipment version of 115.2 (dated 2003), reflecting the long-standing nature of the Solutions framework in EBS 12.1.1 and 12.2.2. The package is not referenced by any other documented package, indicating it is a top-level entry point invoked directly rather than a shared library routine.
Key Procedures and Functions
CHECK_SOLN_IN_PROGRESS— The single documented procedure in the package. It accepts anERRBUFoutput parameter for error messages and aRETCODEoutput parameter indicating completion status (0 for success, 1 for warning, 2 for error). Its logic opens a cursor over Solutions whose status is SAV (saved), NOT (not reviewed), or REJ (rejected), that are flagged as the latest version, and that are currently locked by a valid user. For each such Solution, the procedure callsCS_KB_SECURITY_PVT.IS_COMPLETE_SOLUTION_VISIBLEto test whether the locking user still has complete visibility of the Solution and all of its associated statements within an appropriate Category Group. When that test returns FALSE, the procedure updatesCS_KB_SETS_Bto clear the lock (settingLocked_Byto -1 andLock_Dateto NULL) and, where the Solution is attached to an existing workflow flow, initiates a new workflow process to formalize the release. Audit columnsLast_Updated_ByandLast_Update_Loginare populated fromFND_GLOBALso the change is attributed to the concurrent program session.
Tables Accessed
CS_KB_SETS_B— The base table storing Solution set definitions, including lock ownership (Locked_By), lock date, status, and version flag. The package reads from it via theCS_KB_SETS_VLview to locate qualifying Solutions and writes to it to release locks.CS_KB_WF_FLOW_DETAILS— The workflow flow detail table, outer-joined to the Solution query to identify whether a Solution is currently attached to a workflow process. When a flow detail is present, the procedure creates an associated workflow process as part of the unlock operation.
Usage Notes
The procedure is designed to be executed as a concurrent program rather than from a form, as evidenced by its ERRBUF/RETCODE signature and its use of FND_FILE logging statements. Administrators typically schedule it to run on a periodic basis within the Knowledge Base administrator responsibility to reclaim stale locks. It may also be called from custom PL/SQL code or corrective scripts by passing the two OUT parameters and interpreting the return code, but such invocations should respect the commit strategy of the caller. Because the package depends on CS_KB_SECURITY_PVT for visibility evaluation, its behavior reflects the active Category Group and statement-level security configuration of the affected users. No other documented package references it, so changes to its interface carry limited external impact.