Oracle EBS Late Charges Report Prints the Wrong Date – Date Appears One Day Earlier

📅 Last Updated: August 2026

This guide explains how to troubleshoot an Oracle E-Business Suite Receivables issue where the Late Charges Report prints a date that is one day earlier than the expected date. It covers the symptoms, affected environment, possible date/time considerations, diagnosis, and the Oracle patch associated with the original issue.

Oracle E-Business Suite Receivables provides several reports for analyzing customer transactions, interest, penalties, and late payment charges. Accurate dates are particularly important for financial reports because even a one-day difference can affect reconciliation, customer statements, accounting analysis, and audit verification.

In some Oracle E-Business Suite environments, administrators may encounter a situation where the Late Charges Report displays a date that is earlier than the actual date associated with the transaction or late charge calculation.

For example, a transaction or report parameter may contain a date such as:

31-MAY-2019

while the generated report unexpectedly displays:

30-MAY-2019

This type of discrepancy should not be treated as a simple formatting problem until the underlying data, report parameters, database settings, and application environment have been verified.

Quick Solution

For the Oracle E-Business Suite environment described in this article, the issue was addressed by applying Oracle Patch 26500596. Always verify the patch's applicability to your exact Oracle EBS release and technology stack, test it in a non-production environment first, and perform regression testing before deploying it to production.

Problem Description

The issue occurs when the Oracle E-Business Suite Late Charges Report prints an incorrect date.

The date displayed in the report can be one day earlier than the expected date.

This is particularly important in financial environments because report dates can be used for:

Customer account analysis.
Late payment calculations.
Receivables reconciliation.
Financial reporting.
Customer communication.
Audit verification.
Period-end processing.

Example of the Problem

Assume the Late Charges Report is expected to show the following date:

Expected Date: 31-MAY-2019

However, the generated report displays:

Actual Date: 30-MAY-2019

The difference is exactly one day.

When this behavior occurs consistently, the DBA or Oracle EBS administrator should investigate the report, underlying data, database session settings, application configuration, and known Oracle patches before changing production data.

Affected Oracle E-Business Suite Environment

The original issue documented in this article was observed in the following environment:

Component	Version
Oracle E-Business Suite	R12.1.3
Oracle Receivables	Receivables module
Oracle Database	11.1.0.7.0
Problematic Report	Late Charges Report
Reported Solution	Oracle Patch 26500596

Because Oracle E-Business Suite environments can contain different technology-stack combinations, administrators should not assume that the same patch is applicable to every release. Always validate the patch against the exact EBS release, database version, operating system, and installed product family.

What Is the Oracle Receivables Late Charges Report?

Oracle Receivables provides functionality for identifying and processing charges associated with customers who make payments after their required payment dates.

Late charges may involve interest, penalties, or other configured charges depending on the organization's Receivables configuration and business rules.

Reports associated with this functionality provide administrators and finance users with information that can be used to review late charges and related customer transactions.

Because these processes are date-sensitive, incorrect date handling can have an impact on the usefulness of the resulting report.

Why Is a One-Day Date Difference Important?

A one-day discrepancy may appear minor from a technical perspective, but it can be significant in an enterprise financial system.

For example, if a report is used to determine whether a customer payment was late, an incorrect date could make a transaction appear to belong to a different day.

This can potentially affect:

Late charge analysis.
Customer account review.
Daily reconciliation.
Period-end reporting.
Financial audit processes.
Operational decision-making.

Initial Diagnosis

Before applying a patch, confirm that the problem is reproducible and that the discrepancy is actually generated by the Oracle EBS report.

The administrator should compare:

The date stored in the relevant transaction data.
The date supplied to the report as a parameter.
The date displayed in the report output.
The database session date/time settings.
The application server date/time settings.
The operating system date/time.

This comparison helps distinguish an application/reporting defect from an environment configuration problem.

Check the Database Date and Time

The DBA can check the database server's current date and timestamp using SQL*Plus.

SELECT SYSDATE FROM DUAL;

Also check the database timestamp:

SELECT SYSTIMESTAMP FROM DUAL;

These checks help establish the database server's current date and time.

Check the Database Time Zone

Where a one-day discrepancy is observed, timezone behavior should also be investigated before concluding that the report itself is defective.

Check the database time zone:

SELECT DBTIMEZONE FROM DUAL;

Check the session time zone:

SELECT SESSIONTIMEZONE FROM DUAL;

These values can help determine whether a date or timestamp is being interpreted differently between the database session and the application/reporting layer.

Check the Operating System Date and Time

The operating system date and time should also be verified on the database server.

date

On Linux systems, administrators can also inspect the configured timezone:

timedatectl

If the operating system, database, application server, and user session are configured with inconsistent timezone settings, date-related behavior can become difficult to diagnose.

Do Not Modify Financial Data to Correct the Report

Important: Do not manually update Oracle EBS transaction dates or financial data simply because a report displays an incorrect date.

Oracle E-Business Suite data should be corrected through supported application functionality or an Oracle-provided fix. Direct updates to application tables can compromise data integrity, auditability, and Oracle Supportability.

Known Oracle Patch

The original environment documented for this issue was resolved by applying:

Patch: 26500596

The patch should be treated as the primary Oracle-provided solution for the specific issue described in the original article.

However, Oracle patches are environment-specific. Before applying the patch, verify:

Oracle E-Business Suite release.
Installed Receivables version.
Database release.
Operating system platform.
Existing patches.
Patch prerequisites.
Patch conflicts.
Required OPatch version.

Why Should the Patch Be Tested First?

Oracle E-Business Suite is an integrated application suite. A patch that modifies reporting or Receivables functionality can potentially affect other reports, concurrent programs, or related application components.

Therefore, the correct enterprise approach is:

Identify the exact problem.
Verify the Oracle patch.
Back up the environment.
Apply the patch in a TEST environment.
Run the affected report.
Compare the results with the original output.
Perform regression testing.
Obtain business-user validation.
Schedule production deployment.

Step 1 – Verify the Oracle EBS Environment

Before applying any Oracle patch, first confirm the exact Oracle E-Business Suite environment. This is particularly important because patch applicability depends on the installed EBS release, product family, technology stack, operating system, and database version.

sqlplus / as sysdba

Run:

SELECT banner
FROM v$version;

For the original environment documented in this article, the database version was:

Oracle Database 11.1.0.7.0

Step 2 – Verify the Oracle E-Business Suite Release

One common method is to query the Applications release information:

SELECT release_name
FROM fnd_product_groups;

The original environment was:

Oracle E-Business Suite R12.1.3

Always confirm the actual release in your environment rather than relying on documentation from another server.

Step 3 – Confirm Oracle Receivables Is Installed

Because the reported problem involves the Receivables Late Charges Report, verify that Oracle Receivables is installed and enabled.

You can review the installed Oracle Applications products using:

SELECT application_short_name,
       application_name
FROM fnd_application
ORDER BY application_short_name;

Confirm that the Receivables application is present in the environment before proceeding with troubleshooting.

Step 4 – Reproduce the Problem

Before applying a patch, reproduce the problem in the TEST environment whenever possible.

Run the Late Charges Report using the same parameters that produced the incorrect date.

Record the following information:

Report name.
Report request ID.
Report parameters.
Transaction or customer involved.
Expected date.
Actual date displayed.
Date and time when the request was submitted.

Save a copy of the original report output. This provides a baseline for comparison after applying the patch.

Step 5 – Verify the Database Date and Time

Before concluding that the report has a software defect, verify the database date and time.

SELECT SYSDATE,
       SYSTIMESTAMP,
       DBTIMEZONE,
       SESSIONTIMEZONE
FROM dual;

If the database and session settings are correct and the report still consistently displays a date one day earlier, continue with the patch investigation.

Step 6 – Verify the Operating System Time Zone

On the database server, verify the operating system time and timezone.

date

On Oracle Linux systems, you can also run:

timedatectl

Compare the operating system timezone with the expected timezone used by your Oracle EBS environment.

Step 7 – Check Whether Patch 26500596 Is Already Installed

Before applying Patch 26500596, verify whether it has already been installed.

Oracle E-Business Suite patch inventory should be checked using the appropriate AD utilities and Oracle patch-management tools for the installed EBS release.

For environments where the patch inventory is maintained through Oracle's standard patching utilities, review the relevant patch inventory rather than applying the same patch repeatedly.

The objective is to determine whether:

The patch is already installed.
A superseding patch has already been installed.
The patch conflicts with another installed patch.
Additional prerequisites are required.

Step 8 – Check the Oracle Patch Documentation

Before downloading or applying Patch 26500596, review the official Oracle patch documentation for the exact patch.

Confirm the following:

Supported Oracle EBS release.
Supported operating system.
Required product family.
Prerequisite patches.
Superseded patches.
Patch conflicts.
Required AD/TXK technology stack level.
Required OPatch or EBS patching utility version.

Important

Do not assume that a patch number found in an old technical article is automatically applicable to a newer Oracle EBS environment. Oracle patch applicability changes over time as patches are superseded and technology-stack requirements evolve.

Step 9 – Prepare the TEST Environment

Always test an Oracle EBS patch in a non-production environment before applying it to production.

Before patching, make sure that:

A recent database backup is available.
The application filesystem has been backed up or can be restored.
The current patch inventory has been documented.
Active concurrent requests have been reviewed.
Users have been notified of the maintenance activity.
The TEST environment represents the production configuration as closely as practical.

Step 10 – Stop Required Oracle EBS Services

Follow your organization's standard Oracle EBS patching procedure and stop the application services that must not be running during the patch.

For an Oracle EBS R12.1 environment, service management is normally performed using the Oracle Applications service-control utilities appropriate to the installed configuration.

For example, administrators commonly use:

$ADMIN_SCRIPTS_HOME/adstpall.sh

Verify that the required application services have stopped before beginning the patching operation.

Step 11 – Apply Patch 26500596 in TEST

After confirming patch applicability and completing the required preparation, apply Patch 26500596 according to the Oracle-provided README and the patching procedure appropriate for your EBS release.

The exact command should always be taken from the patch's README because Oracle patching syntax and prerequisites vary between releases and patch types.

Do not blindly reuse a patch command from an old blog post or from another Oracle EBS environment.

Step 12 – Monitor the Patching Process

During patching, monitor the patch log files carefully.

Look for:

Successful file updates.
Database object changes.
Invalid objects.
Prerequisite failures.
Patch conflicts.
Compilation errors.
Failed SQL statements.

Do not ignore a patching error simply because the patch process appears to continue. Resolve errors according to the Oracle patch README and support documentation.

Step 13 – Start Oracle EBS Services

After the patch completes successfully, start the required Oracle EBS services.

For a typical Oracle EBS R12.1 environment:

$ADMIN_SCRIPTS_HOME/adstrtal.sh

Verify that the application services have started successfully before testing the report.

Step 14 – Run the Late Charges Report Again

Submit the same Late Charges Report using the same parameters that were used before applying the patch.

This is important because changing the report parameters would make it difficult to determine whether the patch actually corrected the original problem.

Compare the new report with the original report saved during the diagnosis phase.

Step 15 – Validate the Corrected Date

Check the date that was previously displayed incorrectly.

For example:

Test	Before Fix	After Fix
Expected date	31-MAY-2019	31-MAY-2019
Report date	30-MAY-2019	31-MAY-2019
Result	Incorrect	Correct

The expected result is that the report displays the correct date without the one-day offset.

Step 16 – Perform Regression Testing

Do not stop testing after confirming that one report displays the correct date.

Because Oracle E-Business Suite is an integrated enterprise application, perform appropriate regression testing of related Receivables functionality.

Recommended tests include:

Late Charges processing.
Late Charges Report.
Customer account inquiry.
Receivables transaction inquiry.
Relevant concurrent programs.
Period-end Receivables processing.
Related financial reports.

Step 17 – Obtain Business Validation

Technical validation by the DBA is not sufficient for a financial application issue.

Ask the appropriate Oracle Receivables or Finance business user to confirm that:

The report now displays the correct date.
The report data is consistent with the transaction.
No related report has been affected.
The output is suitable for reconciliation and business processing.

Troubleshooting Checklist

☐ Confirm Oracle EBS release.
☐ Confirm Oracle Receivables version.
☐ Confirm database version.
☐ Reproduce the incorrect date.
☐ Save the original report output.
☐ Verify report parameters.
☐ Check SYSDATE.
☐ Check SYSTIMESTAMP.
☐ Check database timezone.
☐ Check session timezone.
☐ Check operating-system timezone.
☐ Verify Patch 26500596 applicability.
☐ Check whether the patch is already installed.
☐ Review prerequisites and conflicts.
☐ Back up the TEST environment.
☐ Apply the patch in TEST.
☐ Run the same report again.
☐ Confirm the date is corrected.
☐ Perform regression testing.
☐ Obtain business-user approval.

Production Deployment Preparation

After successful TEST validation, prepare a formal production deployment plan.

The plan should include:

Patch number and description.
Current EBS release.
Current patch inventory.
Prerequisite patches.
Maintenance window.
Database backup plan.
Application filesystem backup plan.
Rollback strategy.
Testing procedure.
Business validation procedure.

Important Oracle EBS DBA Note

Never apply an Oracle E-Business Suite patch directly to production simply because it resolved a similar issue in another environment. Always check the current Oracle patch README, prerequisites, conflicts, technology-stack requirements, and support status for your exact environment.

Production Deployment Best Practices

After successfully testing Patch 26500596 in the TEST environment and confirming that the Late Charges Report now displays the correct date, the next step is to plan the production deployment.

Oracle E-Business Suite is a mission-critical enterprise application. Production patching should therefore be performed under a controlled change-management process rather than as an ad-hoc activity.

Recommended Production Deployment Sequence

Obtain business approval for the change.
Confirm the exact patch and prerequisites.
Review the current production patch inventory.
Take the required backups.
Schedule an approved maintenance window.
Notify application and business users.
Stop the required Oracle EBS services.
Apply the patch according to the Oracle-provided README.
Review patch logs for errors.
Start Oracle EBS services.
Run the Late Charges Report.
Verify the previously incorrect date.
Perform regression testing.
Obtain business-user confirmation.
Document the completed change.

Backup and Rollback Planning

Before applying an Oracle EBS patch to production, ensure that an appropriate recovery strategy is available.

The backup and rollback plan should consider:

Oracle Database backup.
Oracle EBS application filesystem.
Oracle EBS technology-stack components where applicable.
Current patch inventory.
Configuration files modified during the change.
Customizations and custom application objects.

The rollback procedure should be documented and reviewed before starting the production change.

Important:

Do not assume that every Oracle EBS patch can simply be removed with an uninstall command. Some patches have dependencies or modify database/application objects in ways that require a specific rollback procedure. Follow the Oracle patch documentation for the exact patch and release.

Date and Time Troubleshooting Considerations

A report displaying a date one day earlier can have multiple possible causes. The documented Patch 26500596 solution should therefore be considered in the context of the complete environment.

When investigating similar problems, check the following layers:

Layer	What to Check
Operating System	System date, time and timezone
Database	SYSDATE, SYSTIMESTAMP and DBTIMEZONE
Database Session	SESSIONTIMEZONE and session-specific settings
Oracle EBS	Application configuration and concurrent request parameters
Report	Report query, parameters and formatting
Output Layer	Report formatting and date representation

This layered approach helps prevent administrators from applying a patch when the actual problem is caused by an environment configuration issue.

Common Administrator Mistakes

1. Changing Database Data Directly

One of the most serious mistakes is manually changing Oracle EBS application data to make the report display the expected date.

Direct updates to Oracle EBS application tables are generally unsupported unless specifically instructed by Oracle Support or an approved Oracle procedure.

2. Applying the Patch Without Checking Prerequisites

An Oracle patch may depend on other patches, technology-stack levels, or patching utilities.

Always review the current Oracle patch documentation before deployment.

3. Testing Only the Affected Report

Although the Late Charges Report is the primary focus, related Receivables functionality should also be tested after patching.

4. Ignoring Date and Time Configuration

Timezone differences can produce confusing date-related symptoms. Always verify the operating system, database, session, and application environment before diagnosing a date problem.

5. Applying a Historical Patch Without Revalidation

The original issue was documented in an older Oracle EBS/database environment. A patch that was appropriate for that environment may have been superseded or replaced in another release.

Always verify the current Oracle Support information for your specific environment.

Frequently Asked Questions

Why does the Late Charges Report show one day earlier?

In the specific Oracle EBS environment documented in this article, the issue was resolved by applying Oracle Patch 26500596. However, a one-day date discrepancy can also be caused by timezone or date/time configuration differences, so the environment should be investigated before applying a fix.

Which Oracle EBS version was affected in the original case?

The original case was documented on Oracle E-Business Suite R12.1.3 with Oracle Database 11.1.0.7.0.

Which patch resolved the original issue?

The documented resolution was Oracle Patch 26500596.

Can I apply Patch 26500596 directly to production?

No. First verify that the patch is applicable to your exact Oracle EBS environment, review its prerequisites and conflicts, test it in a non-production environment, and perform regression testing before production deployment.

Should I change the date directly in an Oracle EBS table?

No. Avoid unsupported direct modifications to Oracle EBS application data. Use supported Oracle functionality or an Oracle-provided patch/fix.

How can I check the database timezone?

Run:

SELECT DBTIMEZONE FROM DUAL;

How can I check the current database timestamp?

Run:

SELECT SYSTIMESTAMP FROM DUAL;

Should I test the report after applying the patch?

Yes. Run the same Late Charges Report with the same parameters used before the fix and compare the output. Then perform appropriate Receivables regression testing.

Production Validation Checklist

☐ Patch applicability confirmed.
☐ Patch prerequisites confirmed.
☐ Patch conflicts reviewed.
☐ Database backup completed.
☐ Application filesystem backup completed where required.
☐ TEST deployment completed successfully.
☐ Late Charges Report tested successfully.
☐ Incorrect date no longer appears.
☐ Related Receivables functionality tested.
☐ Business users validated the output.
☐ Production maintenance window approved.
☐ Production patch successfully completed.
☐ Application services verified.
☐ Production report validated.
☐ Change documented.

Technical Summary

Item	Details
Application	Oracle E-Business Suite
Module	Oracle Receivables
Release	R12.1.3
Database	Oracle Database 11.1.0.7.0
Problem	Late Charges Report displays a date one day earlier
Documented Patch	26500596
Recommended Approach	Verify environment → Test patch → Validate report → Regression test → Deploy to production

Key Lessons for Oracle EBS DBAs

This issue demonstrates an important principle of Oracle E-Business Suite administration: a seemingly simple reporting problem can involve several layers of the application and technology stack.

A professional DBA should not immediately modify data or assume that a report defect is caused by the database. Instead, the investigation should proceed systematically.

Reproduce the issue.
Document the exact symptoms.
Verify the application release.
Verify the database release.
Check operating-system and database date/time settings.
Review existing patches.
Identify the Oracle-supported fix.
Test the fix in a controlled environment.
Perform regression testing.
Deploy through a controlled production change.

About the Author

Rana Abdul Wahid is a seasoned Oracle DBA Consultant with more than 15 years of Oracle Database experience. His technical expertise includes Oracle Database Administration, Oracle E-Business Suite Application DBA, Oracle OCI Cloud DBA, MySQL, Microsoft SQL Server, PostgreSQL, Odoo ERP, and Linux/Unix/Ubuntu/Windows administration.

He focuses on practical Oracle Database, Oracle E-Business Suite, Linux, troubleshooting, backup and recovery, performance, and enterprise infrastructure solutions based on real-world administration experience.

Learn more about the author →

Conclusion

The Oracle E-Business Suite Receivables Late Charges Report date issue can be particularly confusing because the report may appear to contain valid data while displaying a date that is exactly one day earlier than expected.

In the original environment documented in this article, running Oracle E-Business Suite R12.1.3 with Oracle Database 11.1.0.7.0, the issue was resolved using Oracle Patch 26500596.

However, the most important lesson is not simply the patch number. The correct DBA methodology is to reproduce the problem, verify the complete technology stack, investigate date/time configuration, confirm patch applicability, test the Oracle-provided fix in a non-production environment, perform regression testing, and only then deploy the solution to production.

This approach protects the integrity of Oracle E-Business Suite data while providing a controlled and supportable method for resolving production reporting problems.

Final Recommendation

If your Oracle EBS Late Charges Report displays a date one day earlier than expected, do not modify the underlying financial data manually. First verify the date/time configuration and reproduce the issue. Then check the applicability of Patch 26500596 for your exact Oracle EBS environment, test the patch thoroughly, validate the corrected report output, and follow your organization's formal production change-management process.

Disclaimer: Oracle, Oracle E-Business Suite, Oracle Database, and related product names are trademarks of Oracle Corporation. Patch numbers, prerequisites, supported releases, and installation procedures may change over time. Always consult the applicable Oracle documentation and My Oracle Support information for your specific environment before implementing a patch.

Oracle Database Error Solutions & DBA Knowledge Base