|Oracle Common Application Calendar Implementation Guide|
Part Number E13405-04
This chapter covers the following topics:
The Calendar module adopts the Oracle Applications Framework provides essential Calendar functionality including creating and updating appointments, checking resource availability, and viewing scheduled activities through personal calendar views for integrated applications, such as Oracle Sales.
Think of using the HTML Calendar as a personal productivity tool. Individual resources can use it to define and view personal daily activities and appointments. Users can create appointments, tasks or other calendar events, invite attendees for the appointment, and view scheduled activities through different calendar views.
In addition, the HTML Calendar provides an effective mechanism for users to manage group activities by using group or public calendars. Calendar users can request new group or public calendars and get request approvals from the Calendar Administrator. Once the request has been approved, the requestor of the new group calendar becomes the group calendar owner or Group Calendar Administrator of that group calendar and is responsible for any future approvals of that group calendar subscription requests.
To implement HTML Calendar, implementors can embed the Calendar tab into an existing Oracle E-Business Suite module if necessary. The implementor or system administrator must then create a Calendar Administrator. The Calendar Administrator, typically a workflow administrator or system administrator, creates individual calendar users later and is responsible for approving or rejecting new group and public calendar requests as well as starting and stopping required workflow processes.
To be able to use the full functionality of HTML Calendar, the following components must be set up properly:
HTML Task Manager. Use HTML Task Manager to schedule appointments and tasks, and to create repeating appointments for meetings.
HTML Resource Manager. Use HTML Resource Manager to retrieve individual resources for an appointment.
Oracle Workflow. Use Oracle Workflow to send workflow notifications for processing new group calendar requests and subscription requests to existing group calendars.
HTML Tech Stack. Use HTML Tech Stack to display the HTML functionality.
HTML Calendar also uses Accounts Receivable profile options to set the default client and server time zones for a user.
Use the Forms-based Calendar to enter shifts and exceptions in order to define resource availability and unavailability, as well as to create personal To-Do List and view scheduled activities using Calendar Datebook functionality.
The resource work shift information will be displayed as yellow background in the Gantt chart while using Assignment Manager for resource selection. Telesales applications use the Calendar Datebook functionality to view a resource's availability and assigned tasks.
To implement the Forms-based Calendar, implementors need to define a corporate calendar specifically used for resource scheduling, define resource availability as work shifts, define resource unavailability as exceptions, assign shifts and exceptions to a calendar, and then assign resources to that calendar.
To be able to use the full functionality of the Forms-based Calendar, the following components must be set up properly:
Task Manager (Forms). Use Forms-based Task Manager to create personal Todo List (tasks) and to have tasks displayed in different calendar views. The functionalities of Todo List and calendar views reside in the Calendar Datebook and can be accessed through the Telesales application.
Resource Manager. Use Resource Manager to retrieve a specific resource for different calendar views.
Every employee resource with appropriate responsibilities can use the Calendar functionality to create appointments, view personal calendars, and check resource availability. Make sure that all employees exist in the Resource Manager and the resources are linked to the application login user names (FND_User).
The Oracle Applications Framework based Calendar module uses the following profile options; therefore, implementors or system administrators must set them so that the module can work properly:
ATGCA: Enable Web Mail
ATGCA: Web Mail Server URL
Self Service Accessibility Features
The profile option "Self Service Accessibility Features" is used to turn on the access to the Accessibility Daily View if it is set to either "Screen Reader" or "Yes". If it is set to "No", then users can only access the regular Personal Calendar Daily View page.
The following table describes the profile options that are specific to the HTML Calendar.
|JTF HTML Calendar: Administrator||No default value||Site||The JTF HTML Calendar: Administrator profile option sets the Calendar Administrator who grants approval and subscription requests for group and public calendars.||Set the value to the username of the calendar user who grants group and public calendar requests.|
|Client Timezone||America/Los_Angeles||Site||The Client Time zone profile option is used by Calendar to set the default time zone for the client in the Create Appointment window.||Set the value to the location where your appointments take place.|
Setting the time zone from the profile link in the Calendar UI is another way to set and update this profile value.
|JTF HTML Calendar Task Span Days||No||Site||The JTF HTML Calendar Task Span Days profile option sets tasks that spans over more than one day to appear continuously across days on your personal calendar.||Set the profile option to Yes to have your tasks that span over more than one day to appear continuously across days on your personal calendar. |
If the value is set to No, the task shows as a memo for each day affected.
|JTF_PROFILE_DEFAULT_RESPONSIBILITY||22946||User||The JTF_PROFILE_DEFAULT_RESPONSIBILITY profile option sets the default responsibility when using calendar as a standalone application.||Set the value to correspond to the calendar user. The user value is 22946|
|JTF_PROFILE_DEFAULT_APPLICATION||690||User||The JTF_PROFILE_DEFAULT_APPLICATION profile option sets the default application when using calendar as a standalone application.||Set the value to correspond to the calendar user. The user value is 690.|
|ATGCA: Enable Web Mail||No||User||The "ATGCA: Enable Web Mail" profile option is used to enable or disable web mails sent from an integrated webmail, such as Oracle Collaboration Suite, through the Calendar Availability window.||If it is set to Yes, then you can launch webmails through the Availability window. If it is set to No, then you cannot send webmails, but HTML "mailto:" attribute will be used instead.|
|ATGCA: Web Mail Server URL||N/A||User||The "ATGCA: Web Mail Server URL" profile option is used to specify the URL address for the integrated webmail server.||Set valid server URL for the web mail server in order to send web mails through an integrated web mail, such as Oracle Collaboration Suite, from Availability view.|
|Applications SSO Login Types||Both (Site level)|
Local (user level)
|Site and User levels||The "Application SSO Login Types" profile option is used to allow the Palm and Outlook synchronization to work properly if it is set to "Both" when using the Single Sign-On (SSO) feature.|
It is important to note that if integrated applications decide to implement this Single Sign-on feature and once this profile option is set, it may have an impact on the login at the application level. As a result, the sync feature can also be affected.
|Since any changes to the password stored at the local application level (such as Oracle E-Business Suite) can be passed to Oracle Internet Directory (Single Sign-On server), but not vice versa which means that a user's single sign-on password will not necessarily be synchronized with his local application's password. Therefore, if it is set to Both, then the sync required username and password are stored both at the local application level and the external Oracle Internet Directory. If it is set to SSO, then the sync required login information is stored externally at the SSO Server only and not maintained at the application level. Therefore, the sync feature will not work. If it is set to Local, then the sync required login information is stored at the local application level which means that the login is only allowed through the Oracle E-Business Suite local login.|
Implementors or system administrators need to start the following workflow processes, so that the Oracle Applications Framework and HTML based Calendars can work properly:
CAC Calendar Workflows. Use CAC Calendar Workflow to track and route relevant workflow notifications to an appointment owner when an invitee accepts or rejects an invitation.
CAC Reminders. Use CAC Reminders to pick up appointment reminders for scheduled appointments.
To invoke web mail compose window through an integrated Web Mail, such as Oracle Collaboration Suite, from the calendar Availability view and the task Assignment window while creating or updating tasks, implementors or system administrators need to set up profile options to enable this feature and specify correct server URL. However, if Oracle Collaboration suite is not installed, then this feature will not work and link will open default e-mail client.
Calendar uses the following profile options for Web Mail setup:
ATGCA: Enable Web Mail. This profile uses the following values to indicate whether or not to use web mail:
Yes. It indicates that Web Mail is enabled and you can launch webmails through the Availability window and the task Assignment window.
No (default). It indicates that Web Mail is not enabled and HTML "mailto:" attribute will be used instead. Using "mailto:" attribute will invoke default browser e-mail client, such as Netscape Messenger.
ATGCA: Web Mail Server URL. This profile specifies the URL address for the integrated webmail server. It starts with either "http://" or "https://".
Valid Server URL Address
Use the following URL for the invocation of the Oracle Collaboration Suite Web Mail message compose window from a web page:
Note that machine name is required. Port number is usually not part of the URL, but it can be added if necessary depending on how the Oracle Collaboration Suite is installed.
For example, you can set the URL address as follows:
If profile "ATGCA: Enable Web Mail" is set to Yes, system administrators must identify valid server URL for "ATGCA: Web Mail Server URL" profile. Otherwise, the following conditions will be used:
If "ATGCA: Web Mail Server URL" profile value is missing, it has the same effect as "ATGCA: Enable Web Mail" being No. The default "mailto:" attribute would be used.
If "ATGCA: Web Mail Server URL" profile value is invalid but does start with "http", the default browser error "The page cannot be displayed." will be shown.
If "ATGCA: Web Mail Server URL" profile value is invalid and does not start with "http", an unrecoverable HTML error will occur after clicking the e-mail hyperlink from the availability view.
Perform additional implementation steps on the server side to launch webmails successfully, such as including "jtfCalWebMail.js" in your jsp file, and using appropriate syntax to invoke web mail feature or HTML "mailto:".
Copyright © 2000, 2010, Oracle and/or its affiliates. All rights reserved.