Results for “oke_api_missing_value”

16 results




Overview
Explore in AI Chat

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

Overview

The APPS.OKE_DELIVERABLE_BILLING_PVT package body is a private (PVT-classified) PL/SQL implementation within Oracle E-Business Suite that supports the billing of deliverables on Oracle Contracts (OKE/OKC) engagements. It exists to translate accepted project deliverables into billable events, binding the contractual deliverable definition to Oracle Projects billing and revenue structures. This is the operational engine that a user implicitly invokes when recording a "sale purchase bill" against a contract in a manufacturing or commodity-distribution environment (for example, tobacco trading), where a shipment, delivery, or purchase milestone generates a customer invoice line.

The package version documented here (header revision 120.8, dated 21-Nov-2008) is common to the 12.1.1 and 12.2.2 code lines. Private globals such as G_Pkg_Name and g_module support error-handling and message-prefixing conventions used across Oracle Contracts public APIs. The package is not exposed as a public API; it is consumed by two other packages in the deliverable-billing flow.

Key Procedures and Functions

  • CREATE_BILLING_EVENT — Constructs a new billing event for a deliverable, including sequencing, contract and order references, and bill-to information, then persists it as a billable milestone.
  • UPDATE_BILLING_EVENT — Modifies an existing billing event, such as quantity, unit price, description, or billing date, prior to invoicing.
  • INSERT_BILLING_INFO — Inserts the detailed billing and accounting information derived from the deliverable into the billing-event tables.
  • UPDATE_BILLING_INFO — Maintains and re-aligns existing billing detail records when the underlying deliverable or pricing changes.
  • DELETE_BILLING_INFO — Removes billing detail rows associated with a deliverable, typically when a billing event is reversed or cancelled.
  • POPULATE_MC_COLUMNS — Populates multi-currency columns (currency code and converted amounts) on billing records.
  • LOCK_BILLING_INFO — Acquires a locking reference on billing information to prevent concurrent modification during processing.
  • EVENT_LEVEL — Determines the event level (contract, line, or deliverable) at which a billing event is raised, which dictates the granularity of the invoice generated.

Tables Accessed

  • OKE_K_BILLING_EVENTS — the primary billing event store, holding unit price, quantity, currency, revenue amount, and bill line references.
  • OKE_K_DELIVERABLES_B — the deliverable definition, supplying UOM code, inventory organization, and item identity.
  • OKE_K_HEADERS — the contract header, linking the billing event to its governing contract and bill-to organization.
  • OKC_K_HEADERS_B and OKC_K_LINES_B — read to resolve contract number, contract line number, and order number (via the ContractNum and LineNum cursors).
  • OKE_CHG_REQUESTS — change-request context for billing adjustments.
  • PA_EVENTS and PA_EVENTS_S — Oracle Projects events used to obtain the pa_event_id and the next event number per project and task.
  • DUAL — used for scalar evaluations and currency/date defaults.

Usage Notes

This package is invoked internally rather than directly by end users. It is typically triggered from the Oracle Contracts deliverable billing form when a user bills a deliverable, from concurrent programs performing mass billing-event creation, or by the two dependent packages integrated into the same flow. Because it is classified Private, it is not supported for direct customisation; extensions should call the corresponding public APIs. Bugs in event generation, currency population, or contract number resolution should be reported against this package with the ETRM revision reference above.