In the Journal Line Types window, click Conditions

2. In the Seq field, enter a Sequence number.

The details of the condition are created from left to right according to this number.

This number does not necessarily correspond to the evaluation of the condition, as parenthesis and logical operators precedence can affect the order.

3. In the ( field, use the "(" and ")" symbols for grouping a section of a condition.

This is useful when a condition spans multiple lines with the And/Or operators.

4. In the Source field, select a source value.

Source values are seeded by the subledger application or custom application but access to the custom sources defined is also provided. This value is the first operand in the condition line.

5. In the Segment field, if the source is a key flexfield or an Accounting Flexfield, optionally select the segment.

The table below describes the relationship between the Source and the Value Type fields based on the transaction chart of accounts.

Transaction Chart of

Accounts Nature of Source Segments in List of Values

Null Accounting Flexfield All Accounting Flexfield

qualifiers

Not Null Accounting Flexfield All segments for the

transaction chart of accounts

N/A Key Flexfield All segments for the key

flexfield and flexfield structure given by the source

6. In the Operator field, select an operator to evaluate the condition.

7. In the Value Type field, select the value type of the second operand that is evaluated in the condition line.

The value types are:

• Source: This includes any source defined for the application. The source can be seeded by Oracle or it can be a custom source.

• Constant: Choose this value type for a comparison with constant values.

The table below describes the relationship between the source and the value type fields based on the transaction chart of accounts.

Transaction Chart of

Accounts Nature of Source Value Type

Null Accounting Flexfield Can only be Source

Transaction Chart of

Accounts Nature of Source Value Type

Not Null Accounting Flexfield Can be Source or Constant

N/A Key Flexfield or any other

source

Can be Source or Constant

When defining a condition, you can compare one data source with another data source by using the comparison operator, for example, '=' or '<>'. In some cases, the value of one side of the data source could be null or blank when the extract data contains no value for the specific source that is being compared. In such cases, Subledger Accounting will return 'TRUE' or 'FALSE' depending on which

comparison operators are used and which data source is being compared as shown in the table below.

Condition Expected Value

null source = constant or a non-null source false

null source <> constant or a non-null source true

null source = null source true

null source <> null source false

8. If the Segment field to the left of the Independent Value field has a dependent segment and the value type is Constant, in the Independent Value field, enter the value of the segment that the dependent segment is based upon.

This is the value for the independent segment in the key flexfield that the dependent segment value is based upon. For example, the following condition, described in the table below, requires users to choose an independent value before choosing a value for the dependent segment.

Source Segment Operator Value Type Independent

Value

Value

Asset Category Flexfield

Minor Category = Constant BUILDING ADMINISTRAT

ION

9. In the Value field, enter a value as follows:

• If a value type of Constant is selected, then enter a value for the constant and this value is used as the second operand to evaluate the condition.

• If a value type of source is selected, then select an Accounting Flexfield code combination identifier or any other source value from the list of values for this field.

The table below describes the relationship between the source, segment, value type, and Value field.

Source Segment Value Type Value Field List of

Values

Key Flexfield Not populated Constant Complete key

flexfield combination

Key Flexfield Populated Constant Values for the

segment selected

Any other source N/A Constant Values based on

value set or lookup type if specified for the source

Key Flexfield Not Populated Source All key flexfield sources

Key Flexfield Populated Source Includes all

segment and key flexfield sources

Segment N/A Source All segment

sources

Any other source N/A Source All sources of

matching data type

10. If a value type of Source and a value that represents an Accounting Flexfield code combination identifier are entered, optionally select a segment name in the Segment field.

This segment value is used as the second operand in the condition line.

11. In the ) field, use AND/OR values to concatenate two lines together when making complex conditions.

Typically, the AND takes precedence over the OR. Parenthesis are only required to overwrite this precedence. As an example, consider a condition that should use a particular account derivation rule if the following are true:

• The Assets' tracking option is Yes AND.

• The cost is less than $200 or the supplier is ABC.

Not only must the Assets' tracking option be Yes, but either or both of the remaining two conditions must also be true.

This condition utilizes the bracket operators as follows:

(Asset Tracking option = Yes) AND ((Amount < 200) OR (Supplier = ABC))

Copying Journal Line Types and Their Associated Conditions See Copy and Modify Functionality, page 2-6.

Note: If entering a transaction chart of accounts, the journal line type that is created supports this chart of accounts.

This field can only be entered if the line type being copied does not have a chart of accounts already assigned to it. If it does, the new line type that is created inherits the assigned chart of accounts and users cannot change the value.

If copying a nontransaction chart of accounts specific journal line types to a transaction chart of accounts specific journal line type, Subledger Accounting replaces any reference to Accounting Flexfield qualifiers in the conditions with the actual segment names for the qualifiers in the transaction chart of accounts. If no corresponding segment exists, an error message appears.