Results for “invoice_number”

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

Overview

OE_RETROBILL_PVT is a private PL/SQL package in the APPS schema that implements the retro-billing engine for Oracle Order Management. Retro-billing is the process by which pricing adjustments negotiated after an order has been booked—most commonly retrospective discounts, rebates, or volume-based price breaks—are applied back to already-shipped or already-invoiced order lines. Because the adjustments affect downstream Receivables invoices, the package must reconcile order pricing with billing data while preserving the audit trail of the original transaction.

The package is classified as a PVT (private) API, indicating that it is intended for internal use by other Order Management packages rather than as a public integration interface. It is a critical component of the pricing and adjustment subsystem, invoked by OE_ORDER_PUB, OE_INVOICE_PUB, OE_ORDER_PRICE_PVT, OE_LINE_ADJ_UTIL, OE_HEADER_ADJ_UTIL, OE_VALIDATE_HEADER, and OE_DEFAULT_LINE. In Oracle EBS 12.1.1 and 12.2.2, the package body is delivered as VALID in a standard installation, and its dependencies reference the standard SYS.STANDARD package.

The metadata documents twenty procedures and functions covering the complete retro-billing lifecycle: request creation, eligibility checking, adjustment calculation, line updating, RMA handling, purge, and concurrent program processing.

Key Procedures and Functions

• PROCESS_RETROBILL_REQUEST — The primary entry point that drives a retro-billing request through eligibility, adjustment, and update phases.
• PROCESS_RETROBILL_ADJUSTMENTS and PREPROCESS_ADJUSTMENTS — Identify and stage eligible price adjustments prior to application on order lines.
• UPDATE_RETROBILL_LINES and UPDATE_INVALID_DIFF_ADJ — Write calculated retro-billed values back to order lines and correct invalid differentiating adjustments.
• OE_BUILD_RETROBILL_TBL — Constructs the internal working table of retro-bill candidates.
• GET_RETROBILLED_SUM, GET_RETURN_PRICE, GET_MOST_RECENT_RETRO_ADJ, GET_LAST_RETRO_HDRID, GET_LAST_RETRO_LINID, GET_FIRST_LINE_PRICE_LIST_ID, GET_RETRO_PRICING_PHASE_COUNT, and GET_LINE_ADJUSTMENTS — Retrieve aggregates, historical adjustment identifiers, price list references, and line-level adjustment detail used in recalculation.
• RETROBILL_ENABLED — Boolean eligibility check determining whether retro-billing applies to a given order or transaction type.
• INTERFACE_RETROBILLED_RMA and RETURN_RETROBILLED_LINE_CHECK — Handle returns and RMA lines affected by retro-billed pricing.
• INVOICE_NUMBER — Resolves the invoice reference associated with retro-billed lines.
• OE_RETROBILL_CONC_PGM — The concurrent program driver that processes retro-bill requests in batch.
• OE_RETROBILL_PURGE — Removes processed or obsolete retro-billing records from the request interface tables.

Tables Accessed

The package reads and writes OE_RETROBILL_REQUESTS and OE_RETROBILL_REQUEST_S, which store the header and line detail of retro-billing requests. Order data is drawn from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, and OE_ORDER_LINES_ALL, with pricing attributes in OE_ORDER_PRICE_ATTRIBS. Adjustment definitions and associations are read from OE_PRICE_ADJUSTMENTS, OE_PRICE_ADJUSTMENTS_S, OE_PRICE_ADJ_ASSOCS, and OE_PRICE_ADJ_ASSOCS_S. OE_TRANSACTION_TYPES_ALL determines whether a transaction type supports retro-billing, while FND_LANGUAGES and OE_PROCESSING_MSGS / OE_PROCESSING_MSGS_TL supply multilingual messages for errors and status. OE_CONC_REQUEST_IFACE is used when the concurrent program submits processing requests.

Usage Notes

OE_RETROBILL_PVT is invoked indirectly through order entry forms and the Order Management pricing engine whenever an adjustment with retro-billing behavior is defined and applied. Merchandising and Advanced Pricing setups that enable retro-billing drive the calls from OE_ORDER_PUB and OE_ORDER_PRICE_PVT during order or line save. The concurrent program entry point, OE_RETROBILL_CONC_PGM, should be scheduled from the Order Management responsibility to process outstanding OE_RETROBILL_REQUESTS in batch. Because this is a private package, customizations should not call it directly; supported extension points are the public OE_ORDER_PUB and OE_INVOICE_PUB APIs, which internally delegate to this package.