Setting Up Oracle Sales Contracts

This chapter contains all the steps required to use the Oracle Sales Contracts application.

This chapter covers the following topics:

Setting Up Operating Units

To use the Contract Terms Library, you must define operating units in the Oracle Human Resources application. For more information, see the Oracle Human Resources User's Guide. Before you proceed with setting up operating units, using the steps that are provided later, you should identify one global operating unit for your implementation. You must also decide the following for each of the operating units that you want to implement:

Steps

To set up operating units:

  1. Log in to the Human Resources responsibility.

  2. Open the Find Organization window.

    Navigation: Work Structures -> Organization -> Description.

  3. Select the desired operating unit from the list of values.

  4. Click the Find button.

  5. In the Organization Classifications region, place the cursor in the Operating Unit classification.

  6. Click the Others button.

  7. Select the Contract Terms Setup option from the list of values.

  8. In the Contract Terms Setup window, enter values for the following options:

    • Auto Adopt Global Clauses: This enables automatic adoption of global clauses in a local operating unit. The clauses do not have to be approved separately in the local operating unit if the Auto Adopt option is set to Yes.

    • Library Administrator for Sell Intent: Set a library administrator Sell intent to receive notifications when a global clause is created and needs adoption in the local operating unit.

    • Library Approver for Sell Intent: Set a library approver for Sell intent to route workflow approval notifications for clauses and templates.

    • Library Administrator for Buy Intent: Set a library administrator Buy intent to receive notifications when a global clause is created and needs adoption in the local operating unit.

    • Library Approver for Buy Intent: Set a library approver for Buy intent to route workflow approval notifications for clauses and templates.

    • Clause Sequence Category: Provide a value here if you want to activate the AutoNumbering function for clauses in the operating unit. Leave it blank if you want to number clauses manually. For more information, see the Setting Up AutoNumbering section.

    Note: Users who are defined as FND_USERS, using the System Administrator responsibility, can only be assigned the role of Library Administrators or Library Approvers. If the users are no longer valid, you must manually update the information in the contract terms setup. For example, if an employee is no longer with your organization, ensure that the relevant updates are made to the setup that was explained earlier.

Implementing Multiple Organizations Access Control

The Multiple Organizations (Multi-Org) access control feature enables you to define the operating units within a specific responsibility that users can have access to. With the latest release of Oracle Contracts, you can set up Multi-Org access control in the Contract Terms Library. This feature enables users to access multiple operating units from a given responsibility. In the previous release of Oracle Contracts, access to an operating unit through a responsibility was controlled using the MO: Operating Unit profile option. Users could define this profile option and access the library for the specific operating unit.

Steps

To define security profiles:

  1. Log in to the Human Resources responsibility.

  2. Open the Profile page.

    Navigation: Security > Profile page

  3. Provide a name for the profile.

  4. Select a business group to which all the operating units belong. If you have not defined your own business groups, select the default business group.

  5. In the Security type field, select the “Secure Organizations by organization hierarchy and/or organization list” option from the list of values.

  6. Navigate to the Organization Security tab. At this stage, you can select one of the following options:

    • Navigate to the Classification region and provide a list of operating units and their names. This will be the list of operating units under the security profile.

    • Select an organization in the Organization Hierarchy field. To use this option, you must first set up an organization hierarchy. For more information, see the Setting Up Organization Hierarchy.

  7. Save your work.

  8. Run the Security List Maintenance program.

    • You should select the One Named Security Profile option as the value for the Generate Lists for parameter and then provide the value of the security profile that you just created.

    • If you have multiple security profiles, you can run this program as many times as necessary. Also, you must run this program after you update the security profile definitions.

Steps

To set up the organization hierarchy:

  1. Log in to the Human Resources responsibility.

  2. Open the Organization Hierarchy page.

    Navigation: Workstructures > Organization >Hierarchy

  3. Provide a hierarchy name.

  4. Save your work.

  5. Provide the version number and start date.

  6. Save your work and close the window.

  7. Query the hierarchy that you just created.

  8. Navigate to the Subordinates region.

  9. If you receive a warning message that indicates “The organization is not current as at the start date,” ignore it and provide the list of operating units that you want to include in the hierarchy.

  10. Save your work.

Setting Up Profile Options

Set up the following profile options:

Setting Up Approvers and Approval Workflow

The system supports defining a single approver for each of the Buy and Sell intents as standard out-of-the-box functionality. Use the Operating Units setup to identify approvers of clauses and templates in the global and local operating units. For more information, see the Setting Up Operating Units section.

You can customize the approval flows for clauses and templates to route it to multiple approvers or change approvers based on additional context using Oracle Workflow. For more information, see the Oracle Workflow Administrator's Guide.

The workflow names are

Setting Up Lookup Codes

Refer to the Look Up Codes appendix for the list of system, user, and extensible lookup codes. Use these tables to identify the lookup codes that you must define for your implementation. Use the Application Object Library Lookups window to define the lookup codes.

Note: Modifying seeded lookup values can corrupt data that was created using the lookup values. You cannot end date or disable seeded values.

Enabling Keyword Search

The Contract Terms Library supports searches using a clause keyword for both clauses and templates. To enable and effectively use this search feature, you must run the following concurrent processes on a periodic basis:

Setting Up Layout Templates

For formatting and publishing documents, Oracle Contracts leverages the functionality that Oracle XML Publisher provides.

Oracle XML Publisher is delivered with Oracle E-Business Suite. Using Oracle XML Publisher, you can register new layout templates that were created using XSL-FO and generate PDF documents. Layout templates represent the format and layout of business documents and are registered in Oracle XML Publisher in the Template Manager repository. For more information, see the Oracle XML Publisher User's Guide.

Oracle Contracts includes seeded layout templates, along with a XML Schema document that represents the XML structure of the contract data that is used to generate the contract document. A sample XML document with sample contract data is also seeded to enable users to preview the customized or new layout templates during the time of registration.

You cannot modify the seeded layout templates. However, you can download a copy of the layout template to your desktop, modify it, and register it as a new layout template in Oracle XML Publisher.

You can use the seeded layout templates to print the:

Contract Terms Layout Template

Oracle Contract Terms Template is the seeded layout template for printing contract terms. The attributes and seeded values for Oracle Contract Terms Template include:

Deviations Report Layout Templates

This section describes basic steps that are required to customize layout templates using Oracle XML Publisher. The layout template that you select defines how its format and layout appears when you select the Preview option. If the contract template is applied to a business document, a different layout template can be used to format the document. For example, to learn which layout template is applied to the contract terms that are added to a quote, see the Oracle Quoting Users Guide.

For the list of seeded layout templates for Deviations report, see the Seeded Data appendix.

Creating a Layout Template

To change the layout, you must create a new layout template in Oracle XML Publisher.

Example

To create a new template, you should start with a copy of one of the seeded templates, for example, Oracle Contract Terms Template.

The parameters that the Oracle Contract Terms template should use are Application, Data Source Name, Sub Template, and Template Type.

In addition, define the effective date range (start date and end date) of the layout template so that it enables you to preview the contracts and contract templates. If you leave the End Date field blank, you can use the layout template indefinitely.

Prerequisites

You must be familiar with Oracle XML Publisher and have access to Oracle XML Publisher Administrator Responsibility.

Steps

To create a layout template:

  1. Log in to the XML Publisher Administrator responsibility

  2. Click the Templates link.

    The system displays the Templates Search page.

  3. In the Application field, enter Oracle Contracts Core.

  4. Click Go to view the search results.

  5. Click the Duplicate icon for the Oracle Contract Terms template. The system copies the template as a new template.

  6. In the Code field, enter a new code for the template.

  7. In the Name field, enter a new name.

  8. Click Apply to save the new template.

  9. In the Template Files region, click the Download icon for the OKCTERM_en.XSL file.

  10. Save the template to your desktop.

  11. Open the template with a text or XSL editor.

  12. Modify the layout or boilerplate to suit your needs.

  13. Save the template with a new name, for example, MyTemplate_en.xsl.

  14. In the Template Files region, click the Update icon for the OKCTERMS_en.xsl file.

  15. Click the Browse button to locate and select your customized XSL-FO stylesheet (MyTemplate_en.xsl).

  16. Click Apply. The system uploads the file and associates it with your layout template.

  17. Click the Preview button to preview a sample document using your new layout template.

Customizing the Contract Terms XSL-FO Stylesheet

To create a stylesheet for a contract template, you must know the structure of the contract XML document that is transformed by the XSL stylesheet. The XSL-FO stylesheet, in the layout template, is applied to the contract XML document representing a contract template to create a PDF document. For a description of the contract XML format, see the Contract Terms XML Reference appendix.

Setting Up AutoNumbering

Use this setup to number clauses automatically during creation:

For more information about setting up Automatic Numbering feature, see the Oracle E-Business Suite Setup Guide.

Setting Up Value Sets

In this application, value sets are used in:

For more information, see the Defining Value Sets section of the Oracle E-Business Suite Developer's Guide.

Value Sets Used in Clause Variables

You can define value sets for use in clause variables. Value sets are supported subject to the following conditions:

Based on the value set definition, the system displays the list of values in the following formats:

Value Sets Used in Contract Expert Variables and Questions

The value sets that are used in questions and user-defined variables, for Contract Expert, are subject to the following conditions:

Based on the Character format type value set definition, the system displays the list of values in the following formats:

If a Number Format type value set is used, the Expert Runtime/Update Variables screens display a Number only entry field.

Considerations for Setting Up and Using Value Sets

Setting Up Numbering Schemes

When creating contract templates or authoring contracts, you can apply a numbering scheme to the sections and clauses structure. The numbering scheme, applied to a contract template, is automatically applied to business documents in which the contract template is used.

Use the Contract Terms Library to set up and manage numbering schemes.

The system currently supports the following numbering styles:

Steps

To set up numbering schemes:

  1. Navigate to the Numbering Schemes page.

    Navigation: Library > Numbering Schemes tab> Create Numbering Scheme button

  2. Enter the Scheme Name.

  3. Optionally, enter a Description for the scheme.

  4. Optionally, select the Number Clauses check box to automatically number the clauses in addition to sections on a business document.

  5. Click the Add Anther Level button to define the first numbering level.

  6. Enter the following information for the numbering level:

    • In the Sequence field, select a sequence from the list of values.

    • Optionally, enter an End Character. For example ( ) ).

    • Optionally, select the Concatenate with Child check box to ensure that the child level includes the numbering of its parent during previewing and printing of the business document.

      For instance, you would set up the numbering scheme as:

      First level:

      • a, b, c

      • end character is "."

      • Concatenate with Child check box selected

      Second level:

      • I, II, III

      • end character is ")"

      The document will be numbered as:

      • First Level = a.

      • Second Level = a.I)

  7. Click the Refresh button to preview the layout.

  8. Optionally, add additional numbering levels.

  9. Click Apply to save and close the Numbering Scheme page.

    • You cannot delete a numbering scheme after it has been assigned to a contract template or to a business document.

    • If you define a numbering scheme with the a, b, c, numbering type and a specific level with more than 26 entries, the system does not create further alphabets. Instead, the system uses symbols (such as aa, bb) for all entries beyond 26. Preview the template or contract, as applicable, and change the numbering scheme to another type.

Setting Up Function Security

Oracle Contracts enables organizations to control levels of access to authoring contract terms on business documents. Using the function security feature, customers can create custom responsibilities with the desired access controls depending on the users. Many businesses have multiple roles that are involved in the contract negotiation process, including contract negotiators, contract administrators, and contract approvers. The nature and extent of access to contracts can vary depending on the role of these personnel in an organization. Oracle Contracts supports varied levels of access to contract authoring features as noted here:

You can set up the following security function access controls:

The following table displays the functions that each responsibility has access to:

Feature Restricted Authoring Privileges Standard Authoring Privileges Non-standard Authoring Privileges Override Authoring Privileges
Apply or update contract templates; Assignment in a contract Yes Yes Yes Yes
Update contract details; Assign legal contract or contract administrator Yes Yes Yes Yes
Validate contracts Yes Yes Yes Yes
Create and manage deliverables Yes Yes Yes Yes
Update contract details; Update contract sources No Yes Yes Yes
Upload contracts No Yes Yes Yes
Download contracts No Yes Yes Yes
Lock contracts No Yes Yes Yes
Preview contracts Yes Yes Yes Yes
Review contract deviations Yes Yes Yes Yes
Run contract expert Yes Yes Yes Yes
Renumber contracts Yes Yes Yes Yes
Add sections or standard clauses No Yes Yes Yes
Add nonstandard clauses No No Yes Yes
Delete mandatory clauses No No No Yes
Update clauses that are text protected No No No Yes
Change the layout of clauses; Move sections and clauses No No Yes Yes
Add document attachments No Yes Yes Yes
Update variable values No Yes Yes Yes

Setting Up and Customizing Responsibilities

If you want to set up your own responsibility, you can then attach menus to the responsibility, typically by copying existing menus. Subsequently, you can grant or revoke specific functions from the menus, such as the Override Authoring Controls function.

For more information, see the Oracle E-Business Suite Setup Guide.

Migrating Clauses to Contract Terms Library

To support the new features of Oracle Contracts, the Articles schema has changed significantly.

Note: Since release 11.5.10, articles are referred to as clauses. Articles and clauses may be considered synonyms from a product feature perspective. However, in this document we refer to articles as clauses.

Prior to release 11.5.10, clauses did not belong to any specific operating unit. Hence, clauses that were created in the library were accessible to all operating units.

This release contains the following changes:

Therefore, as part of the 11.5.10 upgrade, all clauses will be assigned to an operating unit. If multiple operating units are currently using the same clause, the Migration program assigns the clauses to the global operating unit and automatically adopts the clauses for all local operating units. This enables all operating units to view and use the clauses in authoring documents exactly as they existed prior to 11.5.10.

In prior releases, you could have a single clause in a base language and then translate it to multiple languages. In 11.5.10, each clause is for a single language. As part of the 11.5.10 upgrade, a translated clause is split into one individual clause for each language.

Migration Process Overview

The following figures illustrate the migration of clause data in the 11.5.10 release. The first figure represents the important clause attributes in a pre-11.5.10 environment. The articles and versions existed in OKC_STD_ARTICLES_B/_TL and OKC_STD_ART_VERSIONS_B/_TL. The Article Name and the Article Text were translatable columns in OKC_STD_ARTICLES_TL and OKC_STD_ART_VERSIONS_TL, respectively.

These clauses are of Sell intent and have versions with Approved status. The original reference ID stores the old article ID. Adoption rows are created for each of the three clause versions in the OKC_ARTICLE_ADOPTIONS table. These rows are automatically created for all operating units that are set up to use the Contract Terms Library.

In this example, these rows are created for the local operating unit, Vision Operations, and have an adoption type of Adopted and the adoption status of Approved. Users that belong to these two operating units are now able to view the clauses exactly as they did in the earlier releases. Only the global operating unit, however, can make any updates to these clauses. For more details, see the Migration Steps section.

Standard Clauses After 11.5.10 Migration

the picture is described in the document text

Migration Steps

To migrate standard clauses to release 11.5.10, you must perform several post-upgrade steps. These steps must be performed after the 11.5.10 upgrade is completed.

Steps

To migrate standard clauses:

  1. Define operating units that use contracts. In 11.5.10 release, clauses are migrated to a global operating unit and automatically adopted by all the local operating units. This requires each operating unit to be set up for contract terms by defining additional information for the operating unit. For more information, see the Setting Up Operating Units section. Note that the system will migrate clauses only in those operating units that have used clauses in their contracts. If an operating unit has used clauses in authoring contracts, but has not been set up to use the Contract Terms Library in 11.5.10, the concurrent process will not continue until the setup is completed. You must ensure that all relevant operating units have completed the required setup step in order to use the Contract Terms Library in 11.5.10 release.

  2. Define the global operating unit. After the operating units are created, you must define a global operating unit using the site level OKC: Global Operating Unit profile option. For more information, see the Setting Up Operating Units section.

  3. Migrate standard clauses: To migrate standard clauses to the new 11.5.10 schema, run the Migrate Standard Clauses to 11.5.10 concurrent program. The concurrent program performs the following tasks:

    • In the global operating unit, the program creates global clauses in Approved status.

    • For each local operating unit, the clauses are migrated with adoption type as Adopted as is. All clause relationships are migrated to the local operating units as well.

    • The New Clause Versions table supports descriptive flexfields of size VARCHAR2(150) according to the current Oracle E-business Suite development standards. Note that this is a change from earlier releases in which these columns were of size VARCHAR2(450). The Migration program considers up to 150 bytes during the data conversion.

    • Clauses (including all versions) are migrated to the new schema using the following defaults:

      • Org Id: Global operating unit

      • Status: Approved

      • Intent: Sell

      • Version Number: System generated

      • Clause Language: Translated language

      • Clause Number: Autonumbered

      • Protect Text: No

      • Insert By Reference: No

      • Provision: No

    • Translated articles (including all versions) are created as new clauses with the translated text.

    • Article sets are migrated to folders. All existing FND_LOOKUPS of type ARTICLE_SET are migrated to clause folders and the existing associations are migrated to folder contents.

    • Folders are created for each of the operating units that have been set up under the classification of Contract Terms Library Details. Hence, one article set in pre-11.5.10 release will now have the same number of folders as the number of operating units that you have set up. Folder associations (contents) also will have multiple entries for all the migrated Article Sets and Article Set Members.

    • All incompatibilities are migrated as clause relationships of type Incompatible for every operating unit that has been set up under the Contract Terms Library Details classification. Hence, every incompatibility in a pre-11.5.10 release will now have the same number of relationships as the number of operating units that you have set up.

    • All existing associations between the clause version and contract documents are updated to reflect the newly generated clause version ID.

    Note: Prior to this release, users could attach supporting documents while creating clauses in the library. This feature is not supported in 11.5.10, but all attachments that already have been created are migrated to the new schema for backward compatibility reasons. However, in 11.5.10 release, users cannot access these attachments from the Contract Terms Library

Setting Up Contract Expert Rules

Contract Expert rules use questions and constants along with clauses and system variables to bring clauses into business documents. Contract Expert rules are created based on Buy or Sell intent for a specific organization. These rules can be applicable to all templates of one organization or can be associated with specific templates.

For more information, see the Contract Expert chapter.

Defining Transaction Types in Oracle Order Management

The Transaction Type window, for sales agreements, sales orders, and sales quotes, includes two fields applicable for setting up contract terms: Contract Template and Layout Template. These fields must be updated with appropriate values so that they can be the default values in the Sales Agreement or Sales Order window. From the list of values, you can choose which template to associate with the transaction type, displaying the contract and layout templates that the sales document is associated with the Contract Terms Library. If the layout template is not identified in the Transaction Type window, and you initiate the Preview/Print action, the system displays an error message.

Note that:

Associating Layout Template to Transaction Types

For every operating unit that is implementing Oracle Sales Contracts, you must associate a layout template with the following sales document types: Sales Orders, Sales Agreements, and Quotes. Thus the associated layout template determines the layout of the contract terms associated with the sales document.

Note: In Oracle Order Management, the layout template is defined in the Transaction Type window. 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.

Customizing Contract Terms RTF Stylesheet

To create a stylesheet for a contract template, you must know the structure of the contract XML document that is transformed by the XSL stylesheet. The RTF stylesheet, in the layout template, is applied to the contract XML document representing a contract template to create a PDF document.

Defining Processing Constraints

The processing constraints framework in Oracle Order Management gives you the ability to define the conditions and statuses for which an update can be made to an entity. For example, a sales agreement cannot be updated while it is in the Pending Internal Acceptance status. Likewise, you can define constraints that suite your business practices and prevent changes. These constraints can be defined at the entity level and for each attribute. Sales agreements use the same constraint framework as sales orders. This framework can also be used to set up the conditions that trigger automatic versioning for sales agreements.

For more information, see the Oracle Order Management Users Guide.

Setting Up Contract Repository

Oracle Contracts provides the ability to author and maintain contract terms in buy-side and sell-side Oracle applications. For example, contract terms can be added to purchase agreements created in Oracle Purchasing, or to quotes created in Oracle Quoting.

Oracle Contracts enables you to create miscellaneous contracts, such as license agreements, non-disclosure agreements, and merger agreements, which are not specifically related to the functionality of other Oracle applications. You can also create purchase or sales agreements for miscellaneous items that are outside the normal purchasing or sales flows, for which full execution capabilities are not required.

These types of contracts are stored in a new Contract Repository, and are called Repository contracts. Each Repository contract will have a user-defined contract type, unlike the contracts created in other Oracle applications, which have system-defined contract types.

Repository Contracts are integrated with Contract Terms Library to enable Structured Terms Authoring. A repository contract can include supporting documents and amendments, deliverables with notification capabilities, and risk information. Repository contracts support a flexible approval and signature process, and a bulk import process is available for loading legacy contracts into the system.

This section covers the following topics

Setting Up Profile Options

Define the following profile options:

For more information, see Setting Up Profile Options

Defining Approval Workflows

Define approval hierarchy and approval rules through the Oracle Approvals Manager. For more information, see Setting Up Approvers and Approval Workflow.

Setting Up Contract Types

When users create Repository contracts in Oracle Contracts, they must select and assign one of the user-defined contract types, such as Non-Disclosure Agreement and Partnership Agreement, to the contract. You must define the contract types in advance. User can enable contract terms for Structured Terms Authoring.

Steps

  1. Log in to the Contracts Workbench Administrator responsibility.

  2. Click the Contract Types link. The contract types you define should be unique across all organizations within the company. Note: For your reference, the Contract Types page displays the list of seeded and current user-defined contract types.

  3. Click the Create Contract Type button. The system displays the Create Contract Type page.

  4. In the Name field, enter a unique identifier for the contract type.

  5. Enter a Description for the contract type.

  6. Select an Intent from the list of values. Each contract type should be associated with one intent. The possible values for Intent are Buy, Sell, and Other. If the Contracts Intent Access Control profile option is used, this selection will limit which users will be able to select this contract type.

    Additional Information: If you select intent as Other, Layout Template and Enable Contract Terms are disabled.

  7. Select a Start Date. This is the date that the contract type becomes available.

  8. Optionally, select an End Date for the contract type. After the End Date has passed, when creating new contracts, users will not be able to select this type.

  9. Select the Enable Contract Terms check box.

  10. Select the appropriate Layout Template.

  11. Click the Apply button.

Setting Up Risks

When users create repository contracts in Oracle Contracts, they may select multiple risks associated with these contracts. For example: partner bankruptcy, non-performance of a deliverable, non-compliance with non-disclosure terms, loss or infringement of intellectual property, and damage to property or humans. These risks must be defined in advance.

Steps

  1. Log in to the Contracts Workbench Administrator responsibility.

  2. Click the Risks link.

    Note: For your reference, the Risks page displays the list of all user-defined risks. Oracle Contracts does not provide seeded risks.

  3. The risks you define should be unique across all organizations within the company.

  4. Click the Create Risk button. The system displays the Create Risk page.

  5. In the Name field, enter a unique identifier for the risk.

  6. Enter a Description for the risk.

  7. Select a Start Date.

  8. Optionally, select an End Date for the risk. After the End Date has passed, the risk cannot be selected on a contract

  9. Click Apply to save the risk.

Setting Up Contact Roles

The contact role indicates the responsibility or function of different people in a contract. For example, an employee (internal contact) can be assigned the role of “Purchasing Manager” in a contract. There are no predefined contact roles. You can define an unlimited number of contact roles. These roles will be available to users when adding internal or external contacts to a party on a Repository contract.

Steps

  1. Login to the Contracts Workbench Administrator responsibility.

  2. Click the Contact Roles. For your reference, the Contact Roles page displays the list of all user-defined roles. The roles you define should be unique across all organizations within the company.

  3. Click the Create Contact Role button. The system displays the Create Contact Role page.

  4. In the Name field, enter a unique identifier for the role.

  5. Enter a Description for the role.

  6. Select a Start Date.

  7. Optionally, select an End Date for the role. After the End Date has passed, the role cannot be selected on a contract.

  8. Click Apply to save the role.

Setting Up Contracts Workbench

A single view of all enterprise contracts is essential for effective management of contract activities, and for reporting and analysis of outstanding supplier and customer commitments. Oracle Contracts provides a centralized Contracts Workbench that gives you access and visibility to all contractual agreements in the enterprise.

Contracts Workbench allows contract administrators to see which contracts require attention, provides extensive search capabilities, and has links to common tasks such as creating or approving a contract. Legal and financial managers can use Contracts Workbench as a research tool. A flexible security model ensures that contracts can be viewed or updated only by authorized users.

Contracts Workbench provides a single view of the following types of contracts:

All of these contracts are automatically visible in the Contracts Workbench, as long as they include contract terms.

This section covers the following topics:

Setting Up Profile Options

You can use the Contracts Intent Access Control profile option to restrict the access to contracts. For more information, see the Setting Up Profile Options section

Personalizing Contracts Workbench

Oracle Framework includes the OA Personalization Framework, which enables you to personalize the appearance of Contracts Workbench without modifying any underlying code.

The following are the most common ways to personalize Contracts Workbench:

  1. The default bins for the Contracts Workbench are:

    • Notifications

    • Recent Contracts

    • Expiring Contracts

    • Contract Deliverables

    • Contracts at Risk

    You can use the personalization option to add the Bookmarks bin, remove one of the above bins, or change the order the bins are displayed.

  2. The default columns for the Advanced Search Results page are:

    • Contracts Number

    • Contracts Name

    • Organization

    • Party Name

    • Contract Type

    • Intent

    • Status

    • Effective Date

    You can use the personalization option to remove one of the above columns, change the order the columns are displayed, or add any of the following columns:

    • Contract Administrator

    • Overall Risk

    • Version

    • Expiration Date

    • Termination Date

    • Amount

    • Currency

    • Authoring Party

    The personalization also impacts the Export option. After performing a search, the user can export the search results to a Comma Separated (CSV) file. The exported file will include only the columns shown on the screen. After personalization, columns that are available for personalization but not selected will not be included in the CSV file.

    For more information on personalization, see: Oracle Applications Framework Personalization Guide.