Results for “okl_cs_wf”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_CS_WF is a PL/SQL package in the APPS schema that supports Oracle Lease and Finance Management (OKL/ETRM) customer-service and workflow-driven business processes. Its responsibilities span equipment exchange, customer and vendor fulfillment, delinquency evaluation, service-fee assessment, and consolidated-billing post-processing. The package acts as a coordination layer between lease contracts, receivables, customer master data, and the Oracle Workflow engine, exposing callable APIs that raise workflow events and move contract or billing data between intermediate states. It is classified as an OTHER API in the ETRM 12.2.2 documentation set and is deployed as a validated package with both a specification and body. Because it is referenced by other ETRM packages (notably OKL_CS_PRINCIPAL_PAYDOWN_PVT and OKL_SSC_WF), it forms part of the shared internal service layer rather than a solely standalone utility.

Key Procedures and Functions

The package exposes forty-five documented procedures and functions. The principal groupings are:

Tables Accessed

Through APPS synonyms, OKL_CS_WF reads and writes the following object families:

It also depends on OKL_API and STANDARD for common API error-handling infrastructure.

Usage Notes

OKL_CS_WF is normally invoked indirectly. In Oracle EBS 12.1.1 and 12.2.2, it is called by Oracle Forms-based customer-service and collections screens, by Workflow background processes that consume the events it raises, and by concurrent programs that post consolidated invoices or apply service fees. Custom extensions should call the documented procedures rather than manipulate underlying tables directly, because posting and event-raising logic assumes workflow state transitions are honored. Developers tracing dependent code should note that changing this package can affect OKL_CS_PRINCIPAL_PAYDOWN_PVT and OKL_SSC_WF. Standard APPS schema privileges and the OKL_API error stack should be used for exception handling in any custom wrapper.