Transfer Purge Messages Stuck In RIB Due To Inconsistent Design For Purge Transfer
(Doc ID 2727872.1)
Last updated on MAY 16, 2022
Applies to:Oracle Retail Store Inventory Management - Version 14.1.3 and later
Information in this document applies to any platform.
SIM Batch Modules
Running tsfprg.pc in RMS 14 sends Stockorder delete messages sent from RMS14 to SIM14, the messages get stuck in SIM14 queue as they have already been purged from SIM14 using purge_data_pkg.delete_received_transfers.SIM14 Transfer purge has already been implemented and running for some time. As a result, SIM14 and RMS 14 Purge are on different intervals - systems allow this and business requirements for purge criteria are different for each:
- Aged Transfers in RMS14 are being purged and then purged Transfer information from RMS14 is being interfaced to SIM14 via RIB – Message Family | StockOrder | Message Type – SOHdrDel. RMS14 existing database trigger EC_TABLE_THD_AIUDR on TSFHEAD table is publishing the header level deletes to SIM14 via RIB using RMSMFM_TRANSFERS.ADDTOQ() function.
- However, SIM14 and RMS14 base batches for transfer purge have their own independent purge criteria. SIM14 – DAYS_TO_HOLD_RCVD_TRANSFERS_RECORDS value in sch_sim.config table. RMS14 – TSF_HISTORY_MTHS value in PURGE_CONFIG_OPTIONS table.
As SIM14 and RMS14 are having independent purge processes, Transfer information across these systems is not matching. Due to this, messages for Transfers purged in RMS14 are failing in SIM14 – unable to process them in SIM14 as Transfer doesn’t exist in SIM14.
does not exist for distro number: 6051590940
Steps to reproduce:
- Data to be purged from SIM. Transfer in status 40 - received
- The same transfer in RMS with status closed
- First run PurgeReceivedTransfers.sh batch from SIM
- Run docclose batch from RMS
- Verify DOC_PURGE_QUEUE table in RMS
select * from DOC_PURGE_QUEUE
- Run tsfprg batch from RMS$ ./prepost $UP tsfprg pre
$ ./tsfprg $UP
$ ./prepost $UP tsfprg post
- Verify MPS_STAGED_MESSAGE table in SIM and see the error
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