This chapter covers the following topics:
Oracle Common Application Calendar integrates with other Oracle Applications in the E-Business Suite to provide and extend its functionality. Some are mandatory and some are optional. You must set up the mandatory modules before the Common Application Calendar can run. Setting up the optional modules is not required; however, if they are not set up, then the additional functionality provided by these modules is not available.
Many of these modules are included in your general installation. The following list of modules or applications is included with your installation but if you have not licensed the entire suite, you will only have access to the functionalities and tables. In other words, you will not be able to access the user interface (UI) or APIs for the application.
Note: The exception to the previous paragraph is that some UIs are shared. An example of this is in Oracle HRMS which will "share" some of it's Forms if you do not have HRMS set up.
For information on Oracle E-Business Suite Release 12 system requirements and dependencies, consult the Oracle Applications Installing Oracle Applications Release 12 manual.
Oracle Application Object Library (AOL): Notes uses AOL to set necessary profile options and uses the AOL lookups window to create new note types. (Required)
Oracle Application Object Library (AOL): Assignment Manager uses AOL to set application profile options that are used in various modules.
TCF Server: It must be running and correctly configured to connect to Scheduler and for Gantt charts to display information and render properly.
Oraclel Territory Manager: Assignment Manager uses Territory Manager to retrieve qualified resources identified in a territory. (Optional)
Forms-based Calendar: It is used to provide the availability of qualified resources. The Forms-based Calendar provides the work shift information for a resource. (Optional)
Oracle Contracts: Assignment Manager uses Oracle Contracts to retrieve preferred engineers defined in Contract. (Optional)
Installed Base: Assignment Manager uses Installed Based to retrieve preferred engineers defined in Installed Base. (Optional)
Oracle Application Object Library (AOL): Task Manager uses AOL to manage responsibilities and profile options that are used in various modules. (Required)
Oracle Trading Community Architecture: Task Manager uses TCA to locate the customer contact information when creating a task. (Required)
Oracle Workflow: Task Manager uses Oracle Workflow to send workflow notifications in order to notify personnel about task creation and changes. (Required)
Notes: Task Manager uses Notes to create notes attached to a task. (Optional)
Resource Manager: Task Manager queries Resource Manager to determine the owner and assignee of a resource. (Required)
Assignment Manager: Task Manager uses Assignment Manager to assign qualified resources to a task. (Optional)
Escalation Manager: Task Manager uses Escalation Manager to escalate a task. (Optional)
Oracle Application Object Library (AOL): HTML Calendar uses AOL to create FND users (for example, to create a calendar workflow administrator) with appropriate responsibilities, as well as set necessary profile options. (Required)
HTML Tech Stack: Set up properties in Oracle HTML Stack for debug logging trails and cookie encryption. You also specify default roles and responsibilities for users in this module. (Required)
Resource Manager: HTML-based Calendar queries the Resource Manager tables so that individual resources can make and be invited to appointments. (Required)
Oracle Workflow: HTML Calendar uses Oracle Workflow to send workflow notifications in order to notify personnel about calendar changes. (Required)
Tasks: HTML-based Calendar uses the HTML-based Tasks to create repeating appointments. (Required)
Notes: HTML-based Calendar uses the HTML-based Notes to create a note and attach it to an appointment. (Required)
Oracle Application Object Library (AOL): The Forms-based Calendar module uses AOL to manage responsibilities that are used in various modules. (Required)
Task Manager: The Forms-based Calendar module uses Task Manager to create Todo Lists (tasks). (Required)
Resource Manager: The Forms-based Calendar module uses Resource Manager to assign resources to a calendar. (Required
Oracle Application Object Library (AOL): Escalation Manager uses AOL to set necessary profile options that are used in various modules. (Required)
Oracle Workflow: Escalation Manager uses Oracle Workflow to send workflow notifications to relevant resources when an escalation document is created or updated. (Required)
Service Request: Service requests can be manually escalated through Escalation Manager if necessary. (Optional)
Assignment Manager: Escalation Manager queries the escalation territory defined in Oracle Territory Manager through the Assignment Manager UI to determine the owner of an escalation. (Optional)
Task Manager: Forms-based Task Manager is used to attach additional tasks to an escalation document. Tasks created in the Forms version can be manually escalated through Escalation Manager if necessary. (Optional)
Notes: The Forms-based Notes module is used to attach additional notes information to an escalation document. (Optional)
Oracle Application Object Library (AOL): The Business Rule Monitor uses AOL to set necessary profile options that are used in various modules and to create the Business Rule Monitor Workflow Administrator. (Required)
Oracle Workflow: It is used by the seeded workflow processes to send out workflow notifications to relevant document owners. (Required)
Service Request: Service Requests can be monitored and escalated based on your defined business rules. (Optional)
Escalation Manager: It is used by the seeded workflow processes to create an escalated document when a business rule is violated. (Required)
Oracle Territory Manager: It is used to retrieve qualified resources identified in the escalation territories if the identity of a person who receives notifications defined in the Workflow Attributes window cannot be determined. (Optional)
Task Manager: It is used by the seeded workflow processes to create an automated escalation task. This is generated through the seeded Automated Escalation Template Group for Task Manager (Service Request or Oracle Quality Online) defined in the Forms-based Task Manager. Tasks created in the Forms version can also be automatically escalated when a business rule is violated. (Optional)