Results for “define_billing_methods”

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

Overview

OKE_IMPORT_CONTRACT_PUB is a public PL/SQL package in the APPS schema that provides the programmatic interface for importing and maintaining Oracle E-Business Suite Contracts (OKE) and related OKC contract repository data. It is the primary entry point used by Oracle's contract import tooling, whether invoked interactively from the Contract Import form or executed programmatically from batch processes and custom integrations. The package wraps the underlying OKC_API and OKE_API business logic so that callers do not manipulate the base contract tables directly. In Oracle EBS 12.1.1 and 12.2.2 it retains a VALID status and an API classification of PUB, meaning it is a supported, callable API that Oracle expects external code to reference. Its responsibility is to translate validated import requests into contract headers, lines, line items, deliverables, and billing methods, and to support the reverse operations of updating and deleting those same records.

Key Procedures and Functions

The package exposes fourteen documented procedures. CREATE_CONTRACT_HEADER establishes a new contract header record in the OKC/OKE model. CREATE_CONTRACT_LINE, CREATE_LINE_ITEM, and CREATE_DELIVERABLE add the subordinate line, item, and deliverable structures beneath an existing header. DEFINE_BILLING_METHODS attaches billing method assignments to a contract, while REMOVE_BILLING_METHODS reverses that association. UPDATE_CONTRACT_HEADER, UPDATE_CONTRACT_LINE, UPDATE_LINE_ITEM, and UPDATE_DELIVERABLE perform maintenance on already-created records. DELETE_CONTRACT_LINE, DELETE_DELIVERABLE, and DELETE_CONTRACT remove the respective records and are intended for error-correction and re-import scenarios. Because the API is declarative in purpose, callers supply validated attributes and recurrence information; the package handles the orchestration of the underlying OKC and OKE API calls rather than exposing raw DML.

Tables Accessed

The package reads and writes through APPS synonyms over the contract repository. Header data is persisted in OKE_K_HEADERS and maintained in the broader OKC_K_HEADERS_ALL_B and OKC_K_HEADERS_B structures, with descriptive text held in OKC_K_ARTICLES_B and OKC_K_ARTICLES_TL. Lines are stored in OKE_K_LINES and OKC_K_LINES_B, with line item detail in OKC_K_ITEMS. Party and contact information is resolved from OKC_K_PARTY_ROLES_B and OKC_CONTACTS, while OKC_ANCESTRYS and OKC_ASSENTS support hierarchy and assignment relationships. Organizational context for contract ownership and billing flows through HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS, and scheduling references are drawn from MRP_SCHEDULE_DATES.

Usage Notes

OKE_IMPORT_CONTRACT_PUB is normally invoked by the Contract Import form and its associated concurrent programs during mass contract loads, and by custom PL/SQL routines that need to create or maintain service contracts without manual entry. The package is referenced by no other database packages, indicating it is a top-level integration surface rather than an internal utility. When calling it from custom code, developers should validate input in the API layer and follow the documented procedure order—header first, then lines, items, deliverables, and billing methods—so that the underlying OKC and OKE validation rules are satisfied.