Search Results oe_retrobill_request_s

Overview

OE_RETROBILL_PVT is the private implementation package body behind Oracle Order Management's retro-billing engine in Oracle E-Business Suite 12.1.1 and 12.2.2. Retro-billing addresses the business requirement to reprice previously shipped order lines when a price list, discount, surcharge, or promotion changes after the original order was entered. Rather than manually re-keying adjustments, customers schedule a retro-billing request that recalculates pricing for the affected order lines and generates compensating price adjustments on the sales order.

The package is classified as a PVT (private) API within the APPS schema. It is not intended for direct third-party invocation; the public entry point is the OE_RETROBILL_PUB wrapper and the associated concurrent program. The body orchestrates the full retro-billing lifecycle: identifying candidate lines, re-running Oracle Advanced Pricing (QP) engines against historical pricing phases, computing deltas between the original and current price, and persisting the resulting adjustments through the OE_ORDER_ADJ_PVT and OE_HEADER_ADJ_UTIL interfaces. State is tracked in OE_RETROBILL_REQUESTS and OE_RETROBILL_REQUEST_S, which drive status reporting and re-processing.

Key Procedures and Functions

The body exposes a rich procedural surface. The following describes purpose only; parameter signatures are not documented here.

• PROCESS_RETROBILL_REQUEST — main driver that reads an active request row and coordinates line selection, repricing, and adjustment creation.
• PROCESS_RETROBILL_ADJUSTMENTS — applies computed deltas as price adjustments on order lines via OE_ORDER_ADJ_PVT.
• PREPROCESS_ADJUSTMENTS — prepares staging data and validates eligibility before adjustments are written.
• OE_BUILD_RETROBILL_TBL — constructs the working set of retro-billable lines for the request.
• UPDATE_RETROBILL_LINES — writes back processed line and adjustment identifiers.
• UPDATE_INVALID_DIFF_ADJ — corrects or invalidates adjustments whose delta can no longer be honoured.
• 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, GET_LINE_ADJUSTMENTS, INVOICE_NUMBER — accessors that fetch prior adjustments, prices, pricing-phase counts, price-list context, and invoice identifiers.
• RETROBILL_ENABLED — flag check honouring OE_SYS_PARAMETERS and profile options.
• RETURN_RETROBILLED_LINE_CHECK — validates RMA-return eligibility for retro-billed lines.
• INTERFACE_RETROBILLED_RMA — feeds retro-billed RMA data into the return flow.
• OE_RETROBILL_CONC_PGM — concurrent-program wrapper that drives batch execution.
• OE_RETROBILL_PURGE — archives and purges completed request history.

Tables Accessed

The package references the OE_RETROBILL_REQUESTS and OE_RETROBILL_REQUEST_S synonyms as its primary state store, tracking request criteria, status, and processed counts. Order-line detail is read from OE_ORDER_LINES_ALL, OE_ORDER_LINES, and the OE_AK_ORDER_LINES_V view, with headers in OE_ORDER_HEADERS_ALL and attributes in OE_ORDER_PRICE_ATTRIBS. Pricing context comes from QP_LIST_HEADERS_B, QP_LDETS_V, QP_EVENT_PHASES, QP_PRICING_PHASES, and the QP_PREQ_* temporary tables. Computed adjustments are written to OE_PRICE_ADJUSTMENTS, OE_PRICE_ADJUSTMENTS_S, OE_PRICE_ADJ_ASSOCS, and OE_PRICE_ADJ_ASSOCS_S. Message logging uses OE_PROCESSING_MSGS, OE_PROCESSING_MSGS_TL, FND_MESSAGE, and FND_MSG_PUB. Reference lookups include OE_TRANSACTION_TYPES_ALL, OE_TRANSACTION_TYPES_TL, FND_LANGUAGES, and OE_CONC_REQUEST_IFACE; invoicing ties back through RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL.

Usage Notes

In 12.1.1 and 12.2.2 OE_RETROBILL_PVT is invoked exclusively through the Order Management retro-billing concurrent program, launched from the Sales Orders or Pricing responsibility, or through the public OE_RETROBILL_PUB wrapper. Oracle does not certify direct calls to the _PVT layer; any custom integration should call the public API and rely on the standard request-tracking tables. The package depends heavily on FND_API, FND_GLOBAL, MO_GLOBAL, and OE_DEBUG_PUB, and honours Multi-Org and language settings at runtime. Because it interacts with pricing and adjustment tables, retro-billing jobs should be scheduled during low-activity windows and monitored via the OE_RETROBILL_REQUESTS status columns. Five other packages reference OE_RETROBILL_PVT, but it is not referenced by any database object directly, confirming its internal-only design.