This appendix covers the following topics:
The following table lists in alphabetical order the concurrent programs used by Oracle TeleSales. The table includes the following columns from left to right:
Mandatory: Is the program mandatory for the function?
Concurrent Program Name: Name of the concurrent program.
Description: Explains what the concurrent program does.
| Mandatory | Concurrent Program Name or Group | Description |
|---|---|---|
| No | Assign Territory Accesses | This concurrent program assigns new territory access to sales force employees. The program prepares database tables for parallel processing. Set the following profile options to 100000000 or more. OS: Sort Area Size for TAP OS: Hash Area Size for TAP Run this program after completing the setups in Setting Up Territory Management, and after the JTF Concurrent program "Generate Territory Package" has run. Parameters: Run Mode (New/Total) Lead Status: (All/Open/Closed) Previous Request ID for restart mode only. |
| No | Autocreate Opportunity from Sales lead | Creates opportunities from existing sales leads. This program should be run after the Import Sales Leads program. Parameters: Debug Mode Trace Mode |
| No | Calculate Party Totals | Calculates customer order information gathered in Oracle Order Management. It calculates the last ordered date and the lifetime value or a customer. The lifetime value is a sum of all orders in Order Management. |
| Flatten Employee Hierarchy | This concurrent program is meant only to populate data in resource manager internal tables in order to expedite data display in "Organization" link for Employee hierarchy. Schedule: For about 100,000 employees, this program takes about 2-3 minutes to run. It can be scheduled as a nightly process. |
|
| Flatten Group Hierarchy | This program is used to denormalize the Resource Group hierarchy structure into a flat structure for fast and easy data access. Schedule: For about 4000 groups, and average of 10 level hierarchy structure, this program takes about 10-15 minutes. It can be scheduled as a nightly process. |
|
| No | Generate Access Records | This is a child program of Assign Territory Accesses and does not need to be run separately. |
| Generate Keys for Fuzzy Match | This program, available by logging in under the Receivable Manager responsibility, generates the keys for customer records already in the database. This program must be run before you import leads for the first time and anytime you change the lead import system profile options listed above, but you need not run it every time you import leads. The application generates keys for imported leads automatically | |
| No | Generate Self-Service Territories | Generates the physical territories for named account and geographic self-service territories. When it successfully completes, you must also run Synchronize Territory Assignment Rules. |
| No | Generate Territory Details | This request set runs Generate Self-Service Territories and Synchronize Territory Assignment Rules. |
| No | Synchronize Territory Assignment Rules | To build the territory assignment rules. Otherwise, your territories will not reflect the changes and will not work correctly when Assignment Manager assigns resources. Builds the API that returns the winning territories and resources attached to the winning territories, which are defined in territory setup. |
| Initial Build group-members tables for home bin | Should be run initially. Helps to improve the performance of forecast page when displayed in a home page bin. A materialized view called AS_GROUP_MV is created for faster lookup of group name or group member id. | |
| Yes | Initial Build of Forecast Summary Tables | This program builds the materialized view used for forecasting. This program must be run initially before users can forecast. Run after Refresh AS_PERIOD_DAYS, Refresh of AS_PERIOD_RATES, and Refresh of AS_SALES_CREDITS_DENORM. |
| No | Initial Load of Opportunity Log Tables | This program loads data from the opportunity transaction tables AS_LEADS_LOG, AS_LEAD_LINES_ALL, AS_SALES_CREDITS to the corresponding log tables AS_LEADS_LOG, AS_LEAD_LINES_LOG, AS_SALES_CREDITS_LOG if the transaction data does not have log record in the log tables. The following profile options need to be set to "Yes" before submitting the concurrent program: OS: Enable Tracking Opportunity History Data, OS: Enable Tracking Purchase Line History Data, and OS: Enable Tracking Sales Credits History Data. |
| No | Load Interest Types and Codes to Inventory Categories (Load Categories) | This concurrent program creates inventory categories under the inventory category set "Oracle Sales and Marketing" for each combination of interest types and codes. In order to use this concurrent program, the OS: Inventory Category Integration profile value must be set to Yes. |
| No | OTS: Load Sales Lead Interface Table from Flat File | Use this program to import sales leads from the interface. This program must be run before Auto Create Opportunity from Sales Lead. This moves data from the interface table to AS_SALES_LEADS, AS_SALES_LEADS_LINES, and AS_SALES_LEAD_CONTACTS. If you want to import data from a flat file, you must first run OTS: Load Sales Lead, which moves data from the flat file to the interface table. |
| Yes | Periodically Purge ASF_RECORD_VIEW_HISTORY | This table memorizes which records a user has visited. In order to prevent the table from growing too large, the program should be run as least once a week. If you are running on a database whose table space is a problem, run this program daily. |
| Pipeline Movement | This program moves sales teams and sales credits, and updates the opportunity owner when moving the pipeline from one sales representative to another. | |
| Yes | Purge Deleted Lists | This program should be scheduled to run periodically. The time interval between any two schedules for this program should be at least the number of days specified for ASF_LIST_MIN_PURGE_AGE_IN_DAYS profile for maximum effectiveness. The program does not take any parameters. A value of 10 is set for this profile (ASF_LIST_MIN_PURGE_AGE_IN_DAYS) and the concurrent program can be scheduled to run every 14 days if the profile has not been modified. These are suggested values for the profile and for periodically scheduling the concurrent program. They can be altered depending on the number of lists that are created or deleted within a short time period. |
| No | Refresh AS_PERIOD_DAYS table | This program must be run before you can run the Refresh of as_sales_credits_denorm (in complete mode), Initial Build of Opportunity Bins, Refresh Multi-Currency Conversion Rates, and the Build Materialized View for Forecast Main Page. This sequence of programs must be rerun if the GL period definitions are changed. If this program is run, then the following programs must also be run: Refresh of AS_SALES_CREDITS_DENORM (Complete), Refresh of Forecast Summary Tables, Initial build of Opportunity Bins Data |
| Refresh group-members tables for home bin | Should be run whenever there is a change in the sales hierarchy (and if "my home page report" is being used). These programs improve the performance of forecast page when displayed in a home page bin. A materialized view called AS_GROUP_MV is created for faster lookup of group name or group member id. | |
| Refresh Multi-Currency Conversion Rates (AS_PERIOD_RATES) | Refreshes the multi-currency conversion rates in setting multiple currency. These are pre-requisites for this program: Set up currency conversion rates, Set up reporting currencies, Set up period type/ conversion type mappings, Run concurrent program Refresh AS_PERIOD_DAYS table. | |
| Yes | Refresh of as_sales_credits_denorm | Used for opportunity reports and forecasting functionality. This program must be run before user can run opportunity reports and perform forecasting functions. Parameters: Refresh Mode = complete refresh (Use this mode when running for the first time or doing a complete refresh). Incremental Refresh = Run in this mode for an incremental refresh |
| Refresh of Forecast Summary Tables | This program is used to refresh the materialized view used for forecasting. This program should be run periodically. | |
| No | Refresh of Opportunity Status Aging Summary Table | Refreshes the summary data for opportunities that have been created or updated since the last refresh time. This concurrent program was created to extract status log data from AS_LEADS_LOG, calculate the summary data from the log data, and refresh AS_LOG_STATUS_SUMMARY table with the summary data. |
| Setup Checking for Oracle Sales application | This program validates Sales Setups and produces an error log that the system administrator can use to diagnose invalid setups. Parameters: Upgrade - Yes/No |