Browser version scriptSkip Headers

Oracle® Fusion Procurement, Supplier Contracts and Agreements Guide
11g Release 5 (11.1.5)
Part Number E22850-06
Go to Documentation Home
Home
Go to contents  page
Contents
Book<br />List
Book
List
Go to Feedback page
Contact
Us

Go to previous page
Previous
Go to previous page
Next
PDF

Managing Contract Party Roles

Managing Party Contact Roles

Managing Contract Types

Contract Line Types: Explained

Setting Up Contract Preview and Printing

Managing Contract Party Roles

Setting Up Contract Party Roles and Making Them Available in Contracts: Explained

Party roles provide a way for you to specify the roles of different parties in the contract. For example, a sales contract may include the customer, a partner, and the internal business unit selling the product and service. Your application comes with predefined party roles, but you can create additional roles and you can specify how the roles are used in sales, purchasing, and project contracts.

This topic:

Managing Party Roles

The application comes with the following predefined party role names in the lookup type OKC_PARTY_ROLE. You can add additional lookup codes in the Setup and Maintenance work area by selecting the Manage Contract Party Roles task.


Lookup Code

Meaning

CUSTOMER

Customer

INTERCOMPANY

Internal party

PARTNER

Partner

SUPPLIER

Supplier

THIRD_PARTY

Third party

Making Party Roles Available for Use in Contracts

To make party roles available for use in contracts, you must:

  1. Associate each party role to the appropriate party source by selecting the Manage Contract Roles Sources task in the Contracts work area.

  2. While managing contract types using the Manage Contract Types task in the Setup and Maintenance work area, add each party role to the contract types where you want the party role to be used. You can add a party role either as one of the two primary contract parties (the Buyer Role and the Seller Role) or as a secondary party. You can only have one Seller Role and one Buyer Role in a contract. You can have multiple secondary parties with the same role.

The application includes the following party sources which you cannot modify:


Party Source Code

Name

Description

OKX_PARTY

Customer

Parties in the Trading Community Architecture (TCA) where the party usage is External Legal Entity.

OKX_OPERUNIT

Business Unit

Internal business units.

OKX_VENDOR

Supplier

Parties in TCA where the party usage is Supplier.

OKX_INT_COMP_PARTY

Internal party

Internal parties available for Oracle Fusion Projects interproject billing.

OKX_PARTNER

Partner

Partners. This source is reserved for Oracle Fusion Partner Relationship Management.

You can use the same party role for both buy-intent and sell-intent contracts by associating the party role to different sources. This figure shows how you can reuse the role Customer in both buy and sell contracts. The customer for sales contracts is a TCA party (Customer). The customer for buy contracts is an internal business unit.

To reuse the same party in buy and sell contracts, you:

  1. Select the Customer party role in the Manage Contract Role Sources page.

  2. Set the Sell Intent Source to Customer and the Buy Intent Source to Business Unit.

  3. To use the party role in a contract, you must also enter it in contract types where you want to use it as one of the primary contact parties or as a secondary party.

The setup in this figure will have the following effect:

This figure shows how you can map the
same party role to different party.

Managing Party Contact Roles

Setting Up Party Contact Roles and Making Them Available for Use: Explained

Contact roles specify the roles party contacts play in the contract. Your application comes with a set of predefined contact roles, but you can set up additional contact roles for use with different parties in the contract.

This topic:

Managing Contact Roles

The application comes with the following predefined contact roles in the extensible lookup type OKC_PARTY_CONTACT_ROLE:


Lookup Code

Meaning

BUYER

Buyer

CONTRACT_ADMIN

Contract administrator

EMPLOYEE

Employee

PARTNER_CONTACT

Partner contact

PARTY_CONTACT

Customer contact

SALESPERSON

Salesperson

VENDOR_CONTACT

Supplier contact

You can add additional contact roles by selecting the Manage Contract Contact Roles task in the Setup and Maintenance work area .

Making Contact Roles Available for Use in Contracts

For a contact role to be available for use in contracts, you must navigate to the Manage Contract Role Sources page by selecting the Manage Contract Roles Sources task in the Contracts work area and make the following entries for each of the party roles where you want the contact role to be available:

  1. Select the party role.

  2. Add the contact role.

  3. Enter the sell-intent contact source or the buy-intent contact source or both. Which contact sources you can enter depends on the party source settings for the party role.

The following contact sources come predefined with the application in the system lookup type OKC_PARTY_CONTACT_SOURCE. You cannot edit the contract role sources or add additional ones.


Lookup Code

Meaning

Description

OKX_PARTNER_CONTACT

Partner contact

Used exclusively for Oracle Fusion Partner Management contracts.

OKX_PCONTACT

Customer contact

Contacts of parties in the Trading Community Architecture (TCA) where the party usage is External Legal Entity.

OKX_RSCEMP

Employee

Employees in the internal human resources database.

OKX_SALEPERS

Salesperson

Employees in the internal human resources database.

OKX_VCONTACT

Supplier contact

Contacts of parties in TCA where the party usage is Supplier.

The following figure illustrates the setup required to make a contact role available in both customer and supplier contracts:

  1. The party role Customer is associated with both a sell intent and buy intent source. In a sales contract, a Customer party is a TCA party (party source Customer). In a buy-intent contract, the Customer is an internal business unit.

  2. You make the contact role available in both customer and supplier contracts by specifying the Sell Intent Source as Customer Contact and to the Buy Intent Source as Employee.

  3. In sales contracts, customer contacts will now be TCA party contacts. In procurement contracts, customer contacts will be employees.

This figure shows how you can make
a contact role available in buy-intent and sell-intent contracts.

Managing Contract Types

Contract Types: Explained

A contract type is a contract category that contract authors must select when creating a contract. It is a mandatory setup that determines the nature of the contract. For example, this step determines if the contract is a project contract, a purchasing contract, or simple nondisclosure or employment agreement. A contract type also specifies what kinds of information you can enter and what contract lines, parties, and party contacts are permitted.

This topic provides an overview of the super set of contract type setups for a broad range of contracts. When setting up individual contract types, only a subset of the fields listed here are visible. For example, the project billing option entries are visible only in contract types with a sales-intent, and the notifications fields appear only for contract types with a buy-intent.

Overview

Create contract types by selecting the Manage Contract Types action from the Setup and Maintenance work area. You can also create contract types in the Contracts work area by selecting Contract Types under the Setup task heading. In each contract type you can:

Common Contract Type Entries

The following table describes the common contract type entries:


Field or Option

Description

Class

Indicates the category of the contract you are authoring:

  • Enterprise Contract: Used for authoring both buy and sell contracts where you are buying or selling items and services now. Examples of contracts of this class include contract purchase agreements, project contracts, and repository contracts.

  • Partner Agreement: Used exclusively for Oracle Fusion Partner Management.

  • Purchase Agreement: Used for negotiating a future purchase of goods and services.

You cannot change the class after the contract type is created.

Set

Determines the data security for contracts of this type.

Name

The name contract authors select when authoring contracts.

Description

Description that is visible only for administrators managing contract types.

Allow lines

Selecting this option makes it possible for you to specify what line types can be added to the contract. You cannot change the setting after the contract type is created.

Use external item master

Selecting this option lets you reference items from an external item source master.

Note

This option is available only for sell intent contracts if Allow lines option is available and selected.

Enable Automatic Numbering

Enables automatic numbering of contract lines during contract authoring.

Requires Acceptance

Determines if customer acceptance is required before this type of contract can become active. After approval, the contract is set to the Pending Acceptance status and requires the contract author to enter the date of customer approval before the contract becomes active.

Contract Numbering Method and Contract Sequence Category

Specifies if the contract number is entered manually by the contract author or generated automatically based on the document sequence category you specify.

Intent

Contracts can have either a sell intent (project contracts and partner agreements) or buy intent (purchase contracts).

You cannot change the intent after the contract type is created.

Buyer Role

The party role of the recipient of the goods and services in the contract. For a sales or a project contract, this is the role you set up for the customer. For a purchasing contract, it is the role you set up for the business units in your organization. You cannot edit the entry in this field after contract type creation.

Seller Role

The party role of the party delivering the goods and services covered by the contract. For a sales or a project contract, this is the role you set up for one of the internal business units. For a purchasing contract, it is the role you set up for the supplier. You cannot edit this field after contract type creation.

Contract Owner Role

The contact role assigned to the owner of the contract. Contract ownership is automatically assigned to the employee who creates the contract. The owner is automatically assigned the role you specify here.

Buyer Contact Role

The role you specify in this field specifies the role of the buyer that will be copied from the contract header to the contract fulfillment lines created for contract lines.

Note

This option is available for purchase contracts only:

Requester Contact Role

In purchase contracts only: The role of employee who will be used as the creator of a requisition in Oracle Fusion Purchasing.

Contract Layout Template

The Oracle BI Publisher template that is used to print the entire contract.

Note

This option is not available if Use external item master is enabled.

Terms Layout Template

The Oracle BI Publisher template used to print the contract terms.

Note

This option is not available if Use external item master is enabled.

Notify Before Expiration, Days to Expiration, and Contact Role to be Notified

Selecting this option sends a notification before contract expiration to the individual with the role specified in the Contact Role to Be Notified the number of days specified the Days to Expiration field.

Note

These options are not available if Use external item master is enabled.

Line Types

You can enter the line types permitted by the class you selected for the contract type and only if you selected the Allow Lines option during the contract type creation. The following table describes the possible line types.


Line Type

Description

Buy agreement, free-form

Enables entry of items not tracked in inventory for purchasing. You can create master agreements in the purchasing application from lines of this type.

Buy agreement, item

Enables entry of inventory items for purchasing. You can create master agreements in the purchasing application from lines of this type.

Buy intent, free-form

Enables entry of items not tracked in inventory for purchasing. You can create purchase orders in the purchasing application from lines of this type.

Buy intent, item

Enables entry of inventory items for purchasing. You can create purchase orders in the purchasing application from lines of this type.

Sell intent, free-form, project-based

Enables entry of items not tracked in inventory and displays project-related tabs and fields in a contract. You can associate and bill the line to a project in Oracle Fusion Projects.

Sell intent, item, project-based

Enables entry of inventory items and displays project-related tabs and fields in a contract. You can associate and bill the line to a project in Oracle Fusion Projects.

If you enable Use external item master when creating a contract type, you can create only the following line types:


Line Type

Description

Sell Intent, Subscription

This line type applies to sell contracts and describes the sale of subscription items that are tracked in inventory.

Sell Intent, Bundle

This line type applies to sell contracts and describes the sale of bundled items tracked in inventory. Bundles can include other bundles or items.

Additional Party Roles

You can add party roles that contract authors can add to a contract in addition to the primary parties specified in the Buyer Role and Seller Role fields. A contract author can add multiple additional parties with the same role to the contract.

Project Billing Options

For contract types created for projects (sales-intent contract types of class Enterprise Contract and at least one project line type), you can set the following project billing options:


Option

Description

Intercompany

Enables project billing between internal organizations.

Interproject

Enables billing to other projects.

Enable Billing Controls and Billing Limit Type

Enables billing controls for each contract line, making it possible for you to specify a hard limit or a soft limit as the Billing Limit Type. A soft limit warns you if the billing limit is reached. A hard limit prevents you from billing above the limit.

Enabling Contract Fulfillment Notifications for Purchase Contracts

For purchase contracts, you can use the Notifications tab to specify what contract fulfillment notifications will be sent to what contact role. Available notifications are slightly different for each type of contract:

For contracts with purchase order fulfillment lines, you can notify contacts with a specific role:

For contracts with blanket purchase agreement fulfillment lines or contract purchase agreement fulfillment lines, you can notify:

Enabling Contract Terms Authoring and Other Advanced Options

If you do not enable Use external item master, you can enable contract terms authoring and other advanced contract terms authoring options on the Advanced Authoring Options tab.

Note

If you enable Use external item master, the Advanced Authoring Options tab is not available but Related Contracts option is automatically enabled.

The advanced authoring options are described in the following table:


Option

Description

Enable Terms Authoring

Displays the Contract Terms tab in contracts and enables contract terms authoring using contract terms templates from the Contract Terms Library. You must set up the content of the library from the Terms Library work area before you can take advantage of this feature.

Note

When this option is disabled, contract authors can attach contract terms along with other supporting documents.

Enable Risk Management

Enables the entry of contract risks.

You must set up contract risks selecting the Manage Contracts Risks task in Oracle Fusion Functional Setup Manager.

Enable Interactions

Enables the logging of interactions with customers, employees, and other parties in the contract. Interactions include meetings, phone calls, and e-mail notifications.

Enable Related Contracts

Makes it possible for contract authors to relate contracts to each other.

Key Contract Type Settings for Different Kinds of Contracts: Examples

This topic provides examples of key contract type settings for different kinds of enterprise contracts, including employment agreements, purchase contracts, purchase agreements, and sales contracts with project work.

Employment Agreement

You want to create a standard employment agreement that can be edited during negotiations with a new employee.


Key Contract Type and Related Setups

How It Works

Key contract type setups:

  • Class: Enterprise Contract

  • Intent: Sell or Buy

  • Allow Lines option: Leave unselected

  • Select the Enable Terms Authoring option to permit the use of the contract terms template with the employment agreement.

In the Contract Terms Library, you create the contract terms template and set the template as the default for this contract type.

When you select the contract type, the contract terms template automatically populates the Contract Terms tab in the contract with the terms and conditions. You can edit them during the negotiation with the employee.

Purchase Contract

You want to create a purchase contract that can be used to create and monitor purchase orders within Oracle Fusion Purchasing.


Key Contract Type Setups

How It Works

  • Class: Enterprise Contract

  • Intent: Buy

  • Allow Lines option: Selected

  • You can add two types of lines:

    • Buy-intent Freeform

      For items not tracked by inventory.

    • Buy-intent Item

      For items tracked by inventory.

You enter the goods and services you are purchasing in contract lines. By creating contract fulfillment items for individual or multiple lines, you automatically create purchase orders in Oracle Fusion Purchasing. You can then use these deliverables to monitor the status of each purchase order from within the contract.

Purchase Agreement

You want to create a contract for future purchases which creates blanket purchasing agreements within Oracle Fusion Purchasing.

You want to create a blanket purchase agreement when you know the detail of the goods or services you plan to buy from a specific supplier and want to negotiate their price, but you do not yet know the detail of your delivery schedules.


Key Contract Type Setups

How It Works

  • Class: Purchase Agreement

  • Intent: Buy

  • Allow Lines option: Selected

  • You can add two types of lines:

    • Buy-intent Freeform

      For items not tracked by inventory.

    • Buy-intent Item

      For items tracked by inventory.

By adding deliverables for one or more contract lines, you automatically create blanket purchase agreements in Purchasing. You can use the deliverables to monitor the status of the blanket purchase agreements from within the contract.

Enterprise Sales Contract with Project Work

You want to create a sales contract that governs the billing of items and services to projects in Oracle Fusion Projects.


Key Contract Type Setups

How It Works

  • Class: Enterprise Contract

  • Intent: Sell

  • Allow Lines option: Selected

  • You can add two types of lines:

    • Freeform, Project-Based

      For entering item not tracked in inventory.

    • Item, Project-Based

      For entering inventory items.

  • Use external item master: Selected for referencing an external item master.

    Note

    If you enable Use external item master, the Advanced Options tab is not available.

  • On the Advanced Options tab, leave the Contract Terms Authoring option unselected.

    Note

    While nothing prevents you from using the Contract Terms Library to author contract terms for sales contracts with project work, there is no functional link between the contract terms and the Oracle Fusion Projects application. This means that you cannot monitor the adherence of a project to the terms in the contract.

You add contract lines to specify the goods and services sold, specify the project they are billed to, and enter billing details. The fulfillment and billing of those items is tracked within Oracle Fusion Projects.

Setting Up Contract Types for Different Kinds of Contracts: Points to Consider

This topic explains how to set up contract types for different kinds of enterprise contracts.

Your contract type setup depends on the type of contract you are setting up. The main types are:

For these types of contracts, the key contract type settings are based on the following questions:

  1. Are you selling or buying?

    For Intent, you select either Sell or Buy.

  2. Are you buying or selling now or negotiating a long-term contract with terms, such as pricing, that will govern a future purchase or sale?

    For Class, select Enterprise Contract if you are buying or selling now. If you are negotiating a future purchase or sale, select one of the agreement classes, for instance Purchase Agreement for a future purchase.

  3. Does the contract involve the purchase or sale of specific items?

    If the contract involves the purchase or sale of specific items, then you can specify how those items are entered into contract lines by adding different line types to the contract type. Some line types permit contract authors to select items tracked in inventory; others permit the entry of any item as text, for example, for free-form services.

    Some of the line types support integration with other Fusion applications, for example, project line types support the billing of items through Oracle Fusion Project billing. Buy-intent lines allow the capture of pricing information and support integrations to purchasing systems to create POs or blanket purchase agreements.

The combination of answers to these questions result in the numbered cases in this figure and are described in the different sections of this topic. Some functionality is planned for a future release.

There are other special kinds of contracts where these questions are less relevant or do not apply. These include:

This figure details options for contract
type setup.

Note

* While full integration with sales applications is planned for a future release, you can create sales contracts as documents in the contract repository.

Customer Contracts

This section describes the settings for sell-intent contracts.

Case 3: Customer Contracts with No Lines

Use the following contract type settings to create simple sales contracts with no lines.


Purpose of Contract

Contract Type Settings

Simple customer contract with no lines.

  • Class: Enterprise Contract

  • Intent: Sell

  • Allow Lines option: Deselected

Case 4: Customer Contracts with Lines

The following table describes the key contract type settings for sell-intent contracts for items or services. In this release, you can add lines for selling items and services that are executed as part of a project, for example, project manufactured items or professional services. Lines for selling services and regular inventory-based tangible items are planned for a future release.


Purpose of Contract

Contract Type Settings

Sell items and services that are tracked and billed to one or more projects.

  • Class: Enterprise Contract

  • Intent: Sell

  • Allow Lines option: Selected

  • You can add two types of lines:

    • Freeform - Project Based

      For selling items not tracked in inventory.

    • Item - Project Based

      For selling inventory items.

  • On the Advanced Options tab, leave the Contract Terms Authoring option unselected.

    Note

    While nothing prevents you from using the Contract Terms Library to author contract terms for project contracts, there is no functional link between the contract terms and the Oracle Fusion Projects application. This means that you cannot monitor the adherence of a project to the terms in the contract.

Supplier Contracts

This section describes contract type settings for buy-intent contracts.

Case 5: Supplier Contracts Without Lines

The following table describes the key contract type setups for supplier contracts where you are negotiating purchase of items or services without specifying the actual items to be purchased.


Purpose of Contract

Contract Type Settings

Contract where you negotiate specific terms and conditions or a purchase without specifying the goods and services as contract lines. Contract authors can create a corresponding purchase agreement within Oracle Fusion Purchasing or another integrated purchasing application by adding a contract deliverable for the contract. You can use the deliverable to monitor the status of the agreement, but purchase orders are created and tracked in purchasing.

  • Class: Enterprise Contract

  • Intent: Buy

  • Allow Lines option: Leave unselected

Case 6: Supplier Contracts with Lines

The following table describes the key contract type setups for supplier contracts for immediate purchase of specific items or services.


Purpose of Contract

Contract Type Settings

Purchase goods and services. This type of contract makes it possible for contract authors to create purchase orders in Oracle Fusion Purchasing or another integrated purchasing application from individual contract lines by adding contract deliverables. You can monitor the status of each purchase order directly from the deliverables.

  • Class: Enterprise Contract

  • Intent: Buy

  • Allow Lines option: Selected

  • You can add two types of lines:

    • Buy-intent Freeform

      For items not tracked by inventory.

    • Buy-intent Item

      For items tracked by inventory.

Case 7: Contracts for Future Purchases Without Lines

This table describes the key contract type setups for future purchase contracts without lines.


Purpose of Contract

Contract Type Settings

Contract for future purchase without specifying the goods and services as contract lines.

  • Class: Purchase Agreement

  • Intent: Buy

  • Allow Lines option: Leave unselected

Case 8: Contracts for Future Purchases with Lines

This table describes the key contract type setups for future-purchase contracts with lines.


Purpose of Contract

Contract Type Settings

Create this type of contract when you know the detail of the goods or services you plan to buy from a specific supplier in a period, but you do not yet know the detail of your delivery schedules. You can use this type of contract, sometimes called a blanket purchase agreement, a standing order, or a blanket order, to specify negotiated prices for your items before actually purchasing them. Use this type of contract when you have negotiated volume discounts and want to create releases against these negotiated volumes, or when you commit to specific items, quantities, or amounts. You can issue a blanket release against a blanket purchase agreement to place the actual order (as long as the release is within the blanket agreement affectivity dates).

Contract authors can automatically create corresponding agreements in Oracle Fusion Purchasing or other integrated purchasing applications by adding contract deliverables and monitor the execution of those agreements from the deliverables.

  • Class: Purchase Agreement

  • Intent: Buy

  • Allow Lines option: Selected

  • You can add two types of lines:

    • Buy-intent Freeform

      To purchase items not tracked by inventory.

    • Buy-intent Item

      To purchase items tracked by inventory.

Special Contracts

This section describes the settings you want to use for partner agreements and for miscellaneous contracts.

Case 1: Partner Agreements

Use the following contract type settings for partner agreements in Oracle Partner Relationship Management.


Purpose of Contract

Contract Type Settings

Partner enrollment agreement

  • Class: Partner Agreement

  • Intent: Sell

  • You must enable contract terms authoring by selecting the Enable Terms Authoring option.

Note

Oracle Fusion Partner Relationship Management uses contract types only for applying contract terms templates with boilerplate contracts, so most of the contract type entries do not apply or have no effect.

Case 2: Miscellaneous Contracts

The following table lists the key contract type settings for nondisclosure, employment contracts, and other simple contracts.


Purpose of Contract

Contract Type Settings

Nondisclosure agreement or employment agreement

  • Class: Enterprise Contract

  • Intent: Sell

  • Allow Lines option: Leave unselected

Frequently Asked Questions for Contract Types

Why can't I delete a contract type?

You cannot delete a contract type after it is used to create a contract. However, you can enter an end date to prevent its use in future contracts.

Must I create contract types to author contract terms on purchase orders or sourcing documents such as RFQs?

If you want to author contract terms on individual purchase orders or other Oracle Fusion Sourcing documents, such as RFQs, you are not required to set up contract types. This is because no enterprise contracts are created. The documents themselves are the contracts. All setups to enable contract terms templates and contract terms authoring are done from within Oracle Fusion Purchasing and Sourcing applications.

Contract Line Types: Explained

Using the Manage Contract Line Types task, you can rename the types of lines available for selection when you create contract types. This optional implementation task is available by selecting Setup and Maintenance from the Tools menu and searching on the task name.

Line Types

Line types are names you give to the contract lines.

You must associate each line type name with one of the fixed set of predefined line sources. A line source defines what item you can enter in a contract line and enables functionality of one of the integrated applications to that line. For example, project line sources expose Oracle Fusion Projects fields in contracts and make it possible for contract authors to relate lines to projects. Buy sources make it possible to create contract deliverables for the line and use those contract deliverables to create and manage purchase orders and purchase agreements in Oracle Fusion Purchasing or other integrated purchasing systems.

The application already includes a full set of predefined line type names for all of the available line sources. You can create additional names for use in different contract types, if desired.

The predefined line types names are the same as the names of the lines sources they are associated with.

Line Sources

The application includes the following predefined line sources. These line sources cannot be modified or extended.

If you do not enable the Use external item master option, you can create the following line sources only:


Line Source

Description

Buy agreement, free-form

Enables entry of items not tracked in inventory. You can create master agreements in the purchasing application from lines of this type.

By agreement, item

Enables entry of inventory items. You can create master agreements in the purchasing application from lines of this type.

Buy intent, free-form

Enables entry of items not tracked in inventory. You can create purchase orders in the purchasing application from lines of this type.

Buy intent, item

Enables entry of inventory items. You can create purchase orders in the purchasing application from lines of this type.

Sell intent, free-form, project-based

Enables entry of items not tracked in inventory. You can associate and bill the line to a project in Oracle Fusion Projects.

Sell intent, item, project-based

Enables entry of inventory items. You can associate and bill the line to a project in Oracle Fusion Projects.

If you enable Use external item master, you can create the following line sources only:


Line Source

Description

Sell Intent, Subscription

This line type applies to sell contracts and describes the sale of subscription items that are tracked in inventory.

Sell Intent, Bundle

This line type applies to sell contracts and describes the sale of bundled items tracked in inventory. Bundles can include other bundles or items.

Setting Up Contract Preview and Printing

Contract Printing and Layout Templates: Explained

Previewing and printing clauses, reports, contracts, and contract terms uses a number of Oracle Business Intelligence (BI) Publisher layout templates which specify what information is displayed in the contract and supply the headers, footers, text style, and pagination. The layout templates are RTF files stored in the BI Presentation Catalog. Samples of all the required layout templates are included with the application. You can copy the sample layout templates described here, and edit the copies to add your own boilerplate text, font styles, and logos.

You can copy and edit layout templates used for:

The sample layout templates are available in different subfolders within the Enterprise Contracts folder in the catalog. You can navigate to the folders in the catalog either from the Reports and Analytics pane or by selecting the Reports and Analytics link in the Navigator. Contact your system administrator to grant you the appropriate BI duty roles if these are not available.

You can download the sample templates, copy them, and edit the copies. When you upload your edited copy to the same directory, it becomes immediately available for use within the application.

Restriction

The catalog includes additional layout templates which are used internally by the application. You can edit only the layout templates listed below.

Printing Enterprise Contracts

The application uses two layout templates for printing enterprise contracts, including partner agreements:

You specify which templates you want to use during contract type setup. This means that you can create different layout templates for each contract type. To set up contract types, select Manage Contract Types action from the Setup and Maintenance work area or Contract Types under the Setup task heading in the Contracts work area.

The following figure outlines how the application uses the layout templates when you print an enterprise contract:

  1. The application uses the contract layout template, specified in the Contract Layout field of the contract type, to create a PDF of the contract. If the contract does not include any contract terms, this is the only layout template used.

  2. If the contract includes structured terms, then the application uses the contract terms layout template specified in the Terms Layout Template field to create the contract terms PDF. To create the contract terms PDF, you must set the terms layout template in contract type.

  3. If the contract terms are attached as a file and the file retains the structured terms format, the application creates the contract terms PDF from the file. Contract terms attached as a file can retain the structured XML format if the file was downloaded from the application using the Download Contract action.

  4. The application merges the two generated PDFs into a single PDF.

  5. If the contract terms are attached in a file that is not structured, then the application prints only the contents of the file. It does not print the contract information in the application or use either layout template. If you need help in editing the layout templates, download the sample XML file provided in Enterprise Contracts > Contract Printing > ContractPrintDm.

This figure shows how enterprise contracts
are printed.

Printing of Contract Terms on Purchase Orders and Sourcing Documents

For printing purchasing documents with structured terms, Oracle Fusion Procurement uses two layout templates.

You select both of these templates while setting up business unit properties using the Configure Procurement Business Function task available by navigating to the Setup and Maintenance work area.

If the contract terms are attached rather than authored in the application and the attached file is not structured, then Procurement uses a third layout template which includes a brief sentence explaining that the contract terms are contained in a separate document.


File Name

Description

Location in BI Publisher Catalog Directory

ContractTermsNoMerge

This layout template includes the following text: The contract terms for this (doc type} are listed in a separate document which is either attached to the e-mail you received or sent separately. These contract terms should be read in conjunction with this {doc type}.

The document type name is substituted in the printed contract.

Enterprise Contracts/Contract Terms Printing/Attached Contract Preview

Important

If you edit the ContractTermsNoMerge layout template, then you must save it under the same name in the same directory.

The following figure outlines how the procurement application uses these layout templates for printing

  1. The application uses the document layout template specified in the Document Layout field in the PO or purchase agreement to create the PDF.

  2. If the contract includes structured terms, then the application uses the contact terms layout template to generate the contract terms PDF.

  3. If the contract terms are attached as a file and the file retains the structured terms format, then the application creates the contract terms PDF from the file. Contract terms attached as a file can retain the structured XML format if the file was downloaded from the application using the Download Contract action.

  4. If the contract terms are attached as a file that is not structured, then the application creates a small PDF of the message contained in the layout template ContractTermsNoMerge.

  5. The application merges the two PDFs into a single document PDF.

This figure shows how procurement documents
are printed.

Printing the Contract Deviations Report

The application uses the contract deviations layout template to generate a PDF report of deviations of a contract from company standards. This report can be automatically attached to the notification sent to the contract approvers during contract authoring. You can create different layout templates for each business unit. You specify which layout template you want to use in a specific business unit using either the Specify Customer Contract Business Function Properties or the Specify Supplier Contract Business Function Properties tasks. These tasks are available in the Setup and Maintenance work area.

Separate sample layout files are available for buy-intent and sell-intent contracts. Both are located in the same directory:


File Name

Description

Location in BI Publisher Catalog Directory

SupplierContractDeviations

Layout for printing the contract deviations for all buy-intent contracts.

Enterprise Contracts/Deviations Report/Deviations Report

CustomerContractDeviations

Layout for printing the contract deviations for all sell-intent contracts.

Enterprise Contracts/Deviations Report/Deviations Report

Previewing Contract Terms Templates

Contract Terms Library administrators as well as contract authors can preview the content of a template by selecting the preview icon. For example, a contract author may want to preview a template to verify they are selecting the correct one. The preview lists all the clauses and sections the template contains and any boilerplate included in the layout template. It does not list any additional clauses inserted by Contract Expert rules.

You can create different layout templates for each contract terms template. You specify the layout template to be used for the preview on the General tab while editing the contract terms template. The sample layout template is:


File Name

Description

Location in BI Publisher Catalog Directory

ContractTermsTemplate

This layout template specifies the layout of the contract terms template preview.

Enterprise Contracts/Contract Terms Printing/Contract Terms Download and Preview

Previewing and Importing Clauses

The application uses the clause layout template for:

You can specify which template you want to use in a specific business unit using either the Specify Customer Contract Business Function Properties or the Specify Supplier Contract Business Function Properties tasks. These tasks are available in the Setup and Maintenance work area.

The sample layout template provided is:


File Name

Description

Location in BI Publisher Catalog Directory

ContractTermsLibraryClause

Specifies the layout of clause text in the Contract Terms Library.

Enterprise Contracts/Contract Terms Printing/Clause Export and Preview

Frequently Asked Questions or Contract Preview and Printing

Can you still print the contract if there are no layout templates specified for a contract type?

No, you cannot print or create a PDF of a contract if no contract layout template is specified in the contract type that was used to create the contract. If you do not specify the terms layout template, then you cannot preview the contract terms as a PDF.

What's a layout template?

RTF document that contains the contract layout for printing and preview.

The templates, which can include both formatting, graphics, text, and other layout elements, are stored in the Oracle BI Publisher library. You must specify layout templates when you create a contract type to enable contract printing and the preview of contract terms templates.