BSV is not validated when defining historical rates through 'Assign by Ranges'.
Last updated on MAY 16, 2017
Applies to:Oracle General Ledger - Version 12.0.0 to 12.2.6 [Release 12.0 to 12.2]
Information in this document applies to any platform.
When data is entered in Historical rate form through 'Assign by Ranges', it is not validating the BSV even if BSV is not assigned to that ledger.
If the rates are entered directly in Historical rate form there is no issue. The issue is only with 'Assign by Ranges' in historical form.
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