Search Results dunning




The IEX_DUNNING_PLANS_B table is a critical component within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2, specifically designed to support the functionality of the Collections module (part of Oracle Receivables). This table serves as the foundation for storing dunning plan definitions, which are essential for automating the collections process by defining escalation rules for overdue invoices. Below is a detailed technical breakdown of its structure, purpose, and integration within Oracle EBS.

1. Purpose and Functional Context

The IEX_DUNNING_PLANS_B table stores master data for dunning plans, which are used to systematically manage customer overdue payments. Dunning plans define the sequence of actions (e.g., reminders, letters, or calls) triggered at specific intervals based on invoice aging. This table is part of the Oracle Collections module (IEX), which integrates with Oracle Receivables (AR) to streamline collections workflows.

2. Key Columns and Structure

The table's structure includes columns that define the dunning plan's attributes, such as:
  • DUNNING_PLAN_ID: Primary key, uniquely identifying each dunning plan.
  • NAME: The display name of the dunning plan.
  • DESCRIPTION: A detailed explanation of the plan's purpose.
  • START_DATE_ACTIVE and END_DATE_ACTIVE: Define the plan's validity period.
  • ENABLED_FLAG: Indicates whether the plan is active (Y/N).
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE: Audit columns tracking record creation/modification.
Additional columns may include ORG_ID (for multi-org support) and attributes for customization, such as ATTRIBUTE_CATEGORY and ATTRIBUTE1-15 (flexfield columns).

3. Integration with Other Modules

The table integrates with:
  • Oracle Receivables (AR): Dunning plans are assigned to customer profiles (RA_CUSTOMER_PROFILES) to automate collections.
  • IEX_DUNNING_STEPS_B: Child table storing escalation steps (e.g., letters or calls) linked via DUNNING_PLAN_ID.
  • IEX_STRATEGIES_B: Links dunning plans to broader collection strategies.

4. Technical Considerations

  • Indexes: Typically indexed on DUNNING_PLAN_ID, NAME, and ORG_ID for performance.
  • APIs: Managed via Oracle Collections' PL/SQL APIs (e.g., IEX_DUNNING_PLANS_PKG) for CRUD operations.
  • Multi-Org: Supports ORG_ID to segregate data by operating unit.

5. Customization and Extensions

The table supports flexfields and workflow integrations, allowing businesses to tailor dunning logic. For example:
  • Custom attributes can be added via descriptive flexfields.
  • Workflows can trigger external actions (e.g., SMS alerts) based on plan steps.

6. Data Flow Example

A typical workflow involves:
  1. Creating a dunning plan in IEX_DUNNING_PLANS_B with steps (e.g., "Send Email at 15 days overdue").
  2. Assigning the plan to a customer profile in AR.
  3. Oracle Collections engine evaluates overdue invoices and executes steps per the plan.

7. Conclusion

The IEX_DUNNING_PLANS_B table is a cornerstone of Oracle Collections, enabling systematic management of overdue payments. Its design ensures flexibility, integration with core EBS modules, and scalability for complex collections scenarios. Understanding its structure and relationships is crucial for implementing effective collections strategies in Oracle EBS 12.1.1 or 12.2.2.