How External Commitment Transactions are Validated

Oracle Fusion Project Costing validates all external commitment transactions for a set of predefined and configurable criteria before importing them. External commitment transactions are validated against data entry, standard business rules, and transaction controls.

Settings That Affect External Commitment Transaction Validation

The import and accounting options that you specify at the following levels affect external commitment transactions validation.

Transaction document
Document entry
Project type
Transaction controls

How External Commitment Transactions Are Validated

Validation is a key step in external commitment transaction processing. The following table describes the different types of validations and sample rules within the validation type that govern the validation process.

Validations	Description
Data entry validation	For each commitment transaction, values must be provided for the following required attributes: Commitment transaction business unit ID or name Source ID or name Document ID or name Document entry ID or name Expenditure item date Project ID or name or number Task ID or name or number Expenditure type ID or name Commitment transaction expenditure organization ID or name Commitment transaction creation date Source application commitment transaction number Total commitment quantity Commitment transaction currency Original transaction reference All the provided values must be valid.
Business rule validation	Validations are performed to ensure the following: Costing and accounting attributes of the commitment transactions match with the source, document, and document entry options. Transactions are charged to a project and not a project template. The current project status allows new cost transactions to be incurred. Expenditure item lies within the project dates. Expenditure item lies within task transaction dates. Task is chargeable. Expenditure type of the external commitment transaction is active and is valid for the project unit. Expenditure organization is active. Expenditure item lies within expenditure organization dates.
Transaction control validation	If there are any transaction controls defined at the project or task level, then the application validates all defined transaction controls. The controls are based on combinations of project, task, expenditure category, expenditure type, system person type, and job.

Validations

Description

Data entry validation

For each commitment transaction, values must be provided for the following required attributes:

Commitment transaction business unit ID or name
Source ID or name
Document ID or name
Document entry ID or name
Expenditure item date
Project ID or name or number
Task ID or name or number
Expenditure type ID or name
Commitment transaction expenditure organization ID or name
Commitment transaction creation date
Source application commitment transaction number
Total commitment quantity
Commitment transaction currency
Original transaction reference

All the provided values must be valid.

Business rule validation

Validations are performed to ensure the following:

Costing and accounting attributes of the commitment transactions match with the source, document, and document entry options.
Transactions are charged to a project and not a project template. The current project status allows new cost transactions to be incurred. Expenditure item lies within the project dates.
Expenditure item lies within task transaction dates. Task is chargeable.
Expenditure type of the external commitment transaction is active and is valid for the project unit.
Expenditure organization is active.
Expenditure item lies within expenditure organization dates.

Transaction control validation

If there are any transaction controls defined at the project or task level, then the application validates all defined transaction controls. The controls are based on combinations of project, task, expenditure category, expenditure type, system person type, and job.

Data entry and business rule validations are performed when the administrator in the third-party application independently validates the external commitment transactions with Oracle Fusion Project Costing validation service or as a part of importing commitment transactions using Import External Commitment Transactions service in Oracle Fusion Project Costing.

If the transaction validation results in errors, the application tracks the errors including the cause of the error and the action needed to fix the error. You can review the validation errors in the output from the Oracle Fusion Project Costing external commitment transaction validation service.

Note: Validation rules vary for each transaction based on the transaction source, document and document entry setup, and controls defined for the project and task for which the commitment transaction is incurred.