In the Account Derivation Rules Conditions window, specify conditions for each rule detail line. Priorities determine the order in which account derivation rule conditions are examined. Depending on which of the defined conditions is met, a different account derivation rule detail is employed to create the account.
The Subledger Accounting program evaluates conditions based on the priority of the rule detail. If the conditions for a priority are met and the associated rule detail results in a valid account or segment value, no further priorities are evaluated. Otherwise, the Subledger Accounting program evaluates the conditions for the next priority until a valid account or segment value is derived or there are no more conditions to evaluate.
You can combine Accounting Flexfield rules with segment rules. In this case, Subledger Accounting uses the segment value derived from the segment rule to override the corresponding segment of the Accounting Flexfield. However, if the segment rule has conditions associated with the priorities and none of the conditions are met, no override occurs and therefore the segment value is derived from the Accounting Flexfield rule.
Account derivation rules conditions are created in the same manner as described in Defining Conditions for Journal Line Types.
If a source is a lookup code, Subledger Accounting displays its corresponding meaning in the appropriate language when it is used in header and line descriptions or supporting references. Also, when defining conditions in the AMB, Subledger Accounting displays the translated meaning to the user and stores the untranslated lookup code. Since the untranslated lookup code is used in conditions, conditions can function independently of the language used by the ledger.
Lookup types:
Reduce the number of source values that need to be stored in the transaction object
Help prevent errors by displaying valid, user friendly LOV names for sources that are lookup codes
Overcome many of the restrictions associated with translated sources
The following example illustrates the value of specific sources to set up an account derivation rule Condition.
Consider a rule HQ Capital Purchase as follows:
The rule is to be applied only if the distribution account cost center is the same as the liability account cost center and the Assets' tracking option is Yes. This condition can be expressed as:
Where
Distribution.Cost Center = Liability.Cost Center and
Asset Tracking option = Yes
The following tables describe the setup of the condition.
Account Derivation Rule Condition Example: Setup
| Seq. | ( | Source | Segment | Operator | Value Type | Value | Seg- ment | ) | And/Or |
|---|---|---|---|---|---|---|---|---|---|
| 1 | ( | Distribution Account | Cost Center | = | Source | Liability Account | Cost Center | ) | And |
| 2 | ( | Asset Flag | = | Constant | Yes | ) |
Now assume that the accounting event data, to which the account derivation rule and therefore the condition is applied, has two rows of data to be processed with the values described in the following table.
Account Derivation Rule Condition Example: Accounting Event Data
| Account | Invoice 1 | Invoice 2 | Asset Flag |
|---|---|---|---|
| Distribution Account | 02-640-2210-1234 | 01-780-6120-0000 | Yes |
| Liability Account | 01-640-2210-0000 | 02-782-2210-0000 | Yes |
In the table above, assume the cost center segment as the second segment. Based on this set up, the account derivation rule is applied to derive the account of Invoice 1 only. For the second invoice, even though the Assets' tracking option is set to Yes, the cost center for the Distribution account and Liability account are not the same. Both conditions must be met in order for the rule to apply.