LAST_UPDATE_DATE Field In AR_PAYMENT_SCHEDULES_ALL Not Update Correctly (Doc ID 2081708.1)

Last updated on FEBRUARY 16, 2016

Applies to:

Oracle Financials for the Americas - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Brazil AR - Other

ACTUAL BEHAVIOR
---------------

On the instance which has applied Brazil Latin Localization patch we found the issue below, which is fine on standard instance.

When apply invoice in application window , if we enter invoice number , then left it with no more operations.
After a while ,save this application and then check it in database.
we can find field of last_update_date in ar_payment_schedules_all tables are the time that we entered invoice but not that we save it, which is not correct.

EXPECTED BEHAVIOR
-----------------------
last_update_date in ar_payment_schedules_all should be the same as in ar_receivables_applications_all


STEPS TO REPRODUCE
-----------------------

Navigate: Receipts > Receipts
1. Apply invoice against this receipt by click Apply button
2. In Application form, enter invoice number and applied part of invoice ,
DON'T take any other operation, don't save. Time is 15:23 for example. Wait 4 minutes
3. Save this application and then check in database
4. LAST_UPDATE_DATE in AR_PAYMENT_SCHEDULES_ALL is not the same as the
LAST_UPDATE_DATE date in AR_RECEIVABLE_APPLICATIONS_ALL.


BUSINESS IMPACT
-----------------------
When the application record be created, the update date of table
ar_payment_schedule should be the same as the application. Timestamp is different when
the receipts are applied using Brazil Localization.
LAST_UPDATE_DATE is used for Audit purposes and the reports are
inconsistent for the Brazil Localization applications

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms