You can mark expenditure items as converted when you load expenditure items from another system into Oracle Projects during conversion. To do this, you set the CONVERTED_FLAG to Y (for Yes) in the PA_EXPENDITURE_ITEMS_ALL table.
Some adjustment actions are not permitted for converted items. The following table shows which adjustment actions are and are not allowed for converted items.
| Adjustment Action | Allowed for Converted Items |
|---|---|
| Correct Approved Expenditure Item | YES |
| Allow Billing | YES |
| Billable to Non-Billable | NO |
| Non-Billable to Billable | NO |
| Capitalizable to Non-Capitalizable | NO |
| Non-Capitalizable to Capitalizable | NO |
| Billing Hold | YES |
| One-Time Hold | YES |
| Release Hold | YES |
| Recalculate Burden Cost | NO |
| Recalculate Raw Cost | NO |
| Recalculate Revenue | NO |
| Recalculate Cost/Revenue | NO |
| Change Comment | YES |
| Split | NO |
| Transfer | NO |
| Work Type | NO |
If an item is marked as converted, Oracle Projects assumes that the item does not have all the data required to support the recalculation of cost, revenue, and invoice. Therefore, you cannot perform the adjustment actions that may result in the recalculation of cost, revenue, or invoices for converted items.
Note: Marking items as converted has a similar effect to enabling the transaction source attribute that disallows adjustments on imported transactions originating from that source.