| Code |
Meaning |
Description |
| F01 |
Budgetary control failed due to invalid budgeted task |
Budgetary control failed due to invalid budgeted task |
| F02 |
Budgetary control failed: Invalid parent resource member |
Budgetary control failed due to invalid parent resource member |
| F03 |
Budgetary control failed due to invalid top task |
Budgetary control failed due to invalid top task |
| F04 |
Budgetary control failed due to invalid award number |
Budgetary control failed due to invalid award number |
| F05 |
Budgetary control failed during budget period derivation |
Budgetary control failed during budget period derivation |
| F06 |
Budgetary control failed during burden calculation |
Budgetary control failed during burden calculation |
| F07 |
Budgetary control failed during burden posting |
Budgetary control failed during burden posting |
| F08 |
Adjusted transaction has not been funds checked |
Adjusted transaction has not undergone budgetary control validation |
| F09 |
Budgetary control failed due to incomplete transfer of data |
Budgetary control failed due to incomplete transfer of data |
| F10 |
Transaction failed budgetary control at award level |
Transaction failed budgetary control at award level |
| F100 |
Insufficient funds |
Insufficient funds |
| F101 |
No budget exists at the resource level |
No budget exists at the resource level |
| F102 |
No budget exists at the resource group level |
No budget exists at the resource group level |
| F103 |
No budget exists at the task level |
No budget exists at the task level |
| F104 |
No budget exists at the top task level |
No budget exists at the top task level |
| F105 |
No budget exists at the project level |
No budget exists at the project level |
| F106 |
No budget exists at the project account level |
No budget exists at the project account level |
| F107 |
The transaction account and the budget account are different |
The transaction account and the budget account are different |
| F108 |
The transaction failed funds check at the resource level |
The transaction failed budgetary control at the resource level |
| F109 |
The transaction failed funds check at resource group level |
The transaction failed budgetary control at the resource group level |
| F110 |
The transaction failed budgetary control at the task level |
The transaction failed budgetary control at the task level |
| F111 |
The transaction failed funds check at the top task level |
The transaction failed budgetary control at the top task level |
| F112 |
The transaction failed budgetary control at the project level |
The transaction failed budgetary control at the project level |
| F113 |
The transaction failed funds check at project account level |
The transaction failed budgetary control at project account level |
| F114 |
The transaction failed to populate burden cost |
The transaction failed to populate burden cost |
| F115 |
Failed due to insufficient funds to cover burden cost |
Budgetary control failed because of insufficient funds to cover burden cost |
| F116 |
Failed due to insufficient funds to cover raw cost |
Budgetary control failed because of insufficient funds to cover raw cost |
| F117 |
Failed due to errors in cost distribution |
The transaction failed because of errors in one or more cost distribution lines |
| F118 |
Budgetary control failed due to invalid budget versions |
Budgetary control failed due to invalid budget versions |
| F119 |
Failed because year end rollover process is in progress |
Failed because year end rollover process is in progress |
| F120 |
Budgetary control failed during setup and summarization |
Budgetary control failed during setup and summarization |
| F121 |
The resource list is invalid or null |
The resource list is invalid or null |
| F122 |
The amount type or boundary code is invalid |
The amount type or boundary code is invalid |
| F123 |
The amount type or boundary code is invalid for no time phase |
The amount type or boundary code is invalid for no time phase |
| F124 |
Invalid boundary code for amount type ''Project to date'' |
The boundary code for amount type ''Project to date'' is invalid |
| F125 |
Invalid boundary code for amount type ''Year to date'' |
Invalid boundary code for amount type ''Year to date'' |
| F127 |
Invalid boundary code for amount type ''Period to date'' |
Invalid boundary code for amount type ''Period to date'' |
| F128 |
Budgetary control failed due to invalid resource list member |
Budgetary control failed due to invalid resource list member |
| F129 |
Start date or end date is null for the specified date range |
Start date or end date is null for the specified date range |
| F130 |
Not able to derive PA date |
Not able to derive PA date |
| F131 |
Invalid budget entry method or missing baseline version |
Invalid budget entry method or missing baseline version |
| F132 |
Could not map to a budget line while deriving budget account |
Could not map to a budget line while deriving budget account |
| F134 |
Not able to derive GL date |
Not able to derive GL date |
| F135 |
The encumbrance type is null or invalid |
The encumbrance type is null or invalid |
| F136 |
Funds check failed while calculating start date or end date |
Budgetary control failed while calculating start date or end date |
| F137 |
No matching requisition was found for this purchase order |
No matching requisition was found for this purchase order |
| F138 |
No matching purchase order was found for this invoice |
No matching purchase order was found for this invoice |
| F140 |
Failed due to fatal error while inserting burden cost |
Budgetary control failed due to fatal error while inserting burden cost |
| F141 |
Could not acquire lock: funds checks are running concurrently |
Lock not acquired due to concurrent budgetary control validations |
| F142 |
Budgetary control failed due to unexpected error |
Budgetary control failed due to unexpected error |
| F143 |
Funds check failed because budget baselining is in progress |
Budgetary control failed because baseline process is in progress |
| F144 |
Budgetary control failed for the unreserve mode |
Budgetary control failed for the unreserve mode |
| F145 |
Budgetary control failed for the baseline mode |
Budgetary control failed for the baseline mode |
| F146 |
Budgetary control failed for the reserve mode |
Budgetary control failed for the reserve mode |
| F150 |
The GL budgetary control failed for the check funds mode |
The GL budgetary control failed for the check funds mode |
| F151 |
The GL budgetary control encountered fatal errors |
The GL budgetary control encountered fatal errors |
| F152 |
The CBC budgetary control failed for the check funds mode |
The CBC budgetary control failed for the check funds mode |
| F153 |
The CBC budgetary control encountered fatal errors |
The CBC budgetary control encountered fatal errors |
| F155 |
The GL budgetary control failed for the full mode |
The GL budgetary control failed for the full mode |
| F156 |
The GL budgetary control failed for the partial mode |
The GL budgetary control failed for the partial mode |
| F157 |
The CBC budgetary control failed for the full mode |
The CBC budgetary control failed for the full mode |
| F158 |
The CBC budgetary control failed for the partial mode |
The CBC budgetary control failed for the partial mode |
| F160 |
Budgetary control failed to generate the return code |
Budgetary control failed to generate the return code |
| F161 |
Budgetary control failed to create encumbrance liquidation |
Budgetary control failed to create encumbrance liquidation |
| F162 |
Budgetary control failed to update budget account balances |
Budgetary control failed to update budget account balances |
| F163 |
Budgetary control failed while posting burden cost to GL |
Budgetary control failed while posting burden cost to GL |
| F164 |
Budgetary control failed while posting burden cost to CBC |
Budgetary control failed while posting burden cost to CBC |
| F165 |
No budget account on raw line |
No budget account on raw line |
| F166 |
No baselined budget version exists for this project |
No baselined budget version exists for this project |
| F168 |
Encumbrance accounting event could not be created |
Encumbrance accounting event could not be created |
| F169 |
Account changed for a budget line with existing transaction |
Account changed for a budget line with existing transaction |
| F170 |
Transaction failed in full mode |
Transaction failed in full mode |
| F172 |
Oracle Subledger Accounting engine failed |
Oracle Subledger Accounting engine failed |
| F173 |
Distribution record missing in General Ledger table |
Distribution record missing in General Ledger table |
| P101 |
Budgetary control passed at the project account level |
Transaction passed budgetary control at the project account level |
| P102 |
Budget exceeded but funds approved at Project Account Level |
Transaction passed budgetary control at project account level in advisory mode |
| P103 |
Budgetary control passed at the project level |
Transaction passed budgetary control at project level |
| P104 |
Budget exceeded but funds approved at Project Level |
Transaction passed budgetary control at project level in advisory mode |
| P105 |
Budgetary control passed at the top task level |
Transaction passed budgetary control at top task level |
| P106 |
Budget exceeded but funds approved at Top Task Level |
Transaction passed budgetary control at top task level in advisory mode |
| P107 |
Budgetary control passed at the task level |
Transaction passed budgetary control at task level |
| P108 |
Budget exceeded but funds approved at Task Level |
Transaction passed budgetary control at task level in advisory mode |
| P109 |
Budgetary control passed at the resource group level |
Transaction passed budgetary control at resource group level |
| P110 |
Budget exceeded but funds approved at Resource Group Level |
Budgetary control passed at resource group level in advisory mode |
| P111 |
Budgetary control passed at the resource level |
Transaction passed budgetary control at resource level |
| P112 |
Budget exceeded but funds approved at Resource Level |
Transaction passed budgetary control at resource level in advisory mode |
| P113 |
Increase in funds does not require funds check |
Increase in funds does not require budgetary control validation |
| P114 |
Invoice interfaced from projects does not require funds check |
Invoice interfaced from projects does not require funds check |
| P115 |
Expense report from projects requires no funds check |
Expense report from projects requires no funds check |
| P116 |
Transaction passed budgetary control in force pass mode |
Transaction passed budgetary control in force pass mode |
[Home] [Help]