This appendix covers the following topics:
Oracle Sales and Oracle TeleSales are interoperable if these setup steps are performed:
Leads, Opportunities, Forecast, Sales Category, and Call Center must be set up for use in TeleSales. To do so, log in to Oracle Forms with the TeleSales Administration responsibility. Navigate to the Administration page.
Oracle Sales and Oracle TeleSales each have separate sets of profile options that do not affect the other application. Therefore, when a feature in Oracle TeleSales is dependant on a profile option, setting the TeleSales profile option does not affect Oracle Sales. You must set the corresponding Oracle Sales profile option separately.
Note: Corresponding profile options might have slightly different values. You should choose a value supported by both, if you want the behavior to be the same. Additionally, there might be TeleSales profile options for which there are no corresponding Oracle Sales profile options. You should set these profile options to simulate Oracle Sales behavior, or Oracle Sales should be personalized to simulate TeleSales behavior.
Table Mapping of Oracle TeleSales and Oracle Sales Profile Options provides a mapping of the profiles for Oracle TeleSales and Oracle Sales.
| Oracle TeleSales Profile | Oracle Sales Profile |
|---|---|
| OS: Forecast Sales Credit Type | ASN: Forecast Sales Credit Type |
| OS: Default Opportunity Win Probability | ASN: Default Opportunity Win Probability |
| OS: Default Opportunity Sales Channel | ASN: Default Opportunity Sales Channel |
| OS: Default Opportunity Status | ASN: Default Opportunity Status |
| OS: Default Close Date Days | ASN: Default Close Days Date |
| OS: Default Win/Loss Status | ASN: Default Win/Loss Status |
| OS: Default Status for Leads | ASN: Default Lead Status |
| OS: Opportunity Access Privilege | ASN: Opportunity Access Privilege |
| OS: Customer Access Privilege | ASN: Customer Access Privilege |
| OS: Sales Lead Access Privilege | ASN: Lead Access Privilege |
| OS: Manager Update Access | ASN: Manager Update Access |
| OS: Sales Admin Update Access | ASN: Sales Admin Update Access |
| OS: Default Value for Sales Team Keep Flag | ASN: Default Value for Sales Team Do Not Reassign Flag |
Oracle Sales and Oracle Trading Community Architecture each have separate sets of profile options that do not affect the other application. The profile OSO: Default Country maps to the profile ICX: Territory.
Additionally, some Oracle TeleSales and Leads profile options and lookups must be set to enable interoperation with Oracle Sales. If you do not set these profiles as suggested, you cannot use TeleSales with Oracle Sales.
Table Oracle TeleSales and Leads Profile Options lists Oracle TeleSales and Leads profiles and their suggested values.
| Profile | Value |
|---|---|
| OS: Assign New Lead | No |
| OS: Sales Methodology | Specify a valid value. |
| OS: Sales Lead Default Close Reason | Converted to Opportunity |
| OS: Default Opportunity Sales Stage | Specify a valid value. |
| OS: Lead Link Status | Converted to Opportunity |
| OS: Lead Incubation Channel | <LEAVE BLANK> |
| OS: Activate Sales Interoperability | Yes |
| OS: Lead to Opportunity Move Sales Team | Yes |
| OS: Opportunity Sales Credit Enforce Sales Team Definition | Yes |
| OS: Always Add Creator to Customer Sales Team | Yes |
Table Oracle TeleSales and Oracle Sales Lookups lists the Oracle TeleSales lookups and their corresponding Oracle Sales values.
| Oracle TeleSales Lookup | Oracle Sales Lookup |
|---|---|
| CLOSE_REASON | ASN: Lead Close Reason ASN: Opportunity Close Reason |
| LEAD_CONTACT_ROLE, Opportunity Contact Rank | ASN: Contact Role Type |
| VEHICLE_RESPONSE_CODE | ASN: Vehicle Response Code |
Oracle Sales and Oracle TeleSales provide separate Admin screens that enable administrators to set up each product, and there are additional differences between the two applications in the features and functionality available, as well as differences in the required setup for each. The following areas can require additional setup considerations.
Oracle Sales enables users to designate whether sales methodologies and stages apply to leads, opportunities, or both, while in TeleSales, sales methodologies and stages apply only to opportunities. Therefore, Oracle TeleSales exposes only stages marked as applicable to Opportunities. Existing stages created, including those created through the TeleSales Admin user interface, are treated as applicable to Opportunities only.
Oracle Sales introduces the use of a sales coach, which helps guide a user through a sales methodology stage. Oracle TeleSales does not use this functionality and continues to use Tasks tied to Sales Stages. Oracle Sales users can view the tasks created in Oracle TeleSales. When creating a sales methodology in Oracle TeleSales, the administrator should ensure that the Create tasks for all stages checkbox is not selected. If this check box is selected for a sales methodology whose stages use tasks, and the sales methodology is assigned to an opportunity from Oracle Sales, the tasks are not visible in Oracle TeleSales.
In Oracle TeleSales, the stage is mandatory and the sales methodology is mandatory. In Oracle Sales, they are conditionally mandatory, and if the stage is specified, then the sales methodology becomes mandatory. If the methodology is specified, the sales stage becomes mandatory, only if there is an applicable sales stage. Therefore, Oracle TeleSales requires that at least one stage within each methodology is set up as applicable to an Opportunity.
Oracle TeleSales enables any lead to be converted to an opportunity, regardless of status, while Oracle Sales enables only leads in open status to be converted. Oracle TeleSales enables multiple leads to be converted to the same opportunity by linking these leads to the opportunity, and also enables opportunities to be linked to one or more leads.
When a lead is converted to an opportunity in Oracle Sales, the status is always Converted To Opportunity. When a lead is converted to an opportunity in Oracle TeleSales, the status and close reason are determined by the profile options OS: Lead Link Status and OS: Sales Lead Default Close Reason. Therefore, when Oracle TeleSales and Oracle Sales are interoperating, these profile options should be set to Converted To Opportunity.
If a lead is in a sales stage that is applicable to opportunity, Oracle Sales carries any information entered in the sales coach over to the opportunity. If the lead is converted through Oracle TeleSales, this information is not carried over. If there is no methodology or sales stage designated in the lead, the opportunity in Oracle Sales does not have a methodology or sales stage, whereas Oracle TeleSales uses the methodology and sales stage from the profile options OS: Sales Methodology and OS: Default Opportunity Sales Stage.
In Oracle Sales, the sales team for the lead is carried over to the opportunity, while in Oracle TeleSales, whether or not the sales team is carried over is governed by the profile option OS: Lead to Opportunity Move Sales Team. Therefore, when Oracle Telesales and Oracle Sales are interoperating, this profile option must be set to Yes.
In Oracle TeleSales, when assigning a resource to an opportunity sales team, the user can designate a role and address. Oracle Sales does not support roles and addresses. The sales team is viewable in Oracle Sales.
Oracle Sales automatically adds the logged-in user to the customer sales team. For the logged-on user in Oracle TeleSales to be added to the customer sales team, you must set the profile OS: Always Add Creator to Customer Sales Team to Yes.
Oracle Sales does not support the rolling forecast flag. Opportunities created in Oracle Sales do not have the rolling forecast flag set.
Oracle TeleSales enables users to specify marketing campaigns and offers at either the header and line levels, while Oracle Sales supports only header-level campaigns (not offers). Additionally, in Oracle TeleSales there is a cross validation that ensures that the offer is associated with the selected campaign. If an opportunity with a header-level offer is accessed in Oracle Sales, and the campaign is changed, the offer might no longer be valid. To correct this problem, the user must update the opportunity in Oracle TeleSales.
In Oracle TeleSales, a user with update access can freeze an opportunity, so that it cannot be modified, while in Oracle Sales, a user cannot freeze an opportunity.
Upon closing an opportunity in Oracle TeleSales, the user can enter a key/close competitor and close comment, while in Oracle Sales, this is not an option. For opportunities created in Oracle Sales, the key/close competitor and close comment fields are empty.
In Oracle TeleSales, a user can specify customer budget status for a lead or opportunity. Oracle Sales does not support this information. These fields are blank for leads and opportunities created in Oracle Sales. Oracle Sales supports the budget amount for leads, but not for opportunities.
In Oracle TeleSales, a user can specify an end customer and address. Oracle Sales does not support this data. These fields are blank for opportunities created in Oracle Sales.
In Oracle TeleSales, a user can associate a project to a lead or opportunity or associate a decision time frame with a lead. As Oracle Sales does not support this data, these fields are blank for leads or opportunities created in Oracle Sales.
Oracle TeleSales enables a user to accept or reject leads. This feature is not available in Oracle Sales.
If an Oracle TeleSales user and Oracle Sales user are working on an opportunity at the same time, the application detects the change made by the other person and prevents overwriting. This behavior does not apply to leads, which can be overwritten.
When Oracle Sales is installed, the new Oracle Sales forecasting functionality replaces the existing functionality for Oracle TeleSales. Due to the difference in forecasting functionality between the earlier forecasting version and the new Oracle Sales forecasting, previously-saved product worksheets that have not yet been submitted are end-dated when the Oracle Sales patch is applied.
In Oracle TeleSales, the user can append attachments to tasks, addresses, notes, and relationships. However, these attachments are not available in Oracle Sales. Only attachments for leads, opportunities, customers, and contacts that are added in Oracle Telesales are accessible in Oracle Sales, since Oracle Sales supports attachments in these areas. However, if these attachments are added in any other category apart from the seeded Misc category, they will not be visible in Oracle Sales. Through personalization, you must make them available by adding the category to the Attachment table for the lead, opportunity, customer, or contact. Please refer the Oracle Applications Framework Personalization Guide for information on personalization.
In Oracle Sales, the sales representative and sales manager can access only the commission statement and no other areas of the Oracle Incentive Compensation functionality. In Oracle TeleSales, the telesales agent can access other areas of incentive compensation as well, (for example, Planning, Income Planner, Compensation Plan, and Reports) in addition to the commission statement.
Oracle Sales supports all valid FND currencies. Oracle TeleSales supports only the currencies defined in the Oracle TeleSales lookup type REPORTING_CURRENCY. When selecting values for the REPORTING_CURRENCY lookup, you should select all FND currencies that you are currently using for Oracle Sales.
Account plans and strategic information are captured in Oracle Sales. However, this information is not available in Oracle TeleSales.