This appendix covers the following topics:
The procedure for setting up and changing system profile options is the same for all Oracle applications. For a detailed description of the procedures, refer to the Oracle E-Business Suite Setup Guide.
Navigation: To change profile options, log into Oracle Forms as a System Administrator, and navigate to Profile > System.
Notes
Site (S): This field displays the current value, if set, for all users at the installation site.
Application (A): This field displays the current value, if set, for all users working under responsibilities owned by the application identified in the Find Profile Values block.
Responsibility (R): This field displays the current value, if set, for all users working under the responsibility identified in the Find Profile Values block.
User (U): This field displays the current value, if set, for the application user identified in the Find Profile Values block.
The system profile options used by Oracle Leads Management has the following prefixes:
OS: Oracle Sales
OSO: Oracle Field Sales
PV: Oracle Partner Management
OTS: Oracle TeleSales
The following tables list the system profiles used by Oracle Leads Management by category name and in alphabetical order . The tables include the following columns from left to right:
Req? (Required): "Y" in this column indicates the profile is required for the applications or functions.
New? - "Y" in this column indicates that the profile is new.
Profile Name: Name of the profile.
Description: Explains what the profile does.
Program: Lists the functional areas affected by the profile.
Level: Level at which this profile option can be set. A = Application, S = Site, R = Responsibility, U = User.
Default: Lists the default value for the profile, if any.
The following table lists the default profiles in Oracle Leads Management.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| Y | N | OS: Sales Lead Default Close Reason | The Update Sales Lead API assigns statuses to leads based on the value in the OS: Lead Link Status profile. If the status in the profile is 'Closed', the API picks up the value in this profile. |
Leads | S | - |
| N | N | OS: Default Decision Timeframe for Leads | If the lead record does not have a timeframe value, the value in this profile is set. If this profile is not set, a NULL value is inserted. | Leads | S, R , U | Within 1 week |
| N | N | OS: Default Lead Contact Role | Used for defaulting the contact role on the contact page. | Leads | S,R,U, A | END_USER |
| Y | N | OS: Default Status for Leads | Used as the default status for a lead in the UI and API. If not set, then a NULL value is inserted, and an error notification is displayed. | Leads | S, R, U | New |
| N | N | OS: Default Vehicle Response Code for Leads | Used as the default value in the UI and API. If not set, then a NULL value is inserted in the database. | Leads | S, R, U | User |
| Y | N | OSO: Default Country | Used for defaulting the country selected on the Create Lead page. If not set, the first country in the drop-down list will be chosen by default. | Leads | S, R, A, U | United States |
| N | N | OSO: Default Lead Contact Title | Sets the title for the lead contact. For example, Mr., Ms., and so on. | Leads | S,A,R, U | Ms. |
The following table lists the profiles related to Lead Import.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| Y | N | HZ: Execute API Callouts | Turn on/off business event when TCA entities are modified. Turn off this profile before you run the Import Sales Lead concurrent program. After running the program you must turn the profile on. Turn off this profile before you run the Import Sales Lead concurrent program. After running the program you must turn the profile on. For more information, see Implementation in the Trading Community Architecture Administration Guide and Business Events in the Trading Community Architecture Technical Implementation Guide. |
Import Sales Leads | A, S, R, U | - |
| Y | N | OS: Use DQM Rule code to match Party | Used during Lead Import. The rule associated with this profile decides whether the imported record is a duplicate by checking for a matching Party in the TCA database. | DQM | A, S, R, U | - |
| Y | N | OS: Use DQM Rule code to match Party Site | Used during Lead Import. The rule associated with this profile decides whether the imported record is a duplicate by checking for a matching Party Site in the TCA database. | DQM | A, S, R, U | - |
| Y | N | OS: Use DQM Rule code to match Contact | Used during Lead Import. The rule associated with this profile decides whether the imported record is a duplicate by checking for a matching Contact in the TCA database. | DQM | A,S,R, U | - |
| Y | N | OS: Use DQM Rule code to match Person | Used during Lead Import. The rule associated with this profile decides whether the imported record is a duplicate by checking for a matching Person in the TCA database. | DQM | A,S,R, U | - |
| Y | Y | OS: Activate inactive parties from lead import | Activate inactive parties returned from lead import | DQM | S | Yes |
| Y | Y | OS: Execute Custom Code from Lead Import | Controls the execution of the custom user hook from the Import Sales Lead concurrent program. | Lead | S | Yes |
| Y | N | OM: Item Validation Organization | Manufacturing organization items are validated. This profile is used to set the AS_SALES_LEAD_LINES.organization_id. | Lead | S, R | - |
| Y | Y | OS: Minimum Number of Records for Parallel Processing in Lead Import | Determines the number of child processes to be spawned by the Import Sales Lead concurrent program during parallel lead import. | Lead | S | 400 |
The following table lists the profiles related to the Interaction Matching Engine.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| N | Y | OS: Default Source for Interaction Matching Engine if Interaction does not have Source Code | Source promotion is not mandatory for Interaction. The default value is used when no promotion is specified. | Interaction | S | - |
| Y | Y | OS: Look Back Period in Days for Interactions when Interaction Matching Engine is run for the first time | The Interaction Matching Engine looks for interactions created for the past n days. The value in this profile is used when the engine is run for the very first time. | Interaction | S | 30 |
| Y | Y | OS: Look Back Period in Days for Leads in Interaction Matching Engine | The Interaction Matching Engine looks for leads created during the past n days. If not specified, the number of days is used from this profile. | Interaction | S | 30 |
| Y | Y | OS: Last Interaction ID processed in Interaction Matching Engine | This profile will be invisible and cannot be updated by users. The Interaction Matching Engine updates this profile to denote which interaction ID was the last interaction processed. If the value of this profile is 0, the interactions logged in the last n days as defined by the above profile are processed. | Interaction | S | 0 |
| Y | Y | OS: Default Interaction Score in Interaction Matching Engine | If the interaction does not have any business type matched in the rule, the default score from this profile is used. | Interaction | S | 1 |
| Y | Y | OS: Interaction Score Threshold | When the Import Sales Lead concurrent program processes records in the as_import_interface table, the value from this profile is used as the threshold for creating lead. If the interaction score is less than this value, a lead is not created. | Interaction | S | 20 |
| Y | Y | OS: Interaction Matching Engine matches contact for B2B lead | If set to Y, the Interaction Matching Engine matches primary contacts for B2B leads. If set to N, primary contacts are ignored. | Interaction | S | Y |
The following table lists the profiles related to the Leads Rule Engines.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| Y | Y | OS: Default Qualified Flag for Lead Qualification Engine | When none of the Qualification rule sets match the lead, the default qualification flag is based on this profile. | Leads | S | No |
| Y | Y | OS: Enable Rule Engine Log | If set to 'Y', details about every rule engine run are logged into the pv_entity_rules_applied table. | Leads | S | Y |
| Y | Y | PV: Run lead deduplication rule | This profile controls the execution of the Lead Deduplication rule. If set to 'No', then lead deduplication will not be performed during lead import. | Lead Import | S | Y |
| Y | Y | OS: Execute custom code from lead import | This profile controls the invocation of custom user hook that can be executed for each record in a lead import batch. If the profile value is set to 'No', the custom code will not be executed. | Lead Import | S | Y |
| Y | Y | OS: Escalation Manager for Leads | Set this profile when there is one resource to act as an escalation manager. During the process of assigning a lead to a sales representative, if the maximum number of re-routes are reached, an e-mail is sent to the escalation manager. | Lead Assignment | S | - |
| Y | N | OS: Run Lead Monitor Engine | If set to Y, the lead is processed by the monitoring engine after it is created/updated. | Monitoring Engine | S | Y |
| Y | N | OS: Maximum Reroutes per leads | The number assigned to this profile defines the maximum number of reroutes allowed to a lead that is timed out by the monitoring engine or during automatic assignment. | Leads | S | 3 |
| N | N | OS: Lead View Scorecard data | Set to Y to view the old Score Card Mapping and rank data. | Leads | A,S,R, U | N |
| N | OS: Default Channel for Lead Channel Selection Engine | This sets the default channel for each lead if no channel selection rule sets evaluate to true. | Leads | S | Direct | |
| Y | N | OS: Default Rank for Lead Rating Engine | This sets the default if no rating rule sets evaluate to true. | Leads | S | Cold Lead |
| N | N | OS: Partners Enabled for Leads | If set to Yes, the Preferred Partner LOV in the Lead Details page is displayed. This is useful when the Channel of the lead is Indirect and is routed to a Partner. | Leads | S,A,R, U | No |
The following table lists the profiles related to the assignment of leads.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| N | N | OS: Assign New Lead | if this profile is set to No, then the application uses the Territory Manager to automatically assign resources to the lead. The first person the Territory Manager assigns becomes the owner. The rest of the resources in the territory become sales team members on the lead. If this profile is set to Yes, then the agent must enter the owner manually using the Owner LOV. If the agent does not make an entry, then the lead is assigned to the default user set in OS: Default Resource ID Used for Sales Leads. If no default resource is set, then application assigns ownership to the user updating or importing the lead. Note: If both the resource in this profile and the user who created or updated the lead do not have a valid sales role assigned to them, then the leads you import will not be accessible from either Oracle Sales Online or Oracle TeleSales. |
Leads | S | No |
| N | N | OS: Calendar setting required for assignment | The calendar setting for assigning an owner to a lead. If set to Yes, then the routing APIs check the availability of the resource in JTF Calendar before assigning the lead owner. | Leads | S | N |
| Y | N | OS: Default Lead Marketing Owner | The immature lead owner assignment API will use the default marketing lead owner if a owner cannot be found in the owner table. | Leads | S | - |
| Y | N | OS: Sales Team Creator Keep Flag | Used for defaulting the keep flag in the lead sales team page. | Leads | S,A,R, U | Yes |
| N | N | OS: Default Resource ID Used for Sales Lead Assignment | If the owner of a lead declines the lead, the owner will be the next available resource defined in territory. If all the resources are used up, the lead owner will be the one defined in this profile. The original lead owner, if not defined in territory, will be removed from the sales team. If this profile is not set, the ownership of any unassigned lead is automatically assigned to the user who is currently logged in to the application. |
Territories | S | - |
| N | N | OS: Lead Assignment User Hook | Used by the Sales Online Territory Assignment concurrent program. The program uses the value in this profile to identify if the user hook is enabled. | Territories | S,A,R, U | No |
The following table lists the profiles related to the follow-up of leads.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| N | N | OS: Lead New State Transition | If set to Y, the new state transitioning logic controls the transition of a lead state from one status to another, based on common business logic. If you do not want any additional restrictions, set this profile to N. | Leads | S | Y |
| Y | N | OS: Auto Run Lead Engines While Update | If set to Y, the lead engines are run automatically while updating a lead. If set to N, then the lead is processed manually. However, you can click Run Engines to process the lead via the lead engines. | Leads | S | Y |
| Y | N | OS: Address Required for Person | If set to Y, the Lead Contact page in Oracle Sales Online displays the Create Person button. The person or contact has to be created by clicking this button and entering address information on the Create Person page. If set to N, you can enter contact information in empty rows. | Leads | S | 'N |
| N | N | OS: Address Required for Sales Lead | Makes address entry mandatory for leads. If set to Y, then the address is required. The API gives users an error if the address is required but not present in the record. | Leads | S | No |
| N | N | OS: Default Budget Status for Leads | The value in this profile will be the default value in the UI and API. If not set, this profile inserts a NULL value in the database table. | Leads | S, R, U | Pending |
| N | N | OS: Source Code Mandatory for Leads | Used to make the Campaign Source Code entry mandatory for leads. A Yes setting causes an error to appear if a user tries to save a lead without a source code. | Leads | S | No |
| N | N | OS: Customer Address Required for Customer, Opportunity and Lead | Indicates whether customer address is required for a customer. | Leads | S | No |
| Y | N | OS: Auto-relate Lead note to Customer | While creating a note, this profile is used to automatically relate the note to the customer. | Leads | S,A,R, U | Yes |
| Y | N | OS: Auto-relate Lead note to Primary Contact | While creating a note, this profile is used to automatically relate the note to the primary contact. | Leads | S,A,R, U | No |
| Y | N | OS: Auto-relate Lead task to Customer | While creating a task, this profile option is used to automatically relate the task to the customer. | Leads | S,A,R, U | Yes |
| Y | N | OS: Auto-relate Lead task to Primary Contact | While creating a task, this profile option is used to automatically relate the task to the primary contact. | Leads | S,A,R, U | No |
The following table lists the profiles related to the conversion of leads.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| N | N | OS: Auto Convert Lead to Opportunity | If a channel is defined as INDIRECT in the Channel Setup page, and this profile is set to 'Yes', an opportunity is created for the lead, and the partner matching workflow is started. | Leads | S | Yes |
| N | OS: Lead Incubation Channel | Immature lead owner assignment will be used if the sales channel in this profile matches the channel assigned by the Channel Selection Engine. | Leads | S | - | |
| Y | N | OS: Lead Link Status | The value in this profile is used to set the status of the lead after linking the lead to an opportunity. | Leads | S | Converted to Opportunity |
| Y | N | OS: Lead to Opportunity Move Sales Team | When converting a lead to an opportunity, you can govern whether all the sales team members are copied to the opportunity sales team by setting this profile. If set to Yes, all sales team members are copied to the new opportunity. If set to No, the sales team is limited to the sales representative who converted the lead, plus those sales representatives who are included as per the Territory Manager settings. The Keep flag is copied as is, and the Owner flag is copied as No. | Leads | S | No |
The following table lists the profiles related to Lead Security.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| Y | N | OS: Customer Access Privilege | This profile determines who can view or update customer data. | Leads | S,R,U | Full |
| Y | N | OS: Manager Update Access | If a manager has subordinates in the sales team, the manager's view or update privileges will be determined by this profile. | Leads | S,R,U | View data |
| Y | N | OS: Opportunity Access Privilege | This profile determines who can view or update opportunity data. | Leads | S,R,U | Global Full |
| N | N | OS: Privilege to Change Lead Owner | If set to Yes, you can change the owner of a lead to which you have Update access. Users who do not have this privilege can change the owner of only those leads that they own. This profile is used to allow the user to change lead owner even if the user is not the current owner for lead. | Leads | S, R, U | No |
| Y | N | OS: Sales Admin Update Access | This profile determines whether an administrator can view or update data. | Leads | S,R,U | View data |
| Y | N | OS: Sales Lead Access Privilege | This profile determines who can view or update lead data. | Leads | S, R , U | Full |
| Y | N | OS: Create Organization Privilege | If set to Yes, the Create Organization button is displayed on the Create page. | Leads | S,R,U | Yes |
| Y | N | OS: Create Person Privilege | If set to Y, the Create Person button is displayed on the Create page. | Leads | S,R,U | Yes |
The following table lists leads profiles in Oracle TeleSales (OTS).
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| Y | N | OTS: Default Country | Used for Lead Center in OTS. | TeleSales | S,A,R, U | US |
| Y | N | OTS: Default Party Type | Used to default the party type in Lead Center. | TeleSales | S,A,R, U | PARTY_ RELATI ONSHIP |
| Y | N | OTS: Default Tab in Sales Lead Center | Default tab in Lead Center. | TeleSales | S,A,R, U | AST_SL C_PUR |
| Y | N | OTS: Default Universal Search Tab | Default Universal Search tab. | TeleSales | S,A,R, U | QUICK SEARCH |
| Y | N | OTS: Default Universal Search Type | Default Universal Search type. | TeleSales | S,A,R, U | PARTY_ RELATI ONSHIP |
| Y | N | OTS: Interactions- Enable Automatic Start | Used to automatically start interactions. | TeleSales | S,A,R, U | N |
| Y | N | OTS: Show Campaign and Offer Names instead of Codes | If set to Y,, Campaign Name is shown in the UI instead of Source Name. | TeleSales | S,A,R, U | N |
| N | N | OTS: Default User Role | Used to decide what the user's default role must be when the user logs in. | TeleSales | S,A,R, U | - |
| N | N | OTS: Default User Sales Group | Used to decide what the user's default sales group must be when the user logs in. | TeleSales | S,A,R, U | - |
| N | N | OTS: Minimum Number of Characters for Lookup | Minimum characters for long LOV lookup. | TeleSales | S,A,R, U | - |
| Y | N | OTS: Validation Level for Sales Leads | If the value in the OS: Lead New State Transition is Yes, then the status of a lead that is converted to opportunity should not be updateable. In order to achieve this in the Universal Work Queue (UWQ), set this profile to 90. This ensures consistent behavior in the Lead Center, eBusiness Center, and the UWQ. |
TeleSales | S | 90 |
| Y | N | OTS: Default Tab in Sales Lead Center | Determines which tab is active when the Oracle Telesales Lead Center is launched. | TeleSales | S,A,R, U | AST_SLC_PUR |
| Y | N | OTS: Interactions-Generate Lead Activity | Yes: Tracks activities related to leads. No: Disables tracking of activities related to leads. The default is set at the system level. Option can be set at system, application, responsibility, and user levels. If the default value for the profile option is removed, then the application functions as if the value is No. |
TeleSales | S,A,R, U | No |
| Y | N | OTS: Number of Days Prior to View | Sets the default value of days for leads and opportunities | TeleSales | S,A,R, U | - |
| Y | N | OTS: Use Primary Address to Create Lead in UWQ | Set to Yes to use the primary address when creating a lead. | TeleSales | S,A,R, U | - |
| Y | N | OTS: UWQ - auto launch lead and oppty center | Set to Yes to open Lead Center and Opportunity Center when a new lead or opportunity is created in UWQ. | TeleSales | S,A,R, U | - |
The following table lists profiles related to leads that enable calculations in multiple currencies.
| Req.? | New | Profile Option | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| Y | N | OS: Forecast Calendar | The name of the calendar you are using to manage your forecasts. Used to get the period set name used in the as_period_rates table. | Calendar | S | - |
| Y | N | OS: Daily Conversion Type | Daily conversion type for currency conversion. Used in the amount calculation. | Currency | V | Corporate |
| Y | N | OS: Date Mapping Type | Used to get the pseudo period rate from the start or end of the period. | Currency | S | S |
| Y | N | OS: Maximum Roll Days for Converting Amount | Maximum Roll Days for converting amount if a conversion rate does not exist for a day. Used to get maximum rollup days for currency conversion. | Currency | S | - |
| Y | Y | OS: Default Period Type for Currency Conversion | Default period type for currency conversion. | Currency | S | - |
The following table lists the obsolete profiles.
| Req.? | New? | Profile Name | Description | Program | Level | Default |
|---|---|---|---|---|---|---|
| N | N | OS: Auto assign from lead import | - | - | - | - |
| N | N | OS: Auto ranking from lead import | - | - | - | - |
| N | N | OS: Auto Qualify Lead | Turns automatic qualification for sales leads on or off. A setting of Yes, causes the application to attempt to qualify a lead when the Qualified check box is null. A setting of No means the user must qualify the lead manually by selecting the Qualified check box. If this profile is not set, it is defaulted to 'N'. | - | S | Yes |
| N | N | OS: Budget status required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a budget status to qualify the lead. If the profile option value is No, then lead qualification does not depend budget status entry. | - | S | Yes |
| N | N | OS: Campaign code required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a campaign code to qualify the lead. If the profile option value is No, then lead qualification does not depend on the campaign code. | - | S | Yes |
| N | N | OS: Contact phone required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a contact phone to qualify the lead. If the profile option value is No, then lead qualification does not depend on the contact phone. | - | S | Yes |
| N | N | OS: Contact role required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a contact role to qualify the lead. If the profile option value is No, then lead qualification does not depend on the contact role. | - | S | Yes |
| NOT USED | N | OS: Dead Lead Status | - | - | S | Dead Lead |
| N | N | OS: Decision time frame required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a decision time frame to qualify the lead. If the profile option value is No, then lead qualification does not depend on the decision time frame. | - | S | Yes |
| Y | N | OS: Default Channel for Leads | Used for defaulting value in UI and also in API. If not set, then the application inserts a null value and notifies the user of an error. | - | S, R , U | Direct |
| n/a | N | OS: Default Lead Scorecard | Scorecard to be used for lead ranking. If not set, the scoring engine will not function. While creating leads, the UI retrieves this value and passes it to the scoring APIs. | - | SRA | 1 |
| Y | N | OS: Lead Routing Status | When the routing engine finds a sales lead owner, then the sales lead status is reset to this profile | - | S | New |
| N | N | OS: Project name required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a project name to qualify the lead. If the profile option value is No, then lead qualification does not depend project name. | - | S | Yes |
| N | N | OS: Rank Lead | The Rating Engine is run when this is set to SYSTEM, if the Rank ID is null. | - | S | System |
| N | OS: Run New Lead Qualification, Rating, Channel Selection Engines | If set to Y, the lead is processed by the Leads Rules Engine. If set to N, qualification and ranking engines qualify and rank the lead based on profiles. | - | S | Y | |
| N | N | OS: Sales channel required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a sales channel to qualify the lead. If the profile option value is No, then lead qualification does not depend on sales channel entry. | - | S | Yes |
| N | N | OS: Total budget amount required | Used by auto qualification process in leads API. If value is Yes, then the user must enter a total budget amount to qualify the lead. If the profile option value is No, then lead qualification does not depend on the total budget amount. | - | S | Yes |