Search Results get_write_ptr




Overview

OKC_ARTWF_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Contracts (OKC) module's article and terms-template workflow processing. Its header, dated 2006, defines the interface used by the article import and workflow subsystems. The package acts as a supporting engine for launching Oracle Workflow processes, evaluating article status, and managing notifications associated with article adoption across organizations. Because it is classified as a private package, it is not part of the public API surface and must not be called directly from customer extensions; it is invoked internally by other OKC modules and by the article import workflow.

Key Procedures and Functions

The documented routines fall into several functional clusters:

Parameter lists are deliberately omitted here; refer to the package header for exact signatures.

Tables Accessed

The package reads and writes core Contracts and Workflow tables through APPS synonyms. Article data is stored in OKC_ARTICLES_ALL and OKC_ARTICLE_VERSIONS, with adoption details in OKC_ARTICLE_ADOPTIONS and import staging in OKC_ART_INTERFACE_ALL. Terms template metadata is read from OKC_TERMS_TEMPLATES_ALL. Organization context is resolved through HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, and HR_ORGANIZATION_INFORMATION. Workflow state and notifications are managed via WF_ITEMS, WF_NOTIFICATIONS, and WF_NOTIFICATION_ATTRIBUTES. User information is obtained from FND_USER, with messages from FND_NEW_MESSAGES. DBMS_LOB and DBMS_UTILITY provide large-object and utility support. OKC_ARTWF_PVT is itself referenced by one other package, indicating it sits in a layered call chain rather than at the top of the stack.

Usage Notes

OKC_ARTWF_PVT is a private package and its procedures are called from within Oracle's own OKC code — typically from the article import concurrent program and from workflow function activities. It should never be called directly from customer forms or custom concurrent programs. The procedures TEST, PRINT_TAB, and PRINT_ERR exist only for internal diagnostics and are explicitly documented as unsuitable for application use. Implementers extending Contracts workflow behavior should rely on the documented public OKC APIs rather than this package.