Results for “create_contract_line”

50+ results




Overview
Explore in AI Chat

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

Overview

OKE_IMPORT_CONTRACT_PUB is the public application programming interface for importing and maintaining contract structures within Oracle Enterprise Contracts (OKE/OKC). In Oracle EBS 12.1.1 and 12.2.2, the package body provides the externally callable entry points used by forms, concurrent programs, and integration code to create, update, and delete contract headers, contract lines, deliverables, and line items in a controlled and validated manner. The "_PUB" suffix identifies the package as a published API layer, meaning it is intended for supported external invocation rather than internal use. The body delegates shared validation and messaging logic to OKE_API, referencing constants such as G_FND_APP, G_REQUIRED_VALUE, G_INVALID_VALUE, and G_UNEXPECTED_ERROR to return standardized FND-style messages. The header revision identifier shows this object has been stable since the 11i-era code line, which is characteristic of the EBS contract APIs that were carried forward largely unchanged into Release 12.

Key Procedures and Functions

The documented public interface exposes fourteen procedures that fall into three functional groups:

DEFINE_BILLING_METHODS, the procedure associated with the search term, attaches one or more billing methods to a contract line so that the pricing and invoicing rules of the line are established. REMOVE_BILLING_METHODS reverses that assignment. Both are designed to be called in conjunction with line creation or update, and both respect the same validation and return-status conventions used by the other public procedures. Each procedure returns a standard x_return_status value (success, error, or unexpected error) and writes messages to the FND message stack through the shared exception handling declared in the package body.

Tables Accessed

The package reads and writes contract data through APPS synonyms. Core header and line data reside in OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_B, OKC_K_LINES_B, and OKE_K_HEADERS and OKE_K_LINES. Deliverables and billing items are stored in OKC_K_ITEMS. Supporting structures include OKC_CONTACTS for party contact information, OKC_K_PARTY_ROLES_B for role assignments, OKC_ANCESTRYS for hierarchy relationships, OKC_ASSENTS for assent records, and OKC_K_ARTICLES_B with OKC_K_ARTICLES_TL for contract terms and their translations. Validation logic queries HR_ALL_ORGANIZATION_UNITS, HR_OPERATING_UNITS, and MTL_PARAMETERS, and the package references the view OKE_K_LINES_V along with MRP_SCHEDULE_DATES when deriving organization and scheduling context. These queries confirm that the inventory organization supplied on import must be a master organization defined in MTL_PARAMETERS, and that the authoring organization must be a valid operating unit.

Usage Notes

This package is typically invoked from the Enterprise Contracts import flows, from contract authoring forms that delegate saves to the public API, and from custom integration code loading contracts from external sources. Because it is referenced by zero other packages, it functions as a top-level entry point rather than a shared internal dependency. Callers should initialize the FND message stack, populate the record type structures defined alongside the package specification, and inspect x_return_status before committing. In 12.1.1 and 12.2.2 the behavior is consistent; the primary differences arise from the underlying multi-org and MOAC configuration rather than the API signature. When implementing custom billing method logic, DEFINE_BILLING_METHODS should be called after the contract line exists and before the transaction is committed.