Results for “iex_dunning_pub”

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

Overview

IEX_DUNNING_PUB is the public PL/SQL API package for the Oracle E-Business Suite Advanced Collections (IEX) dunning subsystem. Dunning is the process by which an organization systematically communicates with delinquent customers regarding overdue receivables, escalating from courtesy reminders to formal collection letters and eventually to external collection agencies. IEX_DUNNING_PUB exposes the procedural interface through which application forms, concurrent programs, and custom extensions create dunning correspondence, record dunning history, close completed dunning actions, and manage the cross-reference between a delinquent customer and an external collection agency. In Oracle EBS 12.1.1 and 12.2.2 the package resides in the APPS schema with a status of VALID, and its companion private package IEX_DUNNING_PVT contains the internal implementation logic that the public package delegates to. The API is classified as a PUB (public) interface, meaning it is documented and supported for direct invocation.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within the package body:

• CREATE_AG_DN_XREF — Creates a cross-reference record associating a delinquent customer account with an external collection agency and the dunning correspondence sent to that agency.
• UPDATE_AG_DN_XREF — Maintains existing agency dunning cross-reference records, allowing attributes such as status or agency assignment to be revised.
• DELETE_AG_DN_XREF — Removes an agency dunning cross-reference record when the association is no longer valid.
• SEND_DUNNING — Generates and dispatches dunning correspondence for a delinquency, producing the letter or document output and recording the dunning transaction.
• CLOSE_DUNNING — Marks a dunning action as completed or closed, typically when the underlying delinquency is resolved or the dunning sequence has concluded.
• DAILY_DUNNING — Executes the periodic, set-based dunning run that evaluates delinquencies and issues dunning letters according to configured dunning plans and scoring.
• CALLBACK_CONCUR — Callback entry point used by the concurrent manager to report or process the outcome of a submitted dunning request.
• SEND_DUNNING_CONCUR — Concurrent-program wrapper that submits dunning correspondence generation as a batch process.
• STG_DUNNING_MIG_CONCUR — Concurrent-program entry point supporting staged migration of dunning data.

Parameter lists are intentionally omitted; callers should reference the ETRM package specification for exact signatures.

Tables Accessed

The package queries and maintains the core dunning data model. IEX_DUNNING_PLANS_B, IEX_DUNNING_PLANS_TL, and IEX_DUNNING_PLANS_VL hold the dunning plan definitions, translations, and validated list of values; IEX_DUNNING_PLANS_S is the sequence-based primary key source, which is why a search for "iex_dunning_plans_s" surfaces this package. IEX_DUNNINGS and IEX_DUNNING_TRANSACTIONS record generated dunning events and their detail lines. IEX_DELINQUENCIES and IEX_DELINQUENCIES_ALL supply the delinquent customer population, while AR_PAYMENT_SCHEDULES_ALL, AR_DUNNING_LETTER_SETS, and AR_DUNNING_LETTER_SET_LINES provide receivables balances and letter-set configuration. IEX_AG_DN_XREF and IEX_AG_DN_XREF_S support agency dunning cross-references. Supporting tables include HZ_CUST_SITE_USES_ALL, IEX_APP_PREFERENCES_B and _VL, IEX_SCORES, IEX_OBJECT_FILTERS, IEX_QUESTIONNAIRE_ITEMS, and RA_CUSTOMER_TRX. Framework dependencies include FND_API, FND_CONCURRENT, FND_FILE, FND_GLOBAL, FND_LANGUAGES, FND_LOG, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, FND_REQUEST, MO_GLOBAL, XDO_TEMPLATES_VL, and IEX_XML_PKG.

Usage Notes

IEX_DUNNING_PUB is invoked primarily from the Oracle Advanced Collections dunning workbench and from the Daily Dunning concurrent program, which calls DAILY_DUNNING and SEND_DUNNING to process delinquencies in batch. The CONCUR procedures are registered as concurrent program entry points. Custom code should call only the documented public procedures, rely on FND_MSG_PUB for error handling, and observe the package's dependency on MO_GLOBAL for multi-org security. Because the package is not referenced by any other database object, it functions as a top-level integration surface rather than an internal utility. Callers on 12.1.1 and 12.2.2 may use identical signatures; the five dependent packages that reference IEX_DUNNING_PUB should be validated after any upgrade or patch application.