My Oracle Support Banner

Transactions Persisted With Previous BusinessDate After 'LookupStoreStatus CommException Failure' Occurs In POS (Doc ID 1430364.1)

Last updated on SEPTEMBER 01, 2020

Applies to:

Oracle Retail Point-of-Service - Version 12.0 and later
Information in this document applies to any platform.


POS fails to get the correct businessdate from the database after a failure in LookupStoreStatus (CommException error).  The end result is that transactions on the current business date are associated with the incorrect business date (yesterday's date).

Steps to Recreate:

1. Restart the store server
2. Press F3/POS and log in.  The first call to the database fails with CommException. When the first call is made to fetch store status, the call fails and store status must be retrieved from hard totals.  The following is the error produced:

3. Transaction in TR_TRN is saved with the incorrect Business Date.  This causes the number in RTLOG for that business date to mismatch the count in the DCLOSE record




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.