Search Results iex_bad_api_input

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

Overview

APPS.IEX_PROMISES_PUB is the public PL/SQL API package for the Oracle Advanced Collections (IEX) Promise-to-Pay functionality within Oracle E-Business Suite. Its core business purpose is to create, maintain, and manage customer promises (also known as Promise-to-Pay, or PTP) — commitments made by a delinquent customer to pay a specific amount by a specific date. Organizations rely on this package to record promises captured by collections agents, to advance or revise those promises, to cancel them, and to move selected promises into the collections work queue for follow-up. It also supports strategy management, which governs how promises are handled by scoring and collections workflows. The package follows the Oracle EBS API standards: it defines a package-level application ID (G_APP_ID = 695, the IEX application), a package name constant, and uses FND_API for compatibility checking, savepoint and message-list management, FND_LOG for debug logging, and FND_GLOBAL for session context. The package body header references file iexpyprb.pls (version 120.8.12010000.3), which is consistent with the 12.1.1 and 12.2.2 code lines. As a PUB package, it is the supported API surface that external forms, concurrent programs, and custom extensions should call, rather than manipulating the underlying promise tables directly.

Key Procedures and Functions

• INSERT_PROMISE — Creates a new customer promise record, associating a promise amount, promise date, and related context with the appropriate customer/account and delinquency information.
• UPDATE_PROMISE — Modifies an existing promise, such as revising the promised amount, date, or other attributes before it is fulfilled or broken.
• CANCEL_PROMISE — Cancels a previously recorded promise, typically when the customer's commitment is revoked or superseded.
• MASS_PROMISE — Supports creating or processing promises in bulk, allowing multiple promises to be handled in a single operation rather than one at a time.
• SET_STRATEGY — Associates or assigns a collections strategy to promise handling, influencing how promises are scored and acted upon within Advanced Collections.
• SHOW_IN_UWQ — Moves selected promises into the Universal Work Queue (UWQ), so collections agents see them as actionable tasks, optionally filtered by status and a number of days.
• UPDATE_DEL_STAGE_LEVEL — Updates the delinquency staging level associated with promises, reflecting movement of the customer's account through collections delinquency stages.

Tables Accessed

The package reads and writes several Advanced Collections and Receivables tables. Promise records themselves are persisted through IEX_PROMISE_DETAILS and its sequence IEX_PROMISE_DETAILS_S. Delinquency context is drawn from IEX_DELINQUENCIES and IEX_DELINQUENCIES_ALL. Customer identification uses HZ_PARTIES, while payment schedule information comes from AR_PAYMENT_SCHEDULES. Strategy behavior is governed by IEX_STRATEGIES, and workflow/task routing for promises is handled via IEX_PTP_WF_S. The package also references DBMS_SQL (notably a NUMBER_TABLE used for promise ID collections in SHOW_IN_UWQ), DUAL, and PLITBLM for standard utility purposes.

Usage Notes

IEX_PROMISES_PUB is invoked by Advanced Collections forms, concurrent programs, and custom code that needs to create or manage promises in a supported manner. Because the documented SHOW_IN_UWQ API validates call compatibility via FND_API.Compatible_API_Call and issues its own savepoint, callers must pass a valid API version and honor the returned X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA outputs. Note that the search term "iex_bad_api_input" does not appear as a constant or documented parameter of this package; it most likely originates from FND_API-compatible validation logic (an invalid or missing input parameter passed to a public API), and callers encountering it should verify that mandatory parameters, API versions, and validation levels are supplied correctly. The package is referenced by one other package in the ETRM metadata, reinforcing that it is a shared dependency and that direct DML against the underlying promise tables should be avoided in favor of these public procedures.