Project budget fund check errors and corrective actions

Funds Check Result Messages

The following table lists funds check result codes and messages, and provides

information on responding to each message.

Result Code	Result Text	Corrective Action
F100	Insufficient Funds	Ensure that funds are available
F101	No budget exists at the resource level	Ensure that a budget exists at the resource level
F102	No budget exists at the resource group level	Ensure that a budget exists at the resource group level
F103	No budget exists at the task level	Ensure that a budget exists at the task level
F104	No budget exists at the top task level	Ensure that a budget exists at the top task level
F105	No budget exists at the project level	Ensure that a budget exists at the project level
F106	No budget exists at the project account level	Ensure that a budget exists at the project account level
F108	The transaction failed funds check at the resource level	Increase the budget at the resource level or change the budgetary control level to Advisoryor None
F109	The transaction failed funds check at resource group level	Increase the budget at the resource group level or change the budgetary control level to Advisoryor None
F110	The transaction failed funds check at the task level	Increase the budget at the task level or change the budgetary control level to Advisory or None
F111	The transaction failed funds check at the top task level	Increase the budget at the top task level or change the budgetary control level to Advisory or None
F112	The transaction failed funds check at the project level	Increase the budget at the project level or change the budgetary control level to Advisory or None
F113	The transaction failed funds check at project account level	Increase the budget amount at the project account level
F114	The transaction failed to populate burden cost	Contact your system administrator for assistance
F118	Funds check failed because of invalid budget versions	Create a baseline version for the project budget
F120	Funds check failed during setup and summarization	Contact your system administrator. Your system administrator can run funds validation with PA debug on to identify the error.
F121	The resource list is invalid or null	If the project budget is categorized by resource, then ensure that you assign a resource list to the budget
F122	The amount type or boundary code is invalid	Update the amount type or boundary code in the budgetary control settings for the project
F123	The amount type or boundary code is invalid for no time phase	To create a budget without time phases, select an amount type ofProject to Date and a boundary code of Project in the budgetary control settings for the project
F124	Invalid boundary code for amount type Project To Date	Contact your Oracle Projects super user for assistance. Your Oracle Projects super user can verify the amount type and boundary code combination for the project.
F125	Invalid boundary code for amount type Year To Date	Select either Year or Period as the boundary code in the budgetary control settings for the project
F127	Invalid boundary code for amount type Period To Date	Select Period to Date as the boundary code in the budgetary control settings for the project
F128	Funds check failed because of invalid resource list member	Verify that the resource list member is included in the resource list. If the member is included in the list, then ensure that the resource list member is valid.
F129	Start date or end date is null for the specified date range	For a budget with a Project to Dateamount type and Project boundary code, ensure that a budget line exists for the period or that you specify both a start date and an end date for the project.  For other amount type and boundary code combinations, ensure that a budget exists for the period associated with the transaction.
F130	Start date or end date is null for the specified PA period	For a budget with a Project to Dateamount type and Project boundary code, ensure that a budget line exists for the period or that you specify both a start date and an end date for the project.  In addition, ensure that the PA period is valid.
F131	Funds check failed because of invalid budget entry method	Ensure that the Burdened Costoption is enabled for the budget entry method
F132	Could not map to a budget line while deriving budget account	Ensure that budget lines are generated for all periods
F134	Start date or end date is null for the specified GL period	For a budget with a Project to Dateamount type and Project boundary code, ensure that a budget line exists for the period or that you specify both a start date and an end date for the project.  For a budget with a time phase of GL Period, ensure that the period is valid and that it is not set up as an adjustment period.
F136	Funds check failed while calculating start date or end date	Contact your system administrator.  Your system administrator can trace the process to obtain additional information.
F137	No matching requisition was found for this purchase order	Contact your system administrator.  Data issues can cause this error.
F138	No matching purchase order was found for this invoice	Contact your system administrator.  Data issues can cause this error.
F140	Failed due to fatal error while inserting burden cost	Contact your system administrator.  Your system administrator can trace the process to obtain additional information.
F141	Could not acquire lock: funds checks are running concurrently	Retry the funds check
F142	Funds check failed because of unexpected error	Contact your system administrator.  Your system administrator can trace the process to obtain additional information.
F143	Funds check failed because budget baselining is in progress	Retry the funds check after the baseline process for the budget is complete
F150	The GL funds check failed for the check funds mode	Decrease the project budget or increase the GL budget
F151	The GL funds check encountered fatal errors	Contact your system administrator.  Your system administrator can trace the process to obtain additional information.
F155	The GL funds check failed for the full mode	Decrease the project budget or increase the GL budget
F156	The GL funds check failed for the partial mode	Decrease the project budget or increase the GL budget
F160	Funds check failed to generate the return code	Contact your system administrator.  Your system administrator can trace the process to obtain additional information.
F162	Funds check failed to update budget account balances	Contact your system administrator.  Your system administrator can trace the process to obtain additional information.
F165	No budget account on raw line	Ensure that a budget account exists
F166	No baselined budget version exists for this project	Create a baseline version for the project budget
F168	Encumbrance accounting event could not be created	Contact your system administrator.  Your system administrator can review the log files to obtain additional information.  This error relates to setup for Oracle Subledger Accounting.  If you modified a predefined application accounting definition, then you must revalidate it. In addition, verify any modifications to the predefined subledger accounting setup.
F169	Account changed for a budget line with an existing transaction	Ensure that account has not been changed for a budget line with an existing transaction
F170	Transaction failed in full mode	A related transaction in the process failed. Fix the related distribution line that failed funds check and then rerun the funds check.
F172	Oracle Subledger Accounting application failed	Contact your system administrator.  Your system administrator can review the log files to obtain additional information.  This error relates to setup for Oracle Subledger Accounting.  If you modified a predefined application accounting definition, then you must revalidate it. In addition, verify any modifications to the predefined subledger accounting setup.
F173	Distribution record missing in General Ledger table	Contact your system administrator. Your system administrator can review the log files to obtain additional information.  This error relates to setup for Oracle Subledger Accounting.  If you modified a predefined application accounting definition, then you must revalidate it. In addition, verify any modifications to the predefined subledger accounting setup.

How to Update a Job Code for a Position

Once a position/job combination has been defined and saved, it cannot be changed.

Creating a new one is the only option. However, if you want the new Position to have the original Position name then the first Position name must be edited slightly.

Make a change to the Date Effective Name of the original Position (with the wrong job attached) and save the change as a Correction.

Then the application will allow you to create the new Position with the original name.