FAQ Cleared Date

Document 741217.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.
R12: CE: FAQs: Definitions of Transaction Date, Value Date, Cleared Date And Statement Date and GL date
(Doc ID 741217.1)
In this Document
Purpose
Questions and Answers
References
APPLIES TO:
Oracle Cash Management - Version 11.5.10.2 to 12.2.4 [Release 11.5 to 12.2]

Information in this document applies to any platform.
PURPOSE
The purpose of the article is to respond to the following questions:
Q1. What is: Transaction Date, Value Date, Cleared Date and Statement Date?
Q2. What is the Difference in Transaction Date, Value Date, Cleared Date and Statement Date.?
Q3: What is Anticipated value date?
Q4: General Ledger (GL) date Related to Transaction?
Q5: GL Date for the Sweep Transaction?
Q6: Clarify the GL DATE Default?
QUESTIONS AND ANSWERS
A1.What is: Transaction Date, Value Date, Cleared Date and Statement Date?
Transaction Date: The date the transaction cleared the bank. The default is the statement date.
Value Date (formerly Effective Date): The date when cash activity (payments or receipts) is recognized in a bank account. This date is
important for interest calculations on a bank account. The statement line Value Date can be provided by the bank or entered manually. It is
used to populate the Actual Value Date in Oracle Payables and Oracle Receivables.
Please note the clarification:
Bug: 13560345 - CEXCABMR => VALUE DATE FIELD IS NON UPDATABLE THE SECOND TIME
The value date is the date when the funds will be available in the bank account. When the receipt is reconciled, the actual value date is
updated for the receipt.
When the receipt is unreconciled, the value date should be cleared. When it is again selected for reconciliation, the date should be defaulted
from the bank statement line if it is available. In addition, this must be in the reconciliation window also.
Cleared Date. Date the payment or receipt cleared in Cash Management.
Statement Date: The closing date of the bank statement. The date also includes the timestamp
information provided by your bank. On intra-day bank statements, the timestamp indicates how recent the information is.
Please download the test scenario from this document. Following is the attachment:
VALUE DATE EXAMPLES RECEIPT TYPE OF LINE.docx
-----------------------------------------------------------------------------------------------------------------------
A2. Difference in Transaction Date, Value Date, Cleared Date and Statement Date
a. Difference in Transaction Date and Value Date:
The following example illustrates the difference between the transaction date and the value date on a bank statement line: A receipt is
deposited into your account on December 1. The receipt clears (funds become available) on December 3. The transaction date is December
1 and the value date is December 3.
The relationship between certain bank statement and subledger dates is as follows:
The Transaction Date in the Bank Statement Lines window updates the Cleared Date in Payables and the Transaction Date in Receivables
1 of 9 09/08/2019, 17:56
(History).
The Value Date in the Bank Statement Lines window updates the Actual Value Date in Payables and Receivables.
For release 11.5 and subsequent releases, Value Date replaces Effective Date on the Bank Statement Line window.
b. Difference in Cleared Date and Statement Date.
You can manually clear a Transactions when you have information from the bank that it is cleared
by them.
However if you have not cleared a Transaction and the Bank statement you have received and
processed then the default is the statement line date / statement date when both clearing and RECONCILING is done by RECONCILIATION.
Hence the CLEARED DATE will be statement line date / statement date.
Please note:
Clearing
When you reconcile a transaction, the transaction is first matched to bank statement details and then cleared (if uncleared). Alternatively,
you can manually clear Payables payments, Receivables receipts, miscellaneous transactions, and open interface transactions in Cash
Management prior to reconciliation to maintain more update cash account balances. You can also use Automatic Clearing to clear receipts in
Oracle Receivables.
When you clear a transaction, Cash Management assigns a cleared date, cleared amount, and status to the transaction. Accounting for the
cleared transaction varies by the source. If the transaction is a payment, Payables records the accounting information but you create the
accounting entries in Payables. If the transaction is a receipt or a miscellaneous transaction, Receivables automatically generates the
accounting entries. If the transaction is an open interface transaction, you must customize the CE_999_PKG package to implement
reconciliation accounting. You cannot clear Payroll payments, General Ledger journal entries, or Treasury settlements.
-----------------------------------------------------------------------------------------------------------------------
A3: What is Anticipated value date?
Anticipated Value Date:
This field indicates the number of clearing days between the transaction date and settlement date. If a value for anticipated value days exist
in the payment method, this value will automatically default here. However, the default can be overwritten by the user.
Anticipated Value Date:
This field indicates the anticipated date when the funds will reach the destination bank account. If you select a payment template, this field
is populated as the Transfer Date plus the number of anticipated value
days on the payment template. If you select a payment method, this field is populated as the Transfer Date plus the number of anticipated
value days on the payment method. However, the default can be overwritten by the user.
-----------------------------------------------------------------------------------------------------------------------
A4: GL date Related to Transaction?
GL DATE: The GL date is an internal attribute used for accounting purposes. In autoreconciliation we are giving the GL date only and not
the cleared date. The date that the payment or receipt posts to the general ledger. If you do not choose the Default Dates button, the
default is the system date, if the Payables (AP)/Receivables (AR) period is open. If the period is closed and in the future, the date defaults to
the first date of the latest open period. If the period is closed and not in the future, it defaults to the last date of the latest open period.
• Bank Statement GL Date: The accounting date used to clear the statement.
• Transaction Creation GL Date: The accounting date used to create the transaction.
Error Code Explanation

AP period not open or future : The GL date is not in an open or future period in Oracle Payables.
AR period not open or future: The GL date is not in an open or future period in Oracle Receivables.
Clarification on GL date at different situation:
In case of autoreconciliation system should compare GL date entered in the autoreconciliation program parameter with the payment
date/uncleared date. A validation needs to be added for reconciling each statement line. However, if we need to add this validation for
autoreconciliation it may have performance impact. The reason being the GL date entered on the autoreconciliation program must be
compared for each line matched with the respective transaction. For each matching transaction:
- the system first needs to check if the payment/receipt is being reconciled for the first time (may be through checking the reconciliation
history).
- If its being reconciled for the first time then compare this date with the original transaction date.
- If its already reconciled before, then compare the uncleared date with the entered GL date.
2 of 9 09/08/2019, 17:56
This is Fixed in Bug: 14725907 - AUTORECONCILIATION ALLOWS EARLER GL DATE, at the minimum versions as follows:
12.0 patch/115/sql/ceabrmab.pls 120.56.12000000.53

patch/115/import/US/ce12amg.ldt 120.38.12000000.48


Please note:
1.Create a Bank Statement to which the Payment Can be Reconciled, insure the Statement Header GL Date is in an Open Period.
GL Date: If you selected either the option of Load and Import or Load, Import, and AutoReconciliation, enter the GL Date. This is the default
date for all General Ledger journal entries created by AutoReconciliation. The date must be in an open or future-enterable Payables or
Receivables period.
2.Manually Reconcile the Line Notice the GL Date is Defaulted from the Statement Header
The GL date defaults to the bank statement date. You can update it, or override it on the individual payment or receipt transaction.
3.Manually Unreconcile the Line (Unless the User Changes it, the sysdate is defaulted here. The GL Date on the statement header remains
unchanged, despite this being
the latest GL Date used for Reconciliation or Unreconciliation)
4.Autoreconciliation: The Sysdate is offered as the Default GL Date, however it can be updated to any date in an Open AP and AR Period,
which could be the same as the Statement Header GL Date, or even one before that and before the Payment Date.
GL Date: (Required). The default date for all General Ledger journal entries generated by AutoReconciliation. The date must be in an open
or future-enterable Payables or Receivables period.
The latest clarification on GL DATE and fix:
Patch: 14840476:R12.CE.B This patch modifies how GL date (accounting date) is derived during Autoreconciliation of Sweep Transactions.
Old Behavior: When running autoreconciliation for Sweep Transactions generated from bank statements, the cashflows get reconciled
with
* clearing date = statement line date
* GL date (accounting date) = GL Date given as input parameter to Autorecon
The expectation is that the GL date should actually be the same as the clearing date.
New Behavior: The behaviour for Autoreconciliation program is modified. For Sweep Transactions generated from bank statements,
autoreconciliation will always set the GL Date for reconciliation the be same as Clearing Date, ie,
GL Date = Clearing Date = Statement Line Date.
The Autoreconciliation input parameter GL Date will continue to be used for other transactions (AP/AR/Regular Cashflows).
12.0 patch/115/sql/ceabrmab.pls-120.56.12000000.54
patch/115/sql/ceabrc1b.pls-120.41.12000000.11
Latest over:
R12.0.6:
Patch: 19045160:R12.CE.A 1OFF:5265916:AUTORECONCILIATION: ADDITIONAL MATCHING CRITERIA FOR JE LINES
patch/115/sql/ceabrmab.pls 120.56.12000000.68
R12.1:
Patch: 19149948:R12.CE.B R12.1: Cash Management Recommended Patch Collection (RPC), August, 2014
3 of 9 09/08/2019, 17:56
R12.2:
Patch: 19685806:R12.CE.C This patch fixes the issue wherein line amount in a SWIFT file is not populated correctly in interface form, when
amount is less than 1(when amount has only decimal part)
ce patch/115/sql ceabrc1b.pls 120.49.12020000.8 +
ce patch/115/sql ceabrmab.pls 120.96.12020000.19 +
This password is valid for 21 days: mvMOMMr3
-----------------------------------------------------------------------------------------------------------------------
A5: GL Date for Sweep: When running autoreconciliation for Sweep Transactions generated from bank statements, the cashflows get
reconciled with
* clearing date = statement line date
* GL date (accounting date) = GL Date given as input parameter to Autorecon
The expectation is that the GL date should actually be the same as the clearing date.
Bug: 14840476 - CREATE ACCOUNTING NOT TAKING GL DATE AS CLEARED DATE OR UN-CLEARING DATE
Resolution:
Patch: 14840476:R12.CE.B This patch modifies how GL date (accounting date) is derived during Autoreconciliation of Sweep Transactions.
ce patch/115/sql ceabrmab.pls 120.62.12010000.46
The behaviour for Autoreconciliation program is modified. For Sweep Transactions generated from bank statements,autoreconciliation will
always set the GL Date for reconciliation the be same as Clearing Date, ie, GL Date = Clearing Date = Statement Line Date. The
Autoreconciliation input parameter GL Date will continue to be used for other transactions (AP/AR/Regular Cashflows).
-----------------------------------------------------------------------------------------------------------------------
A6: Clarify the GL DATE Default?
The GL Date is not validated at Bank Statement Creation / Entry because bank statements in R12 can have transactions which use different
subledgers - AP Checks/AR Receipts/CE Cashflows/GL Journals. So to streamline flow, the GL Date validation check is done later during
auto-reconciliation on a transaction-by-transaction basis.
GL DATE Validations:
Bug: 16765752 : R12 #329 CM - SYSTEM DIDN'T CHECK THE GL DATE WHEN ENTER STATEMENT MANUALLY
1). The system does not validate the GL date at the time of entering the bank statement. It does make the check the GL date during
reconciliation or clearing of the statement lines.Therefore, the GL date validation must be checked only during reconciliation or clearing.
2). The GL date of the statement will continue to default from the statement line date.
3).For Sweep Transactions generated from bank statements,autoreconciliation will always set the GL Date for reconciliation the be same as
Clearing Date, ie, GL Date = Clearing Date = Statement Line Date. The Autoreconciliation input parameter GL Date will continue to be used
for other transactions (AP/AR/Regular Cashflows).
Documentation Bug:
Bug: 16889401 - REMOVING THE REFERENCE OF STATEMENT GL DATE VALIDATION
The following is mentioned for the bank statement GL date in user guide: (Managing Bank Statements 4-27, User Guide: Part No. E13483-04
and before)
GL Date: The date that the transaction posts to the General Ledger. The default is the statement date. The GL Date must be in an open or
future-enterable period in Oracle Receivables or Oracle Payables.
Please remove the following: The GL Date must be in an open or future-enterable period in Oracle Receivables or Oracle Payables.
Documentation to reads as: GL Date: The date that the transaction posts to the General Ledger. The default is the statement date.
-----------------------------------------------------------------------------------------------------------------------
A7. Bank Statement Load errors as: GL Date That You Entered Is not in an open or future enterable period in Payable and
Receivables
You load our Bank statements into the Bank Statement Interface, but are unable to tranfer the same because of the following error:
The GL date that you entered is not in an open or future enterable period in Payables and Receivables.
1. Insure Payables and Receivables Period Open:

1).Navigation: Control > Accounting-Open > Periods
2). Navigation: Accounting > Periods-Open > Periods
2. It is a required step that all Legal Entity be setup in the System Parameters with a Legal Entity, Ledger, begin date and all other required
fields in the system parameters setup in Cash Management otherwise you will not be able to view any available data for that Legal Entity or
do any Bank Statement import and autoreconcilation.
4 of 9 09/08/2019, 17:56
-----------------------------------------------------------------------------------------------------------------------
A8. Bank Reconciliation Errors and explanation:
AP period not open or future: The GL date is not in an open or future period in Oracle Payables.
AR period not open or future: The GL date is not in an open or future period in Oracle Receivables.
Bank Statement Window Reference: GL Date: The date that the transaction posts to the General Ledger. The default is the statement
date.
Manual Recobnciliation: GL Date: The date that the transaction posts to the General Ledger. The default is the statement date
Bug: 14390315 - MANUAL RECONCILIATION IS NOT DEFAULTING THE CURRENT DATE AS GL DATE, the Cash Management development
product manager says: "For manual reconciliation, the GL date entered on the bank statement header gets defaulted. This functionality is
already existing and works for all the transactions reconciled manually.
The GL date on the bank statement header defaults to the bank statement date and must be a date in the open period in payables and
receivables. This is clearly documented in the user guide.
Investigation sql:
2. The version of the following to be latest:
patch/115/sql/ceseutlb.pls
patch/115/sql/cebsldrb.pls
(2). Issues / Resolution:
1. When a Payment is Reconciled: What GL date is taken and where one can view it?
A1. In Autoreconciliation, the GL Date used to submit the AutoReconciliation program will be the reconciled GL Date. In manual
reconciliation, the value entered on the GL Date column of the Available Transaction window will be the reconciled GL Date.
After the payment has been reconciled, you can view the GL Date on the Reconciled Transactions window or you can check the last
accounting_date in ap_payment_history table for the payment. If AP has an accounting form, you can probably view it there.
2. When a Payment is UNRECONCILED: What GL date is taken and where one can see it?
A2. If using the Unreconcile program, the sysdate will be used as the unreconciled GL Date. For manual unreconciliation, the value entered
on the GL Date column of the Reconciled Transaction window will be the unreconciled GL Date.
After the payment has been unreconciled, you can check the last accounting_date in ap_payment_history for the unreconciled GL Date.
3. When You RE-RECONCILE : What GL DATE is taken and where one can see it?
A3. same as #1 above
4: THE CLEARING / RECONCILIATION GL DATE CANNOT BE EARLIER THAN THE DATE OF THE PAYMENT
PAYMENT DATE: 01.JUL.2011
GL DATE: 30-JUN-2011
Want to Reconcile Payment Created in: PAYMENT DATE: 01.JUL.2011 in: GL DATE: 30-JUN-2011?
A4: It is not logical to Reconcile a Payment which will be created Tomorrow Today.
Reconciled: The bank has disbursed funds for the payment, and the payment has been reconciled and matched to a bank statement in
Oracle Cash Management. Payables uses this status when the Account for Payment When Payment Clears Payables option is enabled.
Note: 263794.1: The Clearing/Reconciliation GL Date Cannot Be Earlier Than

Note: 377295.1: GL Date Cannot Be Earlier Than The Date Of The Receipt
Note: 378161.1: GL Date When Reconcile, Unreconcile And Rereconcile
5: Why: GL Date is null when you take unreconciled button to view payment transaction against a reconciled bank
statement line, Where Status of Payment 'RECONCILED UNACCOUNTED' ?
As the AP reconciliation accounting flag i.e AP_SYSTEM_PARAMETERS_ALL.RECON_ACCOUNTING_FLAG is set
to 'N', the transaction was reconciled with status 'RECONCILED UNACCOUNTED'.
In this scenario no entry will be made in the AP_PAYMENT_HISTORY_ALL table. The view CE_200_RECONCILED_V which fetches this shows
null GL DATE.
A5:
As the AP reconciliation accounting flag i.e AP_SYSTEM_PARAMETERS_ALL.RECON_ACCOUNTING_FLAG is set
to 'N', the transaction was reconciled with status 'RECONCILED UNACCOUNTED'.
In this scenario no entry will be made in the AP_PAYMENT_HISTORY_ALL table.
The view CE_200_RECONCILED_V is fetching the accounting_date from AP_PAYMENT_HISTORY as gl_date. As there is no entry in
AP_PAYMENTS_HISTORY_ALL table the gl_date will be blank.
When viewing the reconciled transactions. if the AP reconciliation accounting flag is disabled,
5 of 9 09/08/2019, 17:56
the gl_date will be blank. This is Not a Bug.

Note: 758918.1 GL Date Null Where Status of Payment 'RECONCILED UNACCOUNTED' And When View in CE As Reconciled Transactions
6: Why GL Date Defaults To System Date When you Reconcile Journal?

A6: When reconciling journals, always default the GL date to system date and do not revert the GL date back to the original GL date after
the transaction has been selected.
The reason why there is a different logic for Journal Entry Transactions from other transactions for reconciliation is because of accounting
practices. For Journal Entry Transactions, you will want to use the system date because you impact the cash account directly on the date
you create the journal entry (as you know, in CE we only reconcile those Journal Entry Transactions that are booked against the cash
account).
For all other transactions, the cash account is impacted on the day the bank clears them, hence the use of the bank statement GL date.
Note: 249570.1 - CE: CEXCABMR GL Date Defaults To System Date
7:"Your Accounts Payable department needs to close each period two business days before the end of each month. Your
Banking Format File (BAI) banking files won't load cleared checks once Accounts Payable (AP) is closed, so AP has to
manually re-open the period during our automated BAI import on the last two days of each month. Once the files load they
have to re-close the period. This opens up a window of time where transactions are possible in a closed period."
Is there a way to keep the cash management module open for a particular period regardless of period status for AP and AR?
A7:
1. This actually depends on what Business Practice you have. Looks like you want to insure that all BANK STATEMENTS Upto Last day of the
Months has to be RECONCILED to insure appropriate accuracy of clear / reconciliation accounting within the period.
2. However, you get last two days of the bank statement for load/import/recon, when the period is closed. Either you do the Reconcilitaion
in the next GL period or you will have to open the period for AP, GL, AR etc for the period, as the reconciliation accounting is done by the
respective module e.g. Payment by AP etc.
8. When attempting to reconcile a bank statement line that was unreconciled earlier the following error occurs if the GL
Date in the Transactions Available window is not changed to date after the unreconciliation date
Error message:
The clearing/reconciliation GL date cannot be earlier than the unclearing/unreconciliation GL date of this payment
(un_date=19-oct-12)
The clearing/reconciliation GL date cannot be earlier than the unclearing/unreconciliation GL date of this receipt
(un_date=19-oct-12)
A8. The error message "The clearing/reconciliation GL date cannot be earlier than the unclearing/ unreconciliation GL date of this payment"
is given as per functionality when trying to reconcile/clear a transaction with a GL Date that is the earlier or the same as the
unclearing/reconciling GL date previously used for that transaction.
This is explained in Bug: 9372605 - PAYMENT RECONCILED TO WRONG LINE, CANNOT BE RE- RECONCILE USING SAME GL DATE
For the example above, the payment was cleared on 31st March, 2009. The payment was later uncleared on 30th October, 2009. The user
was trying to reconcile it again as of 31st March, 2009 and hence the error message was coming up.
As per the bug the customer was asked to reconcile the payment or clear the payment after
the unclearing event was accounted ie. after 30th October, 2009.
The form is behaving as expected there is no loss of functionality or data issue here. System is behaving as intended
9. On Clearing / Reconciling And the Unclearing/Unreconciled Payment Error APP-CE-53020 AP Period Not Open Or Future
A9. Review: On Clearing / Reconciling And the Unclearing/Unreconciled Payment Error APP-CE-53020 AP Period Not Open Or Future Note:
1321640.1
Issue 10: Autoreconciliation of Receipts and Payments Created in Period (n+1) Can Be Reconciled With Receipts and
Payments Created in Period (n)
Note: 1525417.1 Autoreconciliation of Receipts and Payments Created in Period (n+1) Can Be Reconciled With Receipts and Payments
Created in Period (n)
Patch 14725907:R12.CE.B
Confirm the following file versions:
ceabrmab.pls 120.62.12010000.45
ce12amg.ldt 120.42.12010000.42
11. Selecting Records to Reconcile in the Bank Statement Errors - APP-CE-53021: AR Period Not Open or Future
Note: 1483587.1 Cash Management: Selecting Records to Reconcile in the Bank Statement Errors - APP-CE-53021: AR Period Not Open or
Future
There has been some bugs logged for defaulting of the GL date on the manual reconciliation form.
6 of 9 09/08/2019, 17:56
Some users want it to be system date, some want it to be GL Date from the Statement Header and some want it to be the date of last
activity on the receipt,i.e., last Remitted,Cleared or Uncleared date.
In Bug: 14390315 - MANUAL RECONCILIATION IS NOT DEFAULTING THE CURRENT DATE AS GL DATE, the Cash Management development
product manager says: "For manual reconciliation, the GL date entered on the bank statement header gets defaulted. This functionality is
already existing and works for all the transactions reconciled manually.
The GL date on the bank statement header defaults to the bank statement date and must be a date in the open period in payables and
receivables. This is clearly documented in the user guide.
12. SELECTING RECORDS TO RECONCILE IN THE BANK STATEMENT ERRORS - APP-CE-53021
Bug: 16424636 - SELECTING RECORDS TO RECONCILE IN THE BANK STATEMENT ERRORS - APP-CE-53021
1. Unable to query receipts available for reconciliation on the basis of batch number
2. The default date in the GL Date and Cleared Date columns when attempting to manually reconcile a statement line is not populated
consistently in the Available/Reconciled transactions form.
Resolution: NEW BEHAVIOUR

Receipts can be properly fetched as per batch number.
The form will populate default dates during Manual Reconciliaton, Unreconciliation (Available transactions form and Reconciled
transactions form) as below. This is
applicable when using either "Find" or "Find and Mark" option to select the transactions
During Manual Reconciliaton, Unreconciliation (Available transactions form and Reconciled transactions form):
GL Date:
- The GL date of the transaction selected for reconciliation defaults to the GL date given in the statement header.
- If the GL date of the last activity on the transaction (like receipt remittance or payment creation) is GREATER than statement header GL
date, then that date (transaction GL date) will be populated as the default value
- This default GL date can be updated by the user to any other required date as long as that date is in an open period.
Cleared Date:
- When the Available Transactions form is opened from the Statement lines form, the cleared date defaults to the Statement line date.
- When the Available Transactions form is opened from the Statement headers form, the cleared date defaults to the Statement header
date.
- If this "default" cleared date is less than the GL date of the last transaction activity (like receipt remittance or payment creation) then the
GL date of the last transaction activity is populated as the default value.
- This default cleared date can be updated by the user to any other required date.
This behaviour is applicable when using either "Find" or "Find and Mark" option to select the transactions.
13. GL Date, Cleared Date: Manual Reconciliaton, Unreconciliation (Available transactions form and Reconciled
transactions form):
Bug: 17571324 - UNABLE TO QUERY AVAILABLE RECEIPTS BY BATCH NUMBER
GL Date::
Cleared Date::
date.
This behaviour is applicable when using either "Find" or "Find and Mark" option to select the transactions.
Patch: 18016094:R12.CE.B This patch fixes the issue where in transactions were not ordered in available transactions window
ce forms/US CEXCABMR.fmb 120.194.12010000.90
Patch Applicable over Oracle Applications Release 12.1.x
R12.1:
Patch: 17506440:R12.CE.B MANUAL RECONCILIATION SHOWING INCORRECT AMOUNT RECONCILED FOR STATEMENT LINES
7 of 9 09/08/2019, 17:56
14.: Manually Reconcile: Default date in the GL Date and Cleared Date columns
Bug: 16424636 - SELECTING RECORDS TO RECONCILE IN THE BANK STATEMENT ERRORS - APP-CE-53021
Old Behavior: The default date in the GL Date and Cleared Date columns when attempting to manually reconcile a statement line is not
populated consistently in the Available/Reconciled transactions form.
New Behaviour: The form will populate default dates during Manual Reconciliaton, Unreconciliation (Available transactions form and
Reconciled transactions form) as below. This is applicable when using either "Find"or "Find and Mark" option to select the transactions
During Manual Reconciliaton, Unreconciliation (Available transactions form and Reconciled transactions form)::
1). GL Date::
2). Cleared Date::

date.
The above behaviour is applicable when using either "Find" or "Find and Mark" option to select the transactions.
Fixed at:
R12: 16424636:R12.CE.A

ce patch/115/import/US ce12amg.ldt 120.38.12000000.52
R12.1: 16424636:R12.CE.B
Latest:
Patch: 20030614:R12.CE.B R12.1 CANNOT SEARCH FOR NEXT AVAILABLE ITEM WHEN RECONCILING BANK STATEMENTS
ce patch/115/import/US ce12amg.ldt 120.42.12010000.47 +
R12.2: Above: 16424636:R12.CE.C

Latest:
Patch: 20615747:R12.CE.C This patch fixes the issue wherein Cash Forecast was computing incorrect values for PO's canceled at line level
ce patch/115/odf cevw.odf 120.176.12020000.30
ce forms/US CEXCABMR.fmb 120.259.12020000.32 +
Patch: 20561847:R12.CE.C This patch fixes the issue where reconciliation errors were appearing in the auto-recon execution report even
though the statement was marked as complete.
15. Need to update the GL Date on Bank Statement Headers, need Datafix:
(9). Latest
To insure that you get to latest so that transactions happen in next period if the current period is closed?
Oracle Support strongly recommend you to apply following:
1). Note: 1367845.1 R12: Cash Management Recommended Patch Collection (RPC)
2). Note: 1393113.1 R12 CE Diagnostics BAT, Cashflows, Payment and Receipt
8 of 9 09/08/2019, 17:56
3). Note: 1335039.1 New Archive, Purge and Restore Bank Statement Concurrent Programs
4). Note: 1481222.1 Sub Ledger Accounting (SLA) Recommended Patch Collection (XLA RPC)
The Cash Management Recommended Patch Collection (RPC) patch suggested only includes CE(Cash Management) bug fixes
and does not impact Other module. This patch has already been tested thoroughly by Oracle QA, applied by many customers without any
issues reported and comes with a minimum risk profile.
Oracle Support proactively provides Fixes which improves your application experience.
Hope you appreciate.
(10) Latest Patches:
R12.0.6:
Patch: 19045160:R12.CE.A 1OFF:5265916:AUTORECONCILIATION: ADDITIONAL MATCHING CRITERIA FOR JE LINES
R12.1:
Patch: 19149948:R12.CE.B R12.1: Cash Management Recommended Patch Collection (RPC), August, 2014
R12.2:
Patch: 19685806:R12.CE.C This patch fixes the issue wherein line amount in a SWIFT file is not populated correctly in interface form, when
amount is less than 1(when amount has only decimal part)
ce patch/115/sql ceabrc1b.pls 120.49.12020000.8 +
ce patch/115/sql ceabrmab.pls 120.96.12020000.19 +
REFERENCES
NOTE:263794.1 - R11i: CE: The Clearing/Reconciliation GL Date Cannot Be Earlier Than The Unclearing/Unr
BUG:14725907 - AUTORECONCILIATION ALLOWS EARLER GL DATE
BUG:16424636 - SELECTING RECORDS TO RECONCILE IN THE BANK STATEMENT ERRORS - APP-CE-53021

BUG:14840476 - CREATE ACCOUNTING NOT TAKING GL DATE AS CLEARED DATE OR UN-CLEARING DATE
BUG:17506440 - MANUAL RECONCILIATION SHOWING INCORRECT AMOUNT RECONCILED FOR STATEMENT LINES
NOTE:758918.1 - GL Date Null Where Status of Payment 'RECONCILED UNACCOUNTED' And When View in CE As Reconciled Transactions
BUG:18016094 - JOURNALS ARE NOT ORDERED BY TRX_NUMBER IN AVAILABLE TRANSACTIONS FORM
NOTE:1525417.1 - Autoreconciliation of Receipts and Payments Created in Period (n+1) Can Be Reconciled With Receipts and Payments
Created in Period (n)
NOTE:249570.1 - 11.5- CE: CEXCABMR GL Date Defaults To System Date
BUG:13560345 - 12.1.1: CEXCABMR => VALUE DATE FIELD IS NON UPDATABLE THE SECOND TIME
NOTE:378161.1 - GL Date When Reconcile, Unreconcile And Rereconcile

BUG:16765752 - R12 #329 CM - SYSTEM DIDN'T CHECK THE GL DATE WHEN ENTER STATEMENT MANUALLY
NOTE:1483587.1 - Cash Management: Selecting Records to Reconcile in the Bank Statement Errors - APP-CE-53021: AR Period Not Open or
Future
Didn't find what you are looking for?
9 of 9 09/08/2019, 17:56

FAQ Cleared Date

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FAQ Cleared Date

Uploaded by

Copyright:

Available Formats

Document 741217.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Oracle Cash Management - Version 11.5.10.2 to 12.2.4 [Release 11.5 to 12.2]

The purpose of the article is to respond to the following questions:

QUESTIONS AND ANSWERS

Please note the clarification:

Cleared Date. Date the payment or receipt cleared in Cash Management.

a. Difference in Transaction Date and Value Date:

b. Difference in Cleared Date and Statement Date.

A3: What is Anticipated value date?

Anticipated Value Date:

Anticipated Value Date:

A4: GL date Related to Transaction?

Error Code Explanation

Clarification on GL date at different situation:

12.0 patch/115/sql/ceabrmab.pls 120.56.12000000.53

12.1 patch/115/sql/ceabrmab.pls 120.62.12010000.45

12.2 patch/115/sql/ceabrmab.pls 120.96.12020000.11

The latest clarification on GL DATE and fix:

A6: Clarify the GL DATE Default?

1. Insure Payables and Receivables Period Open:

A8. Bank Reconciliation Errors and explanation:

2. The version of the following to be latest:

(2). Issues / Resolution:

Note: 263794.1: The Clearing/Reconciliation GL Date Cannot Be Earlier Than

the gl_date will be blank. This is Not a Bug.

6: Why GL Date Defaults To System Date When you Reconcile Journal?

Note: 249570.1 - CE: CEXCABMR GL Date Defaults To System Date

12. SELECTING RECORDS TO RECONCILE IN THE BANK STATEMENT ERRORS - APP-CE-53021

Resolution: NEW BEHAVIOUR

Bug: 17571324 - UNABLE TO QUERY AVAILABLE RECEIPTS BY BATCH NUMBER

2). Cleared Date::

ce forms/US CEXCABMR.fmb 120.168.12000000.113

R12.2: Above: 16424636:R12.CE.C

(10) Latest Patches:

BUG:16424636 - SELECTING RECORDS TO RECONCILE IN THE BANK STATEMENT ERRORS - APP-CE-53021

NOTE:378161.1 - GL Date When Reconcile, Unreconcile And Rereconcile

You might also like