Validation and Prevalidation (Oracle General Ledger Users' Guide)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Validation and Prevalidation

During validation and prevalidation, General Ledger will determine all the accounts that are defined by your source and target account specifications, perform validation checking on those accounts, and produce a Mass Maintenance Execution Report, showing any errors, such as:

Overlapping accounts

Disabled accounts

Target accounts that violate cross-validation rules

Move/merge transactions that violate the move/merge prerequisites and business rules

Validation is done automatically when you submit a move/merge request. However, since it is generally a good idea to run your move/merge operations during off-peak hours, you can choose to prevalidate before you submit the move/merge.

Running move/merge during off-peak hours minimizes system performance degradation and the possibility of the move/merge conflicting with other processes. Prevalidating helps ensure that an unattended move/merge operation completes successfully.

If a prevalidation request is successful, General Ledger will create your new target accounts if they do not already exist. The status displayed in the Mass Maintenance Workbench window will be Completed.

If a prevalidation request fails, General Ledger will only create those new target accounts which passed validation. Target accounts that do not pass validation will not be created. The status will be Failed. Review the Mass Maintenance Execution report and correct any noted problems before you submit your move/merge.

Note: If you update your segment values or accounts after a successful prevalidation, your move/merge operation may fail.

Validation and Prevalidation

See Also