Search Results cancel_contract




Overview

OKC_REP_CONTRACT_IMP_PUB is a public PL/SQL API package in the Oracle E-Business Suite Contracts (OKC) module, specifically within the repository contract import framework. It provides the programmatic entry point for creating, deleting, cancelling, and versioning repository-usage contracts from external sources or staging data. The package is declared with AUTHID CURRENT_USER and executes with the privileges of the calling schema, which is standard for public EBS APIs that must respect the caller's security context.

The business purpose is to allow contract data assembled in external systems, integration layers, or interface tables to be validated and persisted into the OKC repository contract tables. A key design feature is the p_create_contract flag, which allows the caller to choose between fully creating a contract within the API call or merely dumping the data to the interface tables for later processing by the concurrent program "CP Import Repository Contract." This two-mode behavior is central to how the API is used in bulk and interactive scenarios alike.

Key Procedures and Functions

  • CREATE_CONTRACT — Overloaded creation routine. One signature accepts a contract record plus parties, party contacts, and risks collections, and optionally creates the contract immediately. A second overload accepts an additional document record, storing the parent document relationship in OKC_REP_CONTRACT_USAGES.
  • DELETE_CONTRACT — Removes the contract identified by the supplied contract identifier, with an optional commit flag.
  • CREATE_NEW_CONTRACT_VERSION — Produces a new version of an existing contract, supporting the versioning model used by repository contracts.
  • CHECK_CONTRACT_EXISTS — Validation helper that determines whether a contract already exists, typically used to prevent duplicate creation before import.
  • ACTIVATE_TASKS_CLOSEOUT — Drives task and closeout-related processing associated with the contract lifecycle.
  • CANCEL_CONTRACT — Cancels an existing contract. This is the procedure retrieved in searches for "cancel_contract" and is the supported API path for programmatic cancellation rather than direct table updates.
  • DELETE_CANCEL_CONTRACT — Combines deletion and cancellation handling, providing a compound operation for contracts that must be removed after being cancelled.

All routines follow the standard EBS API error-handling convention, returning x_return_status, x_msg_count, and x_msg_data so callers can inspect FND message stack output.

Tables Accessed

  • OKC_REP_IMPORT_RUN_ID_S — Sequence used to generate import run identifiers for tracking interface-table loads.
  • DUAL — Used for singleton evaluations and PL/SQL housekeeping.

The package additionally performs DML against the broader OKC_REP_* repository contract and interface tables (contracts, parties, party contacts, risks, usages) as implied by its record-type parameters, though only the two objects above are documented explicitly.

Usage Notes

OKC_REP_CONTRACT_IMP_PUB is invoked from the Contracts import process, custom integration programs, and any code that must load repository contracts without direct table manipulation. When p_create_contract is set to FND_API.G_FALSE, callers should subsequently run the "CP Import Repository Contract" concurrent program to materialize the contract. Business events and concurrent managers typically sit above this API. The three dependent packages that reference it should be reviewed before signature changes. Direct table updates to cancel or delete contracts should be avoided; CANCEL_CONTRACT and DELETE_CONTRACT exist precisely to enforce that rule.