In this chapter you will learn about the mandatory and conditional dependencies for Oracle Sales Contracts to function properly.
This chapter covers the following topics:
This chapter describes dependencies and implementation considerations that you must be familiar with before implementing Oracle Sales Contracts.
The chapter covers the following topics:
Before proceeding with implementation of Oracle Sales Contracts and its dependencies, you must verify that you have installed Oracle applications correctly. For more information, see Oracle E-Business Suite Installation Guide: Using Rapid Install.
To achieve the entire sales contracts business flow, Oracle Sales Contracts is built on infrastructure provided by various Oracle modules. Mandatory dependencies are required for Oracle Sales Contracts to function properly. Conditional dependencies, when integrated, provide additional capabilities. This section describes mandatory and conditional dependencies for Oracle Sales Contracts.
For all the features to function properly, Oracle Sales Contracts requires installation and implementation of the following modules:
Oracle Order Management: Provides the backbone to author, approve, amend, communicate, and print contracts. For more information, see the Oracle Order Management User's Guide and the Oracle Order Management Implementation Guide.
Oracle Contracts: Provides contract terms library, contract document attachment, and contract terms authoring capabilities. For more information, see the Oracle Contracts Implementation and Administration Guide.
Oracle General Ledger: Enables set up of ledgers and books. For complete setup information, see the Oracle General Ledger User Guide. Set of Books is used as part of the setup for automatic numbering of clauses.
Oracle Human Resources: Provides organization setup information. Define or confirm the definitions of your employees in the Oracle Human Resources Management System.
Oracle Workflow: Provides notifications related to approvals of clauses, templates, and contracts. For more information see the Oracle Workflow Administrator's Guide.
Oracle XML Publisher: Provides information on setting up and using RTF and PDF templates that are used to preview and print contracts and contract templates. For more information, see the Oracle XML Publisher Users Guide.
Conditional dependencies include:
Oracle Quoting: Provides the basis to author, manage, and print contracts within the quote life cycle. For more information, see the Oracle Quoting User Guide and Oracle Quoting Implementation Guide.
Oracle iStore Portal: Allows customers and sales personnel to view contract terms and request changes. For more information, see the Oracle iStore Implementation and Administration Guide.
This section describes the implementation considerations specific to Oracle Sales Contracts. Refer to the Oracle Order Management, Oracle Quoting, and Oracle iStore documentations for detailed setup steps for these applications.
This section provides the implementation considerations for:
Specific implementation considerations for using Oracle Order Management are:
Specifying default contract templates: In the Transaction Type window of Order Management, specify a contract template that will be the default template whenever that transaction type is used in a sales agreement. In the Transaction Type window, enter a transaction type where you have entered the Sales Document type as Sales Agreement. The Contracts Template list of values will display all contracts associated with sales agreements. The Layout Template list of values will display all the layout templates in XML Publisher. Select a contract template and a layout template to be associated with the transaction type.
Note: To enable the list of values for the Contract Template and Layout Template, first save the transaction type.
Specifying negotiating flows: In the Transaction Type window, specify the value in the Negotiation Flow as Generic with Approval, and click the Approvals button to enter the list of approvers. The Approvals window enables you to specify the approver names, the sequence in which they will be sent approval notifications, and whether they are currently active in the approval process.
Associating the contract template with the sales document type: In the Contract Terms Library, associate the contract template with the Sales Agreement sales document type.
Specific implementation considerations for Oracle Quoting are:
Using sales contracts: To enable the Sales Contracts functionality in Oracle Quoting, set the profile option OKC: Enable Sales Contracts to Yes.
Using Contract Expert rules: To use Contract Expert rules, set the ASO: Category Set profile option to Inventory Items at the site level.
Specifying layout templates: The system determines the layout of the contract based on the layout template defined for the specific transaction type. In Oracle Quoting, the layout template for a quote is derived from the ASO: Default Layout Template profile option.
Printing quotes: To print quotes containing contract terms, you must use the Oracle XML Publisher printing option.
Specifying default contract templates: Setup the default contract template by specifying an Operating Unit specific quoting parameter. You can set the parameter value by performing the following steps:
Access the HRMS Management responsibility. Navigate to HRMS Manager: Work Structures : Organization and click Description.
Enter the name of OU and click the Find button.
In the Organization Classifications section, place your cursor in the field for that OU.
Click the Others button.
Select the quoting parameters and click the OK button.
Select the quoting parameters. Enter OU in the operating unit field or click on parameters to display parameter selection.
Specific implementation considerations for Oracle iStore are:
Using sales contracts: To enable the Sales Contracts functionality, set the profile option OKC: Enable Sales Contracts to Yes.
Using Contract Expert rules: To use Contract Expert rules, set the ASO: Category Set profile option to Inventory Items at the site level.
Specifying layout templates: The system determines the layout of the contract based on the layout template defined for the specific transaction type. In Oracle iStore, the layout template is derived from the ASO: Default Layout Template profile option.
Printing quotes: To print quotes containing contract terms, you must use the Oracle XML Publisher printing option. Therefore, it is mandatory that you set the profile option ASO: Print Quote Method to XML Publisher at the Site level.
Specifying default contract templates: Set up the ASO: Default Contract Template profile option that determines the default contract template for standard contract terms.