This section explains how project transactions are synchronized between Finance and Operations and Project Operations using dual-write. Whenever a project transaction is posted or updated in Finance and Operations, a corresponding transaction is automatically created or updated in Project Operations. Only transactions originating in Finance and Operations are synchronized.
Go to projects360 integrations > Periodic tasks > Project Operations integration > Create actuals in PO
Hour transactions
Project Operations automatically reflects any actual time transactions recorded in Finance and Operations through dual-write synchronization. This process creates or updates two corresponding “Actual” transactions in Project Operations: one for “Cost” and another for “Revenue”.
Cost transaction
Details of field specifications in Project Operations when the actuals are integrated from Finance and Operations:
Fields | Description |
Record Id | ‘Record Id’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Transaction Class | Fixed value: ‘Time’ |
Transaction Type | Fixed value: ‘Cost’ |
Not-to-exceed Status | ‘Not Applicable’ |
Adjustment Status ID | If ‘Invoice status’ is ‘Adjusted’ in Finance and Operations, then set as ‘Adjusted’ in Project Operations. Otherwise, set as ‘Unadjustable’. |
Document Date | ‘Project date’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Project Contract ID | Initialize by ‘Contract’ field from Project in Project Operations. |
Project Contract Line | Initialize by ‘Contract Line’ from Project in Project Operations. (Write-In Product) |
Project Contract Line Customer | Initialize by ‘Contract Line’ from Project in Project Operations. (Customer associated) |
Project ID | ‘Main project’ (Project level zero) related with Project Id from ‘ProjEmplTrans’ in Finance and Operations. |
Task ID | For project employee transactions (ProjEmplTrans) in Finance and Operations, the system associates them with tasks based on the following logic: 1) If an “Activity number” is present, the “Task ID” linked to that activity is used. 2) If no activity number exists but a parent project is identified, the “Task ID” related to the corresponding subproject is employed. |
Resource role ID | ‘Role Id’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Resource Id | ‘Resource’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Transaction category ID | ‘Category’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Contracting Unit | Blank |
Resourcing Company | ‘Legal entity’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Resourcing Unit | Blank |
Quantity | ‘Hours’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Unit of measure | Defaults from Transaction category |
Price | ‘Cost price’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Amount | ‘Total cost amount’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Tax | Blank |
Extended Amount | ‘Total cost amount’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Currency | ‘Sales currency’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Billing Type | Convert ‘Line property’ field using parameters ‘Billing type defaults’ from ‘projects360 integration parameters’ |
Created On | Date and time on which transaction is created in Project Operations. |
Revenue transaction
Details of field specifications in Project Operations when the actuals are integrated from Finance and Operations:
Fields | Description |
Record Id | ‘Record Id’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Transaction Class | Fixed value: ‘Time’ |
Transaction Type | If ‘Invoice’ field from ‘ProjEmplTrans’ in Finance and Operations has a value, then apply ‘Billed Sales’ value. Otherwise, apply ‘Unbilled Sales’ value. |
Not-to-exceed Status | ‘Not Applicable’ |
Adjustment Status ID | If ‘Invoice status’ is ‘Adjusted’ in Finance and Operations, then set as ‘Adjusted’ in Project Operations. Otherwise, set as ‘Unadjustable’. |
Document Date | ‘Project date’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Project Contract ID | Initialize by ‘Contract’ field from Project in Project Operations. |
Project Contract Line | Initialize by ‘Contract Line’ from Project in Project Operations. (Write-In Product) |
Project Contract Line Customer | Initialize by ‘Contract Line’ from Project in Project Operations. (Customer associated) |
Project ID | ‘Main project’ (Project level zero) related with Project Id from ‘ProjEmplTrans’ in Finance and Operations. |
Task ID | If ‘Activity number’ is populated in ProjEmplTrans, then use Task Id related with activity in Finance and Operations. If there is no activity but there is a parent project, then use Task Id related with subproject in Finance and Operations. |
Resource role ID | ‘Role Id’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Resource Id | ‘Resource’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Transaction category ID | ‘Category’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Contracting Unit | Blank |
Resourcing Company | ‘Legal entity’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Resourcing Unit | Blank |
Quantity | ‘Hours’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Unit of measure | Defaults from Transaction category |
Price | ‘Sales price’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Amount | ‘Total sales amount’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Tax | Blank |
Extended Amount | ‘Total sales amount’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Currency | ‘Sales currency’ field value from ‘ProjEmplTrans’ in Finance and Operations. |
Billing Type | Convert ‘Line property’ field using parameters ‘Billing type defaults’ from ‘projects360 integration parameters’ |
Created On | Date and time on which transaction is created in Project Operations. |
Expense transaction
Recorded actual expense transactions from Finance and Operations are automatically reflected in Project Operations through dual-write synchronization. This process creates or updates two corresponding “Actual” transactions in Project Operations: one for “Cost” and another for “Revenue”.
Cost transaction
Details of field specifications in Project Operations when the actuals are integrated from Finance and Operations:
Fields | Description |
Record Id | ‘Record Id’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Transaction Class | Fixed value: ‘Expense’ |
Transaction Type | Fixed value: Cost |
Not-to-exceed Status | ‘Not Applicable’ |
Adjustment Status ID | If ‘Invoice status’ is ‘Adjusted’ in Finance and Operations, then set as ‘Adjusted’ in Project Operations. Otherwise, set as ‘Unadjustable’. |
Document Date | ‘Project date’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Project Contract ID | Initialize by ‘Contract’ field from Project in Project Operations. |
Project Contract Line | Initialize by ‘Contract Line’ from Project in Project Operations. (Write-In Product) |
Project Contract Line Customer | Initialize by ‘Contract Line’ from Project in Project Operations. (Customer associated) |
Project ID | ‘Main project’ (Project level zero) related with Project Id from ‘ProjCostTrans’ in Finance and Operations. |
Task ID | If ‘Activity number’ is populated in ProjCostTrans, then use Task Id related with activity in Finance and Operations. If there is no activity but there is a parent project, then use Task Id related with subproject in Finance and Operations. |
Resource role ID | ‘Role Id’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Resource Id | ‘Resource’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Transaction category ID | ‘Category’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Contracting Unit | Blank |
Resourcing Company | ‘Legal entity’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Resourcing Unit | Blank |
Quantity | ‘Quantity’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Unit of measure | Defaults from Transaction category. |
Price | ‘Cost price’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Amount | ‘Total cost amount’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Tax | Blank |
Extended Amount | ‘Total cost amount’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Currency | ‘Sales currency’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Billing Type | Convert ‘Line property’ field using parameters ‘Billing type defaults’ from ‘projects360 integration parameters’ |
Created On | Date and time on which transaction is created in Project Operations. |
Revenue transaction
Details of field specifications in Project Operations when the actuals are integrated from Finance and Operations:
Fields | Description |
Record Id | ‘Record Id’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Transaction Class | Fixed value: ‘Expense’ |
Transaction Type | If ‘Invoice’ field from ‘ProjCostTrans’ in Finance and Operations has a value, then apply ‘Billed Sales’ value. Otherwise, apply ‘Unbilled Sales’ value. |
Not-to-exceed Status | ‘Not Applicable’ |
Adjustment Status ID | If ‘Invoice status’ is ‘Adjusted’ in Finance and Operations, then set as ‘Adjusted’ in Project Operations. Otherwise, set as ‘Unadjustable’. |
Document Date | ‘Project date’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Project Contract ID | Initialize by ‘Contract’ field from Project in Project Operations. |
Project Contract Line | Initialize by ‘Contract Line’ from Project in Project Operations. (Write-In Product) |
Project Contract Line Customer | Initialize by ‘Contract Line’ from Project in Project Operations. (Customer associated) |
Project ID | ‘Main project’ (Project level zero) related with Project Id from ‘ProjCostTrans’ in Finance and Operations. |
Task ID | If ‘Activity number’ is populated in ProjCostTrans, then use Task Id related with activity in Finance and Operations. If there is no activity but there is a parent project, then use Task Id related with subproject in Finance and Operations. |
Resource role ID | ‘Role Id’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Resource Id | ‘Resource’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Transaction category ID | ‘Category’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Contracting Unit | Blank |
Resourcing Company | ‘Legal entity’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Resourcing Unit | Blank |
Quantity | ‘Quantity’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Unit of measure | Defaults from Transaction category |
Price | ‘Sales price’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Amount | ‘Total sales amount’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Tax | Blank |
Extended Amount | ‘Total sales amount’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Currency | ‘Sales currency’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Billing Type | Convert ‘Line property’ field using parameters ‘Billing type defaults’ from ‘projects360 integration parameters’ |
Created On | Date and time on which transaction is created in Project Operations. |
Fee transactions
Actual fee transactions recorded will be created or updated in Project Operations from Finance and Operations. This syncing process will create or update only one ‘Actual’ transactions in Project Operations i.e., a ‘Revenue’ transaction.
Revenue transaction
Details of field specifications in Project Operations when the actuals are integrated from Finance and Operations:
Fields | Description |
Record Id | ‘Record Id’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Transaction Class | Fixed value: ‘Fee’ |
Transaction Type | If ‘Invoice’ field from ‘ProjRevenueTrans’ in Finance and Operations has a value, then apply ‘Billed Sales’ value. Otherwise, apply ‘Unbilled Sales’ value. |
Not-to-exceed Status | ‘Not Applicable’ |
Adjustment Status ID | If ‘Invoice status’ is ‘Adjusted’ in Finance and Operations, then set as ‘Adjusted’ in Project Operations. Otherwise, set as ‘Unadjustable’. |
Document Date | ‘Project date’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Project Contract ID | Initialize by ‘Contract’ field from Project in Project Operations. |
Project Contract Line | Initialize by ‘Contract Line’ from Project in Project Operations. (Write-In Product) |
Project Contract Line Customer | Initialize by ‘Contract Line’ from Project in Project Operations. (Customer associated) |
Project ID | ‘Main project’ (Project level zero) related with Project Id from ‘ProjCostTrans’ in Finance and Operations. |
Task ID | If ‘Activity number’ is populated in ProjCostTrans, then use Task Id related with activity in Finance and Operations. If there is no activity but there is a parent project, then use Task Id related with subproject in Finance and Operations. |
Resource role ID | Blank |
Resource Id | Blank |
Transaction category ID | ‘Category’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Contracting Unit | Blank |
Resourcing Company | ‘Legal entity’ field value from ‘ProjCostTrans’ in Finance and Operations. |
Resourcing Unit | Blank |
Quantity | ‘Quantity’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Unit of measure | Defaults from Transaction category |
Price | ‘Sales price’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Amount | ‘Total sales amount’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Tax | Blank |
Extended Amount | ‘Total sales amount’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Currency | ‘Sales currency’ field value from ‘ProjRevenueTrans’ in Finance and Operations. |
Billing Type | Convert ‘Line property’ field using parameters ‘Billing type defaults’ from ‘projects360 integration parameters’ |
Created On | Date and time on which transaction is created in Project Operations. |
Go to Projects > Projects > Actuals tab