A project contract is an agreement between two or more parties with certain terms and conditions associated with a project. Project contract varies with rules and businesses as defined mutually by the parties in consideration with the governing laws. It is a document with clauses applied to a particular project and its execution.
This chapter describes the following flows in Oracle Project Contracts:
Create the Setup Across Product for Project Contract.
Perform Closing Out or Terminate a Project Contract.
Create and Manage a Project Contact and its Deliverable Tracking System.
Author a Sub Contract From a Project Contract.
Create Setup for Change Management and Communications in Project Contract.
Create Setup for Change Management in Project Contract.
Create Setup for Communication Management in Project Contract.
Create a Project Contract and Perform Hold Management Action.
Create a Project Contract Verify Status and Perform Different Contract Operations.
Create a Funding Source for a Project in a Project Contract and Bill it.
Author a Project Contract.
Author a Document with Project Contract and Copy it.
Author a Project Contract and Check Security.
Author a Project Contract and Apply it to a Solicitation.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can set up project contracts.
None.
The following profile options must be set:
Table 40-1 Profile Options for Create the Setup across Product for Project Contract
| Profile | Value |
|---|---|
|
MO: Defaulting Operating Unit |
Vision Project Mfg |
|
MO: Operating Unit |
Vision Project Mfg |
Not applicable.
Not applicable.
This flow creates an invoice, verifies it once it is created, and then creates accounting on it.
None.
The following profile options must be set:
Table 40-2 Profile Options for Create the Setup across Product for Project Contract
| Profile | Value |
|---|---|
|
OKE: Allow Cross Org Access |
No |
|
PA: Cross Project User-Update |
Yes |
Not applicable.
Not applicable.
In this flow, the user can create a project contract and manage the associated attributes. The user can view the deliverables in the deliverable tracking system.
None.
The following profile options must be set:
Table 40-3 Profile Options for Create and Manage a Project Contact and its Deliverable Tracking System
| Profile | Value |
|---|---|
|
OKE: Allow Cross Org Access |
No |
|
PA: Cross Project User-Update |
Yes |
Not applicable.
Not applicable.
In this flow, the user can create a subcontract under a project contract. There can be many subcontracts to accomplish the whole project contract. The user can create many subcontracts under a project contract.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can set up change management and communication to accommodate various changes and communication once the project has started, and apply them accordingly in the project contract.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user sets up change management for creating change request affecting Authoring Workbench, Funding Workbench, Updating Contract and Comparing Versions of contact to accommodate various changes and its management once the project has started, and apply them accordingly in the project contract.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user sets up communication management to accommodate various changes and its management, such as, creating communication, updating communication, adding attachments to communication and deleting communication.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can create a project contract and perform the Hold Management action to accommodate various changes and its management.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can create a project contract, verify the status, and perform different operations to make the contract in accordance with the project, and manage it.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can author a project contract, navigate to Funding Workbench Administrator, and create a funding source for this contract and bill it.
None.
The following profile options must be set:
Table 40-4 Profile Options for Create a Funding Source for a Project in a Project Contract and Bill it
| Profile | Value |
|---|---|
|
OKE: Allow Cross Org Access |
No |
|
PA: Cross Project User-Update |
Yes |
Not applicable.
Not applicable.
In this flow, the user can author a project contract to create a contract, which can later be updated. The user can attach this to a project with stand by terms and conditions. The user can create this with the help of a template or wizard.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can author a project contract to create a contract and attach it to a project with stand by terms and conditions. The user can create this with the help of a template or wizard then, copy it to create a project contract.
None.
Not applicable.
Not applicable.
Not applicable.
In this flow, the user can author a project contract to create a contract, attach it to a project with stand by terms and conditions, and verify the security aspects. The user can access the contract and business details.
None.
Not applicable.
Not applicable.
Not applicable.