Last updated on JUNE 24, 2017
Applies to:Oracle Cash Management - Version 12.1.3 and later
Information in this document applies to any platform.
When scheduling the Bank Statement Import Program to run daily the GL date parameter increments each day and uses sysdate by default. This works throughout the month. However, this behaviour causes issues during month end.
See the following scenario:
On August 1, 2016 the program runs and imports bank statements from prior business day July 29, 2016. However the gl date parameter is defaulted to August 1.
Therefore accounting from auto-reconciliation is happening in the August period instead of the July period which is the business requirement.
NOTE: The user needs the program to always use the bank statement header gl date for autoreconciliation.
The best possible outcome is that the system will use the bank statement header date as the gl date and the users do not need to populate anything.
Is there a SQL or another workaround to default the gl date parameter correctly?
Is there a way to automate the date to be populated correctly in this parameter if the users are going to schedule the program to run daily?
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