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 Concurrent Processing, Oracle E-Business Suite Setup Guide.
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 concurrent program daily. If you send dunning notices only at the beginning of a billing cycle, then run IEX: Send Dunnings for Delinquent Customers concurrent program every month at that time.
When you use Strategies, you need to run the following concurrent programs in this order:
Workflow Background Process: IEX: Collection Strategy Workflow: Initiates the execution of assigned strategies and continues monitoring strategies in progress.
Parameters
Work Item: IEX: Collection Strategy Work Flow
Processed Deferred: Yes
Process Timed Out: Yes
Workflow Background Process: IEX: Strategy Fulfillment Mailer: Executes automated correspondence work items for strategies.
Parameters
Work Item: IEX: Strategy Fulfillment Mailer
Processed Deferred: Yes
Process Timed Out: Yes
IEX: Promise Reconciliation: Verifies if payments were posted for promises; creates broken promise items for UWQ.
IEX: Scoring Engine Harness: Scores and creates delinquencies, and scores customer, accounts, and bill-to locations. Add up to five scoring engines to the scoring engine harness. For more information see: Concurrent Programs for Scoring and Preconfigured Scoring Engines.
IEX: Strategy Management: Compares the object's score with available strategies' ranks and assign appropriate strategies for both parent and child customers, if party group relationship is created. It also creates work items in active strategies.
All of customers defined as a Child customer among party relationship would not be assigned any delinquent strategies by the IEX: Strategy Management concurrent program. In addition, if any open/on-hold strategies associated child customer are closed while running the IEX: Strategy Management concurrent program.
Any Parent customer of group would be assigned appropriate delinquent strategies at PARTY level based on the parent customer's score including the child customer's score components.
Attention: Regardless of Collections Business Level, parent customer always get assigned delinquent strategies at 'PARTY' level ONLY. Therefore you must check the 'Customer' option at Business Level Preferences on the Collections Checklist. Otherwise the Strategy Management concurrent program will be force terminated.
Parameters
Operating Unit: Used for viewing and assigning strategies based on the multiple operating unit levels as specified in the checklist.
Ignore Change Strategy Switch: If set to Yes, the Strategy Management program does not dynamically change the strategy assigned to an object if the score is outside the tolerance level set for the strategy. Ignoring dynamic strategy changing improves system performance. The default is No.
Keep Strategies, Even if the Score Changes: When no value is passed for this parameter, it is defaulted as Yes and strategies won't be reassigned even when score got changed. Run the Strategy Management program with the parameter set as No if strategies to be reassigned when score get changed.
IEX: Assign Collections Level: Interfaces the migrated data from the legacy systems to Oracle Advanced Collections and assigns a specific default Collections level to the migrated segment of customers.
Remember that each concurrent program must be completed before the subsequent concurrent program is submitted to ensure the accuracy of the data and programs.
You can use IEX: Put Strategy On Hold/Release concurrent program to place strategies for a specific operating unit or group of operating units.
You can run the program for Operating Units by setting the IEX: Process Strategies by Operating Unit profile option to "Operating Unit".
You can also run the program for strategies which are not having Operating Units by setting the "IEX: Process Strategies by Operating Unit" profile option to "All".
IEX: Put Strategy On Hold/Release: Initiates the process of putting strategies for an OU or a group of OU's on hold or releasing them from hold.
Note: Strategies of Party, Account, Bill- To, and Delinquency types only will be processed by this program
You can only run the program for "Strategies" or "Dunning Plan and Strategies" collections methods.
Note: If the collection method is "Dunning Plan and Strategies" then at least one Operating Unit accessible to you must be registered with 'Strategies' method else concurrent program will error out.
Parameters
Operating Unit: Select the Operating Unit. Keeping the option blank, will select all operating units as default.
Scoring Engine: Optionally, you can select the scoring engine. The DB View associated with the Scoring engine will be used to filter the Strategies.
Scoring engine LOV will display only the list of scoring engines of "Party", "Account", "Bill-To", and "Delinquency" type.
Activity of Strategies: Shows the Activities which can be performed on Strategies.
Place on Hold
Release on Hold
Status report - List of Strategies in on Hold or released in last 7 days
Hold Days: Give the number of days that the strategies will be placed on hold. Hold Days needs to be greater than 0 and less than 1000 days.
You can list all the strategies which are placed On Hold or Released from Hold by the current concurrent request in the last 7 days in PDF output.
When you are running Dunning Plans, you will need to run the following concurrent programs in this order:
IEX: Send Dunnings for Delinquent Customers: Compares the score of the object with the active dunning plan and sends the dunning letters for all appropriate delinquent customers.
IEX: Create Dunning and Broken Promise Call Backs: Reviews the dunning plan and creates all necessary callback tasks for delinquent customers.
Remember that each concurrent program must be completed before the subsequent concurrent program is submitted to ensure the accuracy of the data and programs.
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:
Credit summary information from the AR_TRX_BAL_SUMMARY table
Trading Community Architecture (TCA) data from the HZ_PARTIES and HZ: CONTACT POINTS tables
Delinquency information from IEX_DELINQUENCIES_ALL AND IEX_PROMISES tables
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
From Date: Leave the parameter blank to run the program in total refresh mode or enter the date the program last ran for incremental mode.
The first time you run this program, leave the From Date parameter blank to initialize and load the data. Then schedule the program to run daily in incremental mode. Enter the date of the previous run in the From Date parameter.
Schedule the program to run periodically with the parameter set to null to ensure all data is captured. Since a total refresh can take several hours to run if your database is large, schedule this to run weekly or at a frequency suitable to you business operations. If the total refresh takes less than 30 minutes to run, you can run the program in total refresh mode more frequently.
Operating Unit: Used for viewing and assigning strategies based on the multiple operating unit levels as specified in the checklist.
The IEX: Populate UWQ Summary Tables concurrent program is submitted only once. The summary program loops for each default collections definition level specified in the Operational Setup. The UWQ summary data is populated for each party based on Collections level only one node at a time. The Collections Definition levels enables the UWQ nodes automatically.
Truncate: When the From Date value is given, then Truncate value defaults to No and cannot be changed. But if the From Date value is NOT given, then Truncate value defaults to Yes and it truncates the IEX_DLN_UWQ_SUMMARY table even though it's processing for single operating unit.
The IEX: Populate UWQ Summary Tables concurrent program is submitted only once. The summary program loops for each default collections definition level specified in the Operational Setup. The UWQ summary data is populated for each party based on Collections level only one node at a time. The Collections Definition levels enables the UWQ nodes automatically.
Generate Territory Packages
IEX: Territory Assignment: defaults to the Multiple Collections level as defined and configured by the Collection Administrator to assign collectors at multiple Collections levels.
Run this program as needed to assign collectors based on collections usage.
You can run the following administrative concurrent programs periodically for system maintenance:
IEX: Clear Delinquency Buffers Table: Run this program to clear the buffer tables used in scoring. Run it only if the scoring concurrent program stops before completing. Do not run this program while any other programs are running.
IEX: Create Dunning and Broken Promise Call Backs This program reviews dunning plans and promises and creates all necessary callback tasks in the Task node on the Collector's Work Queue for delinquent customers. Run this program daily.
IEX: Purge Score History Table: This program purges historical data stored in the IEX_SCORE_HISTORIES table. Run this after scoring if you do not want to save historical scoring data. Clearing the table improves performance and does not affect information available to collectors.
If you maintain score history, run this program infrequently, such as weekly or monthly, to reduce the amount of data stored.
Parameters
Truncate all data: Set to Yes to clear all data from the table quickly. If set to No then table data is purged row by row. Leave this parameter blank if you want purge data using other parameters.
Score Object ID: Purge data for a single customer.
Score Object Code: Purge data for a single object, such as party or transaction.
Request ID: Purge data for a specific scoring engine harness concurrent request ID.
Save Last Run: Set to Yes to save only data from the last time the scoring engine harness ran.
Batch Size: Set the size of the purge batches. Recommended value is 100,000 to 200,000.
IEX: Refresh Metric Summary Table: Use this program to update metric information if you run metrics in batch mode.
IEX: Populate UWQ Summary Table Use this program to initialize and maintain customer information in the Collector's Work Queue.
Refresh AR Transactions Summary Table: Use this program to initialize and maintain customer information.