My Oracle Support Banner

XTsf Subscribe - Creating Invalid 'INV_TSF' Error Messages On Creates (Doc ID 2996301.1)

Last updated on JANUARY 05, 2024

Applies to:

Oracle Retail Merchandising System - Version 16.0.3 and later
Information in this document applies to any platform.


XTsf Subscribe - Creating invalid 'INV_TSF' error messages on Creates

When sending 'EG' type transfers into RMS via the RIB, every single 'xtsfcre' message will log an error message to LOGGER_LOGs for 'INV_TSF'. This is because there is a check in RMSSUB_XTSF_VALIDATE.CHECK_TSF_EXISTS to make sure the TSF_NO being added does not already exist. To check this the code calls the TSF_VALIDATE_SQL.EXIST function which query TSFHEAD to see if the transfer number exists. However, if NOTFOUND this function ALWAYS creates an error message. If user is just checking to make sure a transfer does not exist, they do not want to log error messages.

Thus, the check of whether a transfer exists or not in RMSSUB_XTSF_VALIDATE.CHECK_TSF_EXISTS should not log a message when transfers are being created, thus the TSF_VALIDATE_SQL.EXIST function should not be used here.

Since customers will be creating 80,000 transfers per day via XTSF, this is a lot of processing overhead and also adds a lot of records to LOGGER_LOGS.

The issue can be reproduced at will with the following steps:
1) Create a transfer using XTSF via the RIB.
2) Notice a record is logged to LOGGER_LOGS for 'INV_TSF'.

The issue has the following business impact:
Due to this issue, users is experiencing a lot of processing overhead and also this adds a lot of records to LOGGER_LOGS.




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.