How are project transaction dates defaulted in Oracle Projects?

When you create project cost transactions outside Projects, such as supplier invoices in Oracle Payables, or purchase requisitions in Oracle Procurement, subledger applications use business rules to derive the project cost transaction date (also known as the expenditure item date).

In some applications, this date appears by default, but you may need to enter the date in a few other subledger applications, or alter the derived date if required.. When you import transactions from other subledgers into Oracle Project Costing, an understanding of how expenditure item dates are populated and saved in each of these subledgers can significantly simplify your task.

The derivation of the project cost transaction date depends on the functional flow, for example, procure-to-pay, time cards, and expenses.

Project Cost Transaction Date Derivation in the Procure-to-Pay Flow

The Procure-to-Pay (P2P) flow refers to the process of procuring goods and services required for a project. This flow typically involves the following tasks:

Creating purchase requisitions
Generating purchase orders
Creating and processing invoices for payment
Creating the project cost

Project cost date derivation can be configured at each of these stages; however, here are the derivation rules that are shipped by default:

Project Cost Derivation in the Procure-to-Pay Flow when Period-End Accrual is Enabled for Matched Invoices

Here's a table that lists out the project cost date derivation rules that apply when period-end accrual is enabled for invoices that must match purchase orders associated with them. For a quick definition of period-end accrual, see Considerations for Accruing Expense Items in the Implementing Payables Invoice to Pay guide.

The same set of rules apply when the item is being purchased for an inventory destination.

Note:

You can't update the expenditure item date on a purchase order matched invoice. However you can use the Default Expenditure Item Date for Supplier Cost Transactions profile option to allow for a more current/accurate date to be derived and used on matched invoices.
For more information on profile options associated with Project Costing, see the Project Costing Profile Options section in the Oracle Fusion Cloud Project Management Profile Options page.

Project Cost Date Derivation Rules that Apply when Period-End Accrual is Enabled for Invoices that Must Match Purchase Orders

Task / Stage	Description	Project Cost Transaction Date Derivation	Additional Comments
Purchase Requisition Creation	Team member raises a purchase requisition that includes a request delivery date, for goods or services.	Defaults from the request delivery date.	NA
Purchase Order Creation	A member of the buyer team raises a purchase order for the goods or services required.	Derives from the request delivery date.	NA
Goods or Services Receipt	A member of the buyer team raises a receipt for goods or services received.	Matches the date of receipt.	If the team has enabled accrual on receipts, the actual project cost is brought in from the receipt and not from the invoice.
Invoicing	The vendor submits an invoice for the goods or services delivered.	Derives based on the settings in the Default Expenditure Item Date for Supplier Cost Transactions profile option.	If the date on a matched supplier invoice is not within the duration of a task, project, and award, the project administrator can use the earliest project, task, and award end date to override the project cost date on invoice distributions.
Project Cost Creation.	The project accountant creates the project cost in Projects.	Derives from the project cost date in the invoice.	If there is a difference between the project cost in the invoice and the receipts, then the project accountant brings in the additional cost update into Projects as a separate project cost.

Project Cost Derivation in the Procure-to-Pay Flow when Period-End Accrual is Enabled for Unmatched Invoices

Here's a table that lists out the project cost date derivation rules that apply when period-end accrual is enabled for (two-way or three-way) unmatched invoices. For a quick definition of period-end accrual, see Considerations for Accruing Expense Items in the Implementing Payables Invoice to Pay guide.

Project Cost Date Derivation Rules that Apply when Period-End Accrual is Enabled for Unmatched Invoices

Task / Stage	Description	Project Cost Transaction Date Derivation	Additional Comments
Invoicing	The vendor submits an invoice for goods or services delivered, but there aren't any matching purchase orders or requisitions.	Derives based on the settings in the Default Expenditure Item Date for Supplier Cost Transactionsprofile option.	If the date on a matched supplier invoice is not within the duration of a task, project, and award, the project administrator can use the earliest project, task, and award end date to override the project cost date on invoice distributions.
Project Cost Creation.	The project accountant creates the project cost in Projects.	Derives from the project cost date in the invoice.	NA

Project Cost Derivation in the Procure-to-Pay Flow when Accrual on Receipt is Enabled

Here's a table that lists out the project cost date derivation rules that apply when accrual on receipt is enabled.

Accrual on receipt ensures that project costs get created as goods are shipped and receipts are created. If buyers have enabled accrual on receipt on their purchase orders, the project accountant creates accounting entries against receipts and also bring in the project item if it's project related. If the supplier invoice that arrives (after all goods and services have been delivered) has a cost variation, the project accountant brings in the delta as a new project cost.

Project Cost Date Derivation Rules that Apply when Accrual on Receipt is Enabled

Task / Stage	Description	Project Cost Date Derivation	Additional Comments
Purchase Requisition Creation	Team member raises a purchase requisition that includes a request delivery date, for goods or services.	Defaults from the request delivery date.	NA
Purchase Order Creation	A member of the buyer team raises a purchase order for the goods or services required.	Derives from the request delivery date.	NA
Goods or Services Receipt	A member of the buyer team raises a receipt for goods or services received.	Matches the date of receipt.	If the team has enabled accrual on receipts, the actual project cost is brought in from the receipt and not from the invoice.
Invoicing	The vendor submits an invoice for the goods or services delivered.	Derives based on the settings in the Default Expenditure Item Date for Supplier Cost Transactions profile option.	If the date on a matched supplier invoice is not within the duration of a task, project, and award, the project administrator can use the earliest project, task, and award end date to override the project cost date on invoice distributions.
Project Cost Creation.	The project accountant creates the project cost in Projects.	Derives from the project cost date in the invoice.	If there is a difference between the project cost in the invoice and the receipts, then the project accountant brings in the additional cost update into Projects as a separate project cost.