How Revenue and Cost data is displayed depends heavily on what items are attached to the transactions and the type of Contract the transaction is associated to.

Revenue

Level	Sponsored / Awards	General	Note
Contract ID	Contracts can have multiple contract lines, but Contract Lines only apply to 1 Contract Contract ID = Award ID Sponsored Contract aka Award	Contracts can have multiple contract lines, but Contract Lines only apply to 1 Contract	Sponsored Contracts are also known as Awards
Contract Line ID	Contract Lines should only have 1 project per line, if not, then this is a set up issue. Projects can apply to multiple Contract Lines per Contract.	Contract Lines should only have 1 project per line, if not, then this is a set up issue. Projects can apply to multiple Contract Lines per Contract or multiple Contract Lines across multiple Contracts	FINAH-Contract-View lives at this level
Project ID	Projects only apply to 1 Award but an Award can have multiple Projects. A project should not be used between multiple awards. It does not apply to our business process. however, Oracle allows it and has happened in error.	Projects can apply to multiple Contract Lines per Contract or multiple Contract Lines across multiple Contracts
Task ID	Tasks only apply to 1 Project but a Project can have multiple Tasks.	Tasks only apply to 1 Project but a Project can have multiple Tasks	Task Transactions include the Task Distribution + Revenue Distribution + Accounting Period + Contract ID + Contract Line ID FINAH-ContractRevenue-View lives at this level

Revenue Transactions can come in connected to Contract ID (required) + Contract Line ID (required) + Project ID (optional) + Task ID (optional).
- Because Task ID and Project ID are optional they are sometimes missing. Therefore, you cannot add up the Task ID revenue to equal any of the other level's revenue. You also cannot add up the Project ID revenue to equal any of the other level's revenue.
- Because Contract Line and Contract are required, you can add up the Contract Line Revenue to equal the related Contract Revenue.
If Revenue comes in at Contract ID or Contract Line ID level, the Contract/Contract Line can still have Projects and Tasks associated but the Revenue will be listed as $0 for those Tasks and Projects because Oracle does not distribute it to the lower levels.
- Example where Project revenue total does not match Contract Line revenue as some revenue came in at Contract Line only: Contract 170010-00001, Version 5 Financial Summary
- Example where Project revenue total does not match Contract Line revenue as some revenue came in at Contract Line only: Contract 111461-0001, Version 3 Financial Summary
If Revenue comes in at the Project ID level, the Project can still have Tasks associated but the Revenue will be listed as $0 for those Tasks because Oracle does not distribute it to the lower levels.
Going forward, it is expected that all revenue will come in attached to Project ID and Task ID. FINAH reflects the same levels as seen in Oracle.

$$ Booking	FINAH-Contract-View	FINAH-ContractRevenue-View
$$ booked at Contract	Contract = $$ Contract Line = does not exist in Oracle, null in FINAH Project = not applicable for this view Task = not applicable for this view	Contract = $$ Contract Line = does not exist in Oracle, null in FINAH Project = does not exist in Oracle, null in FINAH Task = does not exist in Oracle, null in FINAH
$$ booked at Contract Line	Contract = $$ Contract Line = $$ Project = does not exist in Oracle, null in FINAH Task = not applicable for this view	Contract = $$ Contract Line = $$ Project = does not exist in Oracle, null in FINAH Task = does not exist in Oracle, null in FINAH
Project	Contract = $$ Contract Line = $$ Project = $$ only if 1 Project per Contract Line Task = not applicable for this view	Contract = $$ Contract Line = $$ Project = $$ Task = does not exist in Oracle, null in FINAH
Task	Not applicable for this view	Contract = $$ Contract Line = $$ Project = $$ Task = $$

Costs

Level

Sponsored

General

Note

Contract ID

Contract ID = Award ID

Use Award ID from Project ID + Budget Period

Use Contract ID from Expenditure Transaction.

Sponsored Contracts are also know as Awards

Project ID

Projects only apply to 1 Award but an Award can have multiple Projects

Project can appear on multiple Contracts, so it's critical to use the Contract ID from the transaction info

Task ID

Tasks only apply to 1 Project but a Project can have multiple Tasks

Tasks only apply to 1 Project but a Project can have multiple Tasks

Expenditure Transactions include the Expenditure Distribution + Accounting Period + Contract ID

Browser not supported