Table of Concurrent Programs

The following table lists by name the concurrent programs used by Oracle Leads Management. 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.

No Assign Territory Accesses This concurrent program assigns new territory access to sales force employees. The program prepares database s for parallel processing.

It requires setting three profile options:

OS: Territory Minimum Number of Records for Parallel Processing OS: Territory Number of Child Processes

OS: Territory Records to Open for Processing Changed Accounts 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/Restart/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 concurrent program. Parameters:

Debug Mode Trace Mode

No Generate Access Records This is a child program of Assign Territory Accesses and does not need to be run separately.

No Generate Territory Packages

This concurrent program, available by logging in under the CRM Administration responsibility, builds the API that returns the winning territories which are defined in territory setup. It must be run at least once before you import leads and each time after you modify the territory setup. You need not run this program every time you import leads.

Yes Initial Build of Opportunity and Lead Bins

Used for the Opportunity and New Leads home page bins and reports. This program must be run initially before users can set up opportunity and new leads bins and reports. This program loads the opportunity and leads materialized view with sales credit

information. A new parameter: Next Extent Size has been added. You can choose the value of the next extent to be allocated for all s and indexes created. Possible values for the parameter are: Small (1M), Medium (5M), Large (10M)

Note: This program must be run anytime the as_sales_credit_denorm is rebuilt or when values such as sales stages and statuses have changed. You should also run when Refresh AS_PERIOD_DAYS is run.

Yes Initial Load for Lead Reports

This program is used to build Leads bins and reports. This should also be run following Refresh of Leads Bins Data so that you can see the latest values in leads reports.

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 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 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 will move data from the flat file to the interface . No Refresh of Leads Bin Data This program is used to run an incremental refresh of the

materialized view used for the Leads bins and reports. This program should be scheduled to run periodically.

No Refresh of Opportunity Bins Data

This program is used to run an incremental refresh of the materialized view used for the opportunity bins and reports. This program should be scheduled to run periodically.

Note: Users will not see opportunities in bins created after the last refresh of Refresh Sales Credit.

No 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

Y Import Sales Leads The lead import concurrent program allows you to import leads into Oracle Sales from other systems. While importing leads, the program also imports data on customers, addresses, and contacts into the customer model (TCA) tables.

Y Workflow Background Process

This program sends notifications and reminders from triggered monitors. The system administrator must schedule it to run everyday, or twice a day, if required.

Y Synchronization program The synchronization concurrent program must be run after every lead import activity. This updates the DQM staging schema with new entries that were created during the lead import.

No DQM Compile All Rules This program must be run when any rules are modified in DQM.

Mandatory

Concurrent Program

Name Description

No DQM Staging Program The DQM Staging Program must be run when DQM is set up for the first time. It creates the staging schema this is vital for existence checking.

The public APIs provided by Oracle Leads Management are described and grouped according to procedures using them.

Sections in this chapter include:

■ Section D.1, "Oracle Leads Management Procedures"

■ Section D.2, "Parameter Specifications"

■ Section D.3, "Type Declarations"

■ Section D.4, "Create Sales Lead"

■ Section D.5, "Update Sales Lead"

■ Section D.6, "Create Sales Lead Lines"

■ Section D.7, "Update Sales Lead Lines"

■ Section D.8, "Delete Sales Lead Lines"

■ Section D.9, "Get Sales Lead Score"

■ Section D.10, "Run Lead Engines"

■ Section D.11, "Build Lead Sales Team"

■ Section D.12, "Rebuild Lead Sales Team"

■ Section D.13, "Start Partner Matching"

■ Section D.14, "Create Sales Lead Contacts"

■ Section D.15, "Update Sales Lead Contacts"

■ Section D.16, "Delete Sales Lead Contacts"