This appendix describes the seed data in Oracle Contracts.
This appendix covers the following topics:
The seeded responsibilities are:
Contracts Workbench Administrator
Contracts Workbench User
Contract Terms Library Administrator
This responsibility can be used only if the MO: Operating Unit profile option has a value that is assigned either at the site level or for this responsibility.
To create new responsibilities for the Contract Terms Library, use the following:
Root Menu: OKC Contracts Application HTML Root Menu
Data Group: Standard
Request Group: Contract Terms Request Group
To create new responsibilities for the Contracts Workbench, use the following:
Root Menu: OKC Contract Repository Root Menu
Request Group: Contract Repository Requests (available to the Contracts Workbench Administrator responsibility)
Note: Changing the seeded menu structure is not recommended. You must first customize the standard menus, and then create responsibilities.
The following table displays the seeded deliverables:
Name | Description |
---|---|
All Contractual Deliverables | All contractual deliverables. |
All Negotiation Deliverables | All negotiation deliverables. |
Buyer Contractual Deliverables | Contractual deliverables for which the buyer is the responsible party. |
Supplier Contractual Deliverables | Contractual deliverables for which the supplier is the responsible party. |
Supplier Negotiation Deliverables | Negotiation deliverables for which the supplier is the responsible party. |
The following table displays the seeded document types:
Name | Description | Document Class | Application |
---|---|---|---|
AUCTION | Auction | SOURCING | Oracle Sourcing |
AUCTION_RESPONSE | Bid | SOURCING | Oracle Sourcing |
B | Sales Agreement | SO | Oracle Order Management |
ISP_PO_REF | iSupplier view of PO documents | PO | Oracle iSupplier Portal |
O | Sales Order | SO | Oracle Order Management |
OKE_BUY | Project Contracts (Buy) | OKE | Oracle Project Contracts |
OKE_SELL | Project Contracts (Sell) | OKE | Oracle Project Contracts |
OKL | Lease Management | OKL | Oracle Lease Management |
OKS | Service Contracts | OKS | Oracle Service Contracts |
PA_BLANKET | Blanket Purchase Agreement | PO | Oracle Purchasing |
PA_CONTRACT | Contract Purchase Agreement | PO | Oracle Purchasing |
PO_STANDARD | Standard Purchase Order | PO | Oracle Purchasing |
PV_PARTNER_PROGRAM | Partner Program | POL | Oracle Partner Management |
QUOTE | Quote | QUOTE | Oracle Order Capture |
RFI | RFI | SOURCING | Oracle Sourcing |
RFI_RESPONSE | RFI Response | SOURCING | Oracle Sourcing |
RFQ | RFQ | SOURCING | Oracle Sourcing |
RFI_RESPONSE | Sourcing Quote | SOURCING | Oracle Sourcing |
A Relationship describes how the contracts are related. Some Related By values imply hierarchical information. Three values indicate that the related contract serves as a master (or parent) and three values indicate a subcontract (child) relationship.
The Related By values are predefined and they operate as pairs. For example, Master has a paired value of Release. Contract X is the contract of record and Contract M is related to Contract X as Master. When you view Contract M and its related contracts, the Related By value for Contract X is Release.
The following table contains the predefined Related By values and their paired values:
Related By | Hierarchy Value (if any) | Paired Value |
---|---|---|
Master | Parent | Release |
Release | Child | Master |
Umbrella | Parent | Governed By |
Governed By | Child | Umbrella |
General Contract | Parent | Subcontract |
Subcontract | Child | General Contract |
References | Referenced By | |
Referenced By | References | |
Renews | Renewed By | |
Renewed By | Renews | |
Replaces | Replaced By | |
Replaced By | Replaces | |
Related | Related |
Relationships between contracts and other documents are generally used in legal contexts. For example:
A master contract consolidates two or more separate but related contracts between the same counterparties into one legal document with overarching terms between the partners. If Contract A relates to Contract B as Master, then Contract B relates to Contract A as Release.
An umbrella contract can be used as a guideline for any future contract. If Contract A relates to Contract B as Umbrella, then Contract B relates to Contract A as Governed By.
A general contract is a prime contract that explains the purpose and significance of commonly used contract clauses. If Contract A relates to Contract B as General Contract, then Contract B relates to Contract A as Subcontract.
A reference contract is like a memo of understanding that you can use to guide your project. If Contract A relates to Contract B as References, then Contract B relates to Contract A as Referenced By.
Contract renewal extends the contract validation date. If Contract A relates to Contract B as Renews, then Contract B relates to Contract A as Renewed By.
Replacement of contract is to use a new statute or terms and conditions. If Contract A relates to Contract B as Replaces, then Contract B relates to Contract A as Replaced By.
Related is a general term. If Contract A relates to Contract B as Related, then Contract B relates to Contract A as Related.
To print contract documents and the Deviations reports, the application provides seeded layout templates in Oracle XML Publisher.
The layout templates are stored in the XML Publisher Layout Template repository.
The seeded layout templates for printing contract terms are:
Oracle Contract Terms Template
Contract Terms Template
Contract Terms Layout Template for iStore
Note: The Contract Terms Layout Template for iStore layout template does not print the clause title. It prints only the clause text under the respective sections.
The following table displays the seeded layout templates for the Deviations report:
Name | Type | Description |
---|---|---|
Contract Deviations Report Layout for Negotiation Response Documents - Sourcing | RTF | The template for the negotiation response documents such as RFQ, RFI, and auction |
Contract Deviations Sourcing Template | RTF | The main Rich Text Format template for Oracle Sourcing |
Contract Deviations Order Management Template | RTF | The main Rich Text Format template for Oracle Order Management |
Contract Deviations Template for Quoting | RTF | The main Rich Text Format template for Oracle Quoting |
Contract Deviations Purchasing Template | RTF | The main Rich Text Format template for Oracle Purchasing |
Contract Deviations Report Template | RTF | Subtemplate for contract deviations summary details |
Contracts RTE Handler Template | XSL-FO | Subtemplate for handling HTML tags that are used in Rich Text Editor for contracts |
Contract Deviations Constants Template | XSL-FO | Subtemplate containing all context information |
Contract Deviations Variable Resolution Template | XSL-FO | Subtemplate for variables resolution |
Contract Deviations Table Variable Resolution for Sell Side | XSL-FO | Subtemplate for resolving the table-type variables in the sell-side documents |
Contract Header Preview Data Definition | XML | Fetches all the user defined attributes for a particular contract type at the time of printing. However, the Layout Template selected must refer to the contract header preview data definition document and this can be modified to print the UDA in any required format. |
The following table lists the different types of notifications that are seeded in Oracle Contracts:
Type | Business Context | Description |
---|---|---|
Clauses | Clause submitted for approval | Notifies the global or local organization approvers when a global or local clause requires approval. |
Clauses | Global Clause approved | Sends a notification to the requestor and library administrators of local organizations when a global clause is approved. |
Clauses | Clause rejected | Sends a notification to the requestor in a global or local organization when a clause is rejected. |
Clauses | Auto-adoption of global clause | Sends a notification to the library administrator of a local organization when a global clause is automatically adopted in that organization. |
Clauses | Global clause available for adoption | Notifies the library administrator of a local organization when a global clause is available for adoption. |
Clauses | Clause requiring approval for adoption | Sends a notification that a global clause was adopted in a local organization and submitted for approval. |
Clauses | Clause adoption approved | Sends a notification that a global clause was approved for adoption in a local organization. |
Clauses | Clause adoption rejected | Sends a notification that a global clause was rejected for adoption in a local organization. |
Contract Templates | Contract template submitted for approval | Notifies global or local organization approvers when a global or local template requires approval. |
Contract Templates | Contract template approved | Sends a notification to requestor when a contract template is approved. |
Contract Templates | Contract template rejected | Sends a notification to requestor in a global or local organization when a contract template is rejected. |
Contract Deliverables | Overdue notification | Sends a notification for overdue status on the due date of the deliverable. |
Contract Deliverables | Before due notification | Sends a notification prior to the due date of a deliverable. |
Contract Deliverables | Escalation notification | Sends a status notification to escalation assignee after the due date if the deliverable was performed. |
Contract Deliverables | Status change notification | Sends a notification when either party changes the status of the deliverable. |
Repository | Approval request notification | Notifies the contract approver when a contract requires approval. |
Repository | Contract approved notification | Notifies the contract approval requester that the contract has been approved. |
Repository | Contract rejected notification | Notifies the contract approval requester that the contract has been rejected. |
Repository | Contract expiration notification | Notifies the contract administrator that a contract is about to expire. |