Skip Headers

Oracle Advanced Collections User Guide
Release 12.1
Part Number E13451-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Administering Oracle Advanced Collections

This chapter describes how to administer the ongoing functions in Oracle Advanced Collections such as running concurrent programs.

This chapter covers the following topics:

Using Preconfigured Components

Oracle Advanced Collections provides preconfigured scoring components, scoring engines, work item templates, strategy templates, metrics formulas, and correspondence templates and queries to use with the application.

You can use these features without any additional setup during the testing phase of your implementation. You can also use these preconfigured elements in your live production environment if they suit your business needs.

For more information on the preconfigured components, see: Preconfigured Correspondence Templates, Oracle Advanced Collections Implementation Guide, Preconfigured Scoring Engines, Oracle Advanced Collections Implementation Guide, Preconfigured Scoring Components, Oracle Advanced Collections Implementation Guide, Preconfigured Strategy Templates, Oracle Advanced Collections Implementation Guide, Preconfigured Strategy Work Items, Oracle Advanced Collections Implementation Guide.

Running Concurrent Programs

Oracle Advanced Collections uses concurrent programs to run batch processes behind the scenes. The administrator is responsible for setting up the parameters for each concurrent program. Each concurrent program runs at the lowest responsibility level, and can be set to run at multiple responsibility or organization levels. For example, administrators can login by country (different responsibilities) and set different parameters to use when running the same concurrent program. The default is set to run at the site level.

When you run a concurrent program, it runs across all operating units in your organization unless you specify an operating unit as one of the parameters.

For detailed instructions for running and maintaining concurrent programs, refer to the Managing Concurrent Processing and Concurrent Programs, Oracle E-Business Suite System Administrator's Guide - Maintenance.

You can use concurrent programs in Advanced Collections to create delinquencies, reconcile promises, assign strategies, execute dunning plans, initialize Credit Management customer information, process Oracle Lease and Finance Management functionality, and more. The concurrent programs and the order you execute them will vary depending on whether you are running Strategies or Dunning Plans, and whether or not you leverage Oracle Lease and Finance Management.

Run concurrent programs as often as you need to keep your operational systems current. For example, if you assign strategy work items every day, then run the IEX: Strategy Management current program daily. If you send dunning notices only at the beginning of a billing cycle, then run IEX: Send Dunnings for Delinquent Customers every month at that time.

If you use Strategies:

When you use Strategies, you need to run the following concurrent programs in this order:

Remember that each concurrent program must be completed before the subsequent concurrent program is submitted to ensure the accuracy of the data and programs.

If you use Dunning Plans:

When you are running Dunning Plans, you will need to run the following concurrent programs in this order:

Remember that each concurrent program must be completed before the subsequent concurrent program is submitted to ensure the accuracy of the data and programs.

If you use Universal Work Queue:

Use the IEX Populate UWQ Summary Table concurrent program to update delinquent customer data in the Collector's Work Queue. This program consolidates information from the following sources and summarizes it in the IEX_DLN_UWQ_SUMMARY table:

The data in the Collector's Work Queue refreshes each time you run the IEX: Populate UWQ Summary Table concurrent program.

Note: This program displays information in the Collectors Work Queue only for the operational data level at which you run strategies. For example, if you run strategies at the account level, the concurrent program will only summarize information for the account level nodes.

The Active, Pending, and Complete subnodes display the total number of delinquencies for the primary node and do not break out the number by subnode status.

Data refreshes after the concurrent program completes.

Parameters

If you use Territory Manager:

For System Maintenance:

You can run the following administrative concurrent programs periodically for system maintenance:

Concurrent Programs for Oracle Lease and Finance Management

Oracle Lease and Finance Management uses the following concurrent programs: