Results for “reopen_promises”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.IEX_PROMISES_BATCH_PUB is a public PL/SQL package body in the Oracle E-Business Suite Advanced Collections (IEX) module. It provides the batch processing engine for customer promise-to-pay records created through the Collections and delinquency management workflow. While IEX_PROMISES_PUB handles the single-record, online creation and maintenance of promises, IEX_PROMISES_BATCH_PUB is designed for set-based operations: it evaluates large volumes of promises, applies payments against them in a defined order, closes or reopens promises on the basis of fulfillment, processes reversals, and drives concurrent (background) processing. The package status is VALID and it is classified as a PUB (public) API, indicating that it is intended for supported external invocation by forms, concurrent programs, or custom code rather than being a private internal helper.
Key Procedures and Functions
- PROCESS_ALL_PROMISES — Master driver that iterates across the full set of eligible promises for processing in a batch run.
- PROCESS_PROMISES — Core worker that evaluates individual promise records and determines the required disposition (fulfillment, closure, retention).
- APPLY_PROMISES_FIFO — Applies available payment amounts against promises using a first-in, first-out allocation sequence.
- PROCESS_REVERSALS — Handles reversal scenarios, unwinding promise records when associated payments are voided, backed out, or adjusted.
- CLOSE_PROMISES — Closes promises that have reached a terminal state, such as full satisfaction of the committed amount.
- REOPEN_PROMISES — Reopens previously closed promises when fulfillment conditions are no longer met.
- PROCESS_PROMISE_CALLBACKS — Invokes callback logic so that dependent processes or integrations can react to promise state transitions.
- IEX_PROMISES_CONCUR — The concurrent-program entry point that orchestrates batch promise processing from the Oracle EBS concurrent manager.
All procedures rely on shared infrastructure in FND_API, FND_MSG_PUB, FND_LOG, and IEX_UTILITIES for error handling, message propagation, and logging.
Tables Accessed
The package reads and writes the core promise and delinquency tables: IEX_PROMISE_DETAILS (promise records), IEX_DELINQUENCIES and IEX_DELINQUENCIES_ALL (delinquent customer state), and IEX_DLN_UWQ_SUMMARY (underwriting queue summary). Payment and adjustment evaluation draws on AR_PAYMENT_SCHEDULES and AR_ADJUSTMENTS. Customer context is resolved through HZ_CUST_ACCOUNTS. The IEX_PRD_APPL_XREF and IEX_PRD_APPL_XREF_S tables (the latter an APPS sequence, and the object referenced in the user's search) provide the product-to-application cross-reference used when applying promises. Task integration uses JTF_OBJECT_USAGES, JTF_TASK_STATUSES_TL, and JTF_TASK_TYPES_TL. Dynamic SQL is supported through DBMS_SQL and PLITBLM. Multi-org security is enforced via MO_GLOBAL and FND_GLOBAL.
Usage Notes
The package is typically invoked through the IEX_PROMISES_CONCUR concurrent program rather than directly. Oracle Advanced Collections oracle forms may call the public procedures when a user triggers batch promise maintenance actions. Custom code should call only the PUB procedures and must supply initialization for FND_GLOBAL and MO_GLOBAL (organization context) prior to invocation. Because batch processing modifies promise and payment state, transactions should be committed at the calling level, and FND_MSG_PUB results should be inspected for error messages. The package is not referenced by any database object, confirming it sits at the top of the dependency hierarchy as an entry point.