How Project Costs are Validated

The application validates cost transactions for data entry, standard business rules, transaction controls, and budgetary control that you set up during implementation.

Setup Options: Transaction Validation

The following table describes the setup options at various levels for validating the project costs.

Setup Level	Validation
Transaction Document Document Entry	Import and accounting options
Project Type	Transaction processing options
Project Task	Transaction controls

Data entry and business rule validations are performed when you create transactions. You can also validate transactions from third-party and certain Oracle Fusion applications before importing them.

How Costs Are Validated

The following table describes the different types of validations performed on project cost transactions.

Validation	Description
Data Entry	The application validates the project name, project number, task name, and task number.
Business Rules	Transaction sources must be valid. Document and document entry must be valid for the transaction source. Transactions aren't charged to a project template or an intercompany provider project. Transactions are billable only if the project type is enabled for billing. Transactions must have an active expenditure type. Transactions with negative quantities must have matching expenditure items, unless they are unmatched transactions. Expenditure item dates must be within expenditure organization dates. Usage item dates must be within the nonlabor resource organization dates. Project status determines whether you can enter new transactions. Expenditure items must be within the project date range. Transaction controls must allow charges of this expenditure type. Tasks for transactions must be lowest level tasks and chargeable. You must charge expenditure items to tasks within the task date range. Employees must be active and have valid human resource assignments for the expenditure item dates.
Transaction Control	All transaction controls based on combinations of project, task, expenditure category, expenditure type, nonlabor resource, person, job, organization, and system person type must pass validation.
Budgetary Control	The application validates transaction amounts against budgetary control that is set at the award and funding source segments or at the project or project and top resource levels. Both actual raw costs and actual burdened costs are checked for funds validation. Only the transactions that fail funds check in a batch are excluded from further processing.

The application tracks validation errors and the corrective actions. You can view the rejected transactions in the Manage Unprocessed Costs page, and rejected adjustment transactions in the Manage Project Costs page. You can reprocess the transactions after fixing the errors.

Validation rules vary for uncosted labor transactions, uncosted nonlabor transactions, and costed and accounted transactions. The following example provides validation checks for uncosted labor transactions.

Example: Validation Checks for Uncosted Labor Transactions

The application validates uncosted labor cost transactions for the following attributes.

Validation Attribute	Criteria
Business Unit Name	Required
Transaction Source	Required
Transaction Document	Required Valid for the expenditure item date
Transaction Document Entry The combination of transaction source, transaction document, and transaction document entry must be valid.	Required Valid for the expenditure item date
Project	Project number or name is required Enabled for cross-charge processing Not a project template Active for the expenditure items date Valid project status that allows creation of new transactions
Task	Valid task number or name Active for the expenditure item date Chargeable
Expenditure Item Date	Required
Expenditure Type	Required Valid and active for the expenditure item date, project unit, and expenditure type class associated to the document entry of the transaction
Organization If you don't provide the organization, the application derives the organization based on the primary human resources assignment of the person.	Active expenditure-owning valid for the expenditure item date If the organization isn't the same as the organization assigned to the primary assignment of the person in HCM, and the transaction document setup doesn't allow for override of person organization, then organization validation fails.
Person If you don't provide the assignment, then the application derives the primary assignment, job, and expenditure organization from the primary assignment of the person for the expenditure item date.	Valid person name or number Valid person assignment that is active for the expenditure item date
Time Card Quantity	Required