Populating Transaction Data

To enable faster performance and greater processing efficiency, Oracle Credit Management populates two summary tables with Oracle Receivables data, such as the amount of open invoices and the percentage of invoices paid late.

Later, during credit reviews, Credit Management examines the data in these prepopulated tables, thus saving processing time and delivering faster results.

The tables are:

Note: Another application in the E-Business Suite, Oracle Advanced Collections, also uses these summary tables.

Two methods exist to populate the summary tables with data:

  1. Initial load (manual implementation step):

    During implementation, set the AR: Allow summary table refresh profile option to Yes. Then, run the Credit Management Refresh AR Transactions Summary Tables concurrent program from the Submit Requests window.

    This program calculates and loads summarized data from Oracle Receivables for all customers.

    Note: Once the concurrent program successfully completes, the profile option is automatically set back to No. If you ever want to reset the summary tables, then you must first set the profile option back to Yes. See: Profile Options and Profile Option Categories Overview.

  2. Continuous updates (automatic process):

    The initial data load is only a snapshot of customer data at a point in time. To ensure that credit reviews access the most current data, all subsequent transactions for your customers must be captured in the summary tables. This data capture is automatically enabled through a series of workflow business events.

    What is a business event? A business event is an occurrence in an internet or intranet application or program that might be significant to other objects in a system or to external agents. See: Events.

    As business events occur in Oracle Receivables, those events are enqueued in the seeded WF_DEFERRED queue, which is the standard queue for deferred subscription processing in the database. As events are enqueued, a seeded PL/SQL agent listener service component named Workflow Deferred Agent Listener runs on a scheduled basis and executes the event subscriptions (already seeded by Credit Management) by updating the summary tables.

    See: Credit Management Application Workflow.

    For instance, a receipt application is an example of an Oracle Receivables business event. Credit Management considers this business event significant because receipt applications impact customer data. Accordingly, Credit Management provides a default subscription to this event, so that when receipt applications are recorded in the system, the Workflow Deferred Agent Listener automatically updates the summary tables during its next scheduled run.

    The business events that can be triggered to populate the summary tables are:

Frequently Asked Questions

The summary tables are not getting updated. How can I troubleshoot this problem?

To run the seeded agent listener, you should ensure that the Workflow Agent Listener Service container is running using Oracle Applications Manager for the version of Oracle Workflow embedded in Oracle Applications, or ensure that the WFALSNRSVC container is running using Oracle Enterprise Manager for the standalone version of Oracle Workflow.

To manage agent listener service components, use Oracle Workflow Manager, which is available as a component of Oracle Applications Manager if you are using the version of Oracle Workflow embedded in Oracle Applications, or as a component of Oracle Enterprise Manager if you are using the standalone version of Oracle Workflow. For more information, please refer to the Oracle Applications Manager online help or the Oracle Enterprise Manager online help.

See: Scheduling Listeners for Local Inbound Agents.