When you use the NOR (NOT OR) operator, both statements must be false for the combined statement to be true. This operator is the same as using the statement NOT (A OR B).

1. |
(2 + 2 = 4) NOR Los Angeles is a city in California (FALSE) |
2. |
(2 + 2 = 4) NOR (1 = 2) (FALSE) |
3. |
(2 + 1 = 4) NOR (2 + 2 = 4) (FALSE) |
4. |
(2 + 1 = 4) NOR (10 < 6) (TRUE) |
The following table is the truth table for the NOR (NOT OR) operator.
Statement A |
Statement B |
A NOR B |
TRUE |
TRUE |
FALSE |
TRUE |
FALSE |
FALSE |
FALSE |
TRUE |
FALSE |
FALSE |
FALSE |
TRUE |
In the FI-SL application component, you would use the NOR (NOT OR) operator when you want the system to check that at least one statement is not <x> (before the system uses the data).
The following graphic uses a truth table for the NOR (NOT OR) operator to determine if transaction data should be substituted.

If the transaction is for account 500000 and/or for cost center 150, then the combined statement is FALSE and the data is not substituted. If the transaction is not for account 500000 or for cost center 150, then the combined statement is TRUE and the data is substituted.