Search Results update_hist_status_detailed

Overview

OKC_REP_SIGN_WF_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, belonging to the Oracle Contracts (OKC) module within the Enterprise Contracts / ETRM product family. The package declares AUTHID CURRENT_USER and executes with the privileges of the invoking user rather than the definer, which is consistent with its role as an internal utility invoked from Oracle Workflow function activities. Its documented purpose is to support the electronic signature and contract preview lifecycle for Oracle Contracts repository documents. The package supplies the workflow-callable entry points that initialize workflow attributes, advance a signature routing list, update signature history status, and process contract signing and rejection outcomes. It is classified as a private (PVT) API, meaning it is not part of the supported public interface for customer extensions; Oracle reserves the right to change its signatures between releases. The header identifies revision 120.0.12020000.3 dated 14-Mar-2013, confirming availability across the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The package exposes nine documented program units, the majority of which follow the Oracle Workflow standard pl/sql callback signature (itemtype, itemkey, actid, funcmode, resultout).

• INITIALIZE_ATTRIBUTES — Invoked by the workflow engine to initialize workflow attributes for the signature process before routing begins.
• HAS_NEXT_SIGNER — Determines whether additional signers remain in the signature list, driving the loop that assigns successive approval notifications.
• UPDATE_HIST_STATUS_DETAILED — Updates detailed signature history status records, maintaining the audit trail of each signing action.
• REJECT_CONTRACT — Handles the rejection branch of the signature process, recording the rejection and terminating or redirecting the workflow.
• SIGN_CONTRACT — Processes the successful signing action, updating the contract status and signature details.
• CON_HAS_TERMS — Evaluates whether the contract under signature has associated terms, a common gating condition in the workflow.
• CON_ATTACH_GENERATED_YN — Indicates whether a generated attachment exists for the contract, used to control preview and delivery behavior.
• CONTRACT_PREVIEW_YN — Returns whether contract preview is enabled; this is the function associated with the search term contract_preview_yn and governs whether signers may preview the contract document prior to signing.
• APPS_INITIALIZE — Standard initialization routine that sets up the APPS environment context for the session.

Tables Accessed

The package reads and writes contract repository and Workflow tables through APPS synonyms:

• OKC_REP_CONTRACTS_ALL and OKC_REP_CONTRACT_VERS — Core contracts repository and version records that hold the agreement being signed.
• OKC_REP_SIGNATURE_DETAILS and OKC_REP_PARTY_CONTACTS — Signature records and party contact information used to build the signer list.
• OKC_CONTRACT_DOCS and OKC_BUS_DOC_TYPES_B — Document attachments and business document type definitions supporting preview and generated output.
• FND_USER, HZ_PARTIES, and HZ_RELATIONSHIPS — TCA and application user data resolving signer identities and party relationships.
• WF_ITEMS and WF_NOTIFICATIONS — Workflow item state and notification records that carry the routing to each signer.
• PLITBLM — The PL/SQL table to bulk collect mapping table, used internally for array processing.

Usage Notes

OKC_REP_SIGN_WF_PVT is not intended for direct invocation by customer code. It is referenced by Oracle Workflow function activities defined for the contract signature item type; the workflow engine passes itemtype, itemkey, actid, and funcmode, and the procedure returns a standard one-character result used to branch the process. Because it is declared AUTHID CURRENT_USER, sessions must already be initialized with the APPS environment, which is why APPS_INITIALIZE is included. The package is documented as being referenced by zero other packages, indicating it sits at the top of the call stack and is driven exclusively by workflow metadata rather than by PL/SQL callers. The search term contract_preview_yn corresponds to the CONTRACT_PREVIEW_YN function, which is typically used as a conditional in the signature notification workflow to determine whether the signer receives a previewable version of the contract. Developers diagnosing signature routing issues should inspect Workflow notification and history records rather than calling this package directly.