Search Results is_prepaid

Overview

OE_PREPAYMENT_UTIL is a utility package in the Oracle Order Management (OE) module of Oracle E-Business Suite, owned by the APPS schema and classified as a UTIL-type API. It encapsulates the business logic that governs prepayment, downpayment, and payment-assurance handling across the order-to-cash flow. In releases 12.1.1 and 12.2.2, the package provides shared helper routines that determine whether an order, line, or payment term qualifies as prepaid, retrieve prepayment and commitment information, evaluate installment and multiple-payment configurations, and support the pay-now and commitment upload processes. Although the ETRM metadata lists 12 documented procedures and functions, the excerpt surfaces the principal ones enumerated below. The package depends on FND_API and OE_ORDER_PUB, and is referenced by 22 other packages, indicating that it is a foundational dependency for order header, line, payment, credit-check, and workflow utilities rather than an end-user-facing entry point.

Key Procedures and Functions

• IS_PREPAID — Evaluates whether a given order or payment context is prepaid, returning the appropriate indicator used by downstream validation and payment logic.
• GET_PREPAYMENT_INFO — Retrieves prepayment details for the specified order context, supplying the data other utilities require to process downstream actions.
• PENDPROCESSPAYMENTS_CONC_PROG — Serves as the concurrent-program entry point for processing pending payments, supporting batch execution of prepayment handling.
• IS_PREPAID_ORDER — Determines whether an order is classified as a prepaid order.
• IS_MULTIPLE_PAYMENTS_ENABLED — Checks whether the multiple-payments feature is enabled for the current configuration.
• IS_MULTIPAYMENTS_ORDER — Identifies whether an order is a multiple-payments order.
• UPLOAD_COMMITMENT — Uploads commitment information associated with prepayment processing, interfacing with the commitment and payment-assurance logic.
• GET_DOWNPAYMENT_AMOUNT — Returns the downpayment amount for the order or line context, used in payment-assurance calculations.
• IS_PREPAID_FOR_PAYMENT_TERM — Determines whether prepayment applies for the specified payment term.
• GET_INSTALLMENT_OPTIONS — Retrieves the installment options configured for the payment context.
• IS_PAY_NOW_LINE — Determines whether a line is designated as a pay-now line.

These routines are consumed by parent utilities such as OE_PREPAYMENT_PVT, OE_HEADER_PAYMENT_UTIL, OE_LINE_PAYMENT_UTIL, OE_VERIFY_PAYMENT_PUB, and OE_CREDIT_CHECK_UTIL.

Tables Accessed

The package reads and writes order-management and payment data through APPS synonyms. OE_ORDER_HEADERS and OE_ORDER_HEADERS_ALL hold order header context used for prepaid and multiple-payment determination. OE_ORDER_LINES_ALL provides line-level data for pay-now and downpayment logic. OE_PAYMENTS stores payment records, while OE_HOLD_SOURCES_ALL and OE_ORDER_HOLDS_ALL supply hold definitions and applicability. OE_PROCESSING_MSGS and OE_PROCESSING_MSGS_TL support message retrieval and translation. Customer and instrument tables HZ_CUST_ACCOUNTS, IBY_PMT_INSTR_USES_ALL, IBY_CREDITCARD, and IBY_FNDCPT_TX_EXTENSIONS supply payer accounts and payment instrument details. PLITBLM is an Oracle-standard PL/SQL index-by table synonym used for transient collections.

Usage Notes

OE_PREPAYMENT_UTIL is invoked indirectly through Order Management forms (OE_OE_FORM_HEADER, OE_DEFAULT_HEADER, OE_DEFAULT_LINE), the payment-assurance workflow (OE_PAYMENT_ASSURANCE_WF), delayed-request processing, and reporting via ONT_OEXOECOD_XMLP_PKG. Its concurrent-program routine, PENDPROCESSPAYMENTS_CONC_PROG, is executed as part of scheduled order payment processing. Because it is referenced by 22 packages and is not intended as a standalone API, customizations should call the higher-level public packages and rely on OE_PREPAYMENT_UTIL only as a shared dependency. Direct invocation should be limited to diagnostic or extension code where no public alternative exists.