My Oracle Support Banner

Till Functions are Impacted While Operating the Register in Offline Mode (Doc ID 2228684.1)

Last updated on JULY 30, 2018

Applies to:

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


Till Functions are impacted when operating the register in the Offline mode for the below two scenarios.

Scenario 1:

Accountability: Register
Count Till at Reconcile: Detail (as_ws.cd_cl_tl_cnt=2)
Blind Close: Y

1. Open the Store from Back office with 1000.00 Operating fund.
2. Open the register 129 and Till 129 (Float 100.00) from Back office.
3. Login to POS and insert the till 129.
4. Perform some regular transactions.
5. Perform each till function transaction (Till Pick Up, Loan, Pay In,Pay Out, Payroll Payout. $ 10.00 Each)
6. Stop the store server.
7. Click ESC.
8. Go to Store Ops, close and reconcile till from POS.
9. Check Till transactions in Summary report.

Below snippet is from Till Summary report. Notice that values for Till Loan, Pay In, Pay Out are shown as 0.00

Till Pickup (10.00)
Till Loan      0.00
Till Pay In    0.00
Till Pay Out  0.00

Scenario 2:

Accountability: Register

1. Open Store / Register / Till from POS.
2. Perform a sale transaction
3. Click on "More F9" >> "TIll Functions F5"
4. Perform each Till Function transaction ( Pickup F2 , Loan F3, Pay In F4, Pay Out F5) on the current Till.
5. When last till function transaction is performed system ask for Login, do not login here and Stop POS Server.
6. Click Esc to go back to main screen.
7. Close and reconcile Till in offline mode.
8. Transactions are queued at Client side.
9. Start Store Server.
10. Server tries to insert these queued transaction in database.
11. Transactions are not persisted into database
12. These transaction are moved to QueueException folder at server.
13. Notice below Exception in the log

Class: $Revision: /rgbustores_13.4x_generic_branch/2 $) @338374: SQLState: 23000
Integrity constraint violation, Source Exception: java.sql.SQLException: ORA-00001: unique constraint (ORBO134.SYS_C00240236) violated

Transaction Name: [TransactionWriteDataTransaction]
Error code: [10] [A referential integrity error occurred during database access.]
Error code (extended): [1]
Description: [SQLState: 23000
Integrity constraint violation, Source Exception: java.sql.SQLException: ORA-00001: unique constraint (ORBO134.SYS_C00240236) violated
Query String: INSERT INTO TR_TRN ( ID_STR_RT, ID_WS, DC_DY_BSN, AI_TRN, ID_OPR, TS_TRN_BGN, TS_TRN_END, TY_TRN, FL_TRG_TRN, ID_EM, INF_CT, TY_INF_CT, SC_TRN, ID_RPSTY_TND, SC_PST_PRCS, TS_MDF_RCRD, TS_CRT_RCRD, FL_TRE_TRN, FL_SLS_ASSC_MDF) VALUES ('01111', '129', '2016-09-25', 327, '0', TO_TIMESTAMP('2016-10-26 01:48:41.215', 'YYYY-MM-DD HH24:MI:SS.FF'), TO_TIMESTAMP('2016-10-26 01:48:41.224', 'YYYY-MM-DD HH24:MI:SS.FF'), '11', '0', null, null, 0, 2, '190', 0, SYSDATE, SYSDATE, '0', '0')
Original exception: [null]

at oracle.retail.stores.domain.arts.JdbcSaveTransaction.insertTransaction(
at oracle.retail.stores.domain.arts.JdbcSaveControlTransaction.insertControlTransaction(
at oracle.retail.stores.domain.arts.JdbcSaveControlTransaction.saveControlTransaction(
at oracle.retail.stores.domain.arts.JdbcSaveControlTransaction.execute(





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.