Unable To Process RTLOG From X-admin To SACS Due to DUP_TRAN Error (Doc ID 3052730.1)

Last updated on OCTOBER 15, 2024

Applies to:

Symptoms

On: MFCS/ReSA 24.0.201.3 version, ReSA - Others, Development Environment

Scenarios exist where the transaction fails in the Oracle SACS staging layer (SVC_RTLOG_DATA_LOAD) and does not make into the actual SACS SA_TRAN_XXXXX tables. Some of the error conditions that happen are:

STOREDAY_LOCK_FAILED
THEAD_IN_ILLEGAL_POS
TTAIL_TRC_STIN
DATAUNEXPECTEDSTORED
STOREDAYNOTREADYTOBELOADED
POSUNEXPECTEDSTOREDAY
STORE_DAY_CLOSED
INVLD_CC_MASK
TRANLVLTAX_NO_IGTAX
INVLD_TSYS
TRAN_NOT_RECOGNIZED
DATAUNEXPECTEDSTOREDAY

The users need a method to reprocess these transactions into SACS (the transaction have been uploaded into the SVC_RTLOG_DATA_STAGING and SVC_RTLOG_DATA_LOAD_HIST tables).

If you attempt to republish the transaction from POS does not work - results in "DUP TRAN" error when loading to the SVC tables.

Steps to recreate the issue:

1. Make store day only to export the POS
2. Push JSON with system ans OMS
3. Load the transaction and run SA_TRANSACTION_PROCESS job
4. No Error has been occurred in HIT table
5. RTLOG file rejected by SIMATPLGOI batch with THEAD_IN_ILLEGAL_POS error.
6. SAIMPTLOGIFIN did not updated the SVC_RTLOG_DATA_LOAD_HIST table
7. Repoll the same transaction through service
8. Run SA_TRANSACTION_PROCESS_JOBs the transaction errored with DUP_TRAN error

Note: Make sure the store does not have any other store day with P or L status when SAIMPTLOGFIN is running.

Cause

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