FulfilOrdCfm Slowly Ignores Completed ORDCUST Records, Delaying All Other Messages
Last updated on JANUARY 31, 2017
Applies to:Oracle Retail Merchandising System - Version 14.0.1 and later
Information in this document applies to any platform.
Customer Order Fulfillment Confirmation Publication API (rmssub_fulfilordb.pls) processes 'C'ompleted customer orders but does not publish record per design. This causes needless delay for message processing of 'P'artially fulfilled or 'X' (no inventory) customer orders.
Steps to Reproduce:
- Create (say, 20) Customer Orders that are fulfilled (ensure from location has stock in RMS) and one more (21st) which has failed ORDCUST.STATUS ('P'artially fulfilled or 'X' (no inventory)).
- Monitor ORDCUST_PUB_INFO (or, FulfilOrdCfm publisher adapter log).
- Verify that GETNXT consistently returns no messages and only one order is changed from 'U' to 'P' status every 10 seconds [rib-rms:FulfilOrdCfm Publisher, channel 1 configuration, which is set to 10 seconds by default].
- Notice that the last record ('P'artially fulfilled or 'X' (no inventory)) waited for 20*10 seconds before it is published.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms