Release 12.1
Part Number E13407-04
Contents
Previous
Next
| Oracle Common Application Calendar User Guide Release 12.1 Part Number E13407-04 | Contents | Previous | Next |
This chapter covers the following topics:
Calendar Synchronization provides the ability to synchronize contacts, tasks, and appointments between the Oracle enterprise database and either Pocket PC or desktop Microsoft Outlook. Calendar Synchronization is used by Oracle Sales for Handhelds. For complete implementation instructions and user information for Oracle Sales for Handhelds, see the Oracle Sales for Handhelds Implementation Guide and the Oracle Sales For Handhelds User Guide.
Users can use Oracle Sales synchronization to synchronize information between laptop, desktop, or Pocket PC devices and the eBusiness Suite. Oracle Sales Synchronization can be used to synchronize:
Appointments
Tasks
Contacts
E-mail interactions (Desktop only)
Synchronization functionality is provided specifically for:
Pocket PC devices running Windows Mobile 2003 or Windows Mobile 5.0
Palm devices running Windows Mobile 5.0
Laptops or desktops with Windows 2000 or Windows XP operating systems running Outlook 2000, Outlook 2002 (XP), Outlook 2003
To use the synchronization with Oracle Sales you need to install the client on your Pocket PC.
Prerequisites
Steps
Open Internet Explorer on your handheld device.
Go to the URL for Applications login for your environment.
Enter your username and password. You are taken directly to Oracle Sales.
Select Pocket Outlook Client Download from the menu.
Click the link for Step 1 in the browser page.
In the Download window, deselect Open File After Download. Download the file.
In the browser page, select the link in Step 2.
In the Download window, leave Open File After Download selected. Download the file.
The client loads and installs automatically in your Pocket PC.
When the server version of the synchronization software is upgraded to a new version, (for example, from version 1.0 to 2.0) all users need to download the new version in order to remain compatible with the server and be able to perform synchronizations. Changes in build number do not cause incompatibility.
Download the client to be able to synchronize appointments, tasks, and contacts between Microsoft Outlook on your desktop and Oracle Sales.
To initialize custom category
If you have your own custom category added to the Master Category List, then proceed with the installation steps. If you do not have your own custom category added to the Master Category List, then you need to create one and remove it using the following steps.
In Outlook select Edit > Categories from the menu .
Click Master Category List.
Add a new Category called Outlook Category.
Click Add.
Click OK.
Click Master Category List.
Select Outlook Category from the list.
Click Delete.
Click OK.
Click OK.
Installation Steps
Login to Oracle Applications and select your Sales User responsibility.
On the Dashboard, go to Preferences > Outlook Synchronization > Client Download.
Follow the instructions on the page.
Your Outlook toolbar includes "Oracle Sales Synchronization" which launches the synchronization program.
If you see a security permission message while synchronizing, answer Yes to continue the synchronization.
When the server version of the synchronization software is upgraded to a new version, (for example, from version 1.0 to 2.0) all users need to download the new version in order to remain compatible with the server and be able to perform synchronizations. Changes in build number do not cause incompatibility.
A situation can occur where you update information for an appointment, contact, or task in Outlook, and also someone else updates the same record either directly on the server or also by synchronizing with the server. If the updated field was blank on either the client or the server, then no conflict occurs. If both users updated the same field with the same value, then there is no conflict.
However, if you update a field for an appointment, contact, or task in Outlook, but someone else also updated the same field with a different value on the server since your last synchronization, then there is a conflict.
The following table shows what happens when fields are updated for the same record, and where conflict occurs.
| Field | Server | Client | Synchronized |
|---|---|---|---|
| Name | Sandy Johnson | Sandy Johnson | Sandy Johnson |
| Organization | Business World | Business World | Business World |
| Phone Number | 650-607-6062 | 650-607-5000 | CONFLICT |
| Fax Number | 650-607-6000 | 650-607-6000 | |
| Email Address | sjohnson@bworld.com | sjohnson@bworld.com |
How conflicts are resolved is determined by your settings in Outlook Synchronization: Preferences. Your choices are:
Server Wins - Duplicate Data: The appointment, task, or contact in your Oracle category used for synchronization is replaced by the object on the server. Your updated object is moved to an Oracle Conflicts category on the client. You can then compare the two as a reminder of what you changed when you updated the object, make the same edits to the object in the Oracle category, and synchronize again. Your client and the server now reflect both changes to the appointment, task, or contact. Your log notes the fact.
This is the default setting.
Server Wins - Replace Client Data: Your information is automatically replaced with the information from the server. Your log notes the fact.
Client Wins - Replace Server Data: The information on the server is automatically replaced with your client data. Your log notes the fact.
Synchronize whenever you want to update information between your Pocket PC and the enterprise database. Review the business flows for examples of what happens with different types of information during synchronization.
Steps
Start menu > Programs > Oracle Sales Synchronization.
Your user name is defaulted. Enter your password.
Perform the synchronization.
Review the log if you see any warning messages to find out what information did not synchronize and why.
If your synchronization preferences are set to Server Wins - Duplicate Data on Client, then go to the Oracle Conflicts category. If one of your objects had a conflict, then your client version was moved to the Oracle Conflicts category and the live version was updated from the server. You need to again update the object and synchronize again for your changes to take place on the server.
If information on the enterprise server was updated since your last synchronization, then the conflict resolution depends upon your synchronization preference settings.
Use Advanced > Full Synchronization only if something is not working right on your Pocket PC. If your synchronization fails or you stop it before completing, then you need to run a full synchronization. Full Synchronization replaces all enterprise data on your Pocket PC with data from the enterprise database.
Synchronize whenever you want to update information between your Desktop Outlook and the enterprise database. Review the business flows for examples of what happens with different types of information during synchronization.
Steps
Outlook Toolbar > Oracle Sales Synchronization
Your user name is defaulted. Enter your password.
Perform the synchronization.
Review the log if you see any warning messages to find out what information did not synchronize and why.
If your synchronization preferences are set to Server Wins - Duplicate Data, then view the Oracle Conflicts category in Outlook. If one of your objects had a conflict, then your client copy was moved to the Oracle Conflicts category and the live version was updated from the server. You need to again update the object and synchronize again for your changes to take place on the server.
If information on the enterprise server was updated since your last synchronization, then the conflict resolution depends upon your synchronization preference settings.
Use Options > Advanced > Full Synchronization only if something is not working right. If your synchronization fails or you stop it before completing, then you need to run a full synchronization. Full Synchronization replaces all enterprise data in Outlook with data from the enterprise database.
Scenario
As a Sales User, sales representative Jerry Weinberg logs into Oracle Sales to prepare his list of contacts for his trip next week.
Jerry navigates to Preferences > Outlook Synchronization > Contacts and reviews his current list of contacts to synchronize. He removes the contacts he doesn't need for the trip. Then he searches and adds the contacts he will be visiting as well as those he may speak to by phone during the week. Only address information that is selected as the Identifying address will synchronize.
While Jerry is meeting with Tom Watkins at Business World, Tom mentions that his title has changed to VP. Jerry updates his Pocket PC with the new job title.
Jerry synchronizes and checks his log. There is an error for his change to Tom Watkins contact information because today someone else changed the fax number for the same contact. His change is replaced with the one on the server. (His preference is set to Server Wins - Replace Client Data.) Jerry changes the title and synchronizes again.
Tom introduces Jerry to a new contact at Business World, Jack Black. Jack gives him his business card and Jerry adds the contact information into his Pocket PC and assigns him the synchronization category (for example, Oracle Contacts).
Note: This is the only category that should be assigned to the contact. If additional categories are assigned, then the contact will not synchronize.
Jerry synchronizes. During synchronization, new contacts are sent to Oracle Trading Community Architecture and checked for duplicates using Data Quality Management. Jerry checks his log. Jack Black's organization already exists and DQM found no potential duplicates for Jack Black, therefore there is no error in the log and Jack Black is added as a contact in the enterprise.
That evening Jerry opens contact information for Jane Bond in his Pocket PC and in the Notes he selects the link to view contact detail information in Oracle Sales. His browser window opens, and after logging in, he views the associated opportunities and notes on line while making his call.
Jerry determines he doesn't need to call Jane again for six months. He deletes the contact from his Pocket PC. He synchronizes and the contact is removed from his list of contacts to synchronize.
If you change the customer name in your client, then the change will not be applied to the enterprise application data. The next time the record is synchronized, the customer name in the enterprise data will overwrite the value in Outlook.
The resolution of conflicts depends upon your setting in Outlook Synchronization: Preferences.
Related Topics
Oracle Trading Community Architecture User Guide
When you create, update, or delete appointment in Outlook or Pocket PC and then synchronize, your changes are reflected in your Oracle Calendar. Also, Oracle Calendar appointments or invitations appear in your Outlook or Pocket PC.
Notes
Category: Oracle appointments created in Outlook or Pocket PC must be assigned the synchronization category (Oracle Appointments) to make appointment details available in the Oracle Sales Calendar.
Invitation: The word indicates an invitation to an appointment created by someone else. To accept the appointment, remove the word Invite and synchronize.
Personal Appointments: Non-Oracle appointments created in Outlook or Pocket PC appear in the Oracle Calendar as read-only appointments with the notation "This is a Non-Oracle Appointment" followed by the appointment name.
Recurring Personal Appointments: Recurring non-Oracle appointments created in Outlook or Pocket PC create recurring appointments for a maximum of five years in the Oracle Calendar after synchronization.
Time Zone: Appointments and repeating appointments created in Outlook or Pocket PC synchronize time zone information with the server. The time zone is converted to saved in the server time zone. When synchronized, the appointment in Outlook and Pocket PC is converted to the individual user's time zones.
Scenario
Customer Tom Watkins from Business World calls to request a demonstration. He talks to sales agent Jerry Weinberg. Using Oracle Sales, Jerry creates an appointment for Thursday at 2:00, adds attendees, and associates the related opportunity. He also assigns the synchronization category (for example, Oracle Appointments).
Note: This is the only category that should be assigned to the appointment for the appointment details to display in the Oracle Sales Calendar. If a different category is used, then the appointment displays as a Time Booking in the Oracle Sales Calendar after synchronization.
Jerry then synchronizes his Pocket PC. In the calendar, he sees the appointment he created in Oracle Sales and another appointment with the word Invite in the subject line. The appointment was set up by product specialist John Smith for Thursday at 1:00. In the appointment notes, he sees that the appointment is for discussing the upcoming demo. He sees the list of attendees as well as information about the opportunity and Business World.
In his Pocket PC, Jerry removes the word Invite from the subject line to accept John’s appointment.
Jerry then realizes that he has a dentist appointment Thursday at 2:00. In his Pocket PC, he creates a personal appointment from 2:00 to 4:00 on Thursday. He then updates his original demonstration appointment with Tom Watkins to occur on Friday at 10:00.
Jerry then synchronizes his Pocket PC. After synchronization, Jerry’s Oracle Sales calendar shows that he accepted John’s appointment, moved the original demonstration appointment, and has a "Non-Oracle Appointment Dentist."
Friday morning, Jerry synchronizes his Pocket PC to make sure his calendar is up to date with the latest information in Oracle Sales. He wants additional information concerning the 10:00 meeting. In the appointment notes, he sees several links to Oracle Sales.
Jerry taps each link on his Pocket PC causing it to open the web browser. After logging into Oracle Sales, Jerry accesses real-time detailed information about Tom Watkins, Business World, and the opportunity.
The meeting goes well, and Jerry wants to close out the appointment. In his Pocket PC, he taps the Appointment Wrap-Up link in the notes section of the appointment. This opens Oracle Sales in the web browser to a page that allows Jerry to add notes, set up a follow-up task, set up a follow-up appointment, and update the opportunity.
Jerry then synchronizes his Pocket PC. The follow-up appointment and task now appear on his Pocket PC.
Repeating appointments with more than 1 year between appointments do not synchronize from the server.
Appointments can repeat up to 99 weeks on the client.
Outlook does not support more than one repeating appointment in a month.
The resolution of conflicts depends upon your setting in Outlook Synchronization: Preferences.
Scenario
Jerry Weinberg's manager assigns a task to both Jerry and to John Smith to write a report about their visit to Business World. The task is created using Oracle Sales and is associated to the contact at Business World and assigned to John and Jerry.
Jerry and John both synchronize their Pocket PCs in the morning and see their task. Both update the status of the task and add to the description using their remote devices. John synchronizes at 1:00. When Jerry synchronizes at 2:00 his task on his device is updated with John's information and his own updates are placed in the Oracle Conflicts category. He updates the task with his information and synchronizes again.
During a meeting with Tom at Business World, Jerry agrees to have technical specialist Harvey Mathers call Tom. He enters this as a task in his Pocket PC, assigns the synchronization category (for example, Oracle Tasks), and synchronizes.
Note: This is the only category that should be assigned to the task. If additional categories are assigned, then the task will not synchronize.
Back in the office, Jerry goes to the task summary in Oracle Sales using his laptop and associates the task to Tom at Business World and assigns the task to Harvey Mathers. (Associations and assignments cannot be done on the wireless device.)
On the road, Jerry changes the category for a task on his Pocket PC so it is no longer the default category for synchronized tasks (for example, "Oracle Tasks"). He synchronizes, and the task is deleted from Oracle Sales.
Recurring tasks are not supported for synchronizing and will generate an error.
The resolution of conflicts depends upon your setting in Outlook Synchronization: Preferences.
Sales representatives working in a collaborative environment need to be aware of various sales activities. Many interactions with contacts occur using e-mail. You can include e-mails in your synchronization of Desktop Outlook which results in the e-mails being recorded in interaction history and becoming available for viewing in Oracle Sales.
E-mails sent to contacts using Desktop Outlook become available to Oracle Sales users in interaction history, including the contents of the e-mails.
E-mails received from contacts via Desktop Outlook also become viewable interactions in Oracle Sales.
When synchronizing, new contacts are created in the enterprise data and any e-mails with the new contacts become interactions for the new contacts.
If there are duplicate contacts and e-mail addresses in the database, then the interactions are associated with all duplicate contacts.
E-mails for an existing contact with an unrecognized e-mail address are not placed in interaction history. An error message appears in the synchronization log.
To record an e-mail communication with a contact as an interaction
Click the Flag for Interaction icon. It changes to a Flagged for Interaction icon, which when clicked, deselects the e-mail so that it will not be synchronized as an interaction.
While reading an e-mail in Desktop Outlook, click the Flag for Interaction icon in the Add-Ins tab. The icon changes to a Flagged for Interaction icon, which when clicked, deselects the e-mail so that it will not be synchronized as an interaction.
In the Desktop Outlook e-mail list, such as your Inbox, highlight one or more e-mails and click the Flag for Interaction icon in the Add-Ins tab.
If you move an e-mail from one IMAP folder to another, then the first e-mail is marked for deletion and the e-mail in the new folder is a copy. The copy does not include the flag for interaction. The first e-mail will synchronize until it is purged. The e-mail copy must be flagged before it will synchronize as an interaction.
Note: If you are using Microsoft Outlook 2007 version then the Flag for Interaction can be found under the Add-Ins menu item.s
To enable e-mail interactions
There is an option in your Outlook preferences for Oracle Sales Synchronization that enables e-mail interactions being recorded in Interaction History.
If you are using OL2000, then the interaction flag does not update automatically unless you make the following change to the parameter that controls the cache used by Outlook.
Quit Outlook.
Start the Registry Editor (regedt32.exe).
Go to the following key in the registry:
HKEY_LOCAL_MACHINE\software\microsoft\office\9.0\outlook
In the Edit menu, click Add Value and add the following:
Value Name: DontCacheInspectors
Data Type: REG_DWORD
Value: 0x1
Click OK and quit the Registry Editor.
Start Outlook.
Copyright © 2000, 2010, Oracle and/or its affiliates. All rights reserved.