Search Results is_opp_creation_allowed

Overview

OKC_OPPORTUNITY_PUB is the public application programming interface for creating and managing sales opportunities within Oracle E-Business Suite's Contracts (OKC) module. In release 12.1.1 and 12.2.2, this package functions as a thin, supported wrapper layered over the private implementation package OKC_OPPORTUNITY_PVT, exposing opportunity creation logic to external callers in a controlled and upgrade-safe manner. The package participates in the broader Opportunity-to-Contract lifecycle, in which a lead or opportunity tracked in the sales pipeline is linked to a contract and progressively qualified through win probability and expected close timing. Because the package is classified as PUB, its signatures are treated as a supported integration surface, and customer extensions should invoke OKC_OPPORTUNITY_PUB rather than the underlying private package.

Key Procedures and Functions

The documented API exposes nine procedures and functions; the principal entry points are described below. Parameter lists are intentionally not reproduced, as they must be confirmed against the installed package specification for the specific release.

• CREATE_OPPORTUNITY — The primary opportunity creation routine and the object of the search term "create_opportunity." It accepts a contract identifier together with qualification attributes such as win probability and expected close duration, and returns the generated lead identifier along with the standard EBS API return status, message count, and message data. Two overloaded forms are documented: a streamlined version and a fuller version that adds API version, commit control, and initialization message list handling. The overload without an output lead identifier internally declares a local variable and delegates to the sibling overload.
• CREATE_OPP_HEADER — Creates the header-level record for an opportunity.
• CREATE_OPP_LINES — Creates the detail or line-level records associated with the opportunity header.
• IS_OPP_CREATION_ALLOWED — A validation function that determines whether opportunity creation is permissible for the given context, typically reflecting setup, security, or processing constraints.
• GET_OPP_DEFAULTS — Retrieves default attribute values used to prepopulate opportunity data.

All creation routines follow the standard EBS API contract, returning x_return_status set to OKC_API.G_RET_STS_SUCCESS on success and populating the message stack for diagnostics.

Tables Accessed

The ETRM metadata does not enumerate the tables referenced through APPS synonyms for this package. Functionally, the create routines persist opportunity header and line data into the OKC opportunity tables and associate the resulting lead with the contract passed in p_contract_id. Callers requiring a definitive list of affected objects should query the package dependencies in the data dictionary of the target instance.

Usage Notes

OKC_OPPORTUNITY_PUB is typically invoked when a contract must be linked to a new opportunity, whether from the Contracts forms, from concurrent processing, or from custom PL/SQL integration code. The p_commit parameter governs transactional control: the public wrapper issues a database commit only when the private routine reports success and p_commit is set to OKC_API.G_TRUE, allowing callers to compose the API into larger transactions. When p_commit is false, the caller is responsible for the commit or rollback. The package is referenced by one other package in the documented dependency set, and the presence of the AFLOG_ENABLED profile check confirms that debug tracing through OKC_DEBUG is available when diagnostic logging is enabled.