Last updated on AUGUST 11, 2016
Applies to:Oracle E-Business Tax - Version 12.0.0 and later
Information in this document applies to any platform.
The objective of this note is to explain the old and current behavior when tax rules using the ‘Not Equal To’ operator are defined.
The tax product supports the ‘Not Equal To’ operator, which is used for the tax condition and tax rules. The ‘Not Equal To’ operator is generally used to define a condition that excludes a single value. The tax rule condition is evaluated as TRUE if the value entered in the transaction is different than the value defined in the condition.
If the user did not enter the value in the transaction (i.e., left the relevant field as NULL), the system used to evaluate the tax rule condition as TRUE. This was incorrect and not in line with the system design.
We have modified the rule evaluation process and ensured that the condition is evaluated as FALSE when the value in the transaction is NULL.
We did not modify the rule evaluation process for fiscal classification/registration status/user defined geography rules. If the value is not defined in the fiscal classification/registration status/user defined geography setup, then NULL is treated as a value.
Refer to the following table for the respective file versions.
|Scenario||Behavior Description||File version details- 12.1.X||File version |
|1||Old behavior- NULL is considered a value and the rule is evaluated as TRUE.||zxdirulenginpvtb.pls 120.124.12010000.4||zxdirulenginpvtb.pls 120.107.12000000.27|
|2||General current behavior- NULL is NOT considered a value and the rule is evaluated as FALSE.||zxdirulenginpvtb.pls 120.124.12010000.5||zxdirulenginpvtb.pls 120.107.12000000.28|
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms