Skip to main content

Cross-Validation Rules


A key flexfield can perform automatic cross-validation of segment values according to rules your organization defines when you customize the key flexfield. You can use cross-validation to closely control the creation of new key flexfield combinations, and you can maintain a consistent and logical set of key flexfield combinations that you need to run your organization.
What is Cross-Validation?
Cross-validation (also known as cross-segment validation) controls the combinations of values you can create when you enter values for key flexfields. A cross-validation rule defines whether a value of a particular segment can be combined with specific values of other segments. Cross-validation is different from segment validation, which controls the values you can enter for a particular segment.
You use cross-validation rules to prevent the creation of combinations that should never exist (combinations with values that should not coexist in the same combination). For example, if your organization manufactures both computer equipment and vehicles such as trucks, you might want to prevent the creation of "hybrid" part numbers for objects such as "truck keyboards" or "CPU headlights".

As another example, if you use the Accounting Flexfield, you may decide that all revenue accounts must have a department. Therefore, all your "revenue" account values (such as all values between 4000 and 5999) must have a corresponding department value other than 000 (which means "non-specific").
For example, suppose you have an Accounting Flexfield where you have a Company or Organization segment with two possible values, 01 and 02. You also have a Natural Account segment, with many possible values, but your company policy requires that Company or Organization 01 uses the natural account values 001 to 499 and Company or Organization 02 uses the natural account values 500 to 999. You can create cross-validation rules to ensure that users cannot create a GL account with combinations of values such as 02-342 or 01-750, for example.

Comments

Post a Comment

Popular posts from this blog

Applying Prepayments to Invoices

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites The invoice type is Standard, Mixed, or Expense Report. Today's date is on or after the Settlement Date of the prepayment. The invoice date is on or after the date of the prepayment. The prepayment is type Temporary, fully paid, validated, not cancelled, has no active holds, and has not already been fully applied. The prepayment has the same supplier, invoice currency and payment currenc...
1 comment
Read more

Overview of Encumbrance Accounting

With General Ledger you can record pre-expenditures commonly known as encumbrances. The primary purpose of tracking encumbrances is to avoid overspending a budget. Encumbrances can also be used to predict cash outflow and as a general planning tool. To use the full capabilities of encumbrance accounting, you must enable the budgetary control flag for a set of books. When you enable the budgetary control flag, the system automatically creates encumbrances from requisitions, purchase orders and other transactions originating in feeder systems such as Purchasing and Payables. When you do not enable the budgetary control flag, you can still enter manual encumbrances via journal entry, but you cannot generate encumbrances from requisitions and purchase orders. You have two options for using encumbrance data to monitor over-expenditure of a budget: After actuals and encumbrances have been posted, you can generate reports to show over-expenditures. You can also can use funds checking to preve...
Post a Comment
Read more

Apply/Unapply Prepayments Window Reference

Payables provides two ways to apply prepayments to an invoice. You can do either of the following: i-> Create or query an invoice and apply one or more prepayments to the invoice. ii-> Create or query the prepayment and apply it to one or more invoices. Selecting an Invoice and Applying it to a Prepayment When you select an invoice and choose the Apply/Unapply Prepayment option in the Invoice Actions window, the Apply/Unapply Prepayments window opens. It automatically displays all prepayments that have been applied to the invoice, and all available Prepayment distributions that you can apply to the invoice. Payables displays prepayment item type distributions that meet the following criteria: same supplier, and invoice currency as the invoice. The prepayment's Settlement Date is on or before today's date. The prepayment's date is on or before the date of the invoice. The prepayment is type Temporary with a status of Available. If you use Automatic Offsets, you can se...
Post a Comment
Read more